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 7

Question 60

While investigating a network policy migration for fictional Cedarbridge Care Systems, the team reports: A playbook restarts network services after every configuration check even when the device configuration is unchanged. Which engineering principle explains the described system behavior?

  1. RESTCONF manipulates YANG-defined resources over HTTP; both resource paths and payload media encoding must match the model.
  2. Model-driven APIs are available only for modules and revisions implemented by the device software, not by the client library alone.
  3. Ansible handlers are triggered by changed tasks and coalesce notifications, separating configuration checks from disruptive service actions.
  4. Infrastructure as code, low-code workflows and custom software solve different state-lifecycle and integration needs.

Explanation

Correct Answer

C:

Ansible handlers are triggered by changed tasks and coalesce notifications, separating configuration checks from disruptive service actions. The corresponding repair is: Notify a handler only when the associated configuration task reports a real change, and apply the restart once if necessary. Acceptance should show: Unchanged reruns cause no service restart, while an approved changed configuration invokes its handler exactly once.

Incorrect Answers

A:

The offered statement is true for this other mechanism: The corresponding repair is: Build the request body from the correct YANG data node and use application/yang-data+json with valid RESTCONF resource paths. It does not explain the facts described here, which follow from: The corresponding repair is: Notify a handler only when the associated configuration task reports a real change, and apply the restart once if necessary.

B:

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: Notify a handler only when the associated configuration task reports a real change, and apply the restart once if necessary. The two mechanisms should not be conflated.

D:

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

Question 61

While investigating a source-of-truth integration for fictional Willowfield Hospitality, the team reports: A Terraform apply starts before policy lint and network simulation checks, allowing an invalid ACL to reach live devices. Which observation would confirm that this exact failure is resolved?

  1. The protected target branch contains one reviewed release commit whose diff matches the approved feature changes.
  2. Lab simulation reproduces the known routing dependency and the candidate change passes normal and failure scenarios.
  3. A repaired pipeline has a documented root cause and passes the originally failing test without bypassing safety gates.
  4. A deliberately invalid network change blocks before deploy and a valid change reaches the deployment stage only after passing gates.

Explanation

Correct Answer

D:

A deliberately invalid network change blocks before deploy and a valid change reaches the deployment stage only after passing gates. This directly verifies the related correction: Make deployment depend on successful prevalidation jobs for schema, policy, simulation and approval checks. It checks the technical distinction: Prevalidation is a safety boundary before changing network state, separate from checks after a change completes.

Incorrect Answers

A:

This observation would test a different technical dependency: 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 issue is governed by: This directly verifies the related correction: Make deployment depend on successful prevalidation jobs for schema, policy, simulation and approval checks. Its decisive check is “A deliberately invalid network change blocks before deploy and a valid change reaches the deployment stage only after passing gates”.

B:

The alternative verifies a different condition: 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 current case instead depends on: This directly verifies the related correction: Make deployment depend on successful prevalidation jobs for schema, policy, simulation and approval checks. Confirm that “A deliberately invalid network change blocks before deploy and a valid change reaches the deployment stage only after passing gates”.

C:

That test belongs to another control with this basis: This directly verifies the related correction: Inspect the failed job logs and classify whether build, dependency, test or environment validation failed before making a targeted fix. In the current case, the governing reason is: This directly verifies the related correction: Make deployment depend on successful prevalidation jobs for schema, policy, simulation and approval checks. The direct verification is “A deliberately invalid network change blocks before deploy and a valid change reaches the deployment stage only after passing gates”.

Question 62

At fictional Elmcrest Theatre, during a conversational network agent pilot, the operator observes: An AI agent ranks an attacker-supplied forum snippet above current Cisco documentation and recommends disabling TLS verification. Which observation would confirm that this exact failure is resolved?

  1. The assistant outputs a reviewable structured plan and no device mutation occurs until the scoped proposal is approved.
  2. The validation crosschecks observed interface or VLAN state before accepting a proposed operation and flags missing telemetry as uncertainty.
  3. The workflow reduces draft effort yet records review and successful technical tests before any proposed config reaches deployment.
  4. A poisoned-source test yields a flagged uncertainty or validated official-source citation instead of an unsafe configuration recommendation.

Explanation

Correct Answer

D:

A poisoned-source test yields a flagged uncertainty or validated official-source citation instead of an unsafe configuration recommendation. This directly verifies the related correction: Ground actionable recommendations in trusted versioned technical references and reject unsupported or conflicting retrieved claims. It checks the technical distinction: Retrieval-augmented systems can inherit false or hostile data; source quality and technical cross-checks must precede action.

Incorrect Answers

A:

The alternative verifies a different condition: This directly verifies the related correction: Convert user requests into a typed proposed intent with explicit targets, preconditions and a separate human-approved execution path. The current case instead depends on: This directly verifies the related correction: Ground actionable recommendations in trusted versioned technical references and reject unsupported or conflicting retrieved claims. Confirm that “A poisoned-source test yields a flagged uncertainty or validated official-source citation instead of an unsafe configuration recommendation”.

B:

That test belongs to another control with this basis: This directly verifies the related correction: Check AI conclusions against fresh independent device and controller evidence with explicit freshness and confidence rules. In the current case, the governing reason is: This directly verifies the related correction: Ground actionable recommendations in trusted versioned technical references and reject unsupported or conflicting retrieved claims. The direct verification is “A poisoned-source test yields a flagged uncertainty or validated official-source citation instead of an unsafe configuration recommendation”.

C:

This observation would test a different technical dependency: This directly verifies the related correction: Use AI assistance for bounded drafts and test generation while assigning accountable reviewers and validating facts against approved sources. The current issue is governed by: This directly verifies the related correction: Ground actionable recommendations in trusted versioned technical references and reject unsupported or conflicting retrieved claims. Its decisive check is “A poisoned-source test yields a flagged uncertainty or validated official-source citation instead of an unsafe configuration recommendation”.

Question 63

At fictional Thornwick Health Trust, during a remote branch provisioning pilot, the operator observes: An engineer builds a RESTCONF URI without a required interface-list key and receives a resource-not-found or ambiguous-target error. Which explanation best matches the actual broken dependency?

  1. Terraform configuration alone does not establish ownership of an already-existing platform object; state import binds it to a resource address.
  2. Safe network automation separates preflight, controlled deployment, verification and recovery instead of assuming all endpoints will succeed.
  3. Infrastructure as code, low-code workflows and custom software solve different state-lifecycle and integration needs.
  4. RESTCONF exposes list entries through resource identifiers determined by the keys declared in the YANG model.

Explanation

Correct Answer

D:

RESTCONF exposes list entries through resource identifiers determined by the keys declared in the YANG model. The corresponding repair is: Address the exact YANG list instance using its fully encoded key values in the RESTCONF data resource path. Acceptance should show: A GET of the specific keyed list entry shows only the authorized VLAN or interface changed, with sibling entries intact.

Incorrect Answers

A:

The offered action targets: The corresponding repair is: Import the existing platform object into Terraform state, align its configuration and inspect a non-destructive plan. The case facts point instead to: The corresponding repair is: Address the exact YANG list instance using its fully encoded key values in the RESTCONF data resource path. Implement “RESTCONF exposes list entries through resource identifiers determined by the keys declared in the YANG model” to address that specific condition.

B:

This alternative is a response to another technical cause: The corresponding repair is: Perform per-device reachability and capability prechecks, capture backups, and stop or roll back on failed postchecks. The reported case instead depends on: The corresponding repair is: Address the exact YANG list instance using its fully encoded key values in the RESTCONF data resource path. The action that directly addresses it is “RESTCONF exposes list entries through resource identifiers determined by the keys declared in the YANG model”.

C:

The proposed action belongs to the mechanism: The corresponding repair is: 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: The corresponding repair is: Address the exact YANG list instance using its fully encoded key values in the RESTCONF data resource path. The corrective choice is “RESTCONF exposes list entries through resource identifiers determined by the keys declared in the YANG model”.

Question 64

During a remote branch provisioning pilot at fictional Northshore Cloud, the change record states: A monitoring script tries to modify an operational telemetry counter through the RESTCONF configuration resource and receives an error. Which control best prevents this particular failure from recurring?

  1. Design resource-state reconciliation and safe retry policies for all create and job-submission requests.
  2. Require inventory-host preview and environment-specific group-variable review in change approval.
  3. Maintain separate configuration-compliance and operational-state assertions for every network change workflow.
  4. Review handler notification conditions and test unchanged and changed execution paths before production scheduling.

Explanation

Correct Answer

C:

Maintain separate configuration-compliance and operational-state assertions for every network change workflow. This prevents the recurrence because yANG distinguishes configuration intent from read-only operational state; successful config writes do not establish runtime protocol health. A matching immediate correction is: Read intended configuration and runtime operational YANG data from their appropriate modeled resources, and write only configurable leaves.

Incorrect Answers

A:

This routine guards against another mechanism: a network transport timeout does not prove server-side failure; blind retries of non-idempotent operations can duplicate effects. The recurring exposure in the current case is: yANG distinguishes configuration intent from read-only operational state; successful config writes do not establish runtime protocol health. The matching preventive check is “Maintain separate configuration-compliance and operational-state assertions for every network change workflow”.

B:

The suggested review tracks a different technical risk: ansible inventory groups and variable precedence determine which devices and values are targeted by a playbook. Here the sustained control must address: yANG distinguishes configuration intent from read-only operational state; successful config writes do not establish runtime protocol health. Choose “Maintain separate configuration-compliance and operational-state assertions for every network change workflow”.

D:

This routine guards against another mechanism: ansible handlers are triggered by changed tasks and coalesce notifications, separating configuration checks from disruptive service actions. The recurring exposure in the current case is: yANG distinguishes configuration intent from read-only operational state; successful config writes do not establish runtime protocol health. The matching preventive check is “Maintain separate configuration-compliance and operational-state assertions for every network change workflow”.

Question 65

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 ongoing engineering assurance should follow the successful fix?

  1. Enforce a shared structured-event schema and test correlation queries during pipeline acceptance.
  2. Include cross-tenant and privilege-escalation negative tests in API CI and audit privileged access decisions.
  3. Version baseline snapshots and specify per-feature allowed changes rather than requiring exact equality for volatile counters.
  4. Monitor clock skew, log forwarding errors and collector persistence capacity.

Explanation

Correct Answer

B:

Include cross-tenant and privilege-escalation negative tests in API CI and audit privileged access decisions. This prevents the recurrence because authentication proves identity but each network resource action requires separate policy-based authorization controls. A matching immediate correction is: Enforce server-side per-resource authorization using authenticated identity and approved tenant or device scope.

Incorrect Answers

A:

The alternative verifies a different condition: an effective logging architecture uses consistent machine-readable context and common correlation fields across distributed jobs. The current case instead depends on: authentication proves identity but each network resource action requires separate policy-based authorization controls. Confirm that “Include cross-tenant and privilege-escalation negative tests in API CI and audit privileged access decisions”.

C:

This observation would test a different technical dependency: pyATS can learn and compare device operational state to detect unintended network effects beyond text config diffs. The current issue is governed by: authentication proves identity but each network resource action requires separate policy-based authorization controls. Its decisive check is “Include cross-tenant and privilege-escalation negative tests in API CI and audit privileged access decisions”.

D:

The alternative verifies a different condition: distributed troubleshooting requires durable transport and consistent time context; ephemeral local logs can be lost or misordered. The current case instead depends on: authentication proves identity but each network resource action requires separate policy-based authorization controls. Confirm that “Include cross-tenant and privilege-escalation negative tests in API CI and audit privileged access decisions”.

Question 66

At fictional Northshore Cloud, an acceptance review of an inventory reconciliation finds: A Python network maintenance loop calls requests.get without a timeout and blocks indefinitely when a switch management plane stops responding. Which targeted correction best addresses the network automation failure?

  1. Move credentials into a protected secret store or Ansible Vault and suppress sensitive task output while keeping access narrowly scoped.
  2. Set explicit connect and read timeouts and catch the resulting exceptions so the worker can report and continue safely.
  3. Respect rate-limit response headers and coordinate bounded exponential backoff with jitter under the shared API budget.
  4. Build the request body from the correct YANG data node and use application/yang-data+json with valid RESTCONF resource paths.

Explanation

Correct Answer

B:

Set explicit connect and read timeouts and catch the resulting exceptions so the worker can report and continue safely. This addresses the problem because python HTTP clients do not guarantee a useful bounded response time unless the caller configures explicit timeouts. Confirm success using: A simulated nonresponsive endpoint times out within the declared bound and produces a per-device failure record without blocking others.

Incorrect Answers

A:

The offered action targets: automation credentials need confidentiality at rest and in output; inventory convenience does not justify committing secrets. The case facts point instead to: python HTTP clients do not guarantee a useful bounded response time unless the caller configures explicit timeouts. Implement “Set explicit connect and read timeouts and catch the resulting exceptions so the worker can report and continue safely” to address that specific condition.

C:

The proposed action belongs to the mechanism: hTTP 429 signals server-enforced rate limits; API client backoff must consider shared rate budgets and Retry-After semantics. Here the stated fault follows a different mechanism: python HTTP clients do not guarantee a useful bounded response time unless the caller configures explicit timeouts. The corrective choice is “Set explicit connect and read timeouts and catch the resulting exceptions so the worker can report and continue safely”.

D:

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: python HTTP clients do not guarantee a useful bounded response time unless the caller configures explicit timeouts. Implement “Set explicit connect and read timeouts and catch the resulting exceptions so the worker can report and continue safely” to address that specific condition.

Question 67

While investigating a source-of-truth integration for fictional Willowfield Hospitality, the team reports: A GitLab CI build succeeds on a developer laptop but fails in the runner because the automation package was never declared as a dependency. Which engineering principle explains the described system behavior?

  1. CI runners start from controlled environments; undeclared local dependencies cannot be assumed present remotely.
  2. Deployment command success is not the same as verified service success; operational checks must follow state changes.
  3. A deployment stage should enforce release scope and approval, not merely execute a command with unrestricted infrastructure access.
  4. Git reset moves HEAD and optionally the index and worktree, making it suitable for carefully revising unpublished local history.

Explanation

Correct Answer

A:

CI runners start from controlled environments; undeclared local dependencies cannot be assumed present remotely. The corresponding repair is: Declare and lock the required dependency in the build manifest and install it in the pipeline's reproducible environment. Acceptance should show: A fresh isolated runner installs the dependency from the manifest and completes the build without relying on developer machine state.

Incorrect Answers

B:

The corresponding repair is: Run objective-based postdeployment checks and fail or roll back the change when observed network behavior contradicts intent. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Declare and lock the required dependency in the build manifest and install it in the pipeline's reproducible environment.

C:

The offered statement is true for this other mechanism: The corresponding repair is: Deploy through bounded environment-scoped jobs with approved service credentials and staged canary or batch rollout. It does not explain the facts described here, which follow from: The corresponding repair is: Declare and lock the required dependency in the build manifest and install it in the pipeline's reproducible environment.

D:

This principle describes a separate cause: The corresponding repair is: Use an appropriate local Git reset to move the branch pointer and rebuild the unpublished commit while protecting wanted working changes. The reported condition is governed by: The corresponding repair is: Declare and lock the required dependency in the build manifest and install it in the pipeline's reproducible environment. The two mechanisms should not be conflated.

Question 68

During a network policy migration at fictional Cobalt Ridge Bank, the change record states: An ACL tool assumes a partial PUT always preserves all omitted siblings, and postchange data shows attributes were removed. What ongoing engineering assurance should follow the successful fix?

  1. Include before-and-after model diff checks and explicit method selection in RESTCONF automation reviews.
  2. Require remote state access controls, locking verification and serialized deployment jobs for shared workspaces.
  3. Require inventory-host preview and environment-specific group-variable review in change approval.
  4. Require a policy-reviewed plan artifact and a clean post-change plan in the automated change workflow.

Explanation

Correct Answer

A:

Include before-and-after model diff checks and explicit method selection in RESTCONF automation reviews. This prevents the recurrence because hTTP PUT represents replacement semantics for a targeted RESTCONF resource, whereas PATCH supports partial edits under the applicable media type. A matching immediate correction is: Choose a supported targeted PATCH or edit operation for partial changes and reserve PUT for intentionally replacing the resource representation.

Incorrect Answers

B:

That safeguard is relevant to: terraform state tracks managed resource associations; concurrent writes without locking can corrupt effective desired-state coordination. The current failure instead follows from: hTTP PUT represents replacement semantics for a targeted RESTCONF resource, whereas PATCH supports partial edits under the applicable media type. Its prevention measure is “Include before-and-after model diff checks and explicit method selection in RESTCONF automation reviews”.

C:

This routine guards against another mechanism: ansible inventory groups and variable precedence determine which devices and values are targeted by a playbook. The recurring exposure in the current case is: hTTP PUT represents replacement semantics for a targeted RESTCONF resource, whereas PATCH supports partial edits under the applicable media type. The matching preventive check is “Include before-and-after model diff checks and explicit method selection in RESTCONF automation reviews”.

D:

The suggested review tracks a different technical risk: terraform compares configuration, recorded state and provider observations to compute a proposed change set before apply. Here the sustained control must address: hTTP PUT represents replacement semantics for a targeted RESTCONF resource, whereas PATCH supports partial edits under the applicable media type. Choose “Include before-and-after model diff checks and explicit method selection in RESTCONF automation reviews”.

Question 69

At fictional Marble Bay Software, an acceptance review of an automation service security audit finds: Automation audit events contain free-form text without change IDs, making it impossible to link one network change to a failure. What technical evidence should be required before closing this change?

  1. Load tests show telemetry consumers keeping up with target throughput or explicitly signaling lost samples without presenting false continuity.
  2. An incident query joins all deployment events by change ID and identifies the failed device and pipeline stage.
  3. A timeline of stage logs identifies the first failing API or schema operation and confirms the targeted repair removes it.
  4. Clients establish a verified TLS session to the expected controller hostname with a valid certificate chain.

Explanation

Correct Answer

B:

An incident query joins all deployment events by change ID and identifies the failed device and pipeline stage. This directly verifies the related correction: Emit structured events with timestamp, device identity, change ID, severity, stage and outcome to the central log destination. It checks the technical distinction: An effective logging architecture uses consistent machine-readable context and common correlation fields across distributed jobs.

Incorrect Answers

A:

That test belongs to another control with this basis: This directly verifies the related correction: Introduce bounded buffering, backpressure monitoring and horizontal ingestion capacity with visible gap or loss reporting. In the current case, the governing reason is: 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 direct verification is “An incident query joins all deployment events by change ID and identifies the failed device and pipeline stage”.

C:

The alternative verifies a different condition: This directly verifies the related correction: Trace correlated event IDs and earliest causal errors through the pipeline instead of treating the final propagated exception as root cause. The current case instead depends on: This directly verifies the related correction: Emit structured events with timestamp, device identity, change ID, severity, stage and outcome to the central log destination. Confirm that “An incident query joins all deployment events by change ID and identifies the failed device and pipeline stage”.

D:

That test belongs to another control with this basis: 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. In the current case, the governing reason is: 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 direct verification is “An incident query joins all deployment events by change ID and identifies the failed device and pipeline stage”.

Question 70

While investigating a source-of-truth integration for fictional Willowfield Hospitality, the team reports: A Terraform apply starts before policy lint and network simulation checks, allowing an invalid ACL to reach live devices. What mechanism is most directly responsible for these symptoms?

  1. Simulation usefulness depends on modeled network dependencies; an incomplete topology cannot validate omitted behaviors.
  2. A reproducible simulation needs controlled topology definitions and readiness gates to avoid timing-dependent false failures.
  3. Compose networks govern container service reachability, while host port publishing determines external exposure.
  4. Prevalidation is a safety boundary before changing network state, separate from checks after a change completes.

Explanation

Correct Answer

D:

Prevalidation is a safety boundary before changing network state, separate from checks after a change completes. The corresponding repair is: Make deployment depend on successful prevalidation jobs for schema, policy, simulation and approval checks. Acceptance should show: A deliberately invalid network change blocks before deploy and a valid change reaches the deployment stage only after passing gates.

Incorrect Answers

A:

This principle describes a separate cause: The corresponding repair is: Model the relevant links, routing peers and failure cases in CML rather than only a minimal happy-path device. The reported condition is governed by: The corresponding repair is: Make deployment depend on successful prevalidation jobs for schema, policy, simulation and approval checks. The two mechanisms should not be conflated.

B:

The corresponding repair is: Provision the CML topology reproducibly and wait for all required node readiness conditions before tests begin. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Make deployment depend on successful prevalidation jobs for schema, policy, simulation and approval checks.

C:

The offered statement is true for this other mechanism: The corresponding repair is: Use purpose-specific networks and expose only the required listener ports while keeping backend services unexposed. It does not explain the facts described here, which follow from: The corresponding repair is: Make deployment depend on successful prevalidation jobs for schema, policy, simulation and approval checks.