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 31

Question 300

While investigating a reproducible simulation for fictional Windward Maritime, the team reports: A YANG-driven script uses a generic key name that is not in the device's supported schema, causing server-side validation rejection. Which targeted correction best addresses the network automation failure?

  1. Define service dependencies with appropriate health checks and resilient application startup or retry behavior.
  2. Inspect the failed job logs and classify whether build, dependency, test or environment validation failed before making a targeted fix.
  3. Run objective-based postdeployment checks and fail or roll back the change when observed network behavior contradicts intent.
  4. Construct JSON using the published YANG container hierarchy, qualified node names and correct value types.

Explanation

Correct Answer

D:

Construct JSON using the published YANG container hierarchy, qualified node names and correct value types. This addresses the problem because yANG defines node hierarchy, namespaces, list keys and data types; conforming JSON must preserve that structure. Confirm success using: The payload validates against the YANG schema and the RESTCONF server accepts the exact intended interface resource. Applied here, the relevant facts are: A YANG-driven script uses a generic key name that is not in the device's supported schema, causing server-side validation rejection. The question asks which targeted correction best addresses the network automation failure.

Incorrect Answers

A:

The offered action targets: container start ordering does not inherently guarantee service readiness; health conditions and retries address that gap. The case facts point instead to: yANG defines node hierarchy, namespaces, list keys and data types; conforming JSON must preserve that structure. Implement “Construct JSON using the published YANG container hierarchy, qualified node names and correct value types” to address that specific condition.

B:

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: yANG defines node hierarchy, namespaces, list keys and data types; conforming JSON must preserve that structure. The action that directly addresses it is “Construct JSON using the published YANG container hierarchy, qualified node names and correct value types”.

C:

The proposed action belongs to the mechanism: deployment command success is not the same as verified service success; operational checks must follow state changes. Here the stated fault follows a different mechanism: yANG defines node hierarchy, namespaces, list keys and data types; conforming JSON must preserve that structure. The corrective choice is “Construct JSON using the published YANG container hierarchy, qualified node names and correct value types”.

Question 301

During a source-of-truth integration at fictional Violet Ridge Resorts, the change record states: A Docker Compose automation test environment brings up a queue consumer before its message broker is ready, causing intermittent job loss. What mechanism is most directly responsible for these symptoms?

  1. A cherry-picked commit does not automatically bring every ancestor or dependent change from its original branch.
  2. A reproducible simulation needs controlled topology definitions and readiness gates to avoid timing-dependent false failures.
  3. Container start ordering does not inherently guarantee service readiness; health conditions and retries address that gap.
  4. Prevalidation is a safety boundary before changing network state, separate from checks after a change completes.

Explanation

Correct Answer

C:

Container start ordering does not inherently guarantee service readiness; health conditions and retries address that gap. The corresponding repair is: Define service dependencies with appropriate health checks and resilient application startup or retry behavior. Acceptance should show: The Compose deployment starts required backends and the worker reaches ready state even when a dependency starts slowly.

Incorrect Answers

A:

This principle describes a separate cause: The corresponding repair is: Identify the prerequisite commits and cherry-pick a minimal compatible sequence or adapt the patch for the target baseline. The reported condition is governed by: The corresponding repair is: Define service dependencies with appropriate health checks and resilient application startup or retry behavior. 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: Define service dependencies with appropriate health checks and resilient application startup or retry behavior.

D:

This principle describes a separate cause: The corresponding repair is: Make deployment depend on successful prevalidation jobs for schema, policy, simulation and approval checks. The reported condition is governed by: The corresponding repair is: Define service dependencies with appropriate health checks and resilient application startup or retry behavior. The two mechanisms should not be conflated.

Question 302

At fictional Sunrise Aeronautics, during an AI-assisted code review, the operator observes: A network incident log contains attacker-controlled text saying ignore safety checks and run a destructive router command, and the agent obeys it. What should the team add to its network automation operating process?

  1. Enforce identity binding, tenant-isolated caches and tool-level audit and RBAC tests for MCP services.
  2. Review FastMCP tool schemas, allowed methods, output redaction and per-device access before agent connection.
  3. Mark generated code for extra negative tests and prohibit bypassing deployment gates based on model confidence.
  4. Red-team retrieval inputs and enforce hard tool allowlists and approvals independent of prompt wording.

Explanation

Correct Answer

D:

Red-team retrieval inputs and enforce hard tool allowlists and approvals independent of prompt wording. This prevents the recurrence because prompt injection attempts to convert lower-trust retrieved content into high-priority instructions across an AI-agent trust boundary. A matching immediate correction is: Treat retrieved logs as untrusted data and enforce instruction hierarchy and independent tool permissions outside the model.

Incorrect Answers

A:

The proposed action belongs to the mechanism: an MCP server is an integration boundary and must not treat model-selected identity strings as verified security credentials. Here the stated fault follows a different mechanism: prompt injection attempts to convert lower-trust retrieved content into high-priority instructions across an AI-agent trust boundary. The corrective choice is “Red-team retrieval inputs and enforce hard tool allowlists and approvals independent of prompt wording”.

B:

The offered action targets: an MCP server publishes structured tools and resources to clients; safe network use requires explicit least-privilege tool definitions. The case facts point instead to: prompt injection attempts to convert lower-trust retrieved content into high-priority instructions across an AI-agent trust boundary. Implement “Red-team retrieval inputs and enforce hard tool allowlists and approvals independent of prompt wording” to address that specific condition.

C:

This alternative is a response to another technical cause: generative systems can propose plausible-looking but incorrect commands; independent executable validation is required for safe infrastructure changes. The reported case instead depends on: prompt injection attempts to convert lower-trust retrieved content into high-priority instructions across an AI-agent trust boundary. The action that directly addresses it is “Red-team retrieval inputs and enforce hard tool allowlists and approvals independent of prompt wording”.

Question 303

While investigating an automation service security audit for fictional Coastal Meadow Labs, the team reports: During a fabric-wide link flap, a subscriber's ingestion queue overflows while dashboards continue displaying incomplete metrics as if current. Which result most directly verifies that the proposed correction worked?

  1. Load tests show telemetry consumers keeping up with target throughput or explicitly signaling lost samples without presenting false continuity.
  2. pyATS comparison shows approved changed values while protected neighbors, interface counters or route counts remain within defined acceptance bounds.
  3. The corrected job authenticates with a valid identity and has exactly the approved resource permissions, with distinct log codes for future failures.
  4. Clients establish a verified TLS session to the expected controller hostname with a valid certificate chain.

Explanation

Correct Answer

A:

Load tests show telemetry consumers keeping up with target throughput or explicitly signaling lost samples without presenting false continuity. This directly verifies the related correction: Introduce bounded buffering, backpressure monitoring and horizontal ingestion capacity with visible gap or loss reporting. It checks the technical distinction: Streaming telemetry pipelines have collectors, transports, ingestion queues and storage capacity that can fail independently of device subscriptions.

Incorrect Answers

B:

This alternative is a response to another technical cause: This directly verifies the related correction: Capture structured prechange operational state with pyATS, apply the change, then compare relevant postchange state and assert expected invariants. The reported case instead depends on: This directly verifies the related correction: Introduce bounded buffering, backpressure monitoring and horizontal ingestion capacity with visible gap or loss reporting. The action that directly addresses it is “Load tests show telemetry consumers keeping up with target throughput or explicitly signaling lost samples without presenting false continuity”.

C:

The proposed action belongs to the mechanism: This directly verifies the related correction: Classify authentication failures and authorization denials separately, then correct token validity or RBAC scope accordingly. Here the stated fault follows a different mechanism: This directly verifies the related correction: Introduce bounded buffering, backpressure monitoring and horizontal ingestion capacity with visible gap or loss reporting. The corrective choice is “Load tests show telemetry consumers keeping up with target throughput or explicitly signaling lost samples without presenting false continuity”.

D:

The offered action targets: 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 case facts point instead to: This directly verifies the related correction: Introduce bounded buffering, backpressure monitoring and horizontal ingestion capacity with visible gap or loss reporting. Implement “Load tests show telemetry consumers keeping up with target throughput or explicitly signaling lost samples without presenting false continuity” to address that specific condition.

Question 304

At fictional Sunrise Aeronautics, during an AI-assisted code review, the operator observes: A Python FastMCP service exposes a broad execute-command tool to an agent that only needs interface status snapshots. What should the engineer change first to resolve this specific issue?

  1. Expose narrowly scoped typed read-only FastMCP tools for approved device and status fields with controlled access.
  2. Bind current request context to fresh authorized inventory and explicit tenant or device selection before tool calls.
  3. Ground actionable recommendations in trusted versioned technical references and reject unsupported or conflicting retrieved claims.
  4. Subject AI-suggested changes to schema and unit tests, simulated network execution, policy checks and human change approval.

Explanation

Correct Answer

A:

Expose narrowly scoped typed read-only FastMCP tools for approved device and status fields with controlled access. This addresses the problem because an MCP server publishes structured tools and resources to clients; safe network use requires explicit least-privilege tool definitions. Confirm success using: A tool listing shows bounded operations and calls return only authorized network telemetry without configuration mutations. Applied here, the relevant facts are: A Python FastMCP service exposes a broad execute-command tool to an agent that only needs interface status snapshots. The question asks what should the engineer change first to resolve this specific issue.

Incorrect Answers

B:

The proposed action belongs to the mechanism: conversation memory is not authoritative network state; stale context and scope leakage create wrong-target operational risk. Here the stated fault follows a different mechanism: an MCP server publishes structured tools and resources to clients; safe network use requires explicit least-privilege tool definitions. The corrective choice is “Expose narrowly scoped typed read-only FastMCP tools for approved device and status fields with controlled access”.

C:

The offered action targets: retrieval-augmented systems can inherit false or hostile data; source quality and technical cross-checks must precede action. The case facts point instead to: an MCP server publishes structured tools and resources to clients; safe network use requires explicit least-privilege tool definitions. Implement “Expose narrowly scoped typed read-only FastMCP tools for approved device and status fields with controlled access” to address that specific condition.

D:

This alternative is a response to another technical cause: generative systems can propose plausible-looking but incorrect commands; independent executable validation is required for safe infrastructure changes. The reported case instead depends on: an MCP server publishes structured tools and resources to clients; safe network use requires explicit least-privilege tool definitions. The action that directly addresses it is “Expose narrowly scoped typed read-only FastMCP tools for approved device and status fields with controlled access”.

Question 305

While investigating a reproducible simulation for fictional Windward Maritime, the team reports: A YANG-driven script uses a generic key name that is not in the device's supported schema, causing server-side validation rejection. What ongoing engineering assurance should follow the successful fix?

  1. Use protected environments, least-privilege deploy tokens and progressive rollout approval conditions.
  2. Generate payload fixtures from reviewed YANG modules and test schema validation before any live update.
  3. Control source updates through review and schedule automated drift detection after deployment.
  4. Add secret scanning and explicit staged-diff review before committing automation changes.

Explanation

Correct Answer

B:

Generate payload fixtures from reviewed YANG modules and test schema validation before any live update. This prevents the recurrence because yANG defines node hierarchy, namespaces, list keys and data types; conforming JSON must preserve that structure. A matching immediate correction is: Construct JSON using the published YANG container hierarchy, qualified node names and correct value types.

Incorrect Answers

A:

The suggested review tracks a different technical risk: a deployment stage should enforce release scope and approval, not merely execute a command with unrestricted infrastructure access. Here the sustained control must address: yANG defines node hierarchy, namespaces, list keys and data types; conforming JSON must preserve that structure. Choose “Generate payload fixtures from reviewed YANG modules and test schema validation before any live update”.

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: yANG defines node hierarchy, namespaces, list keys and data types; conforming JSON must preserve that structure. The matching preventive check is “Generate payload fixtures from reviewed YANG modules and test schema validation before any live update”.

D:

The suggested review tracks a different technical risk: the Git index is the staging area and can be changed independently of the working tree by suitable reset modes. Here the sustained control must address: yANG defines node hierarchy, namespaces, list keys and data types; conforming JSON must preserve that structure. Choose “Generate payload fixtures from reviewed YANG modules and test schema validation before any live update”.

Question 306

At fictional Cedarbridge Care Systems, during a campus API automation rollout, the operator observes: A build runner silently upgrades its Terraform Cisco provider and begins planning previously unseen resource replacements. Which control best prevents this particular failure from recurring?

  1. Test provider upgrades in a sandbox and approve lockfile changes independently of ordinary network configuration edits.
  2. Introduce request budgets, jitter, retry caps and 429 rate metrics into the automation client.
  3. Maintain separate configuration-compliance and operational-state assertions for every network change workflow.
  4. Record per-platform model support and gate model-specific deploy steps on device capability checks.

Explanation

Correct Answer

A:

Test provider upgrades in a sandbox and approve lockfile changes independently of ordinary network configuration edits. This prevents the recurrence because terraform providers translate declarative resources into platform API operations; provider version changes can alter behavior. A matching immediate correction is: Set compatible provider version constraints and commit the provider dependency lock file for reproducible runs.

Incorrect Answers

B:

This routine guards against another mechanism: hTTP 429 signals server-enforced rate limits; API client backoff must consider shared rate budgets and Retry-After semantics. The recurring exposure in the current case is: terraform providers translate declarative resources into platform API operations; provider version changes can alter behavior. The matching preventive check is “Test provider upgrades in a sandbox and approve lockfile changes independently of ordinary network configuration edits”.

C:

The suggested review tracks a different technical risk: yANG distinguishes configuration intent from read-only operational state; successful config writes do not establish runtime protocol health. Here the sustained control must address: terraform providers translate declarative resources into platform API operations; provider version changes can alter behavior. Choose “Test provider upgrades in a sandbox and approve lockfile changes independently of ordinary network configuration edits”.

D:

That safeguard is relevant to: model-driven APIs are available only for modules and revisions implemented by the device software, not by the client library alone. The current failure instead follows from: terraform providers translate declarative resources into platform API operations; provider version changes can alter behavior. Its prevention measure is “Test provider upgrades in a sandbox and approve lockfile changes independently of ordinary network configuration edits”.

Question 307

At fictional Willowfield Hospitality, during a version-control hotfix, the operator observes: A network inventory web worker starts before its database is healthy and crashes during initialization. Which targeted correction best addresses the network automation failure?

  1. Define service dependencies with appropriate health checks and resilient application startup or retry behavior.
  2. Model the relevant links, routing peers and failure cases in CML rather than only a minimal happy-path device.
  3. Safely stash or commit unrelated work and check out the intended branch or detached revision in a clean worktree.
  4. Construct JSON using the published YANG container hierarchy, qualified node names and correct value types.

Explanation

Correct Answer

A:

Define service dependencies with appropriate health checks and resilient application startup or retry behavior. This addresses the problem because container start ordering does not inherently guarantee service readiness; health conditions and retries address that gap. Confirm success using: The Compose deployment starts required backends and the worker reaches ready state even when a dependency starts slowly.

Incorrect Answers

B:

The proposed action belongs to the mechanism: simulation usefulness depends on modeled network dependencies; an incomplete topology cannot validate omitted behaviors. Here the stated fault follows a different mechanism: container start ordering does not inherently guarantee service readiness; health conditions and retries address that gap. The corrective choice is “Define service dependencies with appropriate health checks and resilient application startup or retry behavior”.

C:

The offered action targets: git checkout can change branch and working-tree files; uncommitted modifications must be managed to avoid accidental mixing. The case facts point instead to: container start ordering does not inherently guarantee service readiness; health conditions and retries address that gap. Implement “Define service dependencies with appropriate health checks and resilient application startup or retry behavior” to address that specific condition.

D:

This alternative is a response to another technical cause: yANG defines node hierarchy, namespaces, list keys and data types; conforming JSON must preserve that structure. The reported case instead depends on: container start ordering does not inherently guarantee service readiness; health conditions and retries address that gap. The action that directly addresses it is “Define service dependencies with appropriate health checks and resilient application startup or retry behavior”.

Question 308

At fictional Foxglove Aviation, an acceptance review of a certificate renewal rehearsal finds: A TLS renewal script stores the server private key in world-readable inventory files copied to every automation worker. What acceptance check would prove the intended behavior was restored?

  1. The corrected job authenticates with a valid identity and has exactly the approved resource permissions, with distinct log codes for future failures.
  2. pyATS comparison shows approved changed values while protected neighbors, interface counters or route counts remain within defined acceptance bounds.
  3. Permission checks and artifact scans show no exposed private keys, while the service presents the renewed trusted certificate.
  4. A supported image produces structured parsed data; unsupported output is reported as a test instrumentation error, not a device state failure.

Explanation

Correct Answer

C:

Permission checks and artifact scans show no exposed private keys, while the service presents the renewed trusted certificate. This directly verifies the related correction: Generate and store private keys in restricted secret systems and deploy only to the authorized TLS termination endpoint. It checks the technical distinction: CA-signed certificates are public trust assertions but the associated private key must remain confidential for endpoint authentication. Applied here, the relevant facts are: A TLS renewal script stores the server private key in world-readable inventory files copied to every automation worker. The question asks what acceptance check would prove the intended behavior was restored.

Incorrect Answers

A:

The alternative verifies a different condition: This directly verifies the related correction: Classify authentication failures and authorization denials separately, then correct token validity or RBAC scope accordingly. The current case instead depends on: This directly verifies the related correction: Generate and store private keys in restricted secret systems and deploy only to the authorized TLS termination endpoint. Confirm that “Permission checks and artifact scans show no exposed private keys, while the service presents the renewed trusted certificate”.

B:

That test belongs to another control with this basis: This directly verifies the related correction: Capture structured prechange operational state with pyATS, apply the change, then compare relevant postchange state and assert expected invariants. In the current case, the governing reason is: This directly verifies the related correction: Generate and store private keys in restricted secret systems and deploy only to the authorized TLS termination endpoint. The direct verification is “Permission checks and artifact scans show no exposed private keys, while the service presents the renewed trusted certificate”.

D:

The alternative verifies a different condition: This directly verifies the related correction: Validate parser and platform compatibility and distinguish collection or parsing errors from actual network-state assertion failures. The current case instead depends on: This directly verifies the related correction: Generate and store private keys in restricted secret systems and deploy only to the authorized TLS termination endpoint. Confirm that “Permission checks and artifact scans show no exposed private keys, while the service presents the renewed trusted certificate”.

Question 309

At fictional Amberlight Energy, an acceptance review of an AI-assisted code review finds: A conversational assistant intended for route lookup is accidentally granted Terraform apply permissions to all campus workspaces. What is the appropriate response to this network automation condition?

  1. Bind current request context to fresh authorized inventory and explicit tenant or device selection before tool calls.
  2. Convert user requests into a typed proposed intent with explicit targets, preconditions and a separate human-approved execution path.
  3. Issue read-only scoped identity credentials for diagnostic agents and place separate approval boundaries around mutating tools.
  4. Use AI assistance for bounded drafts and test generation while assigning accountable reviewers and validating facts against approved sources.

Explanation

Correct Answer

C:

Issue read-only scoped identity credentials for diagnostic agents and place separate approval boundaries around mutating tools. This addresses the problem because the model is not a reliable security principal; tool identities and server-side authorization bound the damage of agent errors. Confirm success using: Authorization tests show route queries succeed but unapproved configuration changes are rejected before reaching Cisco APIs.

Incorrect Answers

A:

The offered action targets: conversation memory is not authoritative network state; stale context and scope leakage create wrong-target operational risk. The case facts point instead to: the model is not a reliable security principal; tool identities and server-side authorization bound the damage of agent errors. Implement “Issue read-only scoped identity credentials for diagnostic agents and place separate approval boundaries around mutating tools” to address that specific condition.

B:

This alternative is a response to another technical cause: lLMs are useful for language interpretation but the execution boundary should accept validated structured intents, not arbitrary prose. The reported case instead depends on: the model is not a reliable security principal; tool identities and server-side authorization bound the damage of agent errors. The action that directly addresses it is “Issue read-only scoped identity credentials for diagnostic agents and place separate approval boundaries around mutating tools”.

D:

The offered action targets: aI can accelerate low-risk preparation, but speed benefits must be balanced against hallucination, privacy and review obligations. The case facts point instead to: the model is not a reliable security principal; tool identities and server-side authorization bound the damage of agent errors. Implement “Issue read-only scoped identity credentials for diagnostic agents and place separate approval boundaries around mutating tools” to address that specific condition.

Question 310

During a GitLab deployment pipeline rehearsal at fictional Seabright Learning, the change record states: A GitLab deployment job compiles automation files on the production runner using a different dependency set than unit tests used. What technical evidence should be required before closing this change?

  1. The simulated nodes accept the intended configuration and protocol or connectivity assertions pass under the planned topology.
  2. Generated configs match authoritative source records and postapply compliance detects any remaining unauthorized deviation.
  3. The deployed artifact checksum matches the tested build artifact and the pipeline records its originating commit.
  4. The corrected local branch no longer references the mistaken commit and preserved intended edits are recommitted after validation.

Explanation

Correct Answer

C:

The deployed artifact checksum matches the tested build artifact and the pipeline records its originating commit. This directly verifies the related correction: Produce a reproducible versioned build artifact in the build stage and use that immutable artifact for subsequent validation and deployment. It checks the technical distinction: A CI build stage turns source and fixed dependencies into a traceable deployment input used by later stages.

Incorrect Answers

A:

This observation would test a different technical dependency: This directly verifies the related correction: Build a representative topology in Cisco Modeling Labs and execute the automation against simulated devices before live release. The current issue is governed by: This directly verifies the related correction: Produce a reproducible versioned build artifact in the build stage and use that immutable artifact for subsequent validation and deployment. Its decisive check is “The deployed artifact checksum matches the tested build artifact and the pipeline records its originating commit”.

B:

The alternative verifies a different condition: This directly verifies the related correction: Read authorized desired state from the designated source of truth and reconcile observed drift through an approved change path. The current case instead depends on: This directly verifies the related correction: Produce a reproducible versioned build artifact in the build stage and use that immutable artifact for subsequent validation and deployment. Confirm that “The deployed artifact checksum matches the tested build artifact and the pipeline records its originating commit”.

D:

This observation would test a different technical dependency: This directly verifies the related correction: Use an appropriate local Git reset to move the branch pointer and rebuild the unpublished commit while protecting wanted working changes. The current issue is governed by: This directly verifies the related correction: Produce a reproducible versioned build artifact in the build stage and use that immutable artifact for subsequent validation and deployment. Its decisive check is “The deployed artifact checksum matches the tested build artifact and the pipeline records its originating commit”.