McAfee Secure

Cisco 350-901 Bundle

Exam Code: 350-901

Exam Name Designing, Deploying, and Managing Network Automation Systems

Certification Provider: Cisco

Corresponding Certification: DevNet Professional

Cisco 350-901 Bundle $25.00

100% Cisco 350-901 Guaranteed Success With Testking Training Materials

Get Real 350-901 Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

  • Questions & Answers

    350-901 Questions & Answers

    604 Questions & Answers

    The ultimate exam preparation tool, Questions & Answers mirrors the actual 350-901 exam while allowing you to hone and measure every aspect of your test-taking ability.

  • 350-901 Video Course

    350-901 Training Course

    106 Video Lectures

    350-901 Video Course is developed by Cisco Professionals to help you pass the 350-901 exam.

    Description

    This course will improve your knowledge and skills required to pass Designing, Deploying, and Managing Network Automation Systems exam.

Designing, Deploying, and Managing Network Automation Systems (350-901) Practice Tests

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Total Cost: $164.98
Bundle Price: $139.98

Purchase Individually

  • Questions & Answers

    Questions & Answers

    604 Questions

    $124.99
  • 350-901 Video Course

    Training Course

    106 Video Lectures

    $39.99

Cisco 350-901 Practice Test 69

Question 680

At fictional Cobalt Ridge Bank, an acceptance review of a campus API automation rollout finds: A one-time diagnostic query is forced through the same slow infrastructure apply workflow used for persistent configuration changes. What technical evidence should be required before closing this change?

  1. The job records successes and failures by device, retries only supported transient cases, and does not claim full success when any target fails.
  2. The pilot demonstrates appropriate staged changes for configuration updates and simple bounded queries for read-only diagnostics.
  3. Fresh runners initialize the same reviewed provider build and produce equivalent plans from the same state and configuration.
  4. An induced response-loss test yields one intended network object or operation and records its final state without duplicate changes.

Explanation

Correct Answer

B:

The pilot demonstrates appropriate staged changes for configuration updates and simple bounded queries for read-only diagnostics. This directly verifies the related correction: Select the tool and deployment pattern by risk, state persistence, change scope, rollback capability and approval obligations. It checks the technical distinction: Automation choice is driven by lifecycle and operational risk rather than by a single preferred programming tool. Applied here, the relevant facts are: A one-time diagnostic query is forced through the same slow infrastructure apply workflow used for persistent configuration changes. The question asks what technical evidence should be required before closing this change.

Incorrect Answers

A:

The alternative verifies a different condition: This directly verifies the related correction: Handle per-target HTTP, parsing and retryable exceptions and persist a failure summary without misreporting completed targets. The current case instead depends on: This directly verifies the related correction: Select the tool and deployment pattern by risk, state persistence, change scope, rollback capability and approval obligations. Confirm that “The pilot demonstrates appropriate staged changes for configuration updates and simple bounded queries for read-only diagnostics”.

C:

This observation would test a different technical dependency: This directly verifies the related correction: Set compatible provider version constraints and commit the provider dependency lock file for reproducible runs. The current issue is governed by: This directly verifies the related correction: Select the tool and deployment pattern by risk, state persistence, change scope, rollback capability and approval obligations. Its decisive check is “The pilot demonstrates appropriate staged changes for configuration updates and simple bounded queries for read-only diagnostics”.

D:

The alternative verifies a different condition: This directly verifies the related correction: Before retrying a potentially non-idempotent change, check resulting resource state or use a supported idempotency or operation key. The current case instead depends on: This directly verifies the related correction: Select the tool and deployment pattern by risk, state persistence, change scope, rollback capability and approval obligations. Confirm that “The pilot demonstrates appropriate staged changes for configuration updates and simple bounded queries for read-only diagnostics”.

Question 681

At fictional Seabright Learning, an acceptance review of a reproducible simulation finds: A NetBox-style source of truth lists an old hostname and the automation generates ACL changes for the wrong physical device. Which result most directly verifies that the proposed correction worked?

  1. The device registry maps one approved identity to each physical endpoint and duplicate or stale mappings are flagged.
  2. The corrected local branch no longer references the mistaken commit and preserved intended edits are recommitted after validation.
  3. The payload validates against the YANG schema and the RESTCONF server accepts the exact intended interface resource.
  4. A repaired pipeline has a documented root cause and passes the originally failing test without bypassing safety gates.

Explanation

Correct Answer

A:

The device registry maps one approved identity to each physical endpoint and duplicate or stale mappings are flagged. This directly verifies the related correction: Use stable authoritative device identifiers and reconcile observed inventory to the source-of-truth records before deployment. It checks the technical distinction: A source of truth provides desired canonical inventory, but consumers must resolve identity correctly and reconcile discrepancies. Applied here, the relevant facts are: A NetBox-style source of truth lists an old hostname and the automation generates ACL changes for the wrong physical device. The question asks which result most directly verifies that the proposed correction worked.

Incorrect Answers

B:

This alternative is a response to another technical cause: This directly verifies the related correction: Use an appropriate local Git reset to move the branch pointer and rebuild the unpublished commit while protecting wanted working changes. The reported case instead depends on: This directly verifies the related correction: Use stable authoritative device identifiers and reconcile observed inventory to the source-of-truth records before deployment. The action that directly addresses it is “The device registry maps one approved identity to each physical endpoint and duplicate or stale mappings are flagged”.

C:

The proposed action belongs to the mechanism: This directly verifies the related correction: Construct JSON using the published YANG container hierarchy, qualified node names and correct value types. Here the stated fault follows a different mechanism: This directly verifies the related correction: Use stable authoritative device identifiers and reconcile observed inventory to the source-of-truth records before deployment. The corrective choice is “The device registry maps one approved identity to each physical endpoint and duplicate or stale mappings are flagged”.

D:

The offered action targets: This directly verifies the related correction: Inspect the failed job logs and classify whether build, dependency, test or environment validation failed before making a targeted fix. The case facts point instead to: This directly verifies the related correction: Use stable authoritative device identifiers and reconcile observed inventory to the source-of-truth records before deployment. Implement “The device registry maps one approved identity to each physical endpoint and duplicate or stale mappings are flagged” to address that specific condition.

Question 682

During a conversational network agent pilot at fictional Westlake Biomedicine, the change record states: A network assistant relies on a week-old device inventory from chat history and recommends changing a retired switch. What ongoing engineering assurance should follow the successful fix?

  1. Use egress firewall allowlists, response sanitization, credential isolation and canary tests against tool-output injection.
  2. Expire cached network context, confirm target scope and revalidate resources before agent actions.
  3. Enforce identity binding, tenant-isolated caches and tool-level audit and RBAC tests for MCP services.
  4. Test parameter bounds, tenant authorization and injection input against each FastMCP exposed operation.

Explanation

Correct Answer

B:

Expire cached network context, confirm target scope and revalidate resources before agent actions. This prevents the recurrence because conversation memory is not authoritative network state; stale context and scope leakage create wrong-target operational risk. A matching immediate correction is: Bind current request context to fresh authorized inventory and explicit tenant or device selection before tool calls. Applied here, the relevant facts are: A network assistant relies on a week-old device inventory from chat history and recommends changing a retired switch. The question asks what ongoing engineering assurance should follow the successful fix.

Incorrect Answers

A:

This routine guards against another mechanism: tool results are untrusted external input; unrestricted outbound connectivity turns an injected instruction into a data-exfiltration path. The recurring exposure in the current case is: conversation memory is not authoritative network state; stale context and scope leakage create wrong-target operational risk. The matching preventive check is “Expire cached network context, confirm target scope and revalidate resources before agent actions”.

C:

That safeguard is relevant to: an MCP server is an integration boundary and must not treat model-selected identity strings as verified security credentials. The current failure instead follows from: conversation memory is not authoritative network state; stale context and scope leakage create wrong-target operational risk. Its prevention measure is “Expire cached network context, confirm target scope and revalidate resources before agent actions”.

D:

This routine guards against another mechanism: typed MCP tool schemas improve interoperability but server-side validation remains necessary even for a well-formed client call. The recurring exposure in the current case is: conversation memory is not authoritative network state; stale context and scope leakage create wrong-target operational risk. The matching preventive check is “Expire cached network context, confirm target scope and revalidate resources before agent actions”.

Question 683

At fictional Cedarbridge Care Systems, during a campus API automation rollout, the operator observes: A Meraki dashboard integration treats HTTP 429 as permanent failure and immediately resubmits hundreds of calls in a tight loop. What should the team add to its network automation operating process?

  1. Include before-and-after model diff checks and explicit method selection in RESTCONF automation reviews.
  2. Require inventory-host preview and environment-specific group-variable review in change approval.
  3. Introduce request budgets, jitter, retry caps and 429 rate metrics into the automation client.
  4. Exercise representative 4xx, 5xx, timeout and malformed-payload cases in contract tests before scheduling batches.

Explanation

Correct Answer

C:

Introduce request budgets, jitter, retry caps and 429 rate metrics into the automation client. This prevents the recurrence because hTTP 429 signals server-enforced rate limits; API client backoff must consider shared rate budgets and Retry-After semantics. A matching immediate correction is: Respect rate-limit response headers and coordinate bounded exponential backoff with jitter under the shared API budget. Applied here, the relevant facts are: A Meraki dashboard integration treats HTTP 429 as permanent failure and immediately resubmits hundreds of calls in a tight loop. The question asks what should the team add to its network automation operating process.

Incorrect Answers

A:

The proposed action belongs to the mechanism: hTTP PUT represents replacement semantics for a targeted RESTCONF resource, whereas PATCH supports partial edits under the applicable media type. Here the stated fault follows a different mechanism: hTTP 429 signals server-enforced rate limits; API client backoff must consider shared rate budgets and Retry-After semantics. The corrective choice is “Introduce request budgets, jitter, retry caps and 429 rate metrics into the automation client”.

B:

The offered action targets: ansible inventory groups and variable precedence determine which devices and values are targeted by a playbook. The case facts point instead to: hTTP 429 signals server-enforced rate limits; API client backoff must consider shared rate budgets and Retry-After semantics. Implement “Introduce request budgets, jitter, retry caps and 429 rate metrics into the automation client” to address that specific condition.

D:

The proposed action belongs to the mechanism: robust batch automation isolates errors at the per-resource boundary and retains auditable partial outcomes. Here the stated fault follows a different mechanism: hTTP 429 signals server-enforced rate limits; API client backoff must consider shared rate budgets and Retry-After semantics. The corrective choice is “Introduce request budgets, jitter, retry caps and 429 rate metrics into the automation client”.

Question 684

At fictional Marble Bay Software, an acceptance review of an automation service security audit finds: A change adds a planned network prefix but a naive pyATS diff declares failure solely because the route table is no longer byte-identical. Which result most directly verifies that the proposed correction worked?

  1. Centralized logs survive worker replacement and carry timestamps that correlate with device events within the accepted skew.
  2. Permission checks and artifact scans show no exposed private keys, while the service presents the renewed trusted certificate.
  3. Malicious metacharacter input is rejected and legitimate interface updates produce only approved structured API calls.
  4. The postchange test passes for authorized new routes or neighbors but fails for loss of protected existing reachability.

Explanation

Correct Answer

D:

The postchange test passes for authorized new routes or neighbors but fails for loss of protected existing reachability. This directly verifies the related correction: Write semantic pyATS assertions that permit the approved intended change and reject unrelated regressions. It checks the technical distinction: Postdeployment validation compares expected invariants and intended deltas, not every volatile or purposely changed value. Applied here, the relevant facts are: A change adds a planned network prefix but a naive pyATS diff declares failure solely because the route table is no longer byte-identical. The question asks which result most directly verifies that the proposed correction worked.

Incorrect Answers

A:

The offered action targets: This directly verifies the related correction: Synchronize clocks and ship logs to a durable centralized destination with appropriate secure, reliable transport. The case facts point instead to: the route table is no longer byte-identical. Implement “The postchange test passes for authorized new routes or neighbors but fails for loss of protected existing reachability” to address that specific condition.

B:

This alternative is a response to another technical cause: This directly verifies the related correction: Generate and store private keys in restricted secret systems and deploy only to the authorized TLS termination endpoint. The reported case instead depends on: the route table is no longer byte-identical. The action that directly addresses it is “The postchange test passes for authorized new routes or neighbors but fails for loss of protected existing reachability”.

C:

The proposed action belongs to the mechanism: This directly verifies the related correction: Use typed input schema validation, approved resource allowlists and safe library argument interfaces rather than shell concatenation. Here the stated fault follows a different mechanism: the route table is no longer byte-identical. The corrective choice is “The postchange test passes for authorized new routes or neighbors but fails for loss of protected existing reachability”.

Question 685

While investigating a source-of-truth integration for fictional Willowfield Hospitality, the team reports: A critical ACL validation fix is needed in a stable automation release, but merging the full development branch would introduce unfinished feature code. Which explanation best matches the actual broken dependency?

  1. A reliable source-of-truth workflow separates approved intent from observed device state and defines how changes flow between them.
  2. Prevalidation is a safety boundary before changing network state, separate from checks after a change completes.
  3. Git cherry-pick applies the change introduced by selected commit(s) onto the current branch, creating new history in that branch.
  4. CI runners start from controlled environments; undeclared local dependencies cannot be assumed present remotely.

Explanation

Correct Answer

C:

Git cherry-pick applies the change introduced by selected commit(s) onto the current branch, creating new history in that branch. The corresponding repair is: Cherry-pick the specific reviewed hotfix commit into the target maintenance branch and test the resulting change. Acceptance should show: The maintenance branch contains the intended patch without unrelated feature commits and passes the target release tests. Applied here, the relevant facts are: A critical ACL validation fix is needed in a stable automation release, but merging the full development branch would introduce unfinished feature code. The question asks which explanation best matches the actual broken dependency.

Incorrect Answers

A:

This alternative is a response to another technical cause: The corresponding repair is: Read authorized desired state from the designated source of truth and reconcile observed drift through an approved change path. The reported case instead depends on: The corresponding repair is: Cherry-pick the specific reviewed hotfix commit into the target maintenance branch and test the resulting change. The action that directly addresses it is “Git cherry-pick applies the change introduced by selected commit(s) onto the current branch, creating new history in that branch”.

B:

The proposed action belongs to the mechanism: The corresponding repair is: Make deployment depend on successful prevalidation jobs for schema, policy, simulation and approval checks. Here the stated fault follows a different mechanism: The corresponding repair is: Cherry-pick the specific reviewed hotfix commit into the target maintenance branch and test the resulting change. The corrective choice is “Git cherry-pick applies the change introduced by selected commit(s) onto the current branch, creating new history in that branch”.

D:

This alternative is a response to another technical cause: The corresponding repair is: Declare and lock the required dependency in the build manifest and install it in the pipeline's reproducible environment. The reported case instead depends on: The corresponding repair is: Cherry-pick the specific reviewed hotfix commit into the target maintenance branch and test the resulting change. The action that directly addresses it is “Git cherry-pick applies the change introduced by selected commit(s) onto the current branch, creating new history in that branch”.

Question 686

At fictional Northshore Cloud, an acceptance review of an inventory reconciliation finds: Multiple campus Terraform stacks copy the same VLAN resource block with hardcoded IDs, producing mismatched values after one regional update. Which sustainable preventive control most directly avoids a recurrence?

  1. Exercise representative 4xx, 5xx, timeout and malformed-payload cases in contract tests before scheduling batches.
  2. Design resource-state reconciliation and safe retry policies for all create and job-submission requests.
  3. Review handler notification conditions and test unchanged and changed execution paths before production scheduling.
  4. Publish tested module releases, enforce variable validation, and review module version upgrades across environments.

Explanation

Correct Answer

D:

Publish tested module releases, enforce variable validation, and review module version upgrades across environments. This prevents the recurrence because terraform modules support repeated declarative resource patterns while typed inputs isolate deployment-specific configuration. A matching immediate correction is: Extract a versioned reusable Terraform module with validated input variables for site-specific network parameters. Applied here, the relevant facts are: Multiple campus Terraform stacks copy the same VLAN resource block with hardcoded IDs, producing mismatched values after one regional update. The question asks which sustainable preventive control most directly avoids a recurrence.

Incorrect Answers

A:

The suggested review tracks a different technical risk: robust batch automation isolates errors at the per-resource boundary and retains auditable partial outcomes. Here the sustained control must address: terraform modules support repeated declarative resource patterns while typed inputs isolate deployment-specific configuration. Choose “Publish tested module releases, enforce variable validation, and review module version upgrades across environments”.

B:

That safeguard is relevant to: a network transport timeout does not prove server-side failure; blind retries of non-idempotent operations can duplicate effects. The current failure instead follows from: terraform modules support repeated declarative resource patterns while typed inputs isolate deployment-specific configuration. Its prevention measure is “Publish tested module releases, enforce variable validation, and review module version upgrades across environments”.

C:

This routine guards against another mechanism: ansible handlers are triggered by changed tasks and coalesce notifications, separating configuration checks from disruptive service actions. The recurring exposure in the current case is: terraform modules support repeated declarative resource patterns while typed inputs isolate deployment-specific configuration. The matching preventive check is “Publish tested module releases, enforce variable validation, and review module version upgrades across environments”.

Question 687

During a telemetry quality investigation at fictional Foxglove Aviation, the change record states: A network observability service needs timely OSPF neighbor state, but its collector samples an infrequent batch inventory export. Which explanation best matches the actual broken dependency?

  1. Model-driven telemetry publishes structured device state using subscribed paths and collection modes rather than relying only on slow polling.
  2. Downstream error messages can reflect cascaded failures; causality is established by correlating the earlier specific event and affected resource.
  3. Modern TLS clients validate the connection name against certificate subject alternative names, not merely that a CA issued the cert.
  4. pyATS can learn and compare device operational state to detect unintended network effects beyond text config diffs.

Explanation

Correct Answer

A:

Model-driven telemetry publishes structured device state using subscribed paths and collection modes rather than relying only on slow polling. The corresponding repair is: Configure suitable model-driven telemetry subscriptions for the relevant paths at a collection interval appropriate to the signal. Acceptance should show: The collector receives timestamped updates for the requested YANG paths and captures brief changes within its approved delay budget. Applied here, the relevant facts are: A network observability service needs timely OSPF neighbor state, but its collector samples an infrequent batch inventory export. The question asks which explanation best matches the actual broken dependency.

Incorrect Answers

B:

This alternative is a response to another technical cause: The corresponding repair is: Trace correlated event IDs and earliest causal errors through the pipeline instead of treating the final propagated exception as root cause. The reported case instead depends on: The corresponding repair is: Configure suitable model-driven telemetry subscriptions for the relevant paths at a collection interval appropriate to the signal. The action that directly addresses it is “Model-driven telemetry publishes structured device state using subscribed paths and collection modes rather than relying only on slow polling”.

C:

The proposed action belongs to the mechanism: The corresponding repair is: Use an approved DNS endpoint covered by the certificate SAN or reissue a certificate with correct service identities. Here the stated fault follows a different mechanism: The corresponding repair is: Configure suitable model-driven telemetry subscriptions for the relevant paths at a collection interval appropriate to the signal. The corrective choice is “Model-driven telemetry publishes structured device state using subscribed paths and collection modes rather than relying only on slow polling”.

D:

The offered action targets: The corresponding repair is: Capture structured prechange operational state with pyATS, apply the change, then compare relevant postchange state and assert expected invariants. The case facts point instead to: The corresponding repair is: Configure suitable model-driven telemetry subscriptions for the relevant paths at a collection interval appropriate to the signal. Implement “Model-driven telemetry publishes structured device state using subscribed paths and collection modes rather than relying only on slow polling” to address that specific condition.

Question 688

At fictional Cedarbridge Care Systems, during a campus API automation rollout, the operator observes: A VLAN deployment continues after half the switches fail connectivity tests, creating an incomplete campus rollout. Which result most directly verifies that the proposed correction worked?

  1. The second apply waits or fails safely on an active lock, and state reflects one consistent resource graph after the approved deployment.
  2. A failed device causes a controlled halt and restoration, and successful devices pass their intended config comparisons.
  3. A GET of the specific keyed list entry shows only the authorized VLAN or interface changed, with sibling entries intact.
  4. Separate platform acceptance tests reach equivalent approved network intent on each supported operating system without invalid commands.

Explanation

Correct Answer

B:

A failed device causes a controlled halt and restoration, and successful devices pass their intended config comparisons. This directly verifies the related correction: Perform per-device reachability and capability prechecks, capture backups, and stop or roll back on failed postchecks. It checks the technical distinction: Safe network automation separates preflight, controlled deployment, verification and recovery instead of assuming all endpoints will succeed. Applied here, the relevant facts are: A VLAN deployment continues after half the switches fail connectivity tests, creating an incomplete campus rollout. The question asks which result most directly verifies that the proposed correction worked.

Incorrect Answers

A:

This alternative is a response to another technical cause: This directly verifies the related correction: Configure a shared protected Terraform state backend with supported locking and serialize competing applies against the same state. The reported case instead depends on: This directly verifies the related correction: Perform per-device reachability and capability prechecks, capture backups, and stop or roll back on failed postchecks. The action that directly addresses it is “A failed device causes a controlled halt and restoration, and successful devices pass their intended config comparisons”.

C:

The offered action targets: This directly verifies the related correction: Address the exact YANG list instance using its fully encoded key values in the RESTCONF data resource path. The case facts point instead to: This directly verifies the related correction: Perform per-device reachability and capability prechecks, capture backups, and stop or roll back on failed postchecks. Implement “A failed device causes a controlled halt and restoration, and successful devices pass their intended config comparisons” to address that specific condition.

D:

This alternative is a response to another technical cause: This directly verifies the related correction: Use inventory capability detection and platform-specific adapters behind a common validated intent model. The reported case instead depends on: This directly verifies the related correction: Perform per-device reachability and capability prechecks, capture backups, and stop or roll back on failed postchecks. The action that directly addresses it is “A failed device causes a controlled halt and restoration, and successful devices pass their intended config comparisons”.

Question 689

While investigating a source-of-truth integration for fictional Willowfield Hospitality, the team reports: A lab test succeeds only because the CML topology omits an actual branch transit link where routing loops occur. Which implementation action best meets the observed technical requirement?

  1. Resolve the conflicting lines deliberately against the approved desired network state, run validation, then commit the merged result.
  2. Model the relevant links, routing peers and failure cases in CML rather than only a minimal happy-path device.
  3. Cherry-pick the specific reviewed hotfix commit into the target maintenance branch and test the resulting change.
  4. Make deployment depend on successful prevalidation jobs for schema, policy, simulation and approval checks.

Explanation

Correct Answer

B:

Model the relevant links, routing peers and failure cases in CML rather than only a minimal happy-path device. This addresses the problem because simulation usefulness depends on modeled network dependencies; an incomplete topology cannot validate omitted behaviors. Confirm success using: Lab simulation reproduces the known routing dependency and the candidate change passes normal and failure scenarios. Applied here, the relevant facts are: A lab test succeeds only because the CML topology omits an actual branch transit link where routing loops occur. The question asks which implementation action best meets the observed technical requirement.

Incorrect Answers

A:

The proposed action belongs to the mechanism: git cannot automatically reconcile overlapping divergent edits; a human or reviewed tool must choose the resulting content before merge completion. Here the stated fault follows a different mechanism: simulation usefulness depends on modeled network dependencies; an incomplete topology cannot validate omitted behaviors. The corrective choice is “Model the relevant links, routing peers and failure cases in CML rather than only a minimal happy-path device”.

C:

This alternative is a response to another technical cause: git cherry-pick applies the change introduced by selected commit(s) onto the current branch, creating new history in that branch. The reported case instead depends on: simulation usefulness depends on modeled network dependencies; an incomplete topology cannot validate omitted behaviors. The action that directly addresses it is “Model the relevant links, routing peers and failure cases in CML rather than only a minimal happy-path device”.

D:

The proposed action belongs to the mechanism: prevalidation is a safety boundary before changing network state, separate from checks after a change completes. Here the stated fault follows a different mechanism: simulation usefulness depends on modeled network dependencies; an incomplete topology cannot validate omitted behaviors. The corrective choice is “Model the relevant links, routing peers and failure cases in CML rather than only a minimal happy-path device”.

Question 690

While investigating a reproducible simulation for fictional Windward Maritime, the team reports: A local source-of-truth lab stores application data only in a container writable layer and loses all records after container replacement. Which implementation action best meets the observed technical requirement?

  1. Mount an appropriate persistent named volume or approved bind mount for data that must survive container recreation.
  2. Create a reviewed Git revert commit for the offending change and run the full network automation release tests.
  3. Cherry-pick the specific reviewed hotfix commit into the target maintenance branch and test the resulting change.
  4. Safely stash or commit unrelated work and check out the intended branch or detached revision in a clean worktree.

Explanation

Correct Answer

A:

Mount an appropriate persistent named volume or approved bind mount for data that must survive container recreation. This addresses the problem because ephemeral container writable layers are distinct from Docker managed or host-mounted persistent volumes. Confirm success using: A recreated container reads the expected persistent audit or inventory records from the configured volume. Applied here, the relevant facts are: A local source-of-truth lab stores application data only in a container writable layer and loses all records after container replacement. The question asks which implementation action best meets the observed technical requirement.

Incorrect Answers

B:

This alternative is a response to another technical cause: git revert records an inverse patch in new history rather than moving shared branch pointers backward. The reported case instead depends on: ephemeral container writable layers are distinct from Docker managed or host-mounted persistent volumes. The action that directly addresses it is “Mount an appropriate persistent named volume or approved bind mount for data that must survive container recreation”.

C:

The proposed action belongs to the mechanism: git cherry-pick applies the change introduced by selected commit(s) onto the current branch, creating new history in that branch. Here the stated fault follows a different mechanism: ephemeral container writable layers are distinct from Docker managed or host-mounted persistent volumes. The corrective choice is “Mount an appropriate persistent named volume or approved bind mount for data that must survive container recreation”.

D:

The offered action targets: git checkout can change branch and working-tree files; uncommitted modifications must be managed to avoid accidental mixing. The case facts point instead to: ephemeral container writable layers are distinct from Docker managed or host-mounted persistent volumes. Implement “Mount an appropriate persistent named volume or approved bind mount for data that must survive container recreation” to address that specific condition.