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 that deploys a test service can also modify production Key Vault and network resources through its shared connection.
Which risk most directly follows if the team leaves this problem unresolved?
A compromised pipeline could reconfigure production resources outside its intended deployment target. The failure follows from the described gap because service connections are privileged deployment identities, so resource RBAC and use restrictions should match actual blast radius. Mitigate it by choosing to scope service connection roles and approvals to the smallest necessary Azure resources and pipeline consumers.
That is a credible failure of GitHub App scope: GitHub Apps separate automation identity from a human account and can grant repository-scoped, revocable access. The present scenario instead leaves the service connection scope requirement unresolved, which creates this more direct risk: a compromised pipeline could reconfigure production resources outside its intended deployment target.
That consequence is characteristic of Managed identity versus service principal: Azure-managed workload identities authenticate Azure resources without an application-managed secret, with access granted through role assignments. The present scenario instead leaves the service connection scope requirement unresolved, which creates this more direct risk: a compromised pipeline could reconfigure production resources outside its intended deployment target.
That is a credible failure of Dependabot dependency alerts: Dependency scanning connects known advisories to manifest and lockfile versions and can propose reviewed updates. The present scenario instead leaves the service connection scope requirement unresolved, which creates this more direct risk: a compromised pipeline could reconfigure production resources outside its intended deployment target.
A desktop client update has varied compatibility across internal staff, early adopters and external customers.
Which observation most directly confirms the required DevOps control is effective?
The pilot ring meets stability targets before subsequent rings receive the signed update. This shows that the control was implemented as intended: implement a ring-based rollout with ordered cohorts, monitoring and explicit promotion criteria. It matters because rings separate user populations for controlled exposure and detect population-specific problems before broad deployment.
This observation would support Feature flag dark launch, where the relevant control is use a controlled feature flag with scoped audience targeting and an audited kill switch.
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 Extends security template, where the relevant control is use a governed YAML extends template and required-template checks for enforceable pipeline structure.
A public service deploys new endpoints but support receives no reliable record of what changed for affected users.
Which observation most directly confirms the required DevOps control is effective?
Each deployed version has accurate notes listing the associated changes, breaking behaviors and support actions. This shows that the control was implemented as intended: generate versioned release notes from linked work items, pull requests and approved change records. It matters because releasing documented change history helps consumers and support understand compatible features, fixes and known constraints.
Such evidence would establish Wiki and process diagrams, where the relevant control is maintain reviewed Markdown documentation and Mermaid diagrams alongside the service delivery workflow.
That result would verify Cross-team workflow handoffs, where the relevant control is model explicit states, owners and handoff criteria for each work stage in Azure Boards or GitHub Projects.
This observation would support Webhooks for event integration, where the relevant control is configure authenticated webhooks for specific repository events and handle retries and duplicate deliveries safely.
An operations team enables blind retry for a pipeline step that creates cloud resources without checking whether the first attempt partially succeeded.
Which explanation best supports the needed implementation decision?
Retries are reliable only when repeated execution has a defined effect and partial failures are detectable. The appropriate response is to retry only safe idempotent operations and use checkpoints and explicit recovery for state-changing steps. The expected evidence is that a failed stage resumes or rolls back without duplicate schema changes or conflicting infrastructure resources.
That explanation is about Azure Deployment Environments: Deployment Environments enables self-service provisioning through approved templates rather than arbitrary subscription-wide access.
This describes the mechanism for Artifacts retention policy: Retention should balance recovery evidence, cost and governance rather than indiscriminately retaining or deleting every build.
This reasoning pertains to Pipeline duration hotspot: Critical-path analysis separates true sequential work from jobs that can safely run concurrently.
An internal signing job needs a protected provisioning file only during one authorized deployment.
Which risk most directly follows if the team leaves this problem unresolved?
A private certificate or provisioning file may be leaked through normal artifact downloads. The failure follows from the described gap because secure files are protected pipeline resources with permissions and checks, unlike publicly retrievable general artifacts. Mitigate it by choosing to use Azure Pipelines secure files with access restrictions and approved tasks to deliver the file only to authorized jobs.
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 azure pipelines secure files requirement unresolved, which creates this more direct risk: a private certificate or provisioning file may be leaked through normal artifact downloads.
That is a credible failure of Managed identity versus service principal: Azure-managed workload identities authenticate Azure resources without an application-managed secret, with access granted through role assignments. The present scenario instead leaves the azure pipelines secure files requirement unresolved, which creates this more direct risk: a private certificate or provisioning file may be leaked through normal artifact downloads.
This risk is associated with 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 azure pipelines secure files requirement unresolved, which creates this more direct risk: a private certificate or provisioning file may be leaked through normal artifact downloads.
A GitHub application consumes outdated open-source libraries but no team owns remediation when advisories are published.
Which risk most directly follows if the team leaves this problem unresolved?
Published package vulnerabilities remain present in deployed software despite available patches. The failure follows from the described gap because dependency scanning connects known advisories to manifest and lockfile versions and can propose reviewed updates. Mitigate it by choosing to enable Dependabot alerts and security updates, then validate proposed fixes in CI with clear ownership.
That consequence is characteristic 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 dependabot dependency alerts requirement unresolved, which creates this more direct risk: published package vulnerabilities remain present in deployed software despite available patches.
That is a credible failure of GitHub Advanced Security and Defender: Integrated DevOps security posture helps central teams connect source risk with affected development assets and cloud governance. The present scenario instead leaves the dependabot dependency alerts requirement unresolved, which creates this more direct risk: published package vulnerabilities remain present in deployed software despite available patches.
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 dependabot dependency alerts requirement unresolved, which creates this more direct risk: published package vulnerabilities remain present in deployed software despite available patches.
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 observation most directly confirms the required DevOps control is effective?
The workload obtains a token and reaches only the authorized resource without a credential in source or logs. This shows that the control was implemented as intended: use a managed identity for the Azure-hosted workload and assign minimal target-resource RBAC roles. It matters because azure-managed workload identities authenticate Azure resources without an application-managed secret, with access granted through role assignments.
That result would verify Secret scanning in pull requests, where the relevant control is enable automated secret scanning and push or pull-request protection with clear remediation for exposed values.
This observation would support GitHub App scope, where the relevant control is use a GitHub App installation with narrowly requested repository permissions and short-lived installation tokens.
Such evidence would establish Service connection scope, where the relevant control is scope service connection roles and approvals to the smallest necessary Azure resources and pipeline consumers.
A signed deployment requires a certificate file but the team proposes publishing its private key as an ordinary build artifact.
Which observation most directly confirms the required DevOps control is effective?
Only the designated deployment can access the signing file, and it is not published with the application package. This shows that the control was implemented as intended: use Azure Pipelines secure files with access restrictions and approved tasks to deliver the file only to authorized jobs. It matters because secure files are protected pipeline resources with permissions and checks, unlike publicly retrievable general artifacts.
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.
That result would verify Secret rotation and scope, where the relevant control is separate credentials by environment and purpose, use short lifetimes or federation, and test rotation and revocation.
This observation would support 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.
A city transport API team uses GitHub Issues but testers cannot connect reported bugs to the commits resolving them.
Which risk most directly follows if the team leaves this problem unresolved?
An unlinked production change can bypass review or be impossible to associate with its original requirement. The failure follows from the described gap because linking issues, pull requests, commits, checks, and releases gives stakeholders traceability without requiring a long-lived branch per ticket. Mitigate it by choosing to establish GitHub Flow with short branches, reviewed pull requests, and explicit issue-to-commit and deployment links.
That consequence is characteristic 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 github flow work visibility requirement unresolved, which creates this more direct risk: an unlinked production change can bypass review or be impossible to associate with its original requirement.
This risk is associated with Bug quality feedback loop: Tying operational feedback to original code and acceptance criteria exposes recurring failure patterns and supports process improvement. The present scenario instead leaves the github flow work visibility requirement unresolved, which creates this more direct risk: an unlinked production change can bypass review or be impossible to associate with its original requirement.
That consequence is characteristic of Cross-team workflow handoffs: An explicit work-item flow gives each team a shared view of readiness and blocked dependencies rather than separate informal queues. The present scenario instead leaves the github flow work visibility requirement unresolved, which creates this more direct risk: an unlinked production change can bypass review or be impossible to associate with its original requirement.
A monthly data-processing component has release identity tied to scheduled publications rather than API compatibility levels.
What is the most appropriate action for this DevOps team?
Use a documented CalVer scheme for chronological releases while separately tracking backward-compatibility obligations. Calendar-based versions express release timing, but do not automatically convey semantic API compatibility. A useful check is that the deployed report package maps unambiguously to its publication month and documented compatibility notes.
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.
That intervention fits Desired state configuration: Desired-state tools assess ongoing configuration after provisioning, whereas resource deployment alone does not ensure guest settings persist.
This would instead address Immutable pipeline artifact: Artifact promotion ensures deployment stages share tested bytes rather than rebuilding from potentially changing source or packages.
A deployment engineer cannot demonstrate that the package approved in preproduction is the exact one installed in production.
Which risk most directly follows if the team leaves this problem unresolved?
A new production build may incorporate an untested dependency or compiler result. The failure follows from the described gap because artifact promotion ensures deployment stages share tested bytes rather than rebuilding from potentially changing source or packages. Mitigate it by choosing to publish an immutable versioned build artifact once and promote the same artifact through environments.
This risk is associated with GitHub Actions versus Azure Pipelines: Both GitHub Actions and Azure Pipelines can automate CI/CD, but repository integration and governance capabilities determine the appropriate fit. The present scenario instead leaves the immutable pipeline artifact requirement unresolved, which creates this more direct risk: a new production build may incorporate an untested dependency or compiler result.
That consequence is characteristic of Date-based versioning: Calendar-based versions express release timing, but do not automatically convey semantic API compatibility. The present scenario instead leaves the immutable pipeline artifact requirement unresolved, which creates this more direct risk: a new production build may incorporate an untested dependency or compiler result.
That is a credible failure of GitHub Packages access: Package registry operations are authorized separately from ordinary repository read access, and permissions must match publish or consume operations. The present scenario instead leaves the immutable pipeline artifact requirement unresolved, which creates this more direct risk: a new production build may incorporate an untested dependency or compiler result.
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.