Before promoting a build to the staging "environment", a pipeline must confirm that a downstream ticketing system has recorded an approved change record, querying that external system over HTTPS and proceeding only when it returns an approved status. The check must run unattended on every release. Which environment check type fits this requirement?
- AAn "Invoke REST API" check that calls the ticketing system endpoint and passes the run only when the returned payload reports the change record as approved, evaluated automatically each release. Correct
- BA required reviewers approval that lists the change management team, so they look up the ticket in the external system and approve the run once the record is confirmed as approved.
- CAn "Azure Monitor" alerts check pointed at the ticketing resource, so the pipeline reads fired alerts from the system and proceeds only while the change record alert is inactive.
- DA business hours check on the environment, so the pipeline holds the deployment until a permitted release window opens and assumes the change record was approved during that window.
Why A is correct: The Invoke REST API check calls an external HTTPS endpoint and gates the run on the response, letting the pipeline confirm the approved change record automatically without any human step.
Why B is wrong: A reviewers approval also blocks promotion, but it relies on a person manually checking the ticket, whereas the requirement is an unattended automated call to the external system on every run.
Why C is wrong: The Azure Monitor check reads alert rules on Azure resources, not arbitrary ticketing endpoints, so it cannot query a third-party change system for an approved status as required.
Why D is wrong: A business hours check only restricts when a run may proceed and never queries the ticketing system, so it cannot confirm that an approved change record actually exists.