Release Gates and Approvals in Azure DevOps

1. How can you configure multiple approvers for a single release stage?

Using sequential or parallel approval policies

Creating separate release pipelines

Using manual validation gates only

Disabling automated gates

2. What is a best practice for configuring release gates in production environments?

Use multiple gates with appropriate timeouts and escalation paths

Disable all gates to speed up releases

Use only manual approvals without automated validation

Configure identical gates for all environments

3. How can gates and approvals reduce deployment risk?

By enforcing validation and review checkpoints before critical deployments

By eliminating all manual testing

By automatically rolling back all deployments

By skipping compliance checks

4. In Azure DevOps, what does the 'Invoke Function' gate typically validate?

Custom business logic and deployment readiness via Azure Functions

Code syntax errors

Approval signatures

Artifact compression

5. Which scenario best uses a post-deployment gate with health checks?

Validating application stability before allowing further deployments

Approving code before it enters the build pipeline

Checking artifact availability

Verifying approver identity

6. What is the purpose of setting timeout values on approval gates?

To prevent releases from waiting indefinitely for approvals

To speed up deployment automatically

To block all future deployments

To archive release records

7. How do you use gates to enforce compliance in release pipelines?

By querying audit logs and work items before deployment

By skipping all manual approvals

By disabling post-deployment gates

By using only sequential approvals

8. In Azure DevOps, what is the difference between pre-deployment and post-deployment approvals?

Pre-deployment occurs before release; post-deployment occurs after

Both occur at the same time

Post-deployment is always optional

Pre-deployment gates cannot be automated

9. Which gate type allows you to pause a release and wait for external system validation?

Invoke REST API gate

Manual Validation gate

Query Work Items gate

Schedule-based gate

10. What does the 'Evaluate artifact' gate check in a release pipeline?

Whether required artifacts exist and meet version criteria

Whether approvers have signed off

Whether deployment succeeded

Whether rollback is needed

11. What is the primary purpose of release gates in Azure DevOps?

To automatically deploy to all environments without review

To control and automate approval processes before or after deployment

To replace manual testing entirely

To store deployment artifacts

12. What is the timeout mechanism for approval gates in release pipelines?

Approvals automatically fail after a set time period

Approvals remain pending indefinitely

Approvals are rejected after timeout

Deployments are skipped after timeout

13. Which gate evaluates system behavior and stability after deployment?

Pre-deployment gate

Post-deployment gate

Approval gate

Scheduling gate

14. In Azure DevOps, what does the 'Invoke Function' gate do?

Calls Azure Functions to validate deployment conditions

Executes PowerShell scripts directly

Stores deployment metadata

Manages artifact versioning

15. What is the purpose of a manual validation gate?

To pause deployment and require human review

To automatically validate code quality

To encrypt deployment artifacts

To trigger scheduled releases

16. Which approval type in Azure DevOps requires all approvers to sign off?

Single approval

Sequential approval

Parallel approval

Automatic approval

17. What does the Invoke REST API gate allow you to do?

Call external services to validate deployment conditions

Store deployment logs

Automatically roll back deployments

Archive release artifacts

18. In Azure DevOps, which gate type runs queries to verify system readiness?

Invoke REST API gate

Query Work Items gate

Manual Validation gate

Security Scan gate

19. What is a pre-deployment gate used for in release pipelines?

Validating deployment success after release

Checking conditions and approvals before deployment starts

Storing release notes

Triggering automated rollbacks

20. Which type of gate evaluates deployment readiness by checking infrastructure health?