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 container image passes functional tests while its base image includes a high-severity vulnerable package.
What is the most appropriate action for this DevOps team?
Scan container images and dependencies before promotion, enforce risk-based gates and retain image provenance. Container scanning examines packaged runtime components that may not appear in application source analysis. A useful check is that a deliberately vulnerable image is blocked and the promoted digest maps to an acceptable scan result.
This is designed for Dependabot dependency alerts: Dependency scanning connects known advisories to manifest and lockfile versions and can propose reviewed updates.
This would instead address Workload identity federation: OIDC-based federation exchanges trusted workflow identity assertions for short-lived cloud access, reducing static credential exposure.
That intervention fits GitHub Advanced Security and Defender: Integrated DevOps security posture helps central teams connect source risk with affected development assets and cloud governance.
A pipeline downloads public packages directly on every run and often fails during external registry outages.
Which explanation best supports the needed implementation decision?
Upstream caching serves previously resolved packages from the controlled feed and reduces direct external registry dependence. The appropriate response is to configure an Azure Artifacts feed with upstream sources and retention of approved dependencies. The expected evidence is that a repeat build restores approved dependencies from the feed even when the upstream registry is unavailable.
That explanation is about ARM what-if safety: What-if predicts resource effects without modifying live state, supporting risk review of declarative changes.
This describes the mechanism for Semantic versioning: SemVer communicates compatibility intent by distinguishing major breaks, compatible additions and backward-compatible fixes.
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.
An automation bot holds a user personal access token with access to every organization repository solely to open pull requests.
Which observation most directly confirms the required DevOps control is effective?
The bot updates only installed repositories with the approved permissions and cannot read unrelated projects. This shows that the control was implemented as intended: use a GitHub App installation with narrowly requested repository permissions and short-lived installation tokens. It matters because gitHub Apps separate automation identity from a human account and can grant repository-scoped, revocable access.
This observation would support Azure DevOps least privilege, where the relevant control is assign appropriate Azure DevOps access levels and group roles according to actual work responsibilities.
That result would verify GitHub Advanced Security and Defender, where the relevant control is configure GitHub Advanced Security for the relevant repositories and integrate available findings with Defender for Cloud DevOps Security.
This observation would support Service connection scope, where the relevant control is scope service connection roles and approvals to the smallest necessary Azure resources and pipeline consumers.
A payments API meets response-time targets in staging with negligible requests but fails under peak concurrency.
Which risk most directly follows if the team leaves this problem unresolved?
The application appears correct while failing its performance obligations at real traffic volumes. The failure follows from the described gap because load testing exercises concurrency, capacity and bottlenecks that low-traffic correctness tests do not expose. Mitigate it by choosing to run representative load tests with production-like demand and enforce agreed latency and error thresholds.
That consequence is characteristic of Unit tests fast feedback: Unit tests isolate individual functions or units and provide rapid low-cost correctness feedback before integration environments are needed. The present scenario instead leaves the load test realistic capacity requirement unresolved, which creates this more direct risk: the application appears correct while failing its performance obligations at real traffic volumes.
That is a credible failure of Pipeline duration hotspot: Critical-path analysis separates true sequential work from jobs that can safely run concurrently. The present scenario instead leaves the load test realistic capacity requirement unresolved, which creates this more direct risk: the application appears correct while failing its performance obligations at real traffic volumes.
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 load test realistic capacity requirement unresolved, which creates this more direct risk: the application appears correct while failing its performance obligations at real traffic volumes.
A service owner needs automatic reversal when a new API version exceeds its permitted error budget.
Which explanation best supports the needed implementation decision?
Successful command execution is not proof of healthy user traffic; objective health checks guide safe progression. The appropriate response is to gate deployment completion on service-health metrics and invoke rollback when agreed thresholds fail. The expected evidence is that a failed error-rate or availability threshold stops promotion and restores the known-good version.
This reasoning pertains to Hotfix path: A distinct expedited path preserves essential test and approval controls while avoiding unrelated functionality.
That explanation is about Container image digest promotion: Image digests identify exact content, preserving supply-chain consistency across environments despite tag changes.
This describes the mechanism for Publish test results: Structured test results allow failures and trends to be associated with builds and commits, instead of buried in unstructured logs.
A public repository held an access token in historic commits even after the current file was cleaned up.
What is the most appropriate action for this DevOps team?
Revoke and rotate the exposed credential immediately, remove sensitive history using an approved rewrite and coordinate downstream cleanup. Deleting a current file does not remove earlier Git objects or copies; invalidating the credential is the immediate security control. A useful check is that the exposed token no longer authenticates and approved history-remediation checks find no accessible sensitive object.
This is designed for Scalar for large monorepo: Optimized Git enlistments and reduced working-tree scope can make monorepo operations practical without splitting required source history.
This would instead address Recover one commit safely: Revert preserves the published commit graph while negating the selected change through a new auditable commit.
That intervention fits Feature branching with reviews: Branch protection enables isolated contribution while enforcing a consistent integration gate before accepted code reaches the default branch.
An organization wants a tracking service to react when a repository pull request changes state without polling continuously.
What is the most appropriate action for this DevOps team?
Configure authenticated webhooks for specific repository events and handle retries and duplicate deliveries safely. Event subscriptions push relevant changes to a receiver; delivery validation and idempotency are necessary for dependable automation. A useful check is that a signed event causes one correct downstream update even after a retried webhook delivery.
This is designed for Teams pipeline notifications: Purposeful notifications give stakeholders timely actionable status while original pipeline permissions continue to protect detail.
That intervention fits Lead time versus cycle time: Lead time represents a broader demand-to-delivery interval while cycle time examines active flow through the chosen process boundaries.
This is designed for Wiki and process diagrams: Version-controlled documentation can evolve through ordinary review and makes dependencies inspectable by engineers and operators.
A pipeline's integration tests and package publish step run concurrently although publication requires successful integration evidence.
What is the most appropriate action for this DevOps team?
Declare explicit YAML stage/job dependencies and conditions to enforce required execution order. Pipelines may execute independent jobs in parallel, so dependent stages must be linked to upstream successful work. A useful check is that publish or deploy starts only after all required predecessor tests and signing checks succeed.
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 Parallel matrix builds: Independent job combinations can run concurrently, making compatibility tests faster without weakening the requirement that all pass.
This would instead address Coverage meaningful measurement: Coverage shows code exercised, not whether assertions verify correct outcomes or critical boundary conditions.
A payments API meets response-time targets in staging with negligible requests but fails under peak concurrency.
Which explanation best supports the needed implementation decision?
Load testing exercises concurrency, capacity and bottlenecks that low-traffic correctness tests do not expose. The appropriate response is to run representative load tests with production-like demand and enforce agreed latency and error thresholds. The expected evidence is that at the expected demand level the system meets percentile latency and error-rate targets before deployment.
That explanation is about Build cache with correctness: Correct cache keys improve speed while preventing incompatible or stale cached outputs from silently changing builds.
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.
This reasoning pertains to Flaky test quarantine: Flaky tests weaken confidence in build signals and consume delivery capacity; stabilization restores trustworthy pass/fail evidence.
A payments application receives releases from multiple branches and needs only one production deployment to hold the environment lock.
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.
That is a credible failure of Agent cost management: Pool sizing is a tradeoff between capacity, execution delay and infrastructure or licensing cost. 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.
This risk is associated with Agent image maintenance: Controlled immutable agent baselines reduce drift and known vulnerabilities while retaining build reproducibility. 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 Semantic versioning: SemVer communicates compatibility intent by distinguishing major breaks, compatible additions and backward-compatible fixes. 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.
A proposed infrastructure release may remove a storage resource, but the deployment change is approved without reviewing impact.
Which observation most directly confirms the required DevOps control is effective?
A reviewer sees planned Create, Modify or Delete effects and can stop an unexpected destructive change. This shows that the control was implemented as intended: run an Azure Resource Manager what-if evaluation and review predicted changes before protected deployment. It matters because what-if predicts resource effects without modifying live state, supporting risk review of declarative changes.
That result would verify Pipeline duration hotspot, where the relevant control is measure stage durations and parallelize independent tasks while preserving required dependencies.
Such evidence would establish Bicep module reuse, where the relevant control is package reusable Bicep modules with reviewed parameters and approved module versions.
That result would verify IaC drift detection, where the relevant control is compare deployed Azure state against the declared IaC baseline and reconcile drift through reviewed changes.
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.