AZ-400 Practice Test

Answer choices

1. A. The work-item link proves every pipeline stage passed, for the team’s delivery requirements, as the primary approach to the stated delivery requirements.
2. B. The link provides requirement-to-source traceability, but end-to-end evidence still needs build, test, and release records with independent statuses
3. C. A release tag alone supplies all missing evidence, for the team’s delivery requirements, as the primary approach to the stated security, delivery, and governance requirements.
4. D. Traceability is unnecessary when the source commit is known, for the stated workflow and governance requirements, for the stated delivery requirement.

Wrong-answer review

• A. The work-item link proves every pipeline stage passed, for the team’s delivery requirements, as the primary approach to the stated delivery requirements.: No test or pipeline outcome is contained in the work-item association.
• C. A release tag alone supplies all missing evidence, for the team’s delivery requirements, as the primary approach to the stated security, delivery, and governance requirements.: A tag identifies source state and does not contain build or test results.
• D. Traceability is unnecessary when the source commit is known, for the stated workflow and governance requirements, for the stated delivery requirement.: Knowing source is insufficient for audit, diagnosis, and delivery verification.

Answer choices

1. A. Keep the persistent copy because secure-file protection follows it, as the primary response to the stated security and delivery constraints.
2. B. Print the password in encoded form, for the stated implementation, across the complete workflow.
3. C. Commit the profile so masking is unnecessary, as the primary response to the stated security and delivery constraints.
4. D. Authorize the secure file narrowly, use and delete the local copy within the job, and avoid command-line or logged secret exposure

Answer choices

1. A. The tag enforces both controls once pushed, as the primary response to the stated security and delivery constraints.
2. B. A tag identifies a commit; branch policy and package-registry immutability must be configured separately
3. C. The tag converts all large files to Git LFS pointers, as the primary response to the stated security and delivery constraints.
4. D. The tag grants repository administration to its creator, for the stated implementation, within this workflow.

Answer choices

1. A. The average proves users are unaffected, as the proposed approach to the stated operational requirement.
2. B. Top-level duration is enough and dependency spans add no value, as the proposed design for the stated workflow.
3. C. Scale CPU because every latency problem is compute, as the proposed approach to the stated operational requirement.
4. D. Tail users are affected, and the dependency span localizes the dominant delay for targeted investigation

Answer choices

1. A. Use a deployment job that targets the production environment, within this workflow.
2. B. Add a schedule trigger to the ordinary job, as the proposed approach to the stated operational requirement.
3. C. Move deployment credentials into template parameters, across the complete workflow.
4. D. Run two ordinary jobs in parallel, as the proposed approach to the stated operational requirement.

Answer choices

1. A. Accept every duplicate and edit incidents later, for the team’s delivery requirements.
2. B. Authenticate and deduplicate webhook deliveries, and generate release notes from governed work and version evidence
3. C. Disable responses so delivery remains pending, for the team’s delivery requirements.
4. D. Use unrelated chat history as the release source, for the stated workflow and governance requirements.

Answer choices

1. A. Remove pre-merge validation because it cannot test everything, as the primary response to the stated security and delivery constraints.
2. B. Keep build validation and also run the pipeline on the resulting main branch state
3. C. Use long-lived branches so merge commits never occur, as the primary response to the stated security and delivery constraints.
4. D. Grant policy bypass to avoid the failed post-merge run, for the stated implementation.

Answer choices

1. A. Instrument both components and propagate correlation context through the queue so Application Insights can join their telemetry
2. B. Monitor only queue length, as the primary response to the stated security and delivery constraints, for the stated delivery requirement.
3. C. Assign the same static operation ID to every request, for the stated implementation, as the primary approach to the stated delivery requirements.
4. D. Use deployment history as distributed tracing, as the primary response to the stated security and delivery constraints, for this workflow.

Answer choices

1. A. Run the same source scan repeatedly, as the proposed approach to the stated operational requirement.
2. B. Use a release tag as container analysis, as the proposed design for the stated workflow.
3. C. Scan only after production deployment, as the proposed approach to the stated operational requirement.
4. D. Add pre-promotion image scanning and complementary code, dependency, secret, and license controls with severity policy and approved exceptions

Answer choices

1. A. Keep sharing because pull-request code cannot access the agent, for the stated workflow and governance requirements.
2. B. Add more cached credentials so fork builds succeed, for the team’s delivery requirements, within this workflow.
3. C. Isolate untrusted fork jobs on fresh or restricted agents and reserve the privileged self-hosted pool for trusted workloads with owned maintenance
4. D. Use a demand named trusted to sandbox the process automatically, for the team’s delivery requirements.