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 repository administrator grants all automation identities write access to every project for convenience.
Which risk most directly follows if the team leaves this problem unresolved?
A compromised low-trust account could change production code or repository governance. The failure follows from the described gap because least-privilege repository authorization minimizes the impact of a compromised user or automation token. Mitigate it by choosing to assign repository permissions by task and restrict branch write operations to approved roles and workflows.
That is a credible failure of Merge policy stale approval: Approvals should cover the final content actually merged, rather than an earlier snapshot of the branch. The present scenario instead leaves the repository least privilege requirement unresolved, which creates this more direct risk: a compromised low-trust account could change production code or repository governance.
This risk is associated with Recover one commit safely: Revert preserves the published commit graph while negating the selected change through a new auditable commit. The present scenario instead leaves the repository least privilege requirement unresolved, which creates this more direct risk: a compromised low-trust account could change production code or repository governance.
That consequence is characteristic of Git LFS for binaries: Git LFS replaces eligible large file content in history with lightweight pointers and manages binary content separately. The present scenario instead leaves the repository least privilege requirement unresolved, which creates this more direct risk: a compromised low-trust account could change production code or repository governance.
A developer commits a cloud access key and branch policies permit merging because unit tests pass.
Which observation most directly confirms the required DevOps control is effective?
The leak blocks or flags the proposed change and the exposed credential is revoked before a safe replacement merges. This shows that the control was implemented as intended: enable automated secret scanning and push or pull-request protection with clear remediation for exposed values. It matters because secret scanning detects known credential patterns before promotion and alerts owners to rotate any exposed credential.
Such evidence would establish Container image scanning, where the relevant control is scan container images and dependencies before promotion, enforce risk-based gates and retain image provenance.
That result would verify Key Vault runtime secret retrieval, where the relevant control is store sensitive values in Azure Key Vault and retrieve them through authorized pipeline identities at execution time.
This observation would support 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.
A third-party quality vendor can push directly to protected production branches even though it only needs to report issues.
Which observation most directly confirms the required DevOps control is effective?
Permission tests confirm the vendor can create required reports but cannot modify protected source or settings. This shows that the control was implemented as intended: assign repository permissions by task and restrict branch write operations to approved roles and workflows. It matters because least-privilege repository authorization minimizes the impact of a compromised user or automation token.
Such evidence would establish Merge policy stale approval, where the relevant control is enable review dismissal or fresh approvals when new commits change an approved pull request.
This observation would support Recover one commit safely, where the relevant control is use git revert to create a compensating commit on shared history rather than forcibly resetting the published branch.
Such evidence would establish Remove leaked credential from Git, where the relevant control is revoke and rotate the exposed credential immediately, remove sensitive history using an approved rewrite and coordinate downstream cleanup.
An image publishing job starts before test and signing jobs finish, exposing unverified artifacts to downstream deployments.
Which observation most directly confirms the required DevOps control is effective?
Publish or deploy starts only after all required predecessor tests and signing checks succeed. This shows that the control was implemented as intended: declare explicit YAML stage/job dependencies and conditions to enforce required execution order. It matters because pipelines may execute independent jobs in parallel, so dependent stages must be linked to upstream successful work.
That result would verify Desired state configuration, where the relevant control is use an appropriate Azure Machine Configuration or desired-state policy mechanism to audit and remediate configuration drift.
This observation would support Extends security template, where the relevant control is use a governed YAML extends template and required-template checks for enforceable pipeline structure.
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.
An ML-enabled application tracks large test fixtures in source control and ordinary clone operations take hours.
What is the most appropriate action for this DevOps team?
Use Git LFS for large binaries with explicit patterns while leaving source code in ordinary Git storage. Git LFS replaces eligible large file content in history with lightweight pointers and manages binary content separately. A useful check is that developers can clone code efficiently and retrieve versioned large binaries through an authorized LFS endpoint.
That intervention fits Scalar for large monorepo: Optimized Git enlistments and reduced working-tree scope can make monorepo operations practical without splitting required source history.
This is designed 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 would instead address Merge policy stale approval: Approvals should cover the final content actually merged, rather than an earlier snapshot of the branch.
An infrastructure engineer needs to see which Azure resources a Bicep change will add or modify before applying it.
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 Desired state configuration, where the relevant control is use an appropriate Azure Machine Configuration or desired-state policy mechanism to audit and remediate configuration drift.
This observation would support Environment parameters without secrets, where the relevant control is separate nonsecret environment parameters and inject sensitive values from approved secret stores at deployment.
Such evidence would establish Agent image maintenance, where the relevant control is manage versioned hardened runner images with patch schedules and automated smoke validation.
An online retailer has several developers editing the same API on long-lived branches, delaying integration until release week.
Which explanation best supports the needed implementation decision?
Frequent small integrations reduce divergence while flags separate code integration from customer feature exposure. The appropriate response is to adopt trunk-based integration with short-lived branches, automated tests and feature flags for incomplete work. The expected evidence is that pull requests merge frequently against a passing trunk and incomplete features remain safely disabled.
This reasoning pertains to Repository least privilege: Least-privilege repository authorization minimizes the impact of a compromised user or automation token.
This describes the mechanism for Code owner review: Path-based review rules route sensitive changes to accountable specialists before merge.
This reasoning pertains to Required status checks: Server-enforced branch rules validate executable evidence before integration, independent of informal reviewer assurances.
A developer committed a service credential, deleted it in a later commit and assumes the leak has ended.
Which risk most directly follows if the team leaves this problem unresolved?
The old credential remains exploitable through history, forks or cached copies even after a later deletion. The failure follows from the described gap because deleting a current file does not remove earlier Git objects or copies; invalidating the credential is the immediate security control. Mitigate it by choosing to revoke and rotate the exposed credential immediately, remove sensitive history using an approved rewrite and coordinate downstream cleanup.
This risk is associated with Feature branching with reviews: Branch protection enables isolated contribution while enforcing a consistent integration gate before accepted code reaches the default branch. The present scenario instead leaves the remove leaked credential from git requirement unresolved, which creates this more direct risk: the old credential remains exploitable through history, forks or cached copies even after a later deletion.
That consequence is characteristic of Signed annotated release tags: A release tag marks an intended commit, while signing and tag protection add evidence against unauthorized retargeting. The present scenario instead leaves the remove leaked credential from git requirement unresolved, which creates this more direct risk: the old credential remains exploitable through history, forks or cached copies even after a later deletion.
This risk is associated with Repository least privilege: Least-privilege repository authorization minimizes the impact of a compromised user or automation token. The present scenario instead leaves the remove leaked credential from git requirement unresolved, which creates this more direct risk: the old credential remains exploitable through history, forks or cached copies even after a later deletion.
A front-end request calls several downstream microservices and only a final timeout is recorded in the gateway logs.
What is the most appropriate action for this DevOps team?
Use correlated distributed tracing across instrumented services with propagated operation identifiers. Trace correlation connects related requests and dependencies across service boundaries to reveal end-to-end latency contributors. A useful check is that a single user request displays its dependent spans and the slow or failed downstream component.
This is designed for Kusto query failed requests: Kusto Query Language supports time-window filtering, aggregation and ranking of collected telemetry for focused diagnosis.
This would instead address Application Insights request telemetry: Application-level instrumentation exposes call outcomes and dependency contributions that basic host availability cannot explain.
That intervention fits Telemetry SLO feedback loop: Aligning deployment events to relevant user-facing reliability metrics turns observability into continuous improvement decisions.
A desktop client update has varied compatibility across internal staff, early adopters and external customers.
What is the most appropriate action for this DevOps team?
Implement a ring-based rollout with ordered cohorts, monitoring and explicit promotion criteria. Rings separate user populations for controlled exposure and detect population-specific problems before broad deployment. A useful check is that the pilot ring meets stability targets before subsequent rings receive the signed update.
That intervention fits Reusable YAML template: Includes and parameterized templates centralize repeatable pipeline logic while keeping service-specific inputs explicit.
This is designed for Canary progressive exposure: Progressive exposure limits the blast radius of a defective release and generates production observations before full cutover.
This would instead address Feature flag dark launch: Feature flags decouple delivery of code from exposure of functionality, allowing targeted enablement and rapid disablement.
A production Azure resource is modified directly in the portal so the next pipeline apply surprises the team with unwanted changes.
Which explanation best supports the needed implementation decision?
Infrastructure-as-code remains trustworthy only if manual changes are detected and either approved into code or safely reverted. The appropriate response is to compare deployed Azure state against the declared IaC baseline and reconcile drift through reviewed changes. The expected evidence is that a drift report identifies the change and the approved reconciliation restores the intended configuration.
That explanation is about Environment parameters without secrets: Version-controlled IaC can contain safe configuration values, but privileged credentials require a protected secret delivery path.
This reasoning pertains to ARM what-if safety: What-if predicts resource effects without modifying live state, supporting risk review of declarative changes.
That explanation is about Semantic versioning: SemVer communicates compatibility intent by distinguishing major breaks, compatible additions and backward-compatible fixes.
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.