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 56

Question 550

At fictional Northshore Cloud, an acceptance review of an inventory reconciliation finds: An automation repository embeds router API passwords directly in plain-text host variables committed to a shared source project. Which engineering principle explains the described system behavior?

  1. Terraform modules support repeated declarative resource patterns while typed inputs isolate deployment-specific configuration.
  2. Cross-platform automation benefits from a shared intent model but must translate differences in native device APIs and models.
  3. Automation credentials need confidentiality at rest and in output; inventory convenience does not justify committing secrets.
  4. HTTP 429 signals server-enforced rate limits; API client backoff must consider shared rate budgets and Retry-After semantics.

Explanation

Correct Answer

C:

Automation credentials need confidentiality at rest and in output; inventory convenience does not justify committing secrets. The corresponding repair is: Move credentials into a protected secret store or Ansible Vault and suppress sensitive task output while keeping access narrowly scoped. Acceptance should show: Repository scans and run logs reveal no plain credentials, and the playbook authenticates with approved secret retrieval. Applied here, the relevant facts are: An automation repository embeds router API passwords directly in plain-text host variables committed to a shared source project. The question asks which engineering principle explains the described system behavior.

Incorrect Answers

A:

This principle describes a separate cause: The corresponding repair is: Extract a versioned reusable Terraform module with validated input variables for site-specific network parameters. The reported condition is governed by: The corresponding repair is: Move credentials into a protected secret store or Ansible Vault and suppress sensitive task output while keeping access narrowly scoped. The two mechanisms should not be conflated.

B:

The corresponding repair is: Use inventory capability detection and platform-specific adapters behind a common validated intent model. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Move credentials into a protected secret store or Ansible Vault and suppress sensitive task output while keeping access narrowly scoped.

D:

This principle describes a separate cause: The corresponding repair is: Respect rate-limit response headers and coordinate bounded exponential backoff with jitter under the shared API budget. The reported condition is governed by: The corresponding repair is: Move credentials into a protected secret store or Ansible Vault and suppress sensitive task output while keeping access narrowly scoped. The two mechanisms should not be conflated.

Question 551

During a source-of-truth integration at fictional Violet Ridge Resorts, the change record states: A Terraform workflow change was merged and released, but its logic must be undone without rewriting published branch history. What ongoing engineering assurance should follow the successful fix?

  1. Document backup, ownership and retention policies for every persistent Compose volume.
  2. Prefer revert over reset for shared production branches and validate the inverse patch for dependent changes.
  3. Enforce unique device IDs, provenance and reconciliation reports for source-of-truth integrations.
  4. Set protected branch merge policies and link the squash commit to the reviewed change request.

Explanation

Correct Answer

B:

Prefer revert over reset for shared production branches and validate the inverse patch for dependent changes. This prevents the recurrence because git revert records an inverse patch in new history rather than moving shared branch pointers backward. A matching immediate correction is: Create a reviewed Git revert commit for the offending change and run the full network automation release tests. Applied here, the relevant facts are: A Terraform workflow change was merged and released, but its logic must be undone without rewriting published branch history. The question asks what ongoing engineering assurance should follow the successful fix.

Incorrect Answers

A:

The suggested review tracks a different technical risk: ephemeral container writable layers are distinct from Docker managed or host-mounted persistent volumes. Here the sustained control must address: git revert records an inverse patch in new history rather than moving shared branch pointers backward. Choose “Prefer revert over reset for shared production branches and validate the inverse patch for dependent changes”.

C:

This routine guards against another mechanism: a source of truth provides desired canonical inventory, but consumers must resolve identity correctly and reconcile discrepancies. The recurring exposure in the current case is: git revert records an inverse patch in new history rather than moving shared branch pointers backward. The matching preventive check is “Prefer revert over reset for shared production branches and validate the inverse patch for dependent changes”.

D:

The suggested review tracks a different technical risk: a squash merge consolidates branch changes into a new commit, simplifying target history without preserving each source commit as a separate mainline entry. Here the sustained control must address: git revert records an inverse patch in new history rather than moving shared branch pointers backward. Choose “Prefer revert over reset for shared production branches and validate the inverse patch for dependent changes”.

Question 552

While investigating an AI recommendation accuracy study for fictional Sunrise Aeronautics, the team reports: A read-only network troubleshooting agent runs under a global administrator token and can delete production device configurations. What ongoing engineering assurance should follow the successful fix?

  1. Define permitted AI assistance tiers and required technical approval gates by change risk.
  2. Use retrieval provenance, platform compatibility checks and refusal or escalation criteria for low-confidence device instructions.
  3. Enforce identity binding, tenant-isolated caches and tool-level audit and RBAC tests for MCP services.
  4. Review scopes per AI tool, segregate read/write services and require explicit elevated-change approvals.

Explanation

Correct Answer

D:

Review scopes per AI tool, segregate read/write services and require explicit elevated-change approvals. This prevents the recurrence because the model is not a reliable security principal; tool identities and server-side authorization bound the damage of agent errors. A matching immediate correction is: Issue read-only scoped identity credentials for diagnostic agents and place separate approval boundaries around mutating tools. Applied here, the relevant facts are: A read-only network troubleshooting agent runs under a global administrator token and can delete production device configurations. The question asks what ongoing engineering assurance should follow the successful fix.

Incorrect Answers

A:

That safeguard is relevant to: aI can accelerate low-risk preparation, but speed benefits must be balanced against hallucination, privacy and review obligations. The current failure instead follows from: the model is not a reliable security principal; tool identities and server-side authorization bound the damage of agent errors. Its prevention measure is “Review scopes per AI tool, segregate read/write services and require explicit elevated-change approvals”.

B:

This routine guards against another mechanism: model fluency is not evidence of device capability; uncertain technical recommendations require explicit verification before action. The recurring exposure in the current case is: the model is not a reliable security principal; tool identities and server-side authorization bound the damage of agent errors. The matching preventive check is “Review scopes per AI tool, segregate read/write services and require explicit elevated-change approvals”.

C:

The suggested review tracks a different technical risk: an MCP server is an integration boundary and must not treat model-selected identity strings as verified security credentials. Here the sustained control must address: the model is not a reliable security principal; tool identities and server-side authorization bound the damage of agent errors. Choose “Review scopes per AI tool, segregate read/write services and require explicit elevated-change approvals”.

Question 553

At fictional Seabright Learning, an acceptance review of a reproducible simulation finds: Engineers manually recreate a CML lab from memory each week and results cannot be tied to the version of the test topology. Which targeted correction best addresses the network automation failure?

  1. Identify the prerequisite commits and cherry-pick a minimal compatible sequence or adapt the patch for the target baseline.
  2. Construct JSON using the published YANG container hierarchy, qualified node names and correct value types.
  3. Provision the CML topology reproducibly and wait for all required node readiness conditions before tests begin.
  4. Safely stash or commit unrelated work and check out the intended branch or detached revision in a clean worktree.

Explanation

Correct Answer

C:

Provision the CML topology reproducibly and wait for all required node readiness conditions before tests begin. This addresses the problem because a reproducible simulation needs controlled topology definitions and readiness gates to avoid timing-dependent false failures. Confirm success using: The pipeline consistently reaches a ready test topology and records the versioned lab definition and run results. Applied here, the relevant facts are: Engineers manually recreate a CML lab from memory each week and results cannot be tied to the version of the test topology. The question asks which targeted correction best addresses the network automation failure.

Incorrect Answers

A:

This alternative is a response to another technical cause: a cherry-picked commit does not automatically bring every ancestor or dependent change from its original branch. The reported case instead depends on: a reproducible simulation needs controlled topology definitions and readiness gates to avoid timing-dependent false failures. The action that directly addresses it is “Provision the CML topology reproducibly and wait for all required node readiness conditions before tests begin”.

B:

The proposed action belongs to the mechanism: yANG defines node hierarchy, namespaces, list keys and data types; conforming JSON must preserve that structure. Here the stated fault follows a different mechanism: a reproducible simulation needs controlled topology definitions and readiness gates to avoid timing-dependent false failures. The corrective choice is “Provision the CML topology reproducibly and wait for all required node readiness conditions before tests begin”.

D:

This alternative is a response to another technical cause: git checkout can change branch and working-tree files; uncommitted modifications must be managed to avoid accidental mixing. The reported case instead depends on: a reproducible simulation needs controlled topology definitions and readiness gates to avoid timing-dependent false failures. The action that directly addresses it is “Provision the CML topology reproducibly and wait for all required node readiness conditions before tests begin”.

Question 554

At fictional Cobalt Ridge Bank, an acceptance review of a campus API automation rollout finds: A configuration orchestrator launches a second identical device-change operation when the first asynchronous submission has not yet been acknowledged. What mechanism is most directly responsible for these symptoms?

  1. Terraform modules support repeated declarative resource patterns while typed inputs isolate deployment-specific configuration.
  2. YANG distinguishes configuration intent from read-only operational state; successful config writes do not establish runtime protocol health.
  3. A network transport timeout does not prove server-side failure; blind retries of non-idempotent operations can duplicate effects.
  4. RESTCONF exposes list entries through resource identifiers determined by the keys declared in the YANG model.

Explanation

Correct Answer

C:

A network transport timeout does not prove server-side failure; blind retries of non-idempotent operations can duplicate effects. The corresponding repair is: Before retrying a potentially non-idempotent change, check resulting resource state or use a supported idempotency or operation key. Acceptance should show: An induced response-loss test yields one intended network object or operation and records its final state without duplicate changes. Applied here, the relevant facts are: A configuration orchestrator launches a second identical device-change operation when the first asynchronous submission has not yet been acknowledged. The question asks what mechanism is most directly responsible for these symptoms.

Incorrect Answers

A:

The corresponding repair is: Extract a versioned reusable Terraform module with validated input variables for site-specific network parameters. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Before retrying a potentially non-idempotent change, check resulting resource state or use a supported idempotency or operation key.

B:

The offered statement is true for this other mechanism: The corresponding repair is: Read intended configuration and runtime operational YANG data from their appropriate modeled resources, and write only configurable leaves. It does not explain the facts described here, which follow from: The corresponding repair is: Before retrying a potentially non-idempotent change, check resulting resource state or use a supported idempotency or operation key.

D:

The corresponding repair is: Address the exact YANG list instance using its fully encoded key values in the RESTCONF data resource path. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Before retrying a potentially non-idempotent change, check resulting resource state or use a supported idempotency or operation key.

Question 555

At fictional Sable Valley Power, during a certificate renewal rehearsal, the operator observes: An API integration disables certificate verification after a controller rotates its TLS certificate, exposing management traffic to interception. What underlying technical distinction accounts for this failure?

  1. Latency and retry failures require timing context and per-attempt telemetry; an aggregate success percentage is insufficient.
  2. TLS server validation depends on trusted issuer chains and hostname identity; bypassing verification defeats server authentication.
  3. Hardcoded secrets create persistent exposure and excessive authority; runtime secret retrieval limits both lifetime and access scope.
  4. Time-series cardinality grows with combinations of labels; volatile unique IDs defeat aggregation and strain metric storage.

Explanation

Correct Answer

B:

TLS server validation depends on trusted issuer chains and hostname identity; bypassing verification defeats server authentication. The corresponding repair is: Install the validated issuing CA chain in client trust stores and verify endpoint identity rather than bypassing TLS checks. Acceptance should show: Clients establish a verified TLS session to the expected controller hostname with a valid certificate chain. Applied here, the relevant facts are: An API integration disables certificate verification after a controller rotates its TLS certificate, exposing management traffic to interception. The question asks what underlying technical distinction accounts for this failure.

Incorrect Answers

A:

That test belongs to another control with this basis: The corresponding repair is: Capture per-request endpoint, duration, timeout class, retry attempt and status while preserving sensitive data redaction. In the current case, the governing reason is: The corresponding repair is: Install the validated issuing CA chain in client trust stores and verify endpoint identity rather than bypassing TLS checks. The direct verification is “TLS server validation depends on trusted issuer chains and hostname identity; bypassing verification defeats server authentication”.

C:

The alternative verifies a different condition: The corresponding repair is: Inject short-lived narrowly scoped secrets at runtime from a managed vault and mask them in logs and build artifacts. The current case instead depends on: The corresponding repair is: Install the validated issuing CA chain in client trust stores and verify endpoint identity rather than bypassing TLS checks. Confirm that “TLS server validation depends on trusted issuer chains and hostname identity; bypassing verification defeats server authentication”.

D:

That test belongs to another control with this basis: The corresponding repair is: Normalize telemetry dimensions to stable device and interface identifiers and avoid high-cardinality ephemeral labels. In the current case, the governing reason is: The corresponding repair is: Install the validated issuing CA chain in client trust stores and verify endpoint identity rather than bypassing TLS checks. The direct verification is “TLS server validation depends on trusted issuer chains and hostname identity; bypassing verification defeats server authentication”.

Question 556

During a network policy migration at fictional Cobalt Ridge Bank, the change record states: A switch management project applies new ACLs without taking pre-change configuration backups and cannot restore a known-good policy after errors. What should the engineer change first to resolve this specific issue?

  1. Set compatible provider version constraints and commit the provider dependency lock file for reproducible runs.
  2. Perform per-device reachability and capability prechecks, capture backups, and stop or roll back on failed postchecks.
  3. Build the request body from the correct YANG data node and use application/yang-data+json with valid RESTCONF resource paths.
  4. Refresh managed state and review a generated Terraform plan before applying only the intended network changes.

Explanation

Correct Answer

B:

Perform per-device reachability and capability prechecks, capture backups, and stop or roll back on failed postchecks. This addresses the problem because safe network automation separates preflight, controlled deployment, verification and recovery instead of assuming all endpoints will succeed. Confirm success using: A failed device causes a controlled halt and restoration, and successful devices pass their intended config comparisons. Applied here, the relevant facts are: A switch management project applies new ACLs without taking pre-change configuration backups and cannot restore a known-good policy after errors. 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: terraform providers translate declarative resources into platform API operations; provider version changes can alter behavior. The reported case instead depends on: safe network automation separates preflight, controlled deployment, verification and recovery instead of assuming all endpoints will succeed. The action that directly addresses it is “Perform per-device reachability and capability prechecks, capture backups, and stop or roll back on failed postchecks”.

C:

The offered action targets: rESTCONF manipulates YANG-defined resources over HTTP; both resource paths and payload media encoding must match the model. The case facts point instead to: safe network automation separates preflight, controlled deployment, verification and recovery instead of assuming all endpoints will succeed. Implement “Perform per-device reachability and capability prechecks, capture backups, and stop or roll back on failed postchecks” to address that specific condition.

D:

This alternative is a response to another technical cause: terraform compares configuration, recorded state and provider observations to compute a proposed change set before apply. The reported case instead depends on: safe network automation separates preflight, controlled deployment, verification and recovery instead of assuming all endpoints will succeed. The action that directly addresses it is “Perform per-device reachability and capability prechecks, capture backups, and stop or roll back on failed postchecks”.

Question 557

While investigating a FastMCP security review for fictional Elmcrest Theatre, the team reports: An MCP agent sends malformed VLAN filters and the tool silently falls back to querying every tenant's configuration. What should the engineer change first to resolve this specific issue?

  1. Sanitize inputs and use an approved private or contractually controlled AI service without exposing secrets or regulated network data.
  2. Define typed, validated tool arguments with explicit device allowlists and reject invalid or unauthorized inputs at the server boundary.
  3. Evaluate the agent on a representative labeled test set with difficult, adversarial and negative cases, measuring factual error and unsafe-action rates.
  4. Review generated code provenance, included dependencies and organizational IP policy before accepting it into the repository.

Explanation

Correct Answer

B:

Define typed, validated tool arguments with explicit device allowlists and reject invalid or unauthorized inputs at the server boundary. This addresses the problem because typed MCP tool schemas improve interoperability but server-side validation remains necessary even for a well-formed client call. Confirm success using: Malformed IDs and cross-tenant requests are rejected predictably while approved tool calls return scoped data. Applied here, the relevant facts are: An MCP agent sends malformed VLAN filters and the tool silently falls back to querying every tenant's configuration. The question asks what should the engineer change first to resolve this specific issue.

Incorrect Answers

A:

The proposed action belongs to the mechanism: aI-assisted code tools may process submitted data outside the intended trust boundary, creating privacy and intellectual-property exposure. Here the stated fault follows a different mechanism: typed MCP tool schemas improve interoperability but server-side validation remains necessary even for a well-formed client call. The corrective choice is “Define typed, validated tool arguments with explicit device allowlists and reject invalid or unauthorized inputs at the server boundary”.

C:

This alternative is a response to another technical cause: high aggregate answer accuracy can hide safety-critical errors; validation must measure behavior on representative failure modes. The reported case instead depends on: typed MCP tool schemas improve interoperability but server-side validation remains necessary even for a well-formed client call. The action that directly addresses it is “Define typed, validated tool arguments with explicit device allowlists and reject invalid or unauthorized inputs at the server boundary”.

D:

The proposed action belongs to the mechanism: aI-generated code may embed third-party patterns or dependencies; tool output is not automatically cleared of licensing obligations. Here the stated fault follows a different mechanism: typed MCP tool schemas improve interoperability but server-side validation remains necessary even for a well-formed client call. The corrective choice is “Define typed, validated tool arguments with explicit device allowlists and reject invalid or unauthorized inputs at the server boundary”.

Question 558

At fictional Coastal Meadow Labs, during a production change postcheck, the operator observes: A network rollback reports a timeout, but earlier job logs clearly show the wrong controller endpoint was configured. What is the appropriate response to this network automation condition?

  1. Emit structured events with timestamp, device identity, change ID, severity, stage and outcome to the central log destination.
  2. Write semantic pyATS assertions that permit the approved intended change and reject unrelated regressions.
  3. Trace correlated event IDs and earliest causal errors through the pipeline instead of treating the final propagated exception as root cause.
  4. Generate and store private keys in restricted secret systems and deploy only to the authorized TLS termination endpoint.

Explanation

Correct Answer

C:

Trace correlated event IDs and earliest causal errors through the pipeline instead of treating the final propagated exception as root cause. This addresses the problem because downstream error messages can reflect cascaded failures; causality is established by correlating the earlier specific event and affected resource. Confirm success using: A timeline of stage logs identifies the first failing API or schema operation and confirms the targeted repair removes it. Applied here, the relevant facts are: A network rollback reports a timeout, but earlier job logs clearly show the wrong controller endpoint was configured. The question asks what is the appropriate response to this network automation condition.

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: downstream error messages can reflect cascaded failures; causality is established by correlating the earlier specific event and affected resource. Implement “Trace correlated event IDs and earliest causal errors through the pipeline instead of treating the final propagated exception as root cause” to address that specific condition.

B:

This alternative is a response to another technical cause: postdeployment validation compares expected invariants and intended deltas, not every volatile or purposely changed value. The reported case instead depends on: downstream error messages can reflect cascaded failures; causality is established by correlating the earlier specific event and affected resource. The action that directly addresses it is “Trace correlated event IDs and earliest causal errors through the pipeline instead of treating the final propagated exception as root cause”.

D:

The offered action targets: cA-signed certificates are public trust assertions but the associated private key must remain confidential for endpoint authentication. The case facts point instead to: downstream error messages can reflect cascaded failures; causality is established by correlating the earlier specific event and affected resource. Implement “Trace correlated event IDs and earliest causal errors through the pipeline instead of treating the final propagated exception as root cause” to address that specific condition.

Question 559

During a production change postcheck at fictional Marble Bay Software, the change record states: An internal network automation API checks that users are logged in but does not verify which device groups they are permitted to change. What acceptance check would prove the intended behavior was restored?

  1. An incident query joins all deployment events by change ID and identifies the failed device and pipeline stage.
  2. Clients establish a verified TLS session to the expected controller hostname with a valid certificate chain.
  3. Cross-tenant modification attempts are rejected with a denial and approved users can change only authorized resources.
  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

C:

Cross-tenant modification attempts are rejected with a denial and approved users can change only authorized resources. This directly verifies the related correction: Enforce server-side per-resource authorization using authenticated identity and approved tenant or device scope. It checks the technical distinction: Authentication proves identity but each network resource action requires separate policy-based authorization controls.

Incorrect Answers

A:

This observation would test a different technical dependency: This directly verifies the related correction: Emit structured events with timestamp, device identity, change ID, severity, stage and outcome to the central log destination. The current issue is governed by: This directly verifies the related correction: Enforce server-side per-resource authorization using authenticated identity and approved tenant or device scope. Its decisive check is “Cross-tenant modification attempts are rejected with a denial and approved users can change only authorized resources”.

B:

The alternative verifies a different condition: This directly verifies the related correction: Install the validated issuing CA chain in client trust stores and verify endpoint identity rather than bypassing TLS checks. The current case instead depends on: This directly verifies the related correction: Enforce server-side per-resource authorization using authenticated identity and approved tenant or device scope. Confirm that “Cross-tenant modification attempts are rejected with a denial and approved users can change only authorized resources”.

D:

This observation would test a different technical dependency: This directly verifies the related correction: Authenticate webhook delivery and implement bounded retries with deduplication or delivery-state accounting. The current issue is governed by: This directly verifies the related correction: Enforce server-side per-resource authorization using authenticated identity and approved tenant or device scope. Its decisive check is “Cross-tenant modification attempts are rejected with a denial and approved users can change only authorized resources”.

Question 560

While investigating a network policy migration for fictional Cedarbridge Care Systems, the team reports: A RESTCONF PATCH request sends a bare CLI string as JSON and the IOS XE server rejects it as malformed model data. Which result most directly verifies that the proposed correction worked?

  1. The design review shows the chosen approach fits the resource lifecycle, state ownership and change frequency without redundant infrastructure code.
  2. The device accepts the configured YANG node and a GET of the corresponding resource returns the intended model-shaped value.
  3. The pilot demonstrates appropriate staged changes for configuration updates and simple bounded queries for read-only diagnostics.
  4. The approved plan identifies the precise create, update and destroy operations, and a follow-up plan shows no unintended drift.

Explanation

Correct Answer

B:

The device accepts the configured YANG node and a GET of the corresponding resource returns the intended model-shaped value. 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. It checks the technical distinction: RESTCONF manipulates YANG-defined resources over HTTP; both resource paths and payload media encoding must match the model. Applied here, the relevant facts are: A RESTCONF PATCH request sends a bare CLI string as JSON and the IOS XE server rejects it as malformed model data. 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: Choose a supported declarative IaC framework for persistent desired configuration and targeted scripts for bounded imperative queries or integrations. Here the stated fault follows a different mechanism: 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 corrective choice is “The device accepts the configured YANG node and a GET of the corresponding resource returns the intended model-shaped value”.

C:

This alternative is a response to another technical cause: This directly verifies the related correction: Select the tool and deployment pattern by risk, state persistence, change scope, rollback capability and approval obligations. The reported case instead depends on: 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 action that directly addresses it is “The device accepts the configured YANG node and a GET of the corresponding resource returns the intended model-shaped value”.

D:

The proposed action belongs to the mechanism: This directly verifies the related correction: Refresh managed state and review a generated Terraform plan before applying only the intended network changes. Here the stated fault follows a different mechanism: 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 corrective choice is “The device accepts the configured YANG node and a GET of the corresponding resource returns the intended model-shaped value”.