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 42

Question 410

While investigating a network policy migration for fictional Cedarbridge Care Systems, the team reports: A change board chooses an unreviewed custom deploy script even though the production topology demands staged approval and automated rollback. Which observation would confirm that this exact failure is resolved?

  1. The preflight confirms the required module and revision per target, or marks incompatible devices without making changes.
  2. The approved plan identifies the precise create, update and destroy operations, and a follow-up plan shows no unintended drift.
  3. The pilot demonstrates appropriate staged changes for configuration updates and simple bounded queries for read-only diagnostics.
  4. The device accepts the configured YANG node and a GET of the corresponding resource returns the intended model-shaped value.

Explanation

Correct Answer

C:

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.

Incorrect Answers

A:

The alternative verifies a different condition: This directly verifies the related correction: Discover supported YANG modules or capabilities before using module-specific RESTCONF data paths, and branch for supported models. 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”.

B:

That test belongs to another control with this basis: This directly verifies the related correction: Refresh managed state and review a generated Terraform plan before applying only the intended network changes. In the current case, the governing reason is: This directly verifies the related correction: Select the tool and deployment pattern by risk, state persistence, change scope, rollback capability and approval obligations. The direct verification 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: Build the request body from the correct YANG data node and use application/yang-data+json with valid RESTCONF resource paths. 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 411

At fictional Foxglove Aviation, an acceptance review of a certificate renewal rehearsal finds: A TLS renewal script stores the server private key in world-readable inventory files copied to every automation worker. Which implementation action best meets the observed technical requirement?

  1. Emit structured events with timestamp, device identity, change ID, severity, stage and outcome to the central log destination.
  2. Generate and store private keys in restricted secret systems and deploy only to the authorized TLS termination endpoint.
  3. Write semantic pyATS assertions that permit the approved intended change and reject unrelated regressions.
  4. Capture per-request endpoint, duration, timeout class, retry attempt and status while preserving sensitive data redaction.

Explanation

Correct Answer

B:

Generate and store private keys in restricted secret systems and deploy only to the authorized TLS termination endpoint. This addresses the problem because cA-signed certificates are public trust assertions but the associated private key must remain confidential for endpoint authentication. Confirm success using: Permission checks and artifact scans show no exposed private keys, while the service presents the renewed trusted certificate. Applied here, the relevant facts are: A TLS renewal script stores the server private key in world-readable inventory files copied to every automation worker. The question asks which implementation action best meets the observed technical requirement.

Incorrect Answers

A:

The offered action targets: an effective logging architecture uses consistent machine-readable context and common correlation fields across distributed jobs. The case facts point instead to: cA-signed certificates are public trust assertions but the associated private key must remain confidential for endpoint authentication. Implement “Generate and store private keys in restricted secret systems and deploy only to the authorized TLS termination endpoint” to address that specific condition.

C:

The proposed action belongs to the mechanism: postdeployment validation compares expected invariants and intended deltas, not every volatile or purposely changed value. Here the stated fault follows a different mechanism: cA-signed certificates are public trust assertions but the associated private key must remain confidential for endpoint authentication. The corrective choice is “Generate and store private keys in restricted secret systems and deploy only to the authorized TLS termination endpoint”.

D:

The offered action targets: latency and retry failures require timing context and per-attempt telemetry; an aggregate success percentage is insufficient. The case facts point instead to: cA-signed certificates are public trust assertions but the associated private key must remain confidential for endpoint authentication. Implement “Generate and store private keys in restricted secret systems and deploy only to the authorized TLS termination endpoint” to address that specific condition.

Question 412

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. Which engineering principle explains the described system behavior?

  1. Model-driven APIs are available only for modules and revisions implemented by the device software, not by the client library alone.
  2. HTTP 429 signals server-enforced rate limits; API client backoff must consider shared rate budgets and Retry-After semantics.
  3. Automation choice is driven by lifecycle and operational risk rather than by a single preferred programming tool.
  4. Low-code accelerates common supported integrations but may constrain complex branching and custom transaction semantics.

Explanation

Correct Answer

B:

HTTP 429 signals server-enforced rate limits; API client backoff must consider shared rate budgets and Retry-After semantics. The corresponding repair is: Respect rate-limit response headers and coordinate bounded exponential backoff with jitter under the shared API budget. Acceptance should show: Simulated 429 responses result in delayed, bounded retries and the caller recovers without a retry storm. 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 which engineering principle explains the described system behavior.

Incorrect Answers

A:

This principle describes a separate cause: The corresponding repair is: Discover supported YANG modules or capabilities before using module-specific RESTCONF data paths, and branch for supported models. The reported condition is governed by: The corresponding repair is: Respect rate-limit response headers and coordinate bounded exponential backoff with jitter under the shared API budget. The two mechanisms should not be conflated.

C:

The offered statement is true for this other mechanism: The corresponding repair is: Select the tool and deployment pattern by risk, state persistence, change scope, rollback capability and approval obligations. It does not explain the facts described here, which follow from: The corresponding repair is: Respect rate-limit response headers and coordinate bounded exponential backoff with jitter under the shared API budget.

D:

This principle describes a separate cause: The corresponding repair is: Match workflow complexity, vendor connector capability and error recovery needs to low-code or custom application design after a capability pilot. The reported condition is governed by: The corresponding repair is: Respect rate-limit response headers and coordinate bounded exponential backoff with jitter under the shared API budget. The two mechanisms should not be conflated.

Question 413

During a remote branch provisioning pilot at fictional Northshore Cloud, the change record states: A playbook selects the entire production inventory even though a new OSPF policy is approved only for one distribution switch group. What should the team add to its network automation operating process?

  1. Require inventory-host preview and environment-specific group-variable review in change approval.
  2. Record per-platform model support and gate model-specific deploy steps on device capability checks.
  3. Test 401, refresh failure and 403 paths and enforce tightly scoped secret access and log redaction.
  4. Test provider upgrades in a sandbox and approve lockfile changes independently of ordinary network configuration edits.

Explanation

Correct Answer

A:

Require inventory-host preview and environment-specific group-variable review in change approval. This prevents the recurrence because ansible inventory groups and variable precedence determine which devices and values are targeted by a playbook. A matching immediate correction is: Separate inventory groups and group variables by approved device scope, then constrain the play to the intended group. Applied here, the relevant facts are: A playbook selects the entire production inventory even though a new OSPF policy is approved only for one distribution switch group. The question asks what should the team add to its network automation operating process.

Incorrect Answers

B:

The offered action targets: model-driven APIs are available only for modules and revisions implemented by the device software, not by the client library alone. The case facts point instead to: ansible inventory groups and variable precedence determine which devices and values are targeted by a playbook. Implement “Require inventory-host preview and environment-specific group-variable review in change approval” to address that specific condition.

C:

This alternative is a response to another technical cause: an access-token lifecycle and authorization scope are distinct concerns; repeated reuse of expired or insufficient tokens cannot resolve them. The reported case instead depends on: ansible inventory groups and variable precedence determine which devices and values are targeted by a playbook. The action that directly addresses it is “Require inventory-host preview and environment-specific group-variable review in change approval”.

D:

The proposed action belongs to the mechanism: terraform providers translate declarative resources into platform API operations; provider version changes can alter behavior. Here the stated fault follows a different mechanism: ansible inventory groups and variable precedence determine which devices and values are targeted by a playbook. The corrective choice is “Require inventory-host preview and environment-specific group-variable review in change approval”.

Question 414

At fictional Willowfield Hospitality, during a version-control hotfix, the operator observes: A pipeline declares success when configuration API calls return 200 despite OSPF sessions remaining down on edge routers. What acceptance check would prove the intended behavior was restored?

  1. The target branch builds and tests cleanly with only the required backported changes and no missing dependency references.
  2. The postvalidation stage confirms routes, adjacency and connectivity or triggers the documented recovery workflow with evidence.
  3. The protected target branch contains one reviewed release commit whose diff matches the approved feature changes.
  4. The payload validates against the YANG schema and the RESTCONF server accepts the exact intended interface resource.

Explanation

Correct Answer

B:

The postvalidation stage confirms routes, adjacency and connectivity or triggers the documented recovery workflow with evidence. This directly verifies the related correction: Run objective-based postdeployment checks and fail or roll back the change when observed network behavior contradicts intent. It checks the technical distinction: Deployment command success is not the same as verified service success; operational checks must follow state changes.

Incorrect Answers

A:

That test belongs to another control with this basis: This directly verifies the related correction: Identify the prerequisite commits and cherry-pick a minimal compatible sequence or adapt the patch for the target baseline. In the current case, the governing reason is: This directly verifies the related correction: Run objective-based postdeployment checks and fail or roll back the change when observed network behavior contradicts intent. The direct verification is “The postvalidation stage confirms routes, adjacency and connectivity or triggers the documented recovery workflow with evidence”.

C:

The alternative verifies a different condition: This directly verifies the related correction: Use an approved squash merge to combine reviewed feature changes into one commit while preserving the final content. The current case instead depends on: This directly verifies the related correction: Run objective-based postdeployment checks and fail or roll back the change when observed network behavior contradicts intent. Confirm that “The postvalidation stage confirms routes, adjacency and connectivity or triggers the documented recovery workflow with evidence”.

D:

That test belongs to another control with this basis: This directly verifies the related correction: Construct JSON using the published YANG container hierarchy, qualified node names and correct value types. In the current case, the governing reason is: This directly verifies the related correction: Run objective-based postdeployment checks and fail or roll back the change when observed network behavior contradicts intent. The direct verification is “The postvalidation stage confirms routes, adjacency and connectivity or triggers the documented recovery workflow with evidence”.

Question 415

At fictional Cedarbridge Care Systems, during a campus API automation rollout, the operator observes: A low-code platform is selected for a complex device transaction requiring conditional rollback, but its connector cannot represent required API responses. What acceptance check would prove the intended behavior was restored?

  1. Fresh runners initialize the same reviewed provider build and produce equivalent plans from the same state and configuration.
  2. Invalid IDs are rejected before any outbound request and valid values produce correctly encoded resource targets.
  3. Simulated 429 responses result in delayed, bounded retries and the caller recovers without a retry storm.
  4. A proof of concept demonstrates all required conditional paths, audit fields and rollback needs using the selected approach.

Explanation

Correct Answer

D:

A proof of concept demonstrates all required conditional paths, audit fields and rollback needs using the selected approach. This directly verifies the related correction: Match workflow complexity, vendor connector capability and error recovery needs to low-code or custom application design after a capability pilot. It checks the technical distinction: Low-code accelerates common supported integrations but may constrain complex branching and custom transaction semantics. Applied here, the relevant facts are: A low-code platform is selected for a complex device transaction requiring conditional rollback, but its connector cannot represent required API responses. The question asks what acceptance check would prove the intended behavior was restored.

Incorrect Answers

A:

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: Match workflow complexity, vendor connector capability and error recovery needs to low-code or custom application design after a capability pilot. Its decisive check is “A proof of concept demonstrates all required conditional paths, audit fields and rollback needs using the selected approach”.

B:

The alternative verifies a different condition: This directly verifies the related correction: Validate typed inputs, authorized resource scopes and ranges before constructing API requests, then encode parameters safely. The current case instead depends on: This directly verifies the related correction: Match workflow complexity, vendor connector capability and error recovery needs to low-code or custom application design after a capability pilot. Confirm that “A proof of concept demonstrates all required conditional paths, audit fields and rollback needs using the selected approach”.

C:

That test belongs to another control with this basis: This directly verifies the related correction: Respect rate-limit response headers and coordinate bounded exponential backoff with jitter under the shared API budget. In the current case, the governing reason is: This directly verifies the related correction: Match workflow complexity, vendor connector capability and error recovery needs to low-code or custom application design after a capability pilot. The direct verification is “A proof of concept demonstrates all required conditional paths, audit fields and rollback needs using the selected approach”.

Question 416

During a production change postcheck at fictional Marble Bay Software, the change record states: A gNMI telemetry collector cannot process bursty device messages and drops interface counters without reporting any gaps. Which result most directly verifies that the proposed correction worked?

  1. Correlated traces identify which API operation approaches the timeout threshold and whether backoff reduces the failure rate.
  2. Load tests show telemetry consumers keeping up with target throughput or explicitly signaling lost samples without presenting false continuity.
  3. Centralized logs survive worker replacement and carry timestamps that correlate with device events within the accepted skew.
  4. A simulated receiver outage results in eventual one-time processing or an explicit recorded dead-letter failure without accepting forged requests.

Explanation

Correct Answer

B:

Load tests show telemetry consumers keeping up with target throughput or explicitly signaling lost samples without presenting false continuity. This directly verifies the related correction: Introduce bounded buffering, backpressure monitoring and horizontal ingestion capacity with visible gap or loss reporting. It checks the technical distinction: Streaming telemetry pipelines have collectors, transports, ingestion queues and storage capacity that can fail independently of device subscriptions. Applied here, the relevant facts are: A gNMI telemetry collector cannot process bursty device messages and drops interface counters without reporting any gaps. The question asks which result most directly verifies that the proposed correction worked.

Incorrect Answers

A:

The proposed action belongs to the mechanism: This directly verifies the related correction: Capture per-request endpoint, duration, timeout class, retry attempt and status while preserving sensitive data redaction. Here the stated fault follows a different mechanism: This directly verifies the related correction: Introduce bounded buffering, backpressure monitoring and horizontal ingestion capacity with visible gap or loss reporting. The corrective choice is “Load tests show telemetry consumers keeping up with target throughput or explicitly signaling lost samples without presenting false continuity”.

C:

This alternative is a response to another technical cause: This directly verifies the related correction: Synchronize clocks and ship logs to a durable centralized destination with appropriate secure, reliable transport. The reported case instead depends on: This directly verifies the related correction: Introduce bounded buffering, backpressure monitoring and horizontal ingestion capacity with visible gap or loss reporting. The action that directly addresses it is “Load tests show telemetry consumers keeping up with target throughput or explicitly signaling lost samples without presenting false continuity”.

D:

The proposed action belongs to the mechanism: This directly verifies the related correction: Authenticate webhook delivery and implement bounded retries with deduplication or delivery-state accounting. Here the stated fault follows a different mechanism: This directly verifies the related correction: Introduce bounded buffering, backpressure monitoring and horizontal ingestion capacity with visible gap or loss reporting. The corrective choice is “Load tests show telemetry consumers keeping up with target throughput or explicitly signaling lost samples without presenting false continuity”.

Question 417

At fictional Thornwick Health Trust, during a remote branch provisioning pilot, the operator observes: A temporary inventory update is built as a large Terraform module even though the required API operation is an ephemeral read-only query. Which engineering principle explains the described system behavior?

  1. Ansible handlers are triggered by changed tasks and coalesce notifications, separating configuration checks from disruptive service actions.
  2. Ansible inventory groups and variable precedence determine which devices and values are targeted by a playbook.
  3. Infrastructure as code, low-code workflows and custom software solve different state-lifecycle and integration needs.
  4. Automation credentials need confidentiality at rest and in output; inventory convenience does not justify committing secrets.

Explanation

Correct Answer

C:

Infrastructure as code, low-code workflows and custom software solve different state-lifecycle and integration needs. The corresponding repair is: Choose a supported declarative IaC framework for persistent desired configuration and targeted scripts for bounded imperative queries or integrations. Acceptance should show: The design review shows the chosen approach fits the resource lifecycle, state ownership and change frequency without redundant infrastructure code.

Incorrect Answers

A:

The offered statement is true for this other mechanism: The corresponding repair is: Notify a handler only when the associated configuration task reports a real change, and apply the restart once if necessary. It does not explain the facts described here, which follow from: The corresponding repair is: Choose a supported declarative IaC framework for persistent desired configuration and targeted scripts for bounded imperative queries or integrations.

B:

This principle describes a separate cause: The corresponding repair is: Separate inventory groups and group variables by approved device scope, then constrain the play to the intended group. The reported condition is governed by: The corresponding repair is: Choose a supported declarative IaC framework for persistent desired configuration and targeted scripts for bounded imperative queries or integrations. The two mechanisms should not be conflated.

D:

The offered statement is true for this other mechanism: The corresponding repair is: Move credentials into a protected secret store or Ansible Vault and suppress sensitive task output while keeping access narrowly scoped. It does not explain the facts described here, which follow from: The corresponding repair is: Choose a supported declarative IaC framework for persistent desired configuration and targeted scripts for bounded imperative queries or integrations.

Question 418

During a GitLab deployment pipeline rehearsal at fictional Seabright Learning, the change record states: A merge introduces a network policy defect and a developer tries to revert the merge without identifying its mainline parent. What underlying technical distinction accounts for this failure?

  1. Container start ordering does not inherently guarantee service readiness; health conditions and retries address that gap.
  2. Git checkout can change branch and working-tree files; uncommitted modifications must be managed to avoid accidental mixing.
  3. Git can retrieve individual tracked paths from a commit; selecting file scope avoids broad branch-level rollback.
  4. Reverting a merge requires an explicit mainline perspective so Git knows which parent is the retained baseline.

Explanation

Correct Answer

D:

Reverting a merge requires an explicit mainline perspective so Git knows which parent is the retained baseline. The corresponding repair is: Review the merge graph and select the correct mainline parent when reverting the merge, then validate the resulting tree diff. Acceptance should show: The revert removes only the intended merge effect and network automation tests pass against the protected mainline. Applied here, the relevant facts are: A merge introduces a network policy defect and a developer tries to revert the merge without identifying its mainline parent. The question asks what underlying technical distinction accounts for this failure.

Incorrect Answers

A:

This principle describes a separate cause: The corresponding repair is: Define service dependencies with appropriate health checks and resilient application startup or retry behavior. The reported condition is governed by: The corresponding repair is: Review the merge graph and select the correct mainline parent when reverting the merge, then validate the resulting tree diff. The two mechanisms should not be conflated.

B:

The corresponding repair is: Safely stash or commit unrelated work and check out the intended branch or detached revision in a clean worktree. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Review the merge graph and select the correct mainline parent when reverting the merge, then validate the resulting tree diff.

C:

The offered statement is true for this other mechanism: The corresponding repair is: Restore only the specifically reviewed historical file from the desired revision instead of replacing the whole branch state. It does not explain the facts described here, which follow from: The corresponding repair is: Review the merge graph and select the correct mainline parent when reverting the merge, then validate the resulting tree diff.

Question 419

While investigating an automation service security audit for fictional Coastal Meadow Labs, the team reports: An automation platform relies solely on local volatile logs, and the incident evidence disappears when a deployment container restarts. Which sustainable preventive control most directly avoids a recurrence?

  1. Collect bounded latency histograms, timeout reason labels and retry budgets for critical controller calls.
  2. Monitor clock skew, log forwarding errors and collector persistence capacity.
  3. Add typed error classification and separate authorization and authentication runbooks to API clients.
  4. Require least-privilege service identities, secret scans, expiration alerts and rotation rehearsal.

Explanation

Correct Answer

B:

Monitor clock skew, log forwarding errors and collector persistence capacity. This prevents the recurrence because distributed troubleshooting requires durable transport and consistent time context; ephemeral local logs can be lost or misordered. A matching immediate correction is: Synchronize clocks and ship logs to a durable centralized destination with appropriate secure, reliable transport. Applied here, the relevant facts are: An automation platform relies solely on local volatile logs, and the incident evidence disappears when a deployment container restarts. The question asks which sustainable preventive control most directly avoids a recurrence.

Incorrect Answers

A:

The suggested review tracks a different technical risk: latency and retry failures require timing context and per-attempt telemetry; an aggregate success percentage is insufficient. Here the sustained control must address: distributed troubleshooting requires durable transport and consistent time context; ephemeral local logs can be lost or misordered. Choose “Monitor clock skew, log forwarding errors and collector persistence capacity”.

C:

This routine guards against another mechanism: hTTP 401 generally signals missing or invalid authentication while 403 indicates access denied to an authenticated request. The recurring exposure in the current case is: distributed troubleshooting requires durable transport and consistent time context; ephemeral local logs can be lost or misordered. The matching preventive check is “Monitor clock skew, log forwarding errors and collector persistence capacity”.

D:

The suggested review tracks a different technical risk: hardcoded secrets create persistent exposure and excessive authority; runtime secret retrieval limits both lifetime and access scope. Here the sustained control must address: distributed troubleshooting requires durable transport and consistent time context; ephemeral local logs can be lost or misordered. Choose “Monitor clock skew, log forwarding errors and collector persistence capacity”.

Question 420

At fictional Windward Maritime, during a GitLab deployment pipeline rehearsal, the operator observes: An inventory import creates duplicate switch records because device identity is inferred from mutable display names rather than stable identifiers. Which engineering principle explains the described system behavior?

  1. A source of truth provides desired canonical inventory, but consumers must resolve identity correctly and reconcile discrepancies.
  2. The Git index is the staging area and can be changed independently of the working tree by suitable reset modes.
  3. Git cannot automatically reconcile overlapping divergent edits; a human or reviewed tool must choose the resulting content before merge completion.
  4. Simulation usefulness depends on modeled network dependencies; an incomplete topology cannot validate omitted behaviors.

Explanation

Correct Answer

A:

A source of truth provides desired canonical inventory, but consumers must resolve identity correctly and reconcile discrepancies. The corresponding repair is: Use stable authoritative device identifiers and reconcile observed inventory to the source-of-truth records before deployment. Acceptance should show: The device registry maps one approved identity to each physical endpoint and duplicate or stale mappings are flagged.

Incorrect Answers

B:

This principle describes a separate cause: The corresponding repair is: Unstage the unintended file with an index-only reset or equivalent restore-staged operation, leaving the worktree intact. The reported condition is governed by: The corresponding repair is: Use stable authoritative device identifiers and reconcile observed inventory to the source-of-truth records before deployment. The two mechanisms should not be conflated.

C:

The corresponding repair is: Resolve the conflicting lines deliberately against the approved desired network state, run validation, then commit the merged result. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Use stable authoritative device identifiers and reconcile observed inventory to the source-of-truth records before deployment.

D:

The offered statement is true for this other mechanism: The corresponding repair is: Model the relevant links, routing peers and failure cases in CML rather than only a minimal happy-path device. It does not explain the facts described here, which follow from: The corresponding repair is: Use stable authoritative device identifiers and reconcile observed inventory to the source-of-truth records before deployment.