200-901 Application Deployment and Security Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Remove the integration test stage to speed up the pipeline.

  Why it's wrong here

  Dropping integration testing removes the gate that catches defects spanning multiple components, allowing faulty builds to progress toward production. It is tempting when pipeline duration is the priority, but it would be correct only if unit tests already covered every cross-service interaction, which they do not.

• ✓

  Add a manual approval gate before production deploy.

  Why this is correct

  A manual approval gate inserted before the production deploy stage halts the pipeline so a human verifies build and test results before release. This directly prevents a faulty build from reaching production, whereas earlier automated stages may pass flawed artefacts through.

• ✗

  Use the same environment for testing and production.

  Why it's wrong here

  Sharing one environment between testing and production lets untested configuration and state reach live users, defeating the isolation that staging provides. It is tempting as a cost-saving measure, yet it is the correct choice only when environments are deliberately identical and disposable, which production is not.

Go deeper

Related to this question