GMI Automation & Scripting 1 — Questions and Answers
Question 1: What is the primary benefit of automating repetitive tasks?
- Reduced human error and increased consistency of results (Correct answer)
- Elimination of all human involvement
- Faster execution without any testing needed
- Reduced need for documentation
Correct answer: Reduced human error and increased consistency of results
Automation reduces human error and increases consistency by executing tasks the same way every time, freeing staff for higher-value work.
Question 2: What should be included in every automation script?
- Error handling, logging, and clear documentation of purpose (Correct answer)
- Only the core functionality
- Comments explaining every line of code
- A graphical user interface
Correct answer: Error handling, logging, and clear documentation of purpose
Error handling, logging, and documentation ensure automation scripts are reliable, debuggable, and maintainable by current and future team members.
Question 3: When is automation NOT appropriate?
- For one-time tasks or processes requiring complex human judgment (Correct answer)
- For repetitive tasks performed more than once daily
- For standardized processes with clear rules
- For tasks that currently require manual data entry
Correct answer: For one-time tasks or processes requiring complex human judgment
Automation is not cost-effective for one-time tasks or processes requiring complex human judgment that cannot be reduced to clear rules and decision trees.
Question 4: How should automated processes be monitored?
- Through alerts, dashboards, and regular review of execution logs (Correct answer)
- They do not need monitoring once working
- Only during initial deployment
- By manually checking results weekly
Correct answer: Through alerts, dashboards, and regular review of execution logs
Automated processes require ongoing monitoring through alerts and dashboards to detect failures, performance degradation, and unexpected outcomes promptly.
Question 5: What is the recommended approach for testing automation scripts?
- Test in a non-production environment with realistic data before deployment (Correct answer)
- Test directly in production with live data
- Skip testing for simple scripts
- Test only when major changes are made
Correct answer: Test in a non-production environment with realistic data before deployment
Testing in non-production environments with realistic data catches issues before they affect live systems, preventing potential data loss or service disruption.
Question 6: Why should automation scripts include version control?
- To track changes, enable rollbacks, and support collaborative development (Correct answer)
- To satisfy audit requirements only
- It is only needed for large teams
- To reduce storage requirements
Correct answer: To track changes, enable rollbacks, and support collaborative development
Version control tracks all changes, enables quick rollbacks if issues arise, and supports collaborative development with full change history.
