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
Two independently deployed service versions briefly share one database schema during a rolling upgrade.
What is the most appropriate action for this DevOps team?
Use backward-compatible expand-and-contract schema changes before removing old fields. The expand phase adds compatible schema, data migration occurs safely, and contraction follows after consumers have transitioned. A useful check is that both old and new application versions pass compatibility tests during the overlap window.
This would instead address Blue-green cutover: Blue-green deployment separates preparation from traffic cutover and preserves the previous healthy environment for reversal.
This is designed for Ring deployment cohort: Rings separate user populations for controlled exposure and detect population-specific problems before broad deployment.
This would instead address Central internal package feed: A central package feed provides controlled distribution and dependency metadata instead of silently copying libraries between repositories.
Developers push changes without fast isolation-level checks, discovering simple parsing bugs only after deployment.
Which explanation best supports the needed implementation decision?
Unit tests isolate individual functions or units and provide rapid low-cost correctness feedback before integration environments are needed. The appropriate response is to run fast deterministic unit tests early in CI and fail the build before slower stages on regressions. The expected evidence is that a targeted unit-test failure prevents promotion and reports the failing function within the first CI stage.
That explanation is about Publish test results: Structured test results allow failures and trends to be associated with builds and commits, instead of buried in unstructured logs.
This describes the mechanism for Test agent network isolation: An agent placed on an approved reachable network can exercise private services without exposing those services publicly.
That explanation is about Pipeline duration hotspot: Critical-path analysis separates true sequential work from jobs that can safely run concurrently.
Every CI job downloads identical dependencies and recompiles unchanged modules, but cache sharing is currently disabled.
What is the most appropriate action for this DevOps team?
Introduce keyed dependency or build caching with OS, version and lockfile inputs and validated invalidation. Correct cache keys improve speed while preventing incompatible or stale cached outputs from silently changing builds. A useful check is that a repeated unchanged build uses the cache and a changed lockfile forces a valid fresh restore.
This is designed for Agent image maintenance: Controlled immutable agent baselines reduce drift and known vulnerabilities while retaining build reproducibility.
This would instead address Extends security template: An extends template can constrain allowed pipeline steps, while checks on protected resources prevent easy removal of the requirement.
That intervention fits Concurrent deployment serialization: Serialization prevents conflicting writes to the same mutable production target while allowing independent builds elsewhere.
An enterprise monorepo causes everyday Git status operations to scan many irrelevant directories for each developer.
Which explanation best supports the needed implementation decision?
Optimized Git enlistments and reduced working-tree scope can make monorepo operations practical without splitting required source history. The appropriate response is to evaluate Scalar and sparse or partial checkout strategies for large-repository development. The expected evidence is that representative developers complete status, fetch and build workflows with acceptable latency while retaining needed source access.
That explanation is about Merge policy stale approval: Approvals should cover the final content actually merged, rather than an earlier snapshot of the branch.
This describes the mechanism for Remove leaked credential from Git: Deleting a current file does not remove earlier Git objects or copies; invalidating the credential is the immediate security control.
This reasoning pertains to Repository least privilege: Least-privilege repository authorization minimizes the impact of a compromised user or automation token.
Several teams duplicate networking and Key Vault resource definitions with different default security settings.
Which observation most directly confirms the required DevOps control is effective?
Deployments consume the approved module version and vary only explicit reviewed parameters. This shows that the control was implemented as intended: package reusable Bicep modules with reviewed parameters and approved module versions. It matters because parameterizing common infrastructure definitions enforces coherent defaults while permitting legitimate environment differences.
This observation would support Artifacts retention policy, where the relevant control is apply lifecycle-based retention for artifacts and dependencies consistent with rollback and compliance needs.
That result would verify Environment parameters without secrets, where the relevant control is separate nonsecret environment parameters and inject sensitive values from approved secret stores at deployment.
This observation would support IaC test pipeline, where the relevant control is run IaC linting and validation plus representative nonproduction deployment tests before production approval.
A team reports 95 percent line coverage yet critical error-handling paths are never tested.
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 Build cache with correctness: Correct cache keys improve speed while preventing incompatible or stale cached outputs from silently changing builds. 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 Contract testing independent release: Contract tests check agreed service boundaries, supporting independent deployment while detecting incompatible changes. 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 consequence is characteristic of Integration test service boundary: Integration testing checks behavior between components that unit tests with mocks cannot prove. 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.
A reporting team needs to identify exactly which calendar release of a non-library deliverable was deployed.
Which observation most directly confirms the required DevOps control is effective?
The deployed report package maps unambiguously to its publication month and documented compatibility notes. This shows that the control was implemented as intended: use a documented CalVer scheme for chronological releases while separately tracking backward-compatibility obligations. It matters because calendar-based versions express release timing, but do not automatically convey semantic API compatibility.
That result would verify Agent image maintenance, where the relevant control is manage versioned hardened runner images with patch schedules and automated smoke validation.
This observation would support Package vulnerability response, where the relevant control is maintain dependency inventories and a governed update pipeline that tests and promotes fixed package versions.
Such evidence would establish Package feed views, where the relevant control is use Azure Artifacts feed views to promote packages from prerelease into approved release consumption stages.
A group of independent contributors needs parallel isolated review of code changes before merging to main.
Which explanation best supports the needed implementation decision?
Branch protection enables isolated contribution while enforcing a consistent integration gate before accepted code reaches the default branch. The appropriate response is to use short-lived feature branches and protected pull requests with required reviewers and checks. The expected evidence is that direct pushes are rejected and proposed changes merge only after the configured approvals and successful checks.
This describes the mechanism for Repository least privilege: Least-privilege repository authorization minimizes the impact of a compromised user or automation token.
This reasoning pertains to Required status checks: Server-enforced branch rules validate executable evidence before integration, independent of informal reviewer assurances.
That explanation is about Code owner review: Path-based review rules route sensitive changes to accountable specialists before merge.
Two teams plan in Azure Boards and develop in GitHub, but a released bug fix has no connection to its Azure work item.
Which explanation best supports the needed implementation decision?
The Boards-GitHub integration surfaces development activity against the planning record, supporting end-to-end traceability across services. The appropriate response is to connect Azure Boards with GitHub and associate pull requests and commits with the corresponding work items. The expected evidence is that an auditor opens a work item and sees the linked GitHub pull request, associated commits and status.
This describes the mechanism for Bug quality feedback loop: Tying operational feedback to original code and acceptance criteria exposes recurring failure patterns and supports process improvement.
That explanation is about Wiki and process diagrams: Version-controlled documentation can evolve through ordinary review and makes dependencies inspectable by engineers and operators.
This describes the mechanism for GitHub Flow work visibility: Linking issues, pull requests, commits, checks, and releases gives stakeholders traceability without requiring a long-lived branch per ticket.
A developer can remove the organization's required signing task by deleting a line from a local pipeline YAML file.
What is the most appropriate action for this DevOps team?
Use a governed YAML extends template and required-template checks for enforceable pipeline structure. An extends template can constrain allowed pipeline steps, while checks on protected resources prevent easy removal of the requirement. A useful check is that a pipeline attempting to omit the approved template or run a prohibited task is rejected before a protected release.
This would instead address Immutable pipeline artifact: Artifact promotion ensures deployment stages share tested bytes rather than rebuilding from potentially changing source or packages.
That intervention fits YAML environments approvals: Environment checks are managed on the resource rather than inside the pipeline YAML, resisting bypass by repository edits.
This would instead address YAML multi-stage dependency: Pipelines may execute independent jobs in parallel, so dependent stages must be linked to upstream successful work.
Two production pipelines deploy different versions of the same service simultaneously and overwrite each other's state.
Which risk most directly follows if the team leaves this problem unresolved?
Racing deployments can leave mixed versions and make rollback or incident diagnosis unreliable. The failure follows from the described gap because serialization prevents conflicting writes to the same mutable production target while allowing independent builds elsewhere. Mitigate it by choosing to configure an exclusive environment lock or equivalent serialized deployment control.
This risk is associated with Feature flag dark launch: Feature flags decouple delivery of code from exposure of functionality, allowing targeted enablement and rapid disablement. The present scenario instead leaves the concurrent deployment serialization requirement unresolved, which creates this more direct risk: racing deployments can leave mixed versions and make rollback or incident diagnosis unreliable.
That consequence is characteristic of Pipeline retry boundaries: Retries are reliable only when repeated execution has a defined effect and partial failures are detectable. The present scenario instead leaves the concurrent deployment serialization requirement unresolved, which creates this more direct risk: racing deployments can leave mixed versions and make rollback or incident diagnosis unreliable.
That is a credible failure of Artifacts retention policy: Retention should balance recovery evidence, cost and governance rather than indiscriminately retaining or deleting every build. The present scenario instead leaves the concurrent deployment serialization requirement unresolved, which creates this more direct risk: racing deployments can leave mixed versions and make rollback or incident diagnosis unreliable.
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.