Your team wants to let Copilot coding agent work on low-risk issues autonomously while ensuring human review before shared integration changes are promoted. The current process asks a reviewer to approve every agent action before tests run, which causes long delays and abandoned sessions. Which four actions should you perform in order? 1. Require the integration environment reviewer before deployment jobs proceed 2. Assign every Copilot issue to a senior reviewer before planning starts 3. Let automated tests and code scanning run before the human gate 4. Mark Copilot draft pull requests ready immediately after creation 5. Require branch protection checks for merge-critical validation jobs 6. Review the Copilot draft PR before approving the integration gate

The correct order prioritizes efficiency and safety. First, "Let automated tests and code scanning run before the human gate" (3) allows quick, automated validation, catching obvious issues without human intervention. Next, "Require the integration environment reviewer before deployment jobs proceed" (1) establishes a critical human gate for integration, ensuring quality before shared changes. Then, "Review the Copilot draft PR before approving the integration gate" (6) specifies when the human review of the agent's work occurs – after initial automated checks and before the final integration approval. Finally, "Require branch protection checks for merge-critical validation jobs" (5) adds a robust, automated safety net for critical branches, preventing problematic merges. Incorrect options fail to balance automation and human oversight effectively. For example, assigning every issue to a senior reviewer before planning (2) or marking draft PRs ready immediately (4) would either create bottlenecks or bypass necessary checks too early.