AZ-400 Practice Test

Answer choices

1. A. Grant every developer Manage permissions to override inheritance, as the proposed approach to the stated operational requirement, for this workflow.
2. B. Trace inherited and explicit repository and branch settings, correct the effective access, and keep contribution separate from administration
3. C. Use a release tag to override the Deny, as the proposed approach to the stated operational requirement, as the primary approach for this workflow.
4. D. Grant force push because it is narrower than Contribute, as the proposed design for the stated workflow, as the primary approach for this workflow.

Wrong-answer review

• A. Grant every developer Manage permissions to override inheritance, as the proposed approach to the stated operational requirement, for this workflow.: Broad administration rights exceed the developer's required code role.
• C. Use a release tag to override the Deny, as the proposed approach to the stated operational requirement, as the primary approach for this workflow.: Tags identify commits and do not participate in permission evaluation.
• D. Grant force push because it is narrower than Contribute, as the proposed design for the stated workflow, as the primary approach for this workflow.: Force push enables history rewrite and is not a safer contribution permission.

Answer choices

1. A. Apply the database and application simultaneously, then document after production, as the proposed approach to the stated operational requirement.
2. B. Deploy the application before its required schema and delete the hotfix branch, as the proposed design for the stated workflow.
3. C. Swap an unvalidated slot and treat the slot as a database rollback, as the proposed approach to the stated operational requirement.
4. D. Review and test the hotfix, apply a retry-safe compatible migration, warm and validate a slot before swap, and merge the fix back to main

Answer choices

1. A. Use KQL as an automatic application repair engine, as the primary response to the stated security and delivery constraints.
2. B. Keep the threshold because baselines never depend on workload, for the stated implementation.
3. C. Remove monitoring because quiet services need no baseline, as the primary response to the stated security and delivery constraints.
4. D. Build a workload- and time-appropriate baseline, query the telemetry with KQL, and remediate through a separate operational action

Answer choices

1. A. Use a system-assigned managed identity from an unrelated VM for all pipelines, as the proposed design for the stated workflow.
2. B. Grant every pipeline subscription Owner so deployments never fail, as the proposed approach to the stated operational requirement.
3. C. Use a dedicated application identity or federated service connection scoped to the resource group and authorize only intended pipelines
4. D. Replace Azure RBAC with repository write permission, as the proposed approach to the stated operational requirement.

Answer choices

1. A. Keep a separate long-lived development branch for each feature until the next quarterly release
2. B. Commit changes directly to the deployable default branch once local unit tests pass
3. C. Use short-lived branches and reviewed pull requests to merge into the default branch
4. D. Create a permanent release branch for each production fix instead of reviewed short-lived branches

Answer choices

1. A. More free-form work-item labels without defined ownership or states, as the proposed design for the stated workflow.
2. B. Long-lived branches so each work item has a permanent branch, as the proposed approach to the stated operational requirement.
3. C. Connections from source changes through builds, tests, and releases to the work item, with each result evaluated independently
4. D. A rule that a linked commit is equivalent to a passing test, as the proposed approach to the stated operational requirement.

Answer choices

1. A. Create a release tag because tags remove binary objects, for the team’s delivery requirements.
2. B. Plan a coordinated migration or history rewrite for existing binaries while using Git LFS pointers for future commits
3. C. Enable branch protection because it converts previous blobs to pointers, for the team’s delivery requirements.
4. D. Delete the working-tree file only and keep published history unchanged, for the stated workflow and governance requirements.

Answer choices

1. A. Keep separate hard-coded Bicep files for each environment because declarative deployments cannot be reused, as the proposed design for the stated workflow.
2. B. Replace Bicep with portal changes after every what-if run so the operator can decide what to create, as the proposed approach to the stated operational requirement.
3. C. Create reusable Bicep modules with environment parameters, run what-if as a preview, execute the governed deployment, and validate the application separately.
4. D. Use what-if as the production deployment and skip application tests because no resource changes were applied, as the proposed approach to the stated operational requirement.

Answer choices

1. A. Store every exception only as a metric and discard all context, as the primary response to the stated security and delivery constraints.
2. B. Use metrics for numeric time-series alerting, Logs for queryable detail, and account for sampling when interpreting event counts
3. C. Disable sampling and alerts without evaluating volume or cost, as the primary response to the stated security and delivery constraints.
4. D. Use Logs only because metrics cannot show numeric data, for the stated implementation, within this workflow.

Answer choices

1. A. Subscribe developers individually to Azure Boards work-item email alerts instead of Teams notifications.
2. B. Integrate both GitHub and Azure DevOps updates into the team's shared Teams channel.
3. C. Bookmark the GitHub pull-request queue and Azure Boards query results as links inside Teams.
4. D. Configure an Azure DevOps service hook that sends work-item notifications only to a shared email list.