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 23

Question 220

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

  1. Version lab topology artifacts and run automated readiness verification before configuration tests.
  2. Prefer revert over reset for shared production branches and validate the inverse patch for dependent changes.
  3. Test slow dependency startup and review Compose healthchecks for all network automation support services.
  4. Add secret scanning and explicit staged-diff review before committing automation changes.

Explanation

Correct Answer

C:

Test slow dependency startup and review Compose healthchecks for all network automation support services. This prevents the recurrence because container start ordering does not inherently guarantee service readiness; health conditions and retries address that gap. A matching immediate correction is: Define service dependencies with appropriate health checks and resilient application startup or retry behavior.

Incorrect Answers

A:

This routine guards against another mechanism: a reproducible simulation needs controlled topology definitions and readiness gates to avoid timing-dependent false failures. The recurring exposure in the current case is: container start ordering does not inherently guarantee service readiness; health conditions and retries address that gap. The matching preventive check is “Test slow dependency startup and review Compose healthchecks for all network automation support services”.

B:

The suggested review tracks a different technical risk: git revert records an inverse patch in new history rather than moving shared branch pointers backward. Here the sustained control must address: container start ordering does not inherently guarantee service readiness; health conditions and retries address that gap. Choose “Test slow dependency startup and review Compose healthchecks for all network automation support services”.

D:

This routine guards against another mechanism: the Git index is the staging area and can be changed independently of the working tree by suitable reset modes. The recurring exposure in the current case is: container start ordering does not inherently guarantee service readiness; health conditions and retries address that gap. The matching preventive check is “Test slow dependency startup and review Compose healthchecks for all network automation support services”.

Question 221

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 engineering principle explains the described system behavior?

  1. The model is not a reliable security principal; tool identities and server-side authorization bound the damage of agent errors.
  2. Prompt injection attempts to convert lower-trust retrieved content into high-priority instructions across an AI-agent trust boundary.
  3. AI can accelerate low-risk preparation, but speed benefits must be balanced against hallucination, privacy and review obligations.
  4. Typed MCP tool schemas improve interoperability but server-side validation remains necessary even for a well-formed client call.

Explanation

Correct Answer

C:

AI can accelerate low-risk preparation, but speed benefits must be balanced against hallucination, privacy and review obligations. The corresponding repair is: Use AI assistance for bounded drafts and test generation while assigning accountable reviewers and validating facts against approved sources. Acceptance should show: The workflow reduces draft effort yet records review and successful technical tests before any proposed config reaches deployment.

Incorrect Answers

A:

The corresponding repair is: Issue read-only scoped identity credentials for diagnostic agents and place separate approval boundaries around mutating tools. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Use AI assistance for bounded drafts and test generation while assigning accountable reviewers and validating facts against approved sources.

B:

The offered statement is true for this other mechanism: The corresponding repair is: Treat retrieved logs as untrusted data and enforce instruction hierarchy and independent tool permissions outside the model. It does not explain the facts described here, which follow from: The corresponding repair is: Use AI assistance for bounded drafts and test generation while assigning accountable reviewers and validating facts against approved sources.

D:

The corresponding repair is: Define typed, validated tool arguments with explicit device allowlists and reject invalid or unauthorized inputs at the server boundary. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Use AI assistance for bounded drafts and test generation while assigning accountable reviewers and validating facts against approved sources.

Question 222

During a conversational network agent pilot at fictional Westlake Biomedicine, the change record states: An LLM invents a controller API path not documented in the deployed Cisco software and presents it as a certain fix. What underlying technical distinction accounts for this failure?

  1. Model fluency is not evidence of device capability; uncertain technical recommendations require explicit verification before action.
  2. AI-assisted code tools may process submitted data outside the intended trust boundary, creating privacy and intellectual-property exposure.
  3. AI-generated code may embed third-party patterns or dependencies; tool output is not automatically cleared of licensing obligations.
  4. Tool wrappers must preserve the meaning of missing, stale and failed data for the consumer agent.

Explanation

Correct Answer

A:

Model fluency is not evidence of device capability; uncertain technical recommendations require explicit verification before action. The corresponding repair is: Require citation to a compatible authoritative reference and fail closed or escalate when command syntax or device version is uncertain. Acceptance should show: The assistant identifies missing version evidence and withholds unverified commands instead of fabricating supported APIs.

Incorrect Answers

B:

This principle describes a separate cause: The corresponding repair is: Sanitize inputs and use an approved private or contractually controlled AI service without exposing secrets or regulated network data. The reported condition is governed by: The corresponding repair is: Require citation to a compatible authoritative reference and fail closed or escalate when command syntax or device version is uncertain. The two mechanisms should not be conflated.

C:

The corresponding repair is: Review generated code provenance, included dependencies and organizational IP policy before accepting it into the repository. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Require citation to a compatible authoritative reference and fail closed or escalate when command syntax or device version is uncertain.

D:

The offered statement is true for this other mechanism: The corresponding repair is: Return structured success and error states with source timestamps and bounded API timeouts rather than silently substituting empty values. It does not explain the facts described here, which follow from: The corresponding repair is: Require citation to a compatible authoritative reference and fail closed or escalate when command syntax or device version is uncertain.

Question 223

At fictional Thornwick Health Trust, during a remote branch provisioning pilot, the operator observes: A backup collector hangs during an IOS XE API session because a socket read never completes, delaying all subsequent devices. Which explanation best matches the actual broken dependency?

  1. Ansible's desired-state-aware network modules compare declared configuration with device state before determining required changes.
  2. Many platform APIs paginate large result sets; the first HTTP success response may contain only a subset.
  3. Terraform state tracks managed resource associations; concurrent writes without locking can corrupt effective desired-state coordination.
  4. Python HTTP clients do not guarantee a useful bounded response time unless the caller configures explicit timeouts.

Explanation

Correct Answer

D:

Python HTTP clients do not guarantee a useful bounded response time unless the caller configures explicit timeouts. The corresponding repair is: Set explicit connect and read timeouts and catch the resulting exceptions so the worker can report and continue safely. Acceptance should show: A simulated nonresponsive endpoint times out within the declared bound and produces a per-device failure record without blocking others.

Incorrect Answers

A:

This alternative is a response to another technical cause: The corresponding repair is: Replace non-idempotent shell appends with the platform-aware Ansible network configuration module and explicit desired interface state. The reported case instead depends on: The corresponding repair is: Set explicit connect and read timeouts and catch the resulting exceptions so the worker can report and continue safely. The action that directly addresses it is “Python HTTP clients do not guarantee a useful bounded response time unless the caller configures explicit timeouts”.

B:

The proposed action belongs to the mechanism: The corresponding repair is: Follow the API's documented cursor or Link continuation until exhaustion, merging results while protecting against repeated cursors. Here the stated fault follows a different mechanism: The corresponding repair is: Set explicit connect and read timeouts and catch the resulting exceptions so the worker can report and continue safely. The corrective choice is “Python HTTP clients do not guarantee a useful bounded response time unless the caller configures explicit timeouts”.

C:

The offered action targets: The corresponding repair is: Configure a shared protected Terraform state backend with supported locking and serialize competing applies against the same state. The case facts point instead to: The corresponding repair is: Set explicit connect and read timeouts and catch the resulting exceptions so the worker can report and continue safely. Implement “Python HTTP clients do not guarantee a useful bounded response time unless the caller configures explicit timeouts” to address that specific condition.

Question 224

During a telemetry quality investigation at fictional Foxglove Aviation, the change record states: A webhook collector loses device-change notifications during transient outages because the sender has no retry or acknowledgement tracking. What acceptance check would prove the intended behavior was restored?

  1. A simulated receiver outage results in eventual one-time processing or an explicit recorded dead-letter failure without accepting forged requests.
  2. Malicious metacharacter input is rejected and legitimate interface updates produce only approved structured API calls.
  3. TLS validation succeeds for the intended hostname and fails for unexpected names without disabling verification.
  4. The corrected job authenticates with a valid identity and has exactly the approved resource permissions, with distinct log codes for future failures.

Explanation

Correct Answer

A:

A simulated receiver outage results in eventual one-time processing or an explicit recorded dead-letter failure without accepting forged requests. This directly verifies the related correction: Authenticate webhook delivery and implement bounded retries with deduplication or delivery-state accounting. It checks the technical distinction: Webhooks are asynchronous network events; integrity, delivery acknowledgements and idempotent processing are separate reliability needs. Applied here, the relevant facts are: A webhook collector loses device-change notifications during transient outages because the sender has no retry or acknowledgement tracking. The question asks what acceptance check would prove the intended behavior was restored.

Incorrect Answers

B:

That test belongs to another control with this basis: This directly verifies the related correction: Use typed input schema validation, approved resource allowlists and safe library argument interfaces rather than shell concatenation. In the current case, the governing reason is: the sender has no retry or acknowledgement tracking. The direct verification is “A simulated receiver outage results in eventual one-time processing or an explicit recorded dead-letter failure without accepting forged requests”.

C:

This observation would test a different technical dependency: This directly verifies the related correction: Use an approved DNS endpoint covered by the certificate SAN or reissue a certificate with correct service identities. The current issue is governed by: the sender has no retry or acknowledgement tracking. Its decisive check is “A simulated receiver outage results in eventual one-time processing or an explicit recorded dead-letter failure without accepting forged requests”.

D:

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: the sender has no retry or acknowledgement tracking. Confirm that “A simulated receiver outage results in eventual one-time processing or an explicit recorded dead-letter failure without accepting forged requests”.

Question 225

At fictional Windward Maritime, during a GitLab deployment pipeline rehearsal, the operator observes: An inventory import creates duplicate switch records because device identity is inferred from mutable display names rather than stable identifiers. What technical evidence should be required before closing this change?

  1. The device registry maps one approved identity to each physical endpoint and duplicate or stale mappings are flagged.
  2. The postvalidation stage confirms routes, adjacency and connectivity or triggers the documented recovery workflow with evidence.
  3. The maintenance branch contains the intended patch without unrelated feature commits and passes the target release tests.
  4. The Compose deployment starts required backends and the worker reaches ready state even when a dependency starts slowly.

Explanation

Correct Answer

A:

The device registry maps one approved identity to each physical endpoint and duplicate or stale mappings are flagged. This directly verifies the related correction: Use stable authoritative device identifiers and reconcile observed inventory to the source-of-truth records before deployment. It checks the technical distinction: A source of truth provides desired canonical inventory, but consumers must resolve identity correctly and reconcile discrepancies.

Incorrect Answers

B:

This observation would test a different technical dependency: This directly verifies the related correction: Run objective-based postdeployment checks and fail or roll back the change when observed network behavior contradicts intent. The current issue is governed by: This directly verifies the related correction: Use stable authoritative device identifiers and reconcile observed inventory to the source-of-truth records before deployment. Its decisive check is “The device registry maps one approved identity to each physical endpoint and duplicate or stale mappings are flagged”.

C:

The alternative verifies a different condition: This directly verifies the related correction: Cherry-pick the specific reviewed hotfix commit into the target maintenance branch and test the resulting change. The current case instead depends on: This directly verifies the related correction: Use stable authoritative device identifiers and reconcile observed inventory to the source-of-truth records before deployment. Confirm that “The device registry maps one approved identity to each physical endpoint and duplicate or stale mappings are flagged”.

D:

That test belongs to another control with this basis: This directly verifies the related correction: Define service dependencies with appropriate health checks and resilient application startup or retry behavior. In the current case, the governing reason is: This directly verifies the related correction: Use stable authoritative device identifiers and reconcile observed inventory to the source-of-truth records before deployment. The direct verification is “The device registry maps one approved identity to each physical endpoint and duplicate or stale mappings are flagged”.

Question 226

During an AI recommendation accuracy study at fictional Amberlight Energy, the change record states: An automation team needs to let a network assistant query inventory, but its MCP server returns entire unrestricted controller API objects. Which targeted correction best addresses the network automation failure?

  1. Treat retrieved logs as untrusted data and enforce instruction hierarchy and independent tool permissions outside the model.
  2. Expose narrowly scoped typed read-only FastMCP tools for approved device and status fields with controlled access.
  3. Ground actionable recommendations in trusted versioned technical references and reject unsupported or conflicting retrieved claims.
  4. Bind current request context to fresh authorized inventory and explicit tenant or device selection before tool calls.

Explanation

Correct Answer

B:

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.

Incorrect Answers

A:

This alternative is a response to another technical cause: prompt injection attempts to convert lower-trust retrieved content into high-priority instructions across an AI-agent trust boundary. 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”.

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: conversation memory is not authoritative network state; stale context and scope leakage create wrong-target operational risk. 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 227

While investigating a source-of-truth integration for fictional Willowfield Hospitality, the team reports: A critical ACL validation fix is needed in a stable automation release, but merging the full development branch would introduce unfinished feature code. Which targeted correction best addresses the network automation failure?

  1. Cherry-pick the specific reviewed hotfix commit into the target maintenance branch and test the resulting change.
  2. Provision the CML topology reproducibly and wait for all required node readiness conditions before tests begin.
  3. Inspect the failed job logs and classify whether build, dependency, test or environment validation failed before making a targeted fix.
  4. Deploy through bounded environment-scoped jobs with approved service credentials and staged canary or batch rollout.

Explanation

Correct Answer

A:

Cherry-pick the specific reviewed hotfix commit into the target maintenance branch and test the resulting change. This addresses the problem because git cherry-pick applies the change introduced by selected commit(s) onto the current branch, creating new history in that branch. Confirm success using: The maintenance branch contains the intended patch without unrelated feature commits and passes the target release tests. Applied here, the relevant facts are: A critical ACL validation fix is needed in a stable automation release, but merging the full development branch would introduce unfinished feature code. The question asks which targeted correction best addresses the network automation failure.

Incorrect Answers

B:

The offered action targets: a reproducible simulation needs controlled topology definitions and readiness gates to avoid timing-dependent false failures. The case facts point instead to: git cherry-pick applies the change introduced by selected commit(s) onto the current branch, creating new history in that branch. Implement “Cherry-pick the specific reviewed hotfix commit into the target maintenance branch and test the resulting change” to address that specific condition.

C:

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: git cherry-pick applies the change introduced by selected commit(s) onto the current branch, creating new history in that branch. The action that directly addresses it is “Cherry-pick the specific reviewed hotfix commit into the target maintenance branch and test the resulting change”.

D:

The proposed action belongs to the mechanism: a deployment stage should enforce release scope and approval, not merely execute a command with unrestricted infrastructure access. Here the stated fault follows a different mechanism: git cherry-pick applies the change introduced by selected commit(s) onto the current branch, creating new history in that branch. The corrective choice is “Cherry-pick the specific reviewed hotfix commit into the target maintenance branch and test the resulting change”.

Question 228

At fictional Sable Valley Power, during a certificate renewal rehearsal, the operator observes: A configuration service posts failure webhooks without authentication and receivers accept forged network-change alerts. Which control best prevents this particular failure from recurring?

  1. Monitor certificate expirations and trust-chain changes with automated predeployment verification.
  2. Require least-privilege service identities, secret scans, expiration alerts and rotation rehearsal.
  3. Include service DNS/SAN coverage checks and certificate change testing in controller migration plans.
  4. Rotate webhook credentials and monitor delivery latency, signature validation and replay protection.

Explanation

Correct Answer

D:

Rotate webhook credentials and monitor delivery latency, signature validation and replay protection. This prevents the recurrence because webhooks are asynchronous network events; integrity, delivery acknowledgements and idempotent processing are separate reliability needs. A matching immediate correction is: Authenticate webhook delivery and implement bounded retries with deduplication or delivery-state accounting.

Incorrect Answers

A:

That safeguard is relevant to: tLS server validation depends on trusted issuer chains and hostname identity; bypassing verification defeats server authentication. The current failure instead follows from: webhooks are asynchronous network events; integrity, delivery acknowledgements and idempotent processing are separate reliability needs. Its prevention measure is “Rotate webhook credentials and monitor delivery latency, signature validation and replay protection”.

B:

This routine guards against another mechanism: hardcoded secrets create persistent exposure and excessive authority; runtime secret retrieval limits both lifetime and access scope. The recurring exposure in the current case is: webhooks are asynchronous network events; integrity, delivery acknowledgements and idempotent processing are separate reliability needs. The matching preventive check is “Rotate webhook credentials and monitor delivery latency, signature validation and replay protection”.

C:

The suggested review tracks a different technical risk: modern TLS clients validate the connection name against certificate subject alternative names, not merely that a CA issued the cert. Here the sustained control must address: webhooks are asynchronous network events; integrity, delivery acknowledgements and idempotent processing are separate reliability needs. Choose “Rotate webhook credentials and monitor delivery latency, signature validation and replay protection”.

Question 229

At fictional Coastal Meadow Labs, during a production change postcheck, the operator observes: A batch router update logs identical generic success messages for every device and gives incident responders no affected-host context. Which control best prevents this particular failure from recurring?

  1. Add injection regression tests and prohibit unmanaged shell execution in network automation services.
  2. Define subscription-path ownership, freshness objectives and collector loss alarms for critical operational signals.
  3. Enforce a shared structured-event schema and test correlation queries during pipeline acceptance.
  4. Include cross-tenant and privilege-escalation negative tests in API CI and audit privileged access decisions.

Explanation

Correct Answer

C:

Enforce a shared structured-event schema and test correlation queries during pipeline acceptance. This prevents the recurrence because an effective logging architecture uses consistent machine-readable context and common correlation fields across distributed jobs. A matching immediate correction is: Emit structured events with timestamp, device identity, change ID, severity, stage and outcome to the central log destination.

Incorrect Answers

A:

This routine guards against another mechanism: untrusted input can cross command or configuration boundaries; validation and safe APIs prevent injection into privileged operations. The recurring exposure in the current case is: an effective logging architecture uses consistent machine-readable context and common correlation fields across distributed jobs. The matching preventive check is “Enforce a shared structured-event schema and test correlation queries during pipeline acceptance”.

B:

The suggested review tracks a different technical risk: model-driven telemetry publishes structured device state using subscribed paths and collection modes rather than relying only on slow polling. Here the sustained control must address: an effective logging architecture uses consistent machine-readable context and common correlation fields across distributed jobs. Choose “Enforce a shared structured-event schema and test correlation queries during pipeline acceptance”.

D:

This routine guards against another mechanism: authentication proves identity but each network resource action requires separate policy-based authorization controls. The recurring exposure in the current case is: an effective logging architecture uses consistent machine-readable context and common correlation fields across distributed jobs. The matching preventive check is “Enforce a shared structured-event schema and test correlation queries during pipeline acceptance”.

Question 230

During a production change postcheck at fictional Marble Bay Software, the change record states: Branch controllers send syslog with inconsistent clocks and the SOC cannot order a sequence of ACL policy events. Which control best prevents this particular failure from recurring?

  1. Require least-privilege service identities, secret scans, expiration alerts and rotation rehearsal.
  2. Automate private-key permission checks, key rotation and credential scanning in certificate deployment workflows.
  3. Monitor clock skew, log forwarding errors and collector persistence capacity.
  4. Add injection regression tests and prohibit unmanaged shell execution in network automation services.

Explanation

Correct Answer

C:

Monitor clock skew, log forwarding errors and collector persistence capacity. This prevents the recurrence because distributed troubleshooting requires durable transport and consistent time context; ephemeral local logs can be lost or misordered. A matching immediate correction is: Synchronize clocks and ship logs to a durable centralized destination with appropriate secure, reliable transport.

Incorrect Answers

A:

The suggested review tracks a different technical risk: hardcoded secrets create persistent exposure and excessive authority; runtime secret retrieval limits both lifetime and access scope. Here the sustained control must address: distributed troubleshooting requires durable transport and consistent time context; ephemeral local logs can be lost or misordered. Choose “Monitor clock skew, log forwarding errors and collector persistence capacity”.

B:

That safeguard is relevant to: cA-signed certificates are public trust assertions but the associated private key must remain confidential for endpoint authentication. The current failure instead follows from: distributed troubleshooting requires durable transport and consistent time context; ephemeral local logs can be lost or misordered. Its prevention measure is “Monitor clock skew, log forwarding errors and collector persistence capacity”.

D:

The suggested review tracks a different technical risk: untrusted input can cross command or configuration boundaries; validation and safe APIs prevent injection into privileged operations. Here the sustained control must address: distributed troubleshooting requires durable transport and consistent time context; ephemeral local logs can be lost or misordered. Choose “Monitor clock skew, log forwarding errors and collector persistence capacity”.