100% Latest & Updated Microsoft AZ-400 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 310
A company allows developers to register new internal package names without ownership rules or upstream restrictions. Which risk is directly created by the described failure?
- A dependency confusion attack may insert attacker-controlled code into otherwise reviewed builds.
- Production may contain software not covered by earlier quality and security gates.
- Dependency substitution or disappearance can make releases unreproducible or inject malicious code.
- Consumers may silently adopt breaking updates and experience preventable production failures.
Explanation
Correct Answer
A:A dependency confusion attack may insert attacker-controlled code into otherwise reviewed builds. This is the directly relevant business or security consequence of package feed namespace protection and dependency confusion. Root cause: Dependency-resolution order and namespace trust can allow an external package to impersonate a private library.
Incorrect Answers
B:Production may contain software not covered by earlier quality and security gates. That risk is relevant to pipeline artifact identity and cross-stage immutability, but the specific unresolved condition here concerns package feed namespace protection and dependency confusion and has a different direct consequence.
C:Dependency substitution or disappearance can make releases unreproducible or inject malicious code. That risk is relevant to upstream feed sources and dependency cache integrity, but the specific unresolved condition here concerns package feed namespace protection and dependency confusion and has a different direct consequence.
D:Consumers may silently adopt breaking updates and experience preventable production failures. That risk is relevant to semantic versioning for shared api contract packages, but the specific unresolved condition here concerns package feed namespace protection and dependency confusion and has a different direct consequence.
Question 311
A production rollback fails because Azure Pipelines discarded the validated build artifact after seven days. What change should the DevOps engineer implement FIRST for the stated Azure DevOps requirement?
- Publish artifacts to controlled Azure Artifacts feeds and promote verified package versions through appropriate feed views.
- Publish uniquely identified pipeline artifacts and reuse the same tested run output across all environments.
- Define a consistent CalVer and backport convention with immutable artifacts and explicit environment adoption records.
- Define version-specific artifact retention and immutable references aligned to recovery and evidence requirements.
Explanation
Correct Answer
D:Define version-specific artifact retention and immutable references aligned to recovery and evidence requirements. A rollback plan depends on preserving the actual validated bytes, not just the source commit or pipeline log. Premature artifact deletion can make incident reconstruction and safe restoration impossible.
Incorrect Answers
A:Publish artifacts to controlled Azure Artifacts feeds and promote verified package versions through appropriate feed views. That applies to azure artifacts feed views for verified package promotion, not build artifact retention and reproducible rollback windows.
B:Publish uniquely identified pipeline artifacts and reuse the same tested run output across all environments. That applies to pipeline artifact identity and cross-stage immutability, not build artifact retention and reproducible rollback windows.
C:Define a consistent CalVer and backport convention with immutable artifacts and explicit environment adoption records. That applies to calver version coordination for frequent infrastructure modules, not build artifact retention and reproducible rollback windows.
Question 312
A production rollback fails because Azure Pipelines discarded the validated build artifact after seven days. What check would most directly verify this Microsoft DevOps control?
- Compare deployment manifests and published date versions to validate the exact baseline on representative hosts.
- Test package publishing and download with restricted test workflows and confirm unauthorized repositories cannot pull it.
- Retrieve an archived release and validate its digest, access history, and ability to deploy into a safe test environment.
- Rebuild a recorded release against the approved feed and compare exact package versions and checksums.
Explanation
Correct Answer
C:Retrieve an archived release and validate its digest, access history, and ability to deploy into a safe test environment. A rollback plan depends on preserving the actual validated bytes, not just the source commit or pipeline log.
Incorrect Answers
A:Compare deployment manifests and published date versions to validate the exact baseline on representative hosts. That applies to calver version coordination for frequent infrastructure modules, not build artifact retention and reproducible rollback windows.
B:Test package publishing and download with restricted test workflows and confirm unauthorized repositories cannot pull it. That applies to github packages access using least-privilege workflow credentials, not build artifact retention and reproducible rollback windows.
D:Rebuild a recorded release against the approved feed and compare exact package versions and checksums. That applies to upstream feed sources and dependency cache integrity, not build artifact retention and reproducible rollback windows.
Question 313
A production rollback fails because Azure Pipelines discarded the validated build artifact after seven days. What is the underlying reason the existing approach fails?
- Package registries need separately managed publish and consume permissions, not blanket source repository ownership.
- A rollback plan depends on preserving the actual validated bytes, not just the source commit or pipeline log.
- Feed views and package versions distinguish validated consumable assets from untested build outputs.
- Date-based versions communicate release timing but do not by themselves establish patch lineage or artifact content.
Explanation
Correct Answer
B:A rollback plan depends on preserving the actual validated bytes, not just the source commit or pipeline log. Premature artifact deletion can make incident reconstruction and safe restoration impossible.
Incorrect Answers
A:Package registries need separately managed publish and consume permissions, not blanket source repository ownership. That applies to github packages access using least-privilege workflow credentials, not controlling principle for build artifact retention and reproducible rollback windows.
C:Feed views and package versions distinguish validated consumable assets from untested build outputs. That applies to azure artifacts feed views for verified package promotion, not controlling principle for build artifact retention and reproducible rollback windows.
D:Date-based versions communicate release timing but do not by themselves establish patch lineage or artifact content. That applies to calver version coordination for frequent infrastructure modules, not controlling principle for build artifact retention and reproducible rollback windows.
Question 314
A production rollback fails because Azure Pipelines discarded the validated build artifact after seven days. Which recurring control most directly sustains the required behavior?
- Require changelog review and compatibility validation before publishing shared package versions.
- Review workflow permission scopes and package visibility after repository transfers or organization changes.
- Enforce run-specific artifact references and reject mismatches in release-stage checks.
- Review retention exceptions for supported versions and archive release digests before automatic cleanup.
Explanation
Correct Answer
D:Review retention exceptions for supported versions and archive release digests before automatic cleanup. Premature artifact deletion can make incident reconstruction and safe restoration impossible.
Incorrect Answers
A:Require changelog review and compatibility validation before publishing shared package versions. This helps sustain a control for semantic versioning for shared api contract packages; it does not directly stop recurrence of build artifact retention and reproducible rollback windows described in this case.
B:Review workflow permission scopes and package visibility after repository transfers or organization changes. This helps sustain a control for github packages access using least-privilege workflow credentials; it does not directly stop recurrence of build artifact retention and reproducible rollback windows described in this case.
C:Enforce run-specific artifact references and reject mismatches in release-stage checks.
Question 315
A production rollback fails because Azure Pipelines discarded the validated build artifact after seven days. What is the MOST important consequence if this issue remains unresolved?
- Ambiguous baseline versions make rollback, compliance evidence, and vulnerability remediation unreliable.
- Premature artifact deletion can make incident reconstruction and safe restoration impossible.
- Production may contain software not covered by earlier quality and security gates.
- Dependency substitution or disappearance can make releases unreproducible or inject malicious code.
Explanation
Correct Answer
B:Premature artifact deletion can make incident reconstruction and safe restoration impossible. This is the directly relevant business or security consequence of build artifact retention and reproducible rollback windows. Root cause: A rollback plan depends on preserving the actual validated bytes, not just the source commit or pipeline log.
Incorrect Answers
A:Ambiguous baseline versions make rollback, compliance evidence, and vulnerability remediation unreliable. That risk is relevant to calver version coordination for frequent infrastructure modules, but the specific unresolved condition here concerns build artifact retention and reproducible rollback windows and has a different direct consequence.
C:Production may contain software not covered by earlier quality and security gates. That risk is relevant to pipeline artifact identity and cross-stage immutability, but the specific unresolved condition here concerns build artifact retention and reproducible rollback windows and has a different direct consequence.
D:Dependency substitution or disappearance can make releases unreproducible or inject malicious code. That risk is relevant to upstream feed sources and dependency cache integrity, but the specific unresolved condition here concerns build artifact retention and reproducible rollback windows and has a different direct consequence.
Question 316
A security investigation cannot retrieve the container image that ran during a payment incident from last quarter. What action is MOST appropriate given these constraints?
- Define version-specific artifact retention and immutable references aligned to recovery and evidence requirements.
- Define a consistent CalVer and backport convention with immutable artifacts and explicit environment adoption records.
- Publish uniquely identified pipeline artifacts and reuse the same tested run output across all environments.
- Publish artifacts to controlled Azure Artifacts feeds and promote verified package versions through appropriate feed views.
Explanation
Correct Answer
A:Define version-specific artifact retention and immutable references aligned to recovery and evidence requirements. A rollback plan depends on preserving the actual validated bytes, not just the source commit or pipeline log. Premature artifact deletion can make incident reconstruction and safe restoration impossible.
Incorrect Answers
B:Define a consistent CalVer and backport convention with immutable artifacts and explicit environment adoption records. That applies to calver version coordination for frequent infrastructure modules, not build artifact retention and reproducible rollback windows.
C:Publish uniquely identified pipeline artifacts and reuse the same tested run output across all environments. That applies to pipeline artifact identity and cross-stage immutability, not build artifact retention and reproducible rollback windows.
D:Publish artifacts to controlled Azure Artifacts feeds and promote verified package versions through appropriate feed views. That applies to azure artifacts feed views for verified package promotion, not build artifact retention and reproducible rollback windows.
Question 317
A security investigation cannot retrieve the container image that ran during a payment incident from last quarter. Which test MOST directly confirms the solution?
- Rebuild a recorded release against the approved feed and compare exact package versions and checksums.
- Resolve a package using production feed permissions and verify only the reviewed immutable version is available.
- Retrieve an archived release and validate its digest, access history, and ability to deploy into a safe test environment.
- Compare deployment manifests and published date versions to validate the exact baseline on representative hosts.
Explanation
Correct Answer
C:Retrieve an archived release and validate its digest, access history, and ability to deploy into a safe test environment. A rollback plan depends on preserving the actual validated bytes, not just the source commit or pipeline log.
Incorrect Answers
A:Rebuild a recorded release against the approved feed and compare exact package versions and checksums. That applies to upstream feed sources and dependency cache integrity, not build artifact retention and reproducible rollback windows.
B:Resolve a package using production feed permissions and verify only the reviewed immutable version is available. That applies to azure artifacts feed views for verified package promotion, not build artifact retention and reproducible rollback windows.
D:Compare deployment manifests and published date versions to validate the exact baseline on representative hosts. That applies to calver version coordination for frequent infrastructure modules, not build artifact retention and reproducible rollback windows.
Question 318
A security investigation cannot retrieve the container image that ran during a payment incident from last quarter. What is the underlying reason the existing approach fails?
- Feed views and package versions distinguish validated consumable assets from untested build outputs.
- A rollback plan depends on preserving the actual validated bytes, not just the source commit or pipeline log.
- Date-based versions communicate release timing but do not by themselves establish patch lineage or artifact content.
- Package registries need separately managed publish and consume permissions, not blanket source repository ownership.
Explanation
Correct Answer
B:A rollback plan depends on preserving the actual validated bytes, not just the source commit or pipeline log. Premature artifact deletion can make incident reconstruction and safe restoration impossible.
Incorrect Answers
A:Feed views and package versions distinguish validated consumable assets from untested build outputs. That applies to azure artifacts feed views for verified package promotion, not controlling principle for build artifact retention and reproducible rollback windows.
C:Date-based versions communicate release timing but do not by themselves establish patch lineage or artifact content. That applies to calver version coordination for frequent infrastructure modules, not controlling principle for build artifact retention and reproducible rollback windows.
D:Package registries need separately managed publish and consume permissions, not blanket source repository ownership. That applies to github packages access using least-privilege workflow credentials, not controlling principle for build artifact retention and reproducible rollback windows.
Question 319
A security investigation cannot retrieve the container image that ran during a payment incident from last quarter. Which recurring control most directly sustains the required behavior?
- Review retention exceptions for supported versions and archive release digests before automatic cleanup.
- Enforce run-specific artifact references and reject mismatches in release-stage checks.
- Require changelog review and compatibility validation before publishing shared package versions.
- Review workflow permission scopes and package visibility after repository transfers or organization changes.
Explanation
Correct Answer
A:Review retention exceptions for supported versions and archive release digests before automatic cleanup. Premature artifact deletion can make incident reconstruction and safe restoration impossible.
Incorrect Answers
B:Enforce run-specific artifact references and reject mismatches in release-stage checks.
C:Require changelog review and compatibility validation before publishing shared package versions. This helps sustain a control for semantic versioning for shared api contract packages; it does not directly stop recurrence of build artifact retention and reproducible rollback windows described in this case.
D:Review workflow permission scopes and package visibility after repository transfers or organization changes. This helps sustain a control for github packages access using least-privilege workflow credentials; it does not directly stop recurrence of build artifact retention and reproducible rollback windows described in this case.
Question 320
A security investigation cannot retrieve the container image that ran during a payment incident from last quarter. Choose TWO measures that implement and verify an effective Azure DevOps response to this specific situation. (Choose TWO.)
- Define version-specific artifact retention and immutable references aligned to recovery and evidence requirements.
- Declare build artifact retention and reproducible rollback windows successful solely from a green pipeline status and skip checking its actual control outcome.
- Bypass review and testing for build artifact retention and reproducible rollback windows whenever the release deadline is urgent, applying the change to production immediately.
- Dismiss the known risk for build artifact retention and reproducible rollback windows and keep no evidence or accountable owner after deployment.
- Retrieve an archived release and validate its digest, access history, and ability to deploy into a safe test environment.
Explanation
Correct Answers
A:Define version-specific artifact retention and immutable references aligned to recovery and evidence requirements. A rollback plan depends on preserving the actual validated bytes, not just the source commit or pipeline log. Premature artifact deletion can make incident reconstruction and safe restoration impossible.
E:Retrieve an archived release and validate its digest, access history, and ability to deploy into a safe test environment. A rollback plan depends on preserving the actual validated bytes, not just the source commit or pipeline log.
Incorrect Answers
B:Declare build artifact retention and reproducible rollback windows successful solely from a green pipeline status and skip checking its actual control outcome. It conflicts with the stated operating condition: A rollback plan depends on preserving the actual validated bytes, not just the source commit or pipeline log.
C:Bypass review and testing for build artifact retention and reproducible rollback windows whenever the release deadline is urgent, applying the change to production immediately. It conflicts with the stated operating condition: A rollback plan depends on preserving the actual validated bytes, not just the source commit or pipeline log.
D:Dismiss the known risk for build artifact retention and reproducible rollback windows and keep no evidence or accountable owner after deployment. It conflicts with the stated operating condition: A rollback plan depends on preserving the actual validated bytes, not just the source commit or pipeline log.
Designing and Implementing Microsoft DevOps Solutions (AZ-400) Practice Tests
