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 regulated platform wants pipelines to reject unapproved task types even when repository contributors edit their YAML definitions.
Which explanation best supports the needed implementation decision?
An extends template can constrain allowed pipeline steps, while checks on protected resources prevent easy removal of the requirement. The appropriate response is to use a governed YAML extends template and required-template checks for enforceable pipeline structure. The expected evidence is that a pipeline attempting to omit the approved template or run a prohibited task is rejected before a protected release.
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 describes the mechanism for Build cache with correctness: Correct cache keys improve speed while preventing incompatible or stale cached outputs from silently changing builds.
This reasoning pertains to YAML environments approvals: Environment checks are managed on the resource rather than inside the pipeline YAML, resisting bypass by repository edits.
A repository accepts accidentally pasted personal access tokens and the team discovers them only after public release.
Which explanation best supports the needed implementation decision?
Secret scanning detects known credential patterns before promotion and alerts owners to rotate any exposed credential. The appropriate response is to enable automated secret scanning and push or pull-request protection with clear remediation for exposed values. The expected evidence is that the leak blocks or flags the proposed change and the exposed credential is revoked before a safe replacement merges.
This reasoning pertains to GitHub Advanced Security and Defender: Integrated DevOps security posture helps central teams connect source risk with affected development assets and cloud governance.
That explanation is about Dependabot dependency alerts: Dependency scanning connects known advisories to manifest and lockfile versions and can propose reviewed updates.
This describes the mechanism for Managed identity versus service principal: Azure-managed workload identities authenticate Azure resources without an application-managed secret, with access granted through role assignments.
A government project keeps process diagrams in private slide files that fall out of sync with its Git repository.
Which risk most directly follows if the team leaves this problem unresolved?
Outdated instructions can cause an operator to promote components in the wrong order. The failure follows from the described gap because version-controlled documentation can evolve through ordinary review and makes dependencies inspectable by engineers and operators. Mitigate it by choosing to maintain reviewed Markdown documentation and Mermaid diagrams alongside the service delivery workflow.
That is a credible failure of Teams pipeline notifications: Purposeful notifications give stakeholders timely actionable status while original pipeline permissions continue to protect detail. The present scenario instead leaves the wiki and process diagrams requirement unresolved, which creates this more direct risk: outdated instructions can cause an operator to promote components in the wrong order.
That consequence is characteristic of Mean time to restore: Recovery duration captures actual service impact better than activity counts and can guide investment in incident response. The present scenario instead leaves the wiki and process diagrams requirement unresolved, which creates this more direct risk: outdated instructions can cause an operator to promote components in the wrong order.
That is a credible failure of Versioned release notes: Releasing documented change history helps consumers and support understand compatible features, fixes and known constraints. The present scenario instead leaves the wiki and process diagrams requirement unresolved, which creates this more direct risk: outdated instructions can cause an operator to promote components in the wrong order.
An enterprise monorepo causes everyday Git status operations to scan many irrelevant directories for each developer.
Which observation most directly confirms the required DevOps control is effective?
Representative developers complete status, fetch and build workflows with acceptable latency while retaining needed source access. This shows that the control was implemented as intended: evaluate Scalar and sparse or partial checkout strategies for large-repository development. It matters because optimized Git enlistments and reduced working-tree scope can make monorepo operations practical without splitting required source history.
This observation would support Git LFS for binaries, where the relevant control is use Git LFS for large binaries with explicit patterns while leaving source code in ordinary Git storage.
Such evidence would establish Code owner review, where the relevant control is define CODEOWNERS and require appropriate code-owner approval for protected paths.
This observation would support 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.
A team wants repeatable builds but agents have accumulated different compiler versions and undocumented fixes.
Which risk most directly follows if the team leaves this problem unresolved?
Unpatched or inconsistent agents cause both supply-chain risk and irreproducible pipeline outcomes. The failure follows from the described gap because controlled immutable agent baselines reduce drift and known vulnerabilities while retaining build reproducibility. Mitigate it by choosing to manage versioned hardened runner images with patch schedules and automated smoke validation.
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 agent image maintenance requirement unresolved, which creates this more direct risk: unpatched or inconsistent agents cause both supply-chain risk and irreproducible pipeline outcomes.
That is a credible failure of Rollback health criteria: Successful command execution is not proof of healthy user traffic; objective health checks guide safe progression. The present scenario instead leaves the agent image maintenance requirement unresolved, which creates this more direct risk: unpatched or inconsistent agents cause both supply-chain risk and irreproducible pipeline outcomes.
This risk is associated with 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 agent image maintenance requirement unresolved, which creates this more direct risk: unpatched or inconsistent agents cause both supply-chain risk and irreproducible pipeline outcomes.
A developer commits a cloud access key and branch policies permit merging because unit tests pass.
What is the most appropriate action for this DevOps team?
Enable automated secret scanning and push or pull-request protection with clear remediation for exposed values. Secret scanning detects known credential patterns before promotion and alerts owners to rotate any exposed credential. A useful check is that the leak blocks or flags the proposed change and the exposed credential is revoked before a safe replacement merges.
That intervention fits Container image scanning: Container scanning examines packaged runtime components that may not appear in application source analysis.
This is designed for Workload identity federation: OIDC-based federation exchanges trusted workflow identity assertions for short-lived cloud access, reducing static credential exposure.
This would instead address Dependabot dependency alerts: Dependency scanning connects known advisories to manifest and lockfile versions and can propose reviewed updates.
An application running on an Azure VM needs to read a secret but the team plans to embed a service-principal password in code.
Which explanation best supports the needed implementation decision?
Azure-managed workload identities authenticate Azure resources without an application-managed secret, with access granted through role assignments. The appropriate response is to use a managed identity for the Azure-hosted workload and assign minimal target-resource RBAC roles. The expected evidence is that the workload obtains a token and reaches only the authorized resource without a credential in source or logs.
That explanation is about Dependabot dependency alerts: Dependency scanning connects known advisories to manifest and lockfile versions and can propose reviewed updates.
This reasoning pertains to Service connection scope: Service connections are privileged deployment identities, so resource RBAC and use restrictions should match actual blast radius.
That explanation is about Workload identity federation: OIDC-based federation exchanges trusted workflow identity assertions for short-lived cloud access, reducing static credential exposure.
An Azure Pipeline deploys to Azure using a service-principal client secret that operators must renew manually each quarter.
Which explanation best supports the needed implementation decision?
OIDC-based federation exchanges trusted workflow identity assertions for short-lived cloud access, reducing static credential exposure. The appropriate response is to use a scoped workload identity federation service connection or GitHub OIDC trust instead of storing long-lived cloud secrets. The expected evidence is that the approved job obtains only scoped Azure access without any stored client secret and untrusted branches cannot impersonate it.
This describes the mechanism for GitHub App scope: GitHub Apps separate automation identity from a human account and can grant repository-scoped, revocable access.
This reasoning pertains to Secret scanning in pull requests: Secret scanning detects known credential patterns before promotion and alerts owners to rotate any exposed credential.
This describes the mechanism for Azure DevOps least privilege: Access levels govern available features while permissions and security groups govern allowed actions; both matter for least privilege.
A build pipeline deploys to one resource group but its Azure service connection has contributor rights across the entire subscription.
Which observation most directly confirms the required DevOps control is effective?
An authorized test pipeline can deploy to its resource group but cannot alter other environments. This shows that the control was implemented as intended: scope service connection roles and approvals to the smallest necessary Azure resources and pipeline consumers. It matters because service connections are privileged deployment identities, so resource RBAC and use restrictions should match actual blast radius.
That result would verify Managed identity versus service principal, where the relevant control is use a managed identity for the Azure-hosted workload and assign minimal target-resource RBAC roles.
This observation would support CodeQL static analysis, where the relevant control is run CodeQL analysis appropriate to the code language and act on high-severity findings before release.
Such evidence would establish GitHub App scope, where the relevant control is use a GitHub App installation with narrowly requested repository permissions and short-lived installation tokens.
A developer group wants actionable deployment completion summaries in Microsoft Teams without disclosing build secrets.
Which observation most directly confirms the required DevOps control is effective?
The correct Teams channel receives failure and deployment notifications with working links and no exposed credentials. This shows that the control was implemented as intended: integrate filtered pipeline status notifications with Microsoft Teams and link back to the secured run records. It matters because purposeful notifications give stakeholders timely actionable status while original pipeline permissions continue to protect detail.
Such evidence would establish Mean time to restore, where the relevant control is measure time to restore service from incident impact to verified recovery and trend it alongside incident frequency.
That result would verify Versioned release notes, where the relevant control is generate versioned release notes from linked work items, pull requests and approved change records.
This observation would support Wiki and process diagrams, where the relevant control is maintain reviewed Markdown documentation and Mermaid diagrams alongside the service delivery workflow.
A critical production defect needs a patch today, but the normal release train includes unrelated unverified features.
What is the most appropriate action for this DevOps team?
Create a controlled hotfix path from the production release, validate the targeted change and reconcile it into main. A distinct expedited path preserves essential test and approval controls while avoiding unrelated functionality. A useful check is that only the reviewed fix reaches the supported deployment and its commit is incorporated into ongoing development.
This is designed for Database expand-contract migration: The expand phase adds compatible schema, data migration occurs safely, and contraction follows after consumers have transitioned.
That intervention fits Date-based versioning: Calendar-based versions express release timing, but do not automatically convey semantic API compatibility.
This is designed for Rollback health criteria: Successful command execution is not proof of healthy user traffic; objective health checks guide safe progression.
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.