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.
Which risk most directly follows if the team leaves this problem unresolved?
A compromised human PAT can expose more repositories and persist after an employee changes roles. The failure follows from the described gap because gitHub Apps separate automation identity from a human account and can grant repository-scoped, revocable access. Mitigate it by choosing to use a GitHub App installation with narrowly requested repository permissions and short-lived installation tokens.
That is a credible failure of CodeQL static analysis: Static code analysis can trace risky code patterns and data flow without relying on runtime exploitation to surface the flaw. The present scenario instead leaves the github app scope requirement unresolved, which creates this more direct risk: a compromised human PAT can expose more repositories and persist after an employee changes roles.
This risk is associated with 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 github app scope requirement unresolved, which creates this more direct risk: a compromised human PAT can expose more repositories and persist after an employee changes roles.
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 github app scope requirement unresolved, which creates this more direct risk: a compromised human PAT can expose more repositories and persist after an employee changes roles.
A service must warm and test new App Service code before the production hostname serves it.
Which observation most directly confirms the required DevOps control is effective?
The staged slot passes health checks before swapping to production, and swap reversal remains available. This shows that the control was implemented as intended: deploy to a staging App Service slot, warm the app and swap slots after successful checks. It matters because slots provide a separately deployed target and controlled swap that can reduce disruption when application startup is validated.
Such evidence would establish Environment parameters without secrets, where the relevant control is separate nonsecret environment parameters and inject sensitive values from approved secret stores at deployment.
That result would verify Rollback health criteria, where the relevant control is gate deployment completion on service-health metrics and invoke rollback when agreed thresholds fail.
This observation would support Canary progressive exposure, where the relevant control is use a canary deployment with gradually increased traffic and health-based rollback thresholds.
A build needs a licensed proprietary compiler absent from Microsoft-hosted images and requires durable tool caching.
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.
Such evidence would establish Quality security release gate, where the relevant control is define mandatory test, security and governance gates that block promotion on a failing check.
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.
Such evidence would establish YAML environments approvals, where the relevant control is configure the approval as a protected Azure Pipelines environment check owned outside editable YAML.
A shared deployment token has been reused for years across many production environments and cannot be revoked without downtime.
Which observation most directly confirms the required DevOps control is effective?
An old identity is revoked successfully while each pipeline continues using only its own authorized environment credentials. This shows that the control was implemented as intended: separate credentials by environment and purpose, use short lifetimes or federation, and test rotation and revocation. It matters because scoped identities and rehearsed rotation reduce the security impact and operational disruption of credential compromise.
That result would verify Secret log masking and command safety, where the relevant control is disable unsafe shell tracing and redact credentials while using approved secret variables and non-sensitive diagnostic output.
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.
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.
A compliance integration needs installation-scoped access to selected repositories, but currently runs as an employee identity.
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 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.
Such evidence would establish 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 Workload identity federation, where the relevant control is use a scoped workload identity federation service connection or GitHub OIDC trust instead of storing long-lived cloud secrets.
A production release rebuilds application source independently after staging tests and gets a different dependency resolution.
Which explanation best supports the needed implementation decision?
Artifact promotion ensures deployment stages share tested bytes rather than rebuilding from potentially changing source or packages. The appropriate response is to publish an immutable versioned build artifact once and promote the same artifact through environments. The expected evidence is that artifact checksums and build IDs are identical in staging and production deployment records.
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.
That explanation is about 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.
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.
A regulated enterprise wants predictable public dependencies without granting build agents unrestricted internet access.
What is the most appropriate action for this DevOps team?
Configure an Azure Artifacts feed with upstream sources and retention of approved dependencies. Upstream caching serves previously resolved packages from the controlled feed and reduces direct external registry dependence. A useful check is that a repeat build restores approved dependencies from the feed even when the upstream registry is unavailable.
This would instead address Semantic versioning: SemVer communicates compatibility intent by distinguishing major breaks, compatible additions and backward-compatible fixes.
This is designed for Date-based versioning: Calendar-based versions express release timing, but do not automatically convey semantic API compatibility.
This would instead address Artifacts retention policy: Retention should balance recovery evidence, cost and governance rather than indiscriminately retaining or deleting every build.
Every CI job downloads identical dependencies and recompiles unchanged modules, but cache sharing is currently disabled.
Which observation most directly confirms the required DevOps control is effective?
A repeated unchanged build uses the cache and a changed lockfile forces a valid fresh restore. This shows that the control was implemented as intended: introduce keyed dependency or build caching with OS, version and lockfile inputs and validated invalidation. It matters because correct cache keys improve speed while preventing incompatible or stale cached outputs from silently changing builds.
This observation would support Artifacts retention policy, where the relevant control is apply lifecycle-based retention for artifacts and dependencies consistent with rollback and compliance needs.
Such evidence would establish Quality security release gate, where the relevant control is define mandatory test, security and governance gates that block promotion on a failing check.
This observation would support Migrate classic to YAML, where the relevant control is inventory existing classic tasks and resource checks, migrate logic into versioned YAML and validate parity in parallel.
A production deployment requires release-manager approval even if a contributor edits pipeline YAML after reviewers sign off.
Which risk most directly follows if the team leaves this problem unresolved?
A developer could delete an in-YAML approval step and deploy without independent authorization. The failure follows from the described gap because environment checks are managed on the resource rather than inside the pipeline YAML, resisting bypass by repository edits. Mitigate it by choosing to configure the approval as a protected Azure Pipelines environment check owned outside editable YAML.
That consequence is characteristic 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 yaml environments approvals requirement unresolved, which creates this more direct risk: a developer could delete an in-YAML approval step and deploy without independent authorization.
That is a credible failure of Parallel matrix builds: Independent job combinations can run concurrently, making compatibility tests faster without weakening the requirement that all pass. The present scenario instead leaves the yaml environments approvals requirement unresolved, which creates this more direct risk: a developer could delete an in-YAML approval step and deploy without independent authorization.
This risk is associated with Reusable YAML template: Includes and parameterized templates centralize repeatable pipeline logic while keeping service-specific inputs explicit. The present scenario instead leaves the yaml environments approvals requirement unresolved, which creates this more direct risk: a developer could delete an in-YAML approval step and deploy without independent authorization.
An automation bot holds a user personal access token with access to every organization repository solely to open pull requests.
Which explanation best supports the needed implementation decision?
GitHub Apps separate automation identity from a human account and can grant repository-scoped, revocable access. The appropriate response is to use a GitHub App installation with narrowly requested repository permissions and short-lived installation tokens. The expected evidence is that the bot updates only installed repositories with the approved permissions and cannot read unrelated projects.
That explanation is about Managed identity versus service principal: Azure-managed workload identities authenticate Azure resources without an application-managed secret, with access granted through role assignments.
This describes the mechanism for Container image scanning: Container scanning examines packaged runtime components that may not appear in application source analysis.
This reasoning pertains to Azure DevOps least privilege: Access levels govern available features while permissions and security groups govern allowed actions; both matter for least privilege.
A platform team wants to detect repeated failed pipeline stages from a shared template before individual teams escalate.
Which explanation best supports the needed implementation decision?
CI observability complements application monitoring by identifying delivery-system availability and throughput issues. The appropriate response is to collect Azure Pipelines execution status, queue duration and failure trends and alert on actionable thresholds. The expected evidence is that a pipeline failure spike or queue threshold triggers a routed alert with relevant run details.
That explanation is about Kusto query failed requests: Kusto Query Language supports time-window filtering, aggregation and ranking of collected telemetry for focused diagnosis.
This reasoning pertains to Application Insights request telemetry: Application-level instrumentation exposes call outcomes and dependency contributions that basic host availability cannot explain.
That explanation is about Azure Monitor diagnostic collection: Azure Monitor unifies service-specific telemetry needed to distinguish infrastructure faults from application and container behavior.
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.