You save $69.98
AZ-400 Premium Bundle
- Premium File 398 Questions & Answers
- Last Update: Nov 11, 2026
- Training Course 27 Lectures
- Study Guide 784 Pages
You save $69.98
A deploy stage automatically reruns every failed script, including a non-idempotent database migration that can duplicate updates.
What is the most appropriate action for this DevOps team?
Retry only safe idempotent operations and use checkpoints and explicit recovery for state-changing steps. Retries are reliable only when repeated execution has a defined effect and partial failures are detectable. A useful check is that a failed stage resumes or rolls back without duplicate schema changes or conflicting infrastructure resources.
This would instead address Artifacts retention policy: Retention should balance recovery evidence, cost and governance rather than indiscriminately retaining or deleting every build.
This is designed for Agent cost management: Pool sizing is a tradeoff between capacity, execution delay and infrastructure or licensing cost.
This would instead address Ring deployment cohort: Rings separate user populations for controlled exposure and detect population-specific problems before broad deployment.
A service owner treats increasing line coverage as proof that new authorization logic is correct.
Which explanation best supports the needed implementation decision?
Coverage shows code exercised, not whether assertions verify correct outcomes or critical boundary conditions. The appropriate response is to collect coverage alongside risk-based assertions and branch or integration test evidence for important behavior. The expected evidence is that a coverage report is paired with tests proving normal, failure and authorization paths behave as required.
That explanation is about Ring deployment cohort: Rings separate user populations for controlled exposure and detect population-specific problems before broad deployment.
This describes the mechanism for Quality security release gate: A gate turns verifiable quality and risk evidence into an enforceable deployment decision rather than advisory console output.
That explanation is about Unit tests fast feedback: Unit tests isolate individual functions or units and provide rapid low-cost correctness feedback before integration environments are needed.
A service owner treats increasing line coverage as proof that new authorization logic is correct.
Which risk most directly follows if the team leaves this problem unresolved?
High coverage may create false confidence while important adverse behaviors remain untested. The failure follows from the described gap because coverage shows code exercised, not whether assertions verify correct outcomes or critical boundary conditions. Mitigate it by choosing to collect coverage alongside risk-based assertions and branch or integration test evidence for important behavior.
That consequence is characteristic of Bicep module reuse: Parameterizing common infrastructure definitions enforces coherent defaults while permitting legitimate environment differences. The present scenario instead leaves the coverage meaningful measurement requirement unresolved, which creates this more direct risk: high coverage may create false confidence while important adverse behaviors remain untested.
That is a credible failure of Quality security release gate: A gate turns verifiable quality and risk evidence into an enforceable deployment decision rather than advisory console output. The present scenario instead leaves the coverage meaningful measurement requirement unresolved, which creates this more direct risk: high coverage may create false confidence while important adverse behaviors remain untested.
This risk is associated with Publish test results: Structured test results allow failures and trends to be associated with builds and commits, instead of buried in unstructured logs. The present scenario instead leaves the coverage meaningful measurement requirement unresolved, which creates this more direct risk: high coverage may create false confidence while important adverse behaviors remain untested.
An enterprise wants management-group governance and resource-group application resources deployed through distinct accountable workflows.
What is the most appropriate action for this DevOps team?
Select the appropriate ARM deployment scope and grant the deployment identity only required scoped permissions. Azure Resource Manager scopes determine where resources and policy assignments can be created, independently of template language. A useful check is that a subscription or management-group change runs through its authorized scope while a resource-group build cannot affect higher scopes.
That intervention fits IaC drift detection: Infrastructure-as-code remains trustworthy only if manual changes are detected and either approved into code or safely reverted.
This is designed for Bicep module reuse: Parameterizing common infrastructure definitions enforces coherent defaults while permitting legitimate environment differences.
This would instead address Build cache with correctness: Correct cache keys improve speed while preventing incompatible or stale cached outputs from silently changing builds.
A payments team wants Azure Pipelines production approval owned by the environment administrators, not YAML authors.
Which explanation best supports the needed implementation decision?
Environment checks are managed on the resource rather than inside the pipeline YAML, resisting bypass by repository edits. The appropriate response is to configure the approval as a protected Azure Pipelines environment check owned outside editable YAML. The expected evidence is that the production stage waits for authorized approval, and YAML-only changes cannot remove the check.
That explanation is about YAML multi-stage dependency: Pipelines may execute independent jobs in parallel, so dependent stages must be linked to upstream successful work.
This reasoning pertains to Reusable YAML template: Includes and parameterized templates centralize repeatable pipeline logic while keeping service-specific inputs explicit.
That explanation is about Agent image maintenance: Controlled immutable agent baselines reduce drift and known vulnerabilities while retaining build reproducibility.
A staged Kubernetes application uses an image tag that gets overwritten during unrelated builds before production promotion.
Which observation most directly confirms the required DevOps control is effective?
The production workload reports the same approved image digest that passed integration and scanning gates. This shows that the control was implemented as intended: promote the tested container by immutable digest rather than relying on a mutable tag name. It matters because image digests identify exact content, preserving supply-chain consistency across environments despite tag changes.
Such evidence would establish Build cache with correctness, where the relevant control is introduce keyed dependency or build caching with OS, version and lockfile inputs and validated invalidation.
That result would verify Canary progressive exposure, where the relevant control is use a canary deployment with gradually increased traffic and health-based rollback thresholds.
Such evidence would establish Ring deployment cohort, where the relevant control is implement a ring-based rollout with ordered cohorts, monitoring and explicit promotion criteria.
Two downstream projects accept a new library version automatically without recognizing that a required method was removed.
Which observation most directly confirms the required DevOps control is effective?
A breaking update increments its major version and consumers intentionally opt into the new contract. This shows that the control was implemented as intended: apply semantic versioning and increase the major version for breaking public compatibility changes. It matters because semVer communicates compatibility intent by distinguishing major breaks, compatible additions and backward-compatible fixes.
That result would verify Feature flag dark launch, where the relevant control is use a controlled feature flag with scoped audience targeting and an audited kill switch.
This observation would support Dependency lockfile reproducibility, where the relevant control is commit a dependency lockfile and use deterministic restore or frozen-lockfile build options.
Such evidence would establish Immutable pipeline artifact, where the relevant control is publish an immutable versioned build artifact once and promote the same artifact through environments.
A deployment pipeline references a mutable container tag so production may pull a different image from the one tested.
Which explanation best supports the needed implementation decision?
Image digests identify exact content, preserving supply-chain consistency across environments despite tag changes. The appropriate response is to promote the tested container by immutable digest rather than relying on a mutable tag name. The expected evidence is that the production workload reports the same approved image digest that passed integration and scanning gates.
This describes the mechanism for Hotfix path: A distinct expedited path preserves essential test and approval controls while avoiding unrelated functionality.
This reasoning pertains to Central internal package feed: A central package feed provides controlled distribution and dependency metadata instead of silently copying libraries between repositories.
That explanation is about Database expand-contract migration: The expand phase adds compatible schema, data migration occurs safely, and contraction follows after consumers have transitioned.
An Azure Pipeline deploys to Azure using a service-principal client secret that operators must renew manually each quarter.
Which risk most directly follows if the team leaves this problem unresolved?
A leaked or expired static credential can enable unauthorized deployments or interrupt legitimate release work. The failure follows from the described gap because oIDC-based federation exchanges trusted workflow identity assertions for short-lived cloud access, reducing static credential exposure. Mitigate it by choosing to use a scoped workload identity federation service connection or GitHub OIDC trust instead of storing long-lived cloud secrets.
That consequence is characteristic of Azure DevOps least privilege: Access levels govern available features while permissions and security groups govern allowed actions; both matter for least privilege. The present scenario instead leaves the workload identity federation requirement unresolved, which creates this more direct risk: a leaked or expired static credential can enable unauthorized deployments or interrupt legitimate release work.
This risk is associated with Managed identity versus service principal: Azure-managed workload identities authenticate Azure resources without an application-managed secret, with access granted through role assignments. The present scenario instead leaves the workload identity federation requirement unresolved, which creates this more direct risk: a leaked or expired static credential can enable unauthorized deployments or interrupt legitimate release work.
That consequence is characteristic of Secret log masking and command safety: Masked variables are not a substitute for avoiding secret output; transformed or embedded secret strings can evade automatic redaction. The present scenario instead leaves the workload identity federation requirement unresolved, which creates this more direct risk: a leaked or expired static credential can enable unauthorized deployments or interrupt legitimate release work.
A service owner compares outage teams using ticket closure counts although critical restoration speed varies widely.
What is the most appropriate action for this DevOps team?
Measure time to restore service from incident impact to verified recovery and trend it alongside incident frequency. Recovery duration captures actual service impact better than activity counts and can guide investment in incident response. A useful check is that incident records contain onset and verified recovery times and the restoration trend is shown across comparable events.
This would instead address Teams pipeline notifications: Purposeful notifications give stakeholders timely actionable status while original pipeline permissions continue to protect detail.
That intervention fits Query-based work metrics: Consistent query definitions produce comparable operational metrics from the underlying tracked work rather than manual snapshots.
This would instead address Deployment frequency and failure rate: Delivery speed without failure consequences is incomplete; balanced flow and stability indicators reveal unhealthy tradeoffs.
A shared library build needs to combine application source from one repository and approved infrastructure templates from another.
Which observation most directly confirms the required DevOps control is effective?
The build obtains both approved sources at recorded revisions, and unapproved repositories cannot be checked out. This shows that the control was implemented as intended: declare authorized repository resources and checkout steps with pinned or reviewed source references. It matters because explicit repository resources make multi-repository dependencies reproducible and subject to service-connection and permission checks.
This observation would support Azure Deployment Environments, where the relevant control is provide Azure Deployment Environments based on curated environment definitions and governed identities.
Such evidence would establish Trigger branch and path filters, where the relevant control is set precise branch and path trigger filters, retaining broad protected-branch verification where needed.
That result would verify Reusable YAML template, where the relevant control is extract common stages into version-controlled YAML templates with parameters for safe variations.
or Guarantee your success by buying the full version which covers the full latest pool of questions. (398 Questions, Last Updated on Nov 11, 2026)
Please check your mailbox for a message from support@examlabs.com and follow the directions.