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
An automation bot holds a user personal access token with access to every organization repository solely to open pull requests.
What is the most appropriate action for this DevOps team?
Use a GitHub App installation with narrowly requested repository permissions and short-lived installation tokens. GitHub Apps separate automation identity from a human account and can grant repository-scoped, revocable access. A useful check is that the bot updates only installed repositories with the approved permissions and cannot read unrelated projects.
This is designed for Secret rotation and scope: Scoped identities and rehearsed rotation reduce the security impact and operational disruption of credential compromise.
That intervention fits Managed identity versus service principal: Azure-managed workload identities authenticate Azure resources without an application-managed secret, with access granted through role assignments.
This is designed for Service connection scope: Service connections are privileged deployment identities, so resource RBAC and use restrictions should match actual blast radius.
A regulated project needs repeatable Azure infrastructure deployments reviewed in the same pull requests as application changes.
Which risk most directly follows if the team leaves this problem unresolved?
Manual resource creation produces inconsistent environments and untraceable production changes. The failure follows from the described gap because declarative IaC expresses intended Azure resource configurations and enables repeatable, reviewed deployment rather than manual portal drift. Mitigate it by choosing to define Azure resources in version-controlled Bicep modules and deploy them through reviewed pipelines.
That is a credible failure of 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 bicep as code requirement unresolved, which creates this more direct risk: manual resource creation produces inconsistent environments and untraceable production changes.
This risk is associated with Environment parameters without secrets: Version-controlled IaC can contain safe configuration values, but privileged credentials require a protected secret delivery path. The present scenario instead leaves the bicep as code requirement unresolved, which creates this more direct risk: manual resource creation produces inconsistent environments and untraceable production changes.
That is a credible failure of ARM what-if safety: What-if predicts resource effects without modifying live state, supporting risk review of declarative changes. The present scenario instead leaves the bicep as code requirement unresolved, which creates this more direct risk: manual resource creation produces inconsistent environments and untraceable production changes.
A critical production defect needs a patch today, but the normal release train includes unrelated unverified features.
Which risk most directly follows if the team leaves this problem unresolved?
Deploying the entire main branch may introduce unapproved features during emergency remediation. The failure follows from the described gap because a distinct expedited path preserves essential test and approval controls while avoiding unrelated functionality. Mitigate it by choosing to create a controlled hotfix path from the production release, validate the targeted change and reconcile it into main.
This risk is associated with Azure App Service deployment slot: Slots provide a separately deployed target and controlled swap that can reduce disruption when application startup is validated. The present scenario instead leaves the hotfix path requirement unresolved, which creates this more direct risk: deploying the entire main branch may introduce unapproved features during emergency remediation.
That consequence is characteristic of Package vulnerability response: Traceable package metadata and dependency scanning link vulnerabilities to actual consumers and enable controlled remediation. The present scenario instead leaves the hotfix path requirement unresolved, which creates this more direct risk: deploying the entire main branch may introduce unapproved features during emergency remediation.
That is a credible failure of Canary progressive exposure: Progressive exposure limits the blast radius of a defective release and generates production observations before full cutover. The present scenario instead leaves the hotfix path requirement unresolved, which creates this more direct risk: deploying the entire main branch may introduce unapproved features during emergency remediation.
A deployment pipeline needs to reach a restricted internal network that public hosted runners cannot access.
Which observation most directly confirms the required DevOps control is effective?
The build uses the approved compiler and private endpoint while runner image and permissions are controlled. This shows that the control was implemented as intended: provision managed self-hosted runners or agents with required toolchains, networking and hardened lifecycle controls. It matters because custom execution environments support private dependencies while making the organization responsible for patching, isolation and capacity.
That result would verify Extends security template, where the relevant control is use a governed YAML extends template and required-template checks for enforceable pipeline structure.
This observation would support Bicep module reuse, where the relevant control is package reusable Bicep modules with reviewed parameters and approved module versions.
Such evidence would establish YAML multi-stage dependency, where the relevant control is declare explicit YAML stage/job dependencies and conditions to enforce required execution order.
A repository administrator grants all automation identities write access to every project for convenience.
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.
That result would verify Feature branching with reviews, where the relevant control is use short-lived feature branches and protected pull requests with required reviewers and checks.
Such evidence would establish 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.
That result would verify 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 online store needs to test a new checkout API with a small subset of users before a global rollout.
Which observation most directly confirms the required DevOps control is effective?
Small-percentage traffic meets agreed latency and error thresholds before the rollout expands. This shows that the control was implemented as intended: use a canary deployment with gradually increased traffic and health-based rollback thresholds. It matters because progressive exposure limits the blast radius of a defective release and generates production observations before full cutover.
This observation would support Contract testing independent release, where the relevant control is add producer-consumer contract tests to both pipelines and gate incompatible interface changes before rollout.
Such evidence would establish Database expand-contract migration, where the relevant control is use backward-compatible expand-and-contract schema changes before removing old fields.
This observation would support Rollback health criteria, where the relevant control is gate deployment completion on service-health metrics and invoke rollback when agreed thresholds fail.
An engineer adds command-line tracing to debug production release steps, revealing secret task arguments.
Which risk most directly follows if the team leaves this problem unresolved?
Build readers can recover credentials from logs even when vault access itself is restricted. The failure follows from the described gap because masked variables are not a substitute for avoiding secret output; transformed or embedded secret strings can evade automatic redaction. Mitigate it by choosing to disable unsafe shell tracing and redact credentials while using approved secret variables and non-sensitive diagnostic output.
That consequence is characteristic of Workload identity federation: OIDC-based federation exchanges trusted workflow identity assertions for short-lived cloud access, reducing static credential exposure. The present scenario instead leaves the secret log masking and command safety requirement unresolved, which creates this more direct risk: build readers can recover credentials from logs even when vault access itself is restricted.
That is a credible failure of Secret rotation and scope: Scoped identities and rehearsed rotation reduce the security impact and operational disruption of credential compromise. The present scenario instead leaves the secret log masking and command safety requirement unresolved, which creates this more direct risk: build readers can recover credentials from logs even when vault access itself is restricted.
This risk is associated with Key Vault runtime secret retrieval: A dedicated secret store provides access control, rotation and auditing while preventing credentials from becoming ordinary source artifacts. The present scenario instead leaves the secret log masking and command safety requirement unresolved, which creates this more direct risk: build readers can recover credentials from logs even when vault access itself is restricted.
A pipeline maintains one broad credential for staging, production and audit systems with no rotation procedure.
Which risk most directly follows if the team leaves this problem unresolved?
One leaked token compromises multiple environments and emergency rotation breaks unrelated services. The failure follows from the described gap because scoped identities and rehearsed rotation reduce the security impact and operational disruption of credential compromise. Mitigate it by choosing to separate credentials by environment and purpose, use short lifetimes or federation, and test rotation and revocation.
This risk is associated with Key Vault runtime secret retrieval: A dedicated secret store provides access control, rotation and auditing while preventing credentials from becoming ordinary source artifacts. The present scenario instead leaves the secret rotation and scope requirement unresolved, which creates this more direct risk: one leaked token compromises multiple environments and emergency rotation breaks unrelated services.
That consequence is characteristic of Secret scanning in pull requests: Secret scanning detects known credential patterns before promotion and alerts owners to rotate any exposed credential. The present scenario instead leaves the secret rotation and scope requirement unresolved, which creates this more direct risk: one leaked token compromises multiple environments and emergency rotation breaks unrelated services.
That is a credible failure of Azure Pipelines secure files: Secure files are protected pipeline resources with permissions and checks, unlike publicly retrievable general artifacts. The present scenario instead leaves the secret rotation and scope requirement unresolved, which creates this more direct risk: one leaked token compromises multiple environments and emergency rotation breaks unrelated services.
An online store needs to test a new checkout API with a small subset of users before a global rollout.
What is the most appropriate action for this DevOps team?
Use a canary deployment with gradually increased traffic and health-based rollback thresholds. Progressive exposure limits the blast radius of a defective release and generates production observations before full cutover. A useful check is that small-percentage traffic meets agreed latency and error thresholds before the rollout expands.
That intervention fits Container image digest promotion: Image digests identify exact content, preserving supply-chain consistency across environments despite tag changes.
This would instead address Hosted versus self-hosted agents: Custom execution environments support private dependencies while making the organization responsible for patching, isolation and capacity.
That intervention fits Database expand-contract migration: The expand phase adds compatible schema, data migration occurs safely, and contraction follows after consumers have transitioned.
A deployment engineer cannot demonstrate that the package approved in preproduction is the exact one installed in production.
What is the most appropriate action for this DevOps team?
Publish an immutable versioned build artifact once and promote the same artifact through environments. Artifact promotion ensures deployment stages share tested bytes rather than rebuilding from potentially changing source or packages. A useful check is that artifact checksums and build IDs are identical in staging and production deployment records.
This is designed for Package feed views: Views provide curated subsets of immutable feed packages for different consumer readiness levels.
This would instead address Date-based versioning: Calendar-based versions express release timing, but do not automatically convey semantic API compatibility.
This is designed for Contract testing independent release: Contract tests check agreed service boundaries, supporting independent deployment while detecting incompatible changes.
A reporting team needs to identify exactly which calendar release of a non-library deliverable was deployed.
Which explanation best supports the needed implementation decision?
Calendar-based versions express release timing, but do not automatically convey semantic API compatibility. The appropriate response is to use a documented CalVer scheme for chronological releases while separately tracking backward-compatibility obligations. The expected evidence is that the deployed report package maps unambiguously to its publication month and documented compatibility notes.
This reasoning pertains to Immutable pipeline artifact: Artifact promotion ensures deployment stages share tested bytes rather than rebuilding from potentially changing source or packages.
That explanation is about Pipeline duration hotspot: Critical-path analysis separates true sequential work from jobs that can safely run concurrently.
This describes the mechanism for Dependency lockfile reproducibility: A lockfile records the resolved dependency graph to make repeated builds use the same versions rather than current registry selection.
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.