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 35

Question 340

At fictional Willowfield Hospitality, during a version-control hotfix, the operator observes: A pipeline declares success when configuration API calls return 200 despite OSPF sessions remaining down on edge routers. What should the engineer change first to resolve this specific issue?

  1. Declare and lock the required dependency in the build manifest and install it in the pipeline's reproducible environment.
  2. Run objective-based postdeployment checks and fail or roll back the change when observed network behavior contradicts intent.
  3. Use an appropriate local Git reset to move the branch pointer and rebuild the unpublished commit while protecting wanted working changes.
  4. Inspect the failed job logs and classify whether build, dependency, test or environment validation failed before making a targeted fix.

Explanation

Correct Answer

B:

Run objective-based postdeployment checks and fail or roll back the change when observed network behavior contradicts intent. This addresses the problem because deployment command success is not the same as verified service success; operational checks must follow state changes. Confirm success using: The postvalidation stage confirms routes, adjacency and connectivity or triggers the documented recovery workflow with evidence.

Incorrect Answers

A:

This alternative is a response to another technical cause: cI runners start from controlled environments; undeclared local dependencies cannot be assumed present remotely. The reported case instead depends on: deployment command success is not the same as verified service success; operational checks must follow state changes. The action that directly addresses it is “Run objective-based postdeployment checks and fail or roll back the change when observed network behavior contradicts intent”.

C:

The offered action targets: git reset moves HEAD and optionally the index and worktree, making it suitable for carefully revising unpublished local history. The case facts point instead to: deployment command success is not the same as verified service success; operational checks must follow state changes. Implement “Run objective-based postdeployment checks and fail or roll back the change when observed network behavior contradicts intent” to address that specific condition.

D:

This alternative is a response to another technical cause: a GitLab pipeline exit code identifies failure, while job logs and test artifacts reveal the specific causal stage and assertion. The reported case instead depends on: deployment command success is not the same as verified service success; operational checks must follow state changes. The action that directly addresses it is “Run objective-based postdeployment checks and fail or roll back the change when observed network behavior contradicts intent”.

Question 341

While investigating a source-of-truth integration for fictional Willowfield Hospitality, the team reports: A temporary network automation API container is unintentionally published to every host interface with privileged management endpoints exposed. Which explanation best matches the actual broken dependency?

  1. Git checkout can change branch and working-tree files; uncommitted modifications must be managed to avoid accidental mixing.
  2. Git revert records an inverse patch in new history rather than moving shared branch pointers backward.
  3. Compose networks govern container service reachability, while host port publishing determines external exposure.
  4. A deployment stage should enforce release scope and approval, not merely execute a command with unrestricted infrastructure access.

Explanation

Correct Answer

C:

Compose networks govern container service reachability, while host port publishing determines external exposure. The corresponding repair is: Use purpose-specific networks and expose only the required listener ports while keeping backend services unexposed. Acceptance should show: Network inspection shows the internal service reachable only to authorized app containers and public bindings limited to the approved API. Applied here, the relevant facts are: A temporary network automation API container is unintentionally published to every host interface with privileged management endpoints exposed. The question asks which explanation best matches the actual broken dependency.

Incorrect Answers

A:

The proposed action belongs to the mechanism: The corresponding repair is: Safely stash or commit unrelated work and check out the intended branch or detached revision in a clean worktree. Here the stated fault follows a different mechanism: The corresponding repair is: Use purpose-specific networks and expose only the required listener ports while keeping backend services unexposed. The corrective choice is “Compose networks govern container service reachability, while host port publishing determines external exposure”.

B:

The offered action targets: The corresponding repair is: Create a reviewed Git revert commit for the offending change and run the full network automation release tests. The case facts point instead to: The corresponding repair is: Use purpose-specific networks and expose only the required listener ports while keeping backend services unexposed. Implement “Compose networks govern container service reachability, while host port publishing determines external exposure” to address that specific condition.

D:

The proposed action belongs to the mechanism: The corresponding repair is: Deploy through bounded environment-scoped jobs with approved service credentials and staged canary or batch rollout. Here the stated fault follows a different mechanism: The corresponding repair is: Use purpose-specific networks and expose only the required listener ports while keeping backend services unexposed. The corrective choice is “Compose networks govern container service reachability, while host port publishing determines external exposure”.

Question 342

While investigating an inventory reconciliation for fictional Thornwick Health Trust, the team reports: A network provisioning system assumes every device family exposes identical Terraform provider resources and cannot fulfill a mixed-platform request. What should the engineer change first to resolve this specific issue?

  1. Import the existing platform object into Terraform state, align its configuration and inspect a non-destructive plan.
  2. Extract a versioned reusable Terraform module with validated input variables for site-specific network parameters.
  3. Validate typed inputs, authorized resource scopes and ranges before constructing API requests, then encode parameters safely.
  4. Use inventory capability detection and platform-specific adapters behind a common validated intent model.

Explanation

Correct Answer

D:

Use inventory capability detection and platform-specific adapters behind a common validated intent model. This addresses the problem because cross-platform automation benefits from a shared intent model but must translate differences in native device APIs and models. Confirm success using: Separate platform acceptance tests reach equivalent approved network intent on each supported operating system without invalid commands. Applied here, the relevant facts are: A network provisioning system assumes every device family exposes identical Terraform provider resources and cannot fulfill a mixed-platform request. The question asks what should the engineer change first to resolve this specific issue.

Incorrect Answers

A:

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: cross-platform automation benefits from a shared intent model but must translate differences in native device APIs and models. Implement “Use inventory capability detection and platform-specific adapters behind a common validated intent model” to address that specific condition.

B:

This alternative is a response to another technical cause: terraform modules support repeated declarative resource patterns while typed inputs isolate deployment-specific configuration. The reported case instead depends on: cross-platform automation benefits from a shared intent model but must translate differences in native device APIs and models. The action that directly addresses it is “Use inventory capability detection and platform-specific adapters behind a common validated intent model”.

C:

The proposed action belongs to the mechanism: aPI clients must validate human and external inputs independently of server-side validation to avoid unsafe or unintended changes. Here the stated fault follows a different mechanism: cross-platform automation benefits from a shared intent model but must translate differences in native device APIs and models. The corrective choice is “Use inventory capability detection and platform-specific adapters behind a common validated intent model”.

Question 343

At fictional Westlake Biomedicine, an acceptance review of a FastMCP security review finds: A team forbids all AI support for routine test scaffolding even though repetitive documentation work consumes scarce engineering time. Which control best prevents this particular failure from recurring?

  1. Test parameter bounds, tenant authorization and injection input against each FastMCP exposed operation.
  2. Define permitted AI assistance tiers and required technical approval gates by change risk.
  3. Add explicit timeouts, result freshness metadata and partial-failure contract tests to every MCP tool.
  4. Tag provenance and document freshness, test poisoned retrieval cases, and gate device changes on deterministic validation.

Explanation

Correct Answer

B:

Define permitted AI assistance tiers and required technical approval gates by change risk. This prevents the recurrence because aI can accelerate low-risk preparation, but speed benefits must be balanced against hallucination, privacy and review obligations. A matching immediate correction is: Use AI assistance for bounded drafts and test generation while assigning accountable reviewers and validating facts against approved sources.

Incorrect Answers

A:

This routine guards against another mechanism: typed MCP tool schemas improve interoperability but server-side validation remains necessary even for a well-formed client call. The recurring exposure in the current case is: aI can accelerate low-risk preparation, but speed benefits must be balanced against hallucination, privacy and review obligations. The matching preventive check is “Define permitted AI assistance tiers and required technical approval gates by change risk”.

C:

That safeguard is relevant to: tool wrappers must preserve the meaning of missing, stale and failed data for the consumer agent. The current failure instead follows from: aI can accelerate low-risk preparation, but speed benefits must be balanced against hallucination, privacy and review obligations. Its prevention measure is “Define permitted AI assistance tiers and required technical approval gates by change risk”.

D:

This routine guards against another mechanism: retrieval-augmented systems can inherit false or hostile data; source quality and technical cross-checks must precede action. The recurring exposure in the current case is: aI can accelerate low-risk preparation, but speed benefits must be balanced against hallucination, privacy and review obligations. The matching preventive check is “Define permitted AI assistance tiers and required technical approval gates by change risk”.

Question 344

While investigating an automation service security audit for fictional Coastal Meadow Labs, the team reports: After a controller load-balancer migration, an HTTPS client fails hostname verification because the certificate SAN lists the old hostname. What ongoing engineering assurance should follow the successful fix?

  1. Enforce a shared structured-event schema and test correlation queries during pipeline acceptance.
  2. Rotate webhook credentials and monitor delivery latency, signature validation and replay protection.
  3. Add injection regression tests and prohibit unmanaged shell execution in network automation services.
  4. Include service DNS/SAN coverage checks and certificate change testing in controller migration plans.

Explanation

Correct Answer

D:

Include service DNS/SAN coverage checks and certificate change testing in controller migration plans. This prevents the recurrence because modern TLS clients validate the connection name against certificate subject alternative names, not merely that a CA issued the cert. A matching immediate correction is: Use an approved DNS endpoint covered by the certificate SAN or reissue a certificate with correct service identities. Applied here, the relevant facts are: After a controller load-balancer migration, an HTTPS client fails hostname verification because the certificate SAN lists the old hostname. The question asks what ongoing engineering assurance should follow the successful fix.

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: modern TLS clients validate the connection name against certificate subject alternative names, not merely that a CA issued the cert. Confirm that “Include service DNS/SAN coverage checks and certificate change testing in controller migration plans”.

B:

That test belongs to another control with this basis: webhooks are asynchronous network events; integrity, delivery acknowledgements and idempotent processing are separate reliability needs. In the current case, the governing reason is: modern TLS clients validate the connection name against certificate subject alternative names, not merely that a CA issued the cert. The direct verification is “Include service DNS/SAN coverage checks and certificate change testing in controller migration plans”.

C:

This observation would test a different technical dependency: untrusted input can cross command or configuration boundaries; validation and safe APIs prevent injection into privileged operations. The current issue is governed by: modern TLS clients validate the connection name against certificate subject alternative names, not merely that a CA issued the cert. Its decisive check is “Include service DNS/SAN coverage checks and certificate change testing in controller migration plans”.

Question 345

At fictional Violet Ridge Resorts, an acceptance review of a version-control hotfix finds: A network parsing pipeline runs under a clean container and raises ModuleNotFoundError for a local-only tool used by the scripts. What acceptance check would prove the intended behavior was restored?

  1. GitLab deployment records show the canary passed before other sites changed, and credentials cannot access unrelated workspaces.
  2. The payload validates against the YANG schema and the RESTCONF server accepts the exact intended interface resource.
  3. Network inspection shows the internal service reachable only to authorized app containers and public bindings limited to the approved API.
  4. A fresh isolated runner installs the dependency from the manifest and completes the build without relying on developer machine state.

Explanation

Correct Answer

D:

A fresh isolated runner installs the dependency from the manifest and completes the build without relying on developer machine state. This directly verifies the related correction: Declare and lock the required dependency in the build manifest and install it in the pipeline's reproducible environment. It checks the technical distinction: CI runners start from controlled environments; undeclared local dependencies cannot be assumed present remotely.

Incorrect Answers

A:

That test belongs to another control with this basis: This directly verifies the related correction: Deploy through bounded environment-scoped jobs with approved service credentials and staged canary or batch rollout. In the current case, the governing reason is: This directly verifies the related correction: Declare and lock the required dependency in the build manifest and install it in the pipeline's reproducible environment. The direct verification is “A fresh isolated runner installs the dependency from the manifest and completes the build without relying on developer machine state”.

B:

This observation would test a different technical dependency: This directly verifies the related correction: Construct JSON using the published YANG container hierarchy, qualified node names and correct value types. The current issue is governed by: This directly verifies the related correction: Declare and lock the required dependency in the build manifest and install it in the pipeline's reproducible environment. Its decisive check is “A fresh isolated runner installs the dependency from the manifest and completes the build without relying on developer machine state”.

C:

The alternative verifies a different condition: This directly verifies the related correction: Use purpose-specific networks and expose only the required listener ports while keeping backend services unexposed. The current case instead depends on: This directly verifies the related correction: Declare and lock the required dependency in the build manifest and install it in the pipeline's reproducible environment. Confirm that “A fresh isolated runner installs the dependency from the manifest and completes the build without relying on developer machine state”.

Question 346

At fictional Marble Bay Software, an acceptance review of an automation service security audit finds: A change adds a planned network prefix but a naive pyATS diff declares failure solely because the route table is no longer byte-identical. Which explanation best matches the actual broken dependency?

  1. CA-signed certificates are public trust assertions but the associated private key must remain confidential for endpoint authentication.
  2. Model-driven telemetry publishes structured device state using subscribed paths and collection modes rather than relying only on slow polling.
  3. Postdeployment validation compares expected invariants and intended deltas, not every volatile or purposely changed value.
  4. Hardcoded secrets create persistent exposure and excessive authority; runtime secret retrieval limits both lifetime and access scope.

Explanation

Correct Answer

C:

Postdeployment validation compares expected invariants and intended deltas, not every volatile or purposely changed value. The corresponding repair is: Write semantic pyATS assertions that permit the approved intended change and reject unrelated regressions. Acceptance should show: The postchange test passes for authorized new routes or neighbors but fails for loss of protected existing reachability.

Incorrect Answers

A:

This alternative is a response to another technical cause: The corresponding repair is: Generate and store private keys in restricted secret systems and deploy only to the authorized TLS termination endpoint. The reported case instead depends on: The corresponding repair is: Write semantic pyATS assertions that permit the approved intended change and reject unrelated regressions. The action that directly addresses it is “Postdeployment validation compares expected invariants and intended deltas, not every volatile or purposely changed value”.

B:

The proposed action belongs to the mechanism: The corresponding repair is: Configure suitable model-driven telemetry subscriptions for the relevant paths at a collection interval appropriate to the signal. Here the stated fault follows a different mechanism: The corresponding repair is: Write semantic pyATS assertions that permit the approved intended change and reject unrelated regressions. The corrective choice is “Postdeployment validation compares expected invariants and intended deltas, not every volatile or purposely changed value”.

D:

This alternative is a response to another technical cause: 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 reported case instead depends on: The corresponding repair is: Write semantic pyATS assertions that permit the approved intended change and reject unrelated regressions. The action that directly addresses it is “Postdeployment validation compares expected invariants and intended deltas, not every volatile or purposely changed value”.

Question 347

While investigating a network policy migration for fictional Cedarbridge Care Systems, the team reports: An engineer pushes a Terraform change to production without reviewing a plan, unexpectedly replacing a live network object instead of editing it. What is the appropriate response to this network automation condition?

  1. Validate typed inputs, authorized resource scopes and ranges before constructing API requests, then encode parameters safely.
  2. Discover supported YANG modules or capabilities before using module-specific RESTCONF data paths, and branch for supported models.
  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

D:

Refresh managed state and review a generated Terraform plan before applying only the intended network changes. This addresses the problem because terraform compares configuration, recorded state and provider observations to compute a proposed change set before apply. Confirm success using: The approved plan identifies the precise create, update and destroy operations, and a follow-up plan shows no unintended drift.

Incorrect Answers

A:

The proposed action belongs to the mechanism: aPI clients must validate human and external inputs independently of server-side validation to avoid unsafe or unintended changes. Here the stated fault follows a different mechanism: terraform compares configuration, recorded state and provider observations to compute a proposed change set before apply. The corrective choice is “Refresh managed state and review a generated Terraform plan before applying only the intended network changes”.

B:

The offered action targets: model-driven APIs are available only for modules and revisions implemented by the device software, not by the client library alone. The case facts point instead to: terraform compares configuration, recorded state and provider observations to compute a proposed change set before apply. Implement “Refresh managed state and review a generated Terraform plan before applying only the intended network changes” to address that specific condition.

C:

This alternative is a response to another technical cause: rESTCONF manipulates YANG-defined resources over HTTP; both resource paths and payload media encoding must match the model. The reported case instead depends on: terraform compares configuration, recorded state and provider observations to compute a proposed change set before apply. The action that directly addresses it is “Refresh managed state and review a generated Terraform plan before applying only the intended network changes”.

Question 348

At fictional Cobalt Ridge Bank, an acceptance review of a campus API automation rollout finds: A Terraform automation run misses out-of-band interface edits and applies a broad change from stale assumptions. What ongoing engineering assurance should follow the successful fix?

  1. Review handler notification conditions and test unchanged and changed execution paths before production scheduling.
  2. Add multi-page integration tests and monitor continuation tokens and retrieved counts on every scheduled inventory run.
  3. Require a policy-reviewed plan artifact and a clean post-change plan in the automated change workflow.
  4. Maintain separate configuration-compliance and operational-state assertions for every network change workflow.

Explanation

Correct Answer

C:

Require a policy-reviewed plan artifact and a clean post-change plan in the automated change workflow. This prevents the recurrence because terraform compares configuration, recorded state and provider observations to compute a proposed change set before apply. A matching immediate correction is: Refresh managed state and review a generated Terraform plan before applying only the intended network changes.

Incorrect Answers

A:

That safeguard is relevant to: ansible handlers are triggered by changed tasks and coalesce notifications, separating configuration checks from disruptive service actions. The current failure instead follows from: terraform compares configuration, recorded state and provider observations to compute a proposed change set before apply. Its prevention measure is “Require a policy-reviewed plan artifact and a clean post-change plan in the automated change workflow”.

B:

This routine guards against another mechanism: many platform APIs paginate large result sets; the first HTTP success response may contain only a subset. The recurring exposure in the current case is: terraform compares configuration, recorded state and provider observations to compute a proposed change set before apply. The matching preventive check is “Require a policy-reviewed plan artifact and a clean post-change plan in the automated change workflow”.

D:

That safeguard is relevant to: yANG distinguishes configuration intent from read-only operational state; successful config writes do not establish runtime protocol health. The current failure instead follows from: terraform compares configuration, recorded state and provider observations to compute a proposed change set before apply. Its prevention measure is “Require a policy-reviewed plan artifact and a clean post-change plan in the automated change workflow”.

Question 349

While investigating a network policy migration for fictional Cedarbridge Care Systems, the team reports: A Python script retries a POST creating a network object after an ambiguous timeout and creates a duplicate because the first request already succeeded. What technical evidence should be required before closing this change?

  1. Plans for two independently configured sites show correct separate VLAN IDs or address values while sharing one reviewed module version.
  2. Simulated 429 responses result in delayed, bounded retries and the caller recovers without a retry storm.
  3. The preflight confirms the required module and revision per target, or marks incompatible devices without making changes.
  4. An induced response-loss test yields one intended network object or operation and records its final state without duplicate changes.

Explanation

Correct Answer

D:

An induced response-loss test yields one intended network object or operation and records its final state without duplicate changes. This directly verifies the related correction: Before retrying a potentially non-idempotent change, check resulting resource state or use a supported idempotency or operation key. It checks the technical distinction: A network transport timeout does not prove server-side failure; blind retries of non-idempotent operations can duplicate effects.

Incorrect Answers

A:

This observation would test a different technical dependency: This directly verifies the related correction: Extract a versioned reusable Terraform module with validated input variables for site-specific network parameters. The current issue is governed by: This directly verifies the related correction: Before retrying a potentially non-idempotent change, check resulting resource state or use a supported idempotency or operation key. Its decisive check is “An induced response-loss test yields one intended network object or operation and records its final state without duplicate changes”.

B:

The alternative verifies a different condition: This directly verifies the related correction: Respect rate-limit response headers and coordinate bounded exponential backoff with jitter under the shared API budget. The current case instead depends on: This directly verifies the related correction: Before retrying a potentially non-idempotent change, check resulting resource state or use a supported idempotency or operation key. Confirm that “An induced response-loss test yields one intended network object or operation and records its final state without duplicate changes”.

C:

That test belongs to another control with this basis: This directly verifies the related correction: Discover supported YANG modules or capabilities before using module-specific RESTCONF data paths, and branch for supported models. In the current case, the governing reason is: This directly verifies the related correction: Before retrying a potentially non-idempotent change, check resulting resource state or use a supported idempotency or operation key. The direct verification is “An induced response-loss test yields one intended network object or operation and records its final state without duplicate changes”.

Question 350

At fictional Seabright Learning, an acceptance review of a reproducible simulation finds: A deployment stage targets all routers at once despite an approved plan to canary one site before fleet rollout. What ongoing engineering assurance should follow the successful fix?

  1. Require postchange telemetry and rollback thresholds for network pipeline release completion.
  2. Require path-limited recovery commands and postrestore diffs for surgical automation-file reversions.
  3. Control source updates through review and schedule automated drift detection after deployment.
  4. Use protected environments, least-privilege deploy tokens and progressive rollout approval conditions.

Explanation

Correct Answer

D:

Use protected environments, least-privilege deploy tokens and progressive rollout approval conditions. This prevents the recurrence because a deployment stage should enforce release scope and approval, not merely execute a command with unrestricted infrastructure access. A matching immediate correction is: Deploy through bounded environment-scoped jobs with approved service credentials and staged canary or batch rollout.

Incorrect Answers

A:

The suggested review tracks a different technical risk: deployment command success is not the same as verified service success; operational checks must follow state changes. Here the sustained control must address: a deployment stage should enforce release scope and approval, not merely execute a command with unrestricted infrastructure access. Choose “Use protected environments, least-privilege deploy tokens and progressive rollout approval conditions”.

B:

That safeguard is relevant to: git can retrieve individual tracked paths from a commit; selecting file scope avoids broad branch-level rollback. The current failure instead follows from: a deployment stage should enforce release scope and approval, not merely execute a command with unrestricted infrastructure access. Its prevention measure is “Use protected environments, least-privilege deploy tokens and progressive rollout approval conditions”.

C:

This routine guards against another mechanism: a reliable source-of-truth workflow separates approved intent from observed device state and defines how changes flow between them. The recurring exposure in the current case is: a deployment stage should enforce release scope and approval, not merely execute a command with unrestricted infrastructure access. The matching preventive check is “Use protected environments, least-privilege deploy tokens and progressive rollout approval conditions”.