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 64

Question 630

During a telemetry quality investigation at fictional Foxglove Aviation, the change record states: A webhook collector loses device-change notifications during transient outages because the sender has no retry or acknowledgement tracking. What underlying technical distinction accounts for this failure?

  1. Model-driven test tools depend on supported device schemas and parser versions; missing parsed data is not proof of missing network function.
  2. HTTP 401 generally signals missing or invalid authentication while 403 indicates access denied to an authenticated request.
  3. Webhooks are asynchronous network events; integrity, delivery acknowledgements and idempotent processing are separate reliability needs.
  4. Streaming telemetry pipelines have collectors, transports, ingestion queues and storage capacity that can fail independently of device subscriptions.

Explanation

Correct Answer

C:

Webhooks are asynchronous network events; integrity, delivery acknowledgements and idempotent processing are separate reliability needs. The corresponding repair is: Authenticate webhook delivery and implement bounded retries with deduplication or delivery-state accounting. Acceptance should show: A simulated receiver outage results in eventual one-time processing or an explicit recorded dead-letter failure without accepting forged requests.

Incorrect Answers

A:

The offered statement is true for this other mechanism: The corresponding repair is: Validate parser and platform compatibility and distinguish collection or parsing errors from actual network-state assertion failures. It does not explain the facts described here, which follow from: The corresponding repair is: Authenticate webhook delivery and implement bounded retries with deduplication or delivery-state accounting.

B:

This principle describes a separate cause: The corresponding repair is: Classify authentication failures and authorization denials separately, then correct token validity or RBAC scope accordingly. The reported condition is governed by: The corresponding repair is: Authenticate webhook delivery and implement bounded retries with deduplication or delivery-state accounting. The two mechanisms should not be conflated.

D:

The offered statement is true for this other mechanism: The corresponding repair is: Introduce bounded buffering, backpressure monitoring and horizontal ingestion capacity with visible gap or loss reporting. It does not explain the facts described here, which follow from: The corresponding repair is: Authenticate webhook delivery and implement bounded retries with deduplication or delivery-state accounting.

Question 631

At fictional Northshore Cloud, an acceptance review of an inventory reconciliation finds: A Meraki inventory collector reads only the first page of network devices and silently reports dozens of branches missing. What should the engineer change first to resolve this specific issue?

  1. Read intended configuration and runtime operational YANG data from their appropriate modeled resources, and write only configurable leaves.
  2. Follow the API's documented cursor or Link continuation until exhaustion, merging results while protecting against repeated cursors.
  3. Import the existing platform object into Terraform state, align its configuration and inspect a non-destructive plan.
  4. Replace non-idempotent shell appends with the platform-aware Ansible network configuration module and explicit desired interface state.

Explanation

Correct Answer

B:

Follow the API's documented cursor or Link continuation until exhaustion, merging results while protecting against repeated cursors. This addresses the problem because many platform APIs paginate large result sets; the first HTTP success response may contain only a subset. Confirm success using: The final inventory count includes all pages and a test endpoint with three pages is retrieved without duplicates. Applied here, the relevant facts are: A Meraki inventory collector reads only the first page of network devices and silently reports dozens of branches missing. The question asks what should the engineer change first to resolve this specific issue.

Incorrect Answers

A:

This alternative is a response to another technical cause: yANG distinguishes configuration intent from read-only operational state; successful config writes do not establish runtime protocol health. The reported case instead depends on: many platform APIs paginate large result sets; the first HTTP success response may contain only a subset. The action that directly addresses it is “Follow the API's documented cursor or Link continuation until exhaustion, merging results while protecting against repeated cursors”.

C:

The offered action targets: terraform configuration alone does not establish ownership of an already-existing platform object; state import binds it to a resource address. The case facts point instead to: many platform APIs paginate large result sets; the first HTTP success response may contain only a subset. Implement “Follow the API's documented cursor or Link continuation until exhaustion, merging results while protecting against repeated cursors” to address that specific condition.

D:

This alternative is a response to another technical cause: ansible's desired-state-aware network modules compare declared configuration with device state before determining required changes. The reported case instead depends on: many platform APIs paginate large result sets; the first HTTP success response may contain only a subset. The action that directly addresses it is “Follow the API's documented cursor or Link continuation until exhaustion, merging results while protecting against repeated cursors”.

Question 632

At fictional Foxglove Aviation, an acceptance review of a certificate renewal rehearsal finds: A network monitoring rollout tags every counter with a constantly changing session token and storage performance collapses. What is the appropriate response to this network automation condition?

  1. Trace correlated event IDs and earliest causal errors through the pipeline instead of treating the final propagated exception as root cause.
  2. Capture structured prechange operational state with pyATS, apply the change, then compare relevant postchange state and assert expected invariants.
  3. Generate and store private keys in restricted secret systems and deploy only to the authorized TLS termination endpoint.
  4. Normalize telemetry dimensions to stable device and interface identifiers and avoid high-cardinality ephemeral labels.

Explanation

Correct Answer

D:

Normalize telemetry dimensions to stable device and interface identifiers and avoid high-cardinality ephemeral labels. This addresses the problem because time-series cardinality grows with combinations of labels; volatile unique IDs defeat aggregation and strain metric storage. Confirm success using: The series count remains bounded while operators can still filter reliably by site, device and interface. Applied here, the relevant facts are: A network monitoring rollout tags every counter with a constantly changing session token and storage performance collapses. The question asks what is the appropriate response to this network automation condition.

Incorrect Answers

A:

The proposed action belongs to the mechanism: downstream error messages can reflect cascaded failures; causality is established by correlating the earlier specific event and affected resource. Here the stated fault follows a different mechanism: time-series cardinality grows with combinations of labels; volatile unique IDs defeat aggregation and strain metric storage. The corrective choice is “Normalize telemetry dimensions to stable device and interface identifiers and avoid high-cardinality ephemeral labels”.

B:

The offered action targets: pyATS can learn and compare device operational state to detect unintended network effects beyond text config diffs. The case facts point instead to: time-series cardinality grows with combinations of labels; volatile unique IDs defeat aggregation and strain metric storage. Implement “Normalize telemetry dimensions to stable device and interface identifiers and avoid high-cardinality ephemeral labels” to address that specific condition.

C:

This alternative is a response to another technical cause: cA-signed certificates are public trust assertions but the associated private key must remain confidential for endpoint authentication. The reported case instead depends on: time-series cardinality grows with combinations of labels; volatile unique IDs defeat aggregation and strain metric storage. The action that directly addresses it is “Normalize telemetry dimensions to stable device and interface identifiers and avoid high-cardinality ephemeral labels”.

Question 633

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. Which result most directly verifies that the proposed correction worked?

  1. A site-context switch triggers a fresh scoped lookup and proposed actions reference currently authorized device identifiers.
  2. Invalid module parameters or destructive unrelated changes fail the predeployment gates and never reach production devices.
  3. A poisoned-source test yields a flagged uncertainty or validated official-source citation instead of an unsafe configuration recommendation.
  4. The validation crosschecks observed interface or VLAN state before accepting a proposed operation and flags missing telemetry as uncertainty.

Explanation

Correct Answer

A:

A site-context switch triggers a fresh scoped lookup and proposed actions reference currently authorized device identifiers. This directly verifies the related correction: Bind current request context to fresh authorized inventory and explicit tenant or device selection before tool calls. It checks the technical distinction: Conversation memory is not authoritative network state; stale context and scope leakage create wrong-target operational risk. 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 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: Subject AI-suggested changes to schema and unit tests, simulated network execution, policy checks and human change approval. The reported case instead depends on: This directly verifies the related correction: Bind current request context to fresh authorized inventory and explicit tenant or device selection before tool calls. The action that directly addresses it is “A site-context switch triggers a fresh scoped lookup and proposed actions reference currently authorized device identifiers”.

C:

The proposed action belongs to the mechanism: This directly verifies the related correction: Ground actionable recommendations in trusted versioned technical references and reject unsupported or conflicting retrieved claims. Here the stated fault follows a different mechanism: This directly verifies the related correction: Bind current request context to fresh authorized inventory and explicit tenant or device selection before tool calls. The corrective choice is “A site-context switch triggers a fresh scoped lookup and proposed actions reference currently authorized device identifiers”.

D:

The offered action targets: This directly verifies the related correction: Check AI conclusions against fresh independent device and controller evidence with explicit freshness and confidence rules. The case facts point instead to: This directly verifies the related correction: Bind current request context to fresh authorized inventory and explicit tenant or device selection before tool calls. Implement “A site-context switch triggers a fresh scoped lookup and proposed actions reference currently authorized device identifiers” to address that specific condition.

Question 634

While investigating an AI recommendation accuracy study for fictional Sunrise Aeronautics, the team reports: A FastMCP tool hides a Cisco API timeout and fabricates an empty device interface list that the agent treats as a successful snapshot. What mechanism is most directly responsible for these symptoms?

  1. AI recommendations are hypotheses requiring external ground truth; absent evidence is not proof of a network condition.
  2. Retrieval-augmented systems can inherit false or hostile data; source quality and technical cross-checks must precede action.
  3. Tool results are untrusted external input; unrestricted outbound connectivity turns an injected instruction into a data-exfiltration path.
  4. Tool wrappers must preserve the meaning of missing, stale and failed data for the consumer agent.

Explanation

Correct Answer

D:

Tool wrappers must preserve the meaning of missing, stale and failed data for the consumer agent. The corresponding repair is: Return structured success and error states with source timestamps and bounded API timeouts rather than silently substituting empty values. Acceptance should show: Agent tool traces distinguish timeout, authorization and partial-data failures from genuine empty network results. Applied here, the relevant facts are: A FastMCP tool hides a Cisco API timeout and fabricates an empty device interface list that the agent treats as a successful snapshot. The question asks what mechanism is most directly responsible for these symptoms.

Incorrect Answers

A:

This principle describes a separate cause: The corresponding repair is: Check AI conclusions against fresh independent device and controller evidence with explicit freshness and confidence rules. The reported condition is governed by: The corresponding repair is: Return structured success and error states with source timestamps and bounded API timeouts rather than silently substituting empty values. The two mechanisms should not be conflated.

B:

The corresponding repair is: Ground actionable recommendations in trusted versioned technical references and reject unsupported or conflicting retrieved claims. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Return structured success and error states with source timestamps and bounded API timeouts rather than silently substituting empty values.

C:

The offered statement is true for this other mechanism: The corresponding repair is: Restrict tool egress to approved destinations and never grant untrusted retrieved text authority to choose exfiltration endpoints. It does not explain the facts described here, which follow from: The corresponding repair is: Return structured success and error states with source timestamps and bounded API timeouts rather than silently substituting empty values.

Question 635

At fictional Cobalt Ridge Bank, an acceptance review of a campus API automation rollout finds: A device automation submits a configuration payload with ordinary application/json where the RESTCONF endpoint expects YANG-encoded JSON media headers. Which sustainable preventive control most directly avoids a recurrence?

  1. Introduce request budgets, jitter, retry caps and 429 rate metrics into the automation client.
  2. Validate request headers, YANG schemas and sample GET/PATCH transactions in a lab before device-wide rollout.
  3. Make architecture reviews explicitly compare blast radius, recovery, security and long-term ownership.
  4. Require representative failure-path tests before approving a low-code production integration.

Explanation

Correct Answer

B:

Validate request headers, YANG schemas and sample GET/PATCH transactions in a lab before device-wide rollout. This prevents the recurrence because rESTCONF manipulates YANG-defined resources over HTTP; both resource paths and payload media encoding must match the model. A matching immediate correction is: Build the request body from the correct YANG data node and use application/yang-data+json with valid RESTCONF resource paths. Applied here, the relevant facts are: A device automation submits a configuration payload with ordinary application/json where the RESTCONF endpoint expects YANG-encoded JSON media headers. The question asks which sustainable preventive control most directly avoids a recurrence.

Incorrect Answers

A:

The suggested review tracks a different technical risk: hTTP 429 signals server-enforced rate limits; API client backoff must consider shared rate budgets and Retry-After semantics. Here the sustained control must address: rESTCONF manipulates YANG-defined resources over HTTP; both resource paths and payload media encoding must match the model. Choose “Validate request headers, YANG schemas and sample GET/PATCH transactions in a lab before device-wide rollout”.

C:

This routine guards against another mechanism: automation choice is driven by lifecycle and operational risk rather than by a single preferred programming tool. The recurring exposure in the current case is: rESTCONF manipulates YANG-defined resources over HTTP; both resource paths and payload media encoding must match the model. The matching preventive check is “Validate request headers, YANG schemas and sample GET/PATCH transactions in a lab before device-wide rollout”.

D:

The suggested review tracks a different technical risk: low-code accelerates common supported integrations but may constrain complex branching and custom transaction semantics. Here the sustained control must address: rESTCONF manipulates YANG-defined resources over HTTP; both resource paths and payload media encoding must match the model. Choose “Validate request headers, YANG schemas and sample GET/PATCH transactions in a lab before device-wide rollout”.

Question 636

During a network policy migration at fictional Cobalt Ridge Bank, the change record states: A team builds a custom Python service for straightforward ticket-triggered device tagging already supported by an approved audited low-code connector. What should the engineer change first to resolve this specific issue?

  1. Address the exact YANG list instance using its fully encoded key values in the RESTCONF data resource path.
  2. Match workflow complexity, vendor connector capability and error recovery needs to low-code or custom application design after a capability pilot.
  3. Follow the API's documented cursor or Link continuation until exhaustion, merging results while protecting against repeated cursors.
  4. Extract a versioned reusable Terraform module with validated input variables for site-specific network parameters.

Explanation

Correct Answer

B:

Match workflow complexity, vendor connector capability and error recovery needs to low-code or custom application design after a capability pilot. This addresses the problem because low-code accelerates common supported integrations but may constrain complex branching and custom transaction semantics. Confirm success using: A proof of concept demonstrates all required conditional paths, audit fields and rollback needs using the selected approach.

Incorrect Answers

A:

The offered action targets: rESTCONF exposes list entries through resource identifiers determined by the keys declared in the YANG model. The case facts point instead to: low-code accelerates common supported integrations but may constrain complex branching and custom transaction semantics. Implement “Match workflow complexity, vendor connector capability and error recovery needs to low-code or custom application design after a capability pilot” to address that specific condition.

C:

The proposed action belongs to the mechanism: many platform APIs paginate large result sets; the first HTTP success response may contain only a subset. Here the stated fault follows a different mechanism: low-code accelerates common supported integrations but may constrain complex branching and custom transaction semantics. The corrective choice is “Match workflow complexity, vendor connector capability and error recovery needs to low-code or custom application design after a capability pilot”.

D:

The offered action targets: terraform modules support repeated declarative resource patterns while typed inputs isolate deployment-specific configuration. The case facts point instead to: low-code accelerates common supported integrations but may constrain complex branching and custom transaction semantics. Implement “Match workflow complexity, vendor connector capability and error recovery needs to low-code or custom application design after a capability pilot” to address that specific condition.

Question 637

At fictional Willowfield Hospitality, during a version-control hotfix, the operator observes: Two developers change the same ACL rule in separate Git branches, and a merge creates conflict markers that would break the automation YAML. Which explanation best matches the actual broken dependency?

  1. A cherry-picked commit does not automatically bring every ancestor or dependent change from its original branch.
  2. Git cherry-pick applies the change introduced by selected commit(s) onto the current branch, creating new history in that branch.
  3. Deployment command success is not the same as verified service success; operational checks must follow state changes.
  4. Git cannot automatically reconcile overlapping divergent edits; a human or reviewed tool must choose the resulting content before merge completion.

Explanation

Correct Answer

D:

Git cannot automatically reconcile overlapping divergent edits; a human or reviewed tool must choose the resulting content before merge completion. The corresponding repair is: Resolve the conflicting lines deliberately against the approved desired network state, run validation, then commit the merged result. Acceptance should show: The merged file has no conflict markers, passes schema tests and retains the intended requirements from both branches. Applied here, the relevant facts are: Two developers change the same ACL rule in separate Git branches, and a merge creates conflict markers that would break the automation YAML. 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: Identify the prerequisite commits and cherry-pick a minimal compatible sequence or adapt the patch for the target baseline. The reported case instead depends on: The corresponding repair is: Resolve the conflicting lines deliberately against the approved desired network state, run validation, then commit the merged result. The action that directly addresses it is “Git cannot automatically reconcile overlapping divergent edits; a human or reviewed tool must choose the resulting content before merge completion”.

B:

The proposed action belongs to the mechanism: The corresponding repair is: Cherry-pick the specific reviewed hotfix commit into the target maintenance branch and test the resulting change. Here the stated fault follows a different mechanism: The corresponding repair is: Resolve the conflicting lines deliberately against the approved desired network state, run validation, then commit the merged result. The corrective choice is “Git cannot automatically reconcile overlapping divergent edits; a human or reviewed tool must choose the resulting content before merge completion”.

C:

The offered action targets: The corresponding repair is: Run objective-based postdeployment checks and fail or roll back the change when observed network behavior contradicts intent. The case facts point instead to: The corresponding repair is: Resolve the conflicting lines deliberately against the approved desired network state, run validation, then commit the merged result. Implement “Git cannot automatically reconcile overlapping divergent edits; a human or reviewed tool must choose the resulting content before merge completion” to address that specific condition.

Question 638

At fictional Violet Ridge Resorts, an acceptance review of a version-control hotfix finds: A pipeline skips a failing YANG schema check because the deploy stage is not explicitly dependent on prevalidation success. Which targeted correction best addresses the network automation failure?

  1. Make deployment depend on successful prevalidation jobs for schema, policy, simulation and approval checks.
  2. Validate leaf type and range constraints and include every mandatory keyed-list attribute in the encoded configuration.
  3. Create a reviewed Git revert commit for the offending change and run the full network automation release tests.
  4. Safely stash or commit unrelated work and check out the intended branch or detached revision in a clean worktree.

Explanation

Correct Answer

A:

Make deployment depend on successful prevalidation jobs for schema, policy, simulation and approval checks. This addresses the problem because prevalidation is a safety boundary before changing network state, separate from checks after a change completes. Confirm success using: A deliberately invalid network change blocks before deploy and a valid change reaches the deployment stage only after passing gates. Applied here, the relevant facts are: A pipeline skips a failing YANG schema check because the deploy stage is not explicitly dependent on prevalidation success. The question asks which targeted correction best addresses the network automation failure.

Incorrect Answers

B:

That action addresses another technical layer: YANG and JSON schema validation check data types, allowable ranges and required keyed-list fields; this is distinct from successfully completing a later deployment or workflow step. It does not correct this specific failure, which is explained by: prevalidation is a safety boundary before changing network state, separate from checks after a change completes. The case-matched action is “Make deployment depend on successful prevalidation jobs for schema, policy, simulation and approval checks”.

C:

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: prevalidation is a safety boundary before changing network state, separate from checks after a change completes. The action that directly addresses it is “Make deployment depend on successful prevalidation jobs for schema, policy, simulation and approval checks”.

D:

The proposed action belongs to the mechanism: git checkout can change branch and working-tree files; uncommitted modifications must be managed to avoid accidental mixing. Here the stated fault follows a different mechanism: prevalidation is a safety boundary before changing network state, separate from checks after a change completes. The corrective choice is “Make deployment depend on successful prevalidation jobs for schema, policy, simulation and approval checks”.

Question 639

At fictional Willowfield Hospitality, during a version-control hotfix, the operator observes: Two developers change the same ACL rule in separate Git branches, and a merge creates conflict markers that would break the automation YAML. Which result most directly verifies that the proposed correction worked?

  1. The merged file has no conflict markers, passes schema tests and retains the intended requirements from both branches.
  2. Lab simulation reproduces the known routing dependency and the candidate change passes normal and failure scenarios.
  3. The payload validates against the YANG schema and the RESTCONF server accepts the exact intended interface resource.
  4. The simulated nodes accept the intended configuration and protocol or connectivity assertions pass under the planned topology.

Explanation

Correct Answer

A:

The merged file has no conflict markers, passes schema tests and retains the intended requirements from both branches. This directly verifies the related correction: Resolve the conflicting lines deliberately against the approved desired network state, run validation, then commit the merged result. It checks the technical distinction: Git cannot automatically reconcile overlapping divergent edits; a human or reviewed tool must choose the resulting content before merge completion. Applied here, the relevant facts are: Two developers change the same ACL rule in separate Git branches, and a merge creates conflict markers that would break the automation YAML. 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: Model the relevant links, routing peers and failure cases in CML rather than only a minimal happy-path device. The reported case instead depends on: This directly verifies the related correction: Resolve the conflicting lines deliberately against the approved desired network state, run validation, then commit the merged result. The action that directly addresses it is “The merged file has no conflict markers, passes schema tests and retains the intended requirements from both branches”.

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: Resolve the conflicting lines deliberately against the approved desired network state, run validation, then commit the merged result. The corrective choice is “The merged file has no conflict markers, passes schema tests and retains the intended requirements from both branches”.

D:

The offered action targets: This directly verifies the related correction: Build a representative topology in Cisco Modeling Labs and execute the automation against simulated devices before live release. The case facts point instead to: This directly verifies the related correction: Resolve the conflicting lines deliberately against the approved desired network state, run validation, then commit the merged result. Implement “The merged file has no conflict markers, passes schema tests and retains the intended requirements from both branches” to address that specific condition.

Question 640

During a remote branch provisioning pilot at fictional Northshore Cloud, the change record states: A vendor-specific CLI string is applied unchanged to several network operating systems and fails on unsupported command syntax. Which explanation best matches the actual broken dependency?

  1. HTTP 429 signals server-enforced rate limits; API client backoff must consider shared rate budgets and Retry-After semantics.
  2. Cross-platform automation benefits from a shared intent model but must translate differences in native device APIs and models.
  3. YANG distinguishes configuration intent from read-only operational state; successful config writes do not establish runtime protocol health.
  4. Terraform modules support repeated declarative resource patterns while typed inputs isolate deployment-specific configuration.

Explanation

Correct Answer

B:

Cross-platform automation benefits from a shared intent model but must translate differences in native device APIs and models. The corresponding repair is: Use inventory capability detection and platform-specific adapters behind a common validated intent model. Acceptance should show: Separate platform acceptance tests reach equivalent approved network intent on each supported operating system without invalid commands. Applied here, the relevant facts are: A vendor-specific CLI string is applied unchanged to several network operating systems and fails on unsupported command syntax. 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: Respect rate-limit response headers and coordinate bounded exponential backoff with jitter under the shared API budget. The reported case instead depends on: The corresponding repair is: Use inventory capability detection and platform-specific adapters behind a common validated intent model. The action that directly addresses it is “Cross-platform automation benefits from a shared intent model but must translate differences in native device APIs and models”.

C:

The offered action targets: The corresponding repair is: Read intended configuration and runtime operational YANG data from their appropriate modeled resources, and write only configurable leaves. The case facts point instead to: The corresponding repair is: Use inventory capability detection and platform-specific adapters behind a common validated intent model. Implement “Cross-platform automation benefits from a shared intent model but must translate differences in native device APIs and models” to address that specific condition.

D:

This alternative is a response to another technical cause: The corresponding repair is: Extract a versioned reusable Terraform module with validated input variables for site-specific network parameters. The reported case instead depends on: The corresponding repair is: Use inventory capability detection and platform-specific adapters behind a common validated intent model. The action that directly addresses it is “Cross-platform automation benefits from a shared intent model but must translate differences in native device APIs and models”.