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 8

Question 70

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

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

Explanation

Correct Answer

D:

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

Incorrect Answers

A:

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

B:

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

C:

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

Question 71

During a conversational network agent pilot at fictional Westlake Biomedicine, the change record states: A FastMCP network information tool accepts an arbitrary device identifier and forwards it directly into a privileged shell expression. Which implementation action best meets the observed technical requirement?

  1. Separate read-only diagnostic tools from mutating tools and require an explicit scoped approval step before any privileged operation.
  2. Define typed, validated tool arguments with explicit device allowlists and reject invalid or unauthorized inputs at the server boundary.
  3. Check AI conclusions against fresh independent device and controller evidence with explicit freshness and confidence rules.
  4. Bind current request context to fresh authorized inventory and explicit tenant or device selection before tool calls.

Explanation

Correct Answer

B:

Define typed, validated tool arguments with explicit device allowlists and reject invalid or unauthorized inputs at the server boundary. This addresses the problem because typed MCP tool schemas improve interoperability but server-side validation remains necessary even for a well-formed client call. Confirm success using: Malformed IDs and cross-tenant requests are rejected predictably while approved tool calls return scoped data.

Incorrect Answers

A:

The proposed action belongs to the mechanism: agent tool chaining can enlarge the blast radius of an ambiguous user instruction unless execution permissions are independently gated. Here the stated fault follows a different mechanism: typed MCP tool schemas improve interoperability but server-side validation remains necessary even for a well-formed client call. The corrective choice is “Define typed, validated tool arguments with explicit device allowlists and reject invalid or unauthorized inputs at the server boundary”.

C:

This alternative is a response to another technical cause: aI recommendations are hypotheses requiring external ground truth; absent evidence is not proof of a network condition. The reported case instead depends on: typed MCP tool schemas improve interoperability but server-side validation remains necessary even for a well-formed client call. The action that directly addresses it is “Define typed, validated tool arguments with explicit device allowlists and reject invalid or unauthorized inputs at the server boundary”.

D:

The proposed action belongs to the mechanism: 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: typed MCP tool schemas improve interoperability but server-side validation remains necessary even for a well-formed client call. The corrective choice is “Define typed, validated tool arguments with explicit device allowlists and reject invalid or unauthorized inputs at the server boundary”.

Question 72

During a remote branch provisioning pilot at fictional Northshore Cloud, the change record states: A team declares an existing production VLAN as a new Terraform resource and an apply attempts to create a duplicate object. Which implementation action best meets the observed technical requirement?

  1. Choose a supported declarative IaC framework for persistent desired configuration and targeted scripts for bounded imperative queries or integrations.
  2. Perform per-device reachability and capability prechecks, capture backups, and stop or roll back on failed postchecks.
  3. Import the existing platform object into Terraform state, align its configuration and inspect a non-destructive plan.
  4. Use the supported token refresh flow with secret storage and distinguish unauthenticated 401 from authorized-but-forbidden 403 responses.

Explanation

Correct Answer

C:

Import the existing platform object into Terraform state, align its configuration and inspect a non-destructive plan. This addresses the problem because terraform configuration alone does not establish ownership of an already-existing platform object; state import binds it to a resource address. Confirm success using: The imported resource maps to the intended live identifier and the reviewed plan does not attempt duplicate creation or replacement.

Incorrect Answers

A:

The offered action targets: infrastructure as code, low-code workflows and custom software solve different state-lifecycle and integration needs. The case facts point instead to: terraform configuration alone does not establish ownership of an already-existing platform object; state import binds it to a resource address. Implement “Import the existing platform object into Terraform state, align its configuration and inspect a non-destructive plan” to address that specific condition.

B:

This alternative is a response to another technical cause: safe network automation separates preflight, controlled deployment, verification and recovery instead of assuming all endpoints will succeed. The reported case instead depends on: terraform configuration alone does not establish ownership of an already-existing platform object; state import binds it to a resource address. The action that directly addresses it is “Import the existing platform object into Terraform state, align its configuration and inspect a non-destructive plan”.

D:

The offered action targets: an access-token lifecycle and authorization scope are distinct concerns; repeated reuse of expired or insufficient tokens cannot resolve them. The case facts point instead to: terraform configuration alone does not establish ownership of an already-existing platform object; state import binds it to a resource address. Implement “Import the existing platform object into Terraform state, align its configuration and inspect a non-destructive plan” to address that specific condition.

Question 73

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

  1. Use protected environments, least-privilege deploy tokens and progressive rollout approval conditions.
  2. Enforce unique device IDs, provenance and reconciliation reports for source-of-truth integrations.
  3. Include negative tests for out-of-range values, missing keys and incorrect scalar types in model-driven build gates.
  4. Record source commit IDs, test cross-branch compatibility and review cherry-pick conflict resolutions.

Explanation

Correct Answer

B:

Enforce unique device IDs, provenance and reconciliation reports for source-of-truth integrations. This prevents the recurrence because a source of truth provides desired canonical inventory, but consumers must resolve identity correctly and reconcile discrepancies. A matching immediate correction is: Use stable authoritative device identifiers and reconcile observed inventory to the source-of-truth records before deployment.

Incorrect Answers

A:

This routine guards against another mechanism: a deployment stage should enforce release scope and approval, not merely execute a command with unrestricted infrastructure access. The recurring exposure in the current case is: a source of truth provides desired canonical inventory, but consumers must resolve identity correctly and reconcile discrepancies. The matching preventive check is “Enforce unique device IDs, provenance and reconciliation reports for source-of-truth integrations”.

C:

That safeguard is relevant to: model-based configuration encoding is constrained by YANG leaf types, ranges and required list keys, not arbitrary YAML structure. The current failure instead follows from: a source of truth provides desired canonical inventory, but consumers must resolve identity correctly and reconcile discrepancies. Its prevention measure is “Enforce unique device IDs, provenance and reconciliation reports for source-of-truth integrations”.

D:

This routine guards against another mechanism: git cherry-pick applies the change introduced by selected commit(s) onto the current branch, creating new history in that branch. The recurring exposure in the current case is: a source of truth provides desired canonical inventory, but consumers must resolve identity correctly and reconcile discrepancies. The matching preventive check is “Enforce unique device IDs, provenance and reconciliation reports for source-of-truth integrations”.

Question 74

During an AI recommendation accuracy study at fictional Amberlight Energy, the change record states: A chatbot ingests a device syslog message that impersonates a system instruction and escalates the bot to a privileged configuration tool. Which engineering principle explains the described system behavior?

  1. An MCP server publishes structured tools and resources to clients; safe network use requires explicit least-privilege tool definitions.
  2. Agent tool chaining can enlarge the blast radius of an ambiguous user instruction unless execution permissions are independently gated.
  3. Typed MCP tool schemas improve interoperability but server-side validation remains necessary even for a well-formed client call.
  4. Prompt injection attempts to convert lower-trust retrieved content into high-priority instructions across an AI-agent trust boundary.

Explanation

Correct Answer

D:

Prompt injection attempts to convert lower-trust retrieved content into high-priority instructions across an AI-agent trust boundary. The corresponding repair is: Treat retrieved logs as untrusted data and enforce instruction hierarchy and independent tool permissions outside the model. Acceptance should show: Injection test logs are summarized as evidence but never cause unauthorized configuration or secret-retrieval tool calls.

Incorrect Answers

A:

The corresponding repair is: Expose narrowly scoped typed read-only FastMCP tools for approved device and status fields with controlled access. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Treat retrieved logs as untrusted data and enforce instruction hierarchy and independent tool permissions outside the model.

B:

The offered statement is true for this other mechanism: The corresponding repair is: Separate read-only diagnostic tools from mutating tools and require an explicit scoped approval step before any privileged operation. It does not explain the facts described here, which follow from: The corresponding repair is: Treat retrieved logs as untrusted data and enforce instruction hierarchy and independent tool permissions outside the model.

C:

This principle describes a separate cause: The corresponding repair is: Define typed, validated tool arguments with explicit device allowlists and reject invalid or unauthorized inputs at the server boundary. The reported condition is governed by: The corresponding repair is: Treat retrieved logs as untrusted data and enforce instruction hierarchy and independent tool permissions outside the model. The two mechanisms should not be conflated.

Question 75

While investigating a source-of-truth integration for fictional Willowfield Hospitality, the team reports: A lab test succeeds only because the CML topology omits an actual branch transit link where routing loops occur. Which result most directly verifies that the proposed correction worked?

  1. Lab simulation reproduces the known routing dependency and the candidate change passes normal and failure scenarios.
  2. The runner resolves the reviewed versions and integration tests pass consistently across repeated clean builds.
  3. The Compose deployment starts required backends and the worker reaches ready state even when a dependency starts slowly.
  4. The payload validates against the YANG schema and the RESTCONF server accepts the exact intended interface resource.

Explanation

Correct Answer

A:

Lab simulation reproduces the known routing dependency and the candidate change passes normal and failure scenarios. This directly verifies the related correction: Model the relevant links, routing peers and failure cases in CML rather than only a minimal happy-path device. It checks the technical distinction: Simulation usefulness depends on modeled network dependencies; an incomplete topology cannot validate omitted behaviors.

Incorrect Answers

B:

This alternative is a response to another technical cause: This directly verifies the related correction: Pin compatible build tool and package versions, update the lockfile and test upgrades in a separate controlled pipeline. The reported case instead depends on: This directly verifies the related correction: Model the relevant links, routing peers and failure cases in CML rather than only a minimal happy-path device. The action that directly addresses it is “Lab simulation reproduces the known routing dependency and the candidate change passes normal and failure scenarios”.

C:

The proposed action belongs to the mechanism: This directly verifies the related correction: Define service dependencies with appropriate health checks and resilient application startup or retry behavior. Here the stated fault follows a different mechanism: This directly verifies the related correction: Model the relevant links, routing peers and failure cases in CML rather than only a minimal happy-path device. The corrective choice is “Lab simulation reproduces the known routing dependency and the candidate change passes normal and failure scenarios”.

D:

The offered action targets: This directly verifies the related correction: Construct JSON using the published YANG container hierarchy, qualified node names and correct value types. The case facts point instead to: This directly verifies the related correction: Model the relevant links, routing peers and failure cases in CML rather than only a minimal happy-path device. Implement “Lab simulation reproduces the known routing dependency and the candidate change passes normal and failure scenarios” to address that specific condition.

Question 76

During a conversational network agent pilot at fictional Westlake Biomedicine, the change record states: An AI network diagnostic tool receives a malicious API description instructing it to send secrets to an external webhook. What mechanism is most directly responsible for these symptoms?

  1. Tool wrappers must preserve the meaning of missing, stale and failed data for the consumer agent.
  2. Tool results are untrusted external input; unrestricted outbound connectivity turns an injected instruction into a data-exfiltration path.
  3. Conversation memory is not authoritative network state; stale context and scope leakage create wrong-target operational risk.
  4. High aggregate answer accuracy can hide safety-critical errors; validation must measure behavior on representative failure modes.

Explanation

Correct Answer

B:

Tool results are untrusted external input; unrestricted outbound connectivity turns an injected instruction into a data-exfiltration path. The corresponding repair is: Restrict tool egress to approved destinations and never grant untrusted retrieved text authority to choose exfiltration endpoints. Acceptance should show: A simulated malicious tool response cannot trigger outbound requests to unapproved destinations or reveal hidden credentials.

Incorrect Answers

A:

This principle describes a separate cause: The corresponding repair is: Return structured success and error states with source timestamps and bounded API timeouts rather than silently substituting empty values. The reported condition is governed by: The corresponding repair is: Restrict tool egress to approved destinations and never grant untrusted retrieved text authority to choose exfiltration endpoints. The two mechanisms should not be conflated.

C:

The offered statement is true for this other mechanism: The corresponding repair is: Bind current request context to fresh authorized inventory and explicit tenant or device selection before tool calls. It does not explain the facts described here, which follow from: The corresponding repair is: Restrict tool egress to approved destinations and never grant untrusted retrieved text authority to choose exfiltration endpoints.

D:

This principle describes a separate cause: The corresponding repair is: Evaluate the agent on a representative labeled test set with difficult, adversarial and negative cases, measuring factual error and unsafe-action rates. The reported condition is governed by: The corresponding repair is: Restrict tool egress to approved destinations and never grant untrusted retrieved text authority to choose exfiltration endpoints. The two mechanisms should not be conflated.

Question 77

During an AI recommendation accuracy study at fictional Amberlight Energy, the change record states: A chatbot ingests a device syslog message that impersonates a system instruction and escalates the bot to a privileged configuration tool. What is the appropriate response to this network automation condition?

  1. Authenticate each MCP client, authorize its tool calls by tenant identity and isolate credential/session context.
  2. Sanitize inputs and use an approved private or contractually controlled AI service without exposing secrets or regulated network data.
  3. Treat retrieved logs as untrusted data and enforce instruction hierarchy and independent tool permissions outside the model.
  4. Check AI conclusions against fresh independent device and controller evidence with explicit freshness and confidence rules.

Explanation

Correct Answer

C:

Treat retrieved logs as untrusted data and enforce instruction hierarchy and independent tool permissions outside the model. This addresses the problem because prompt injection attempts to convert lower-trust retrieved content into high-priority instructions across an AI-agent trust boundary. Confirm success using: Injection test logs are summarized as evidence but never cause unauthorized configuration or secret-retrieval tool calls.

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 “Treat retrieved logs as untrusted data and enforce instruction hierarchy and independent tool permissions outside the model”.

B:

The offered action targets: aI-assisted code tools may process submitted data outside the intended trust boundary, creating privacy and intellectual-property exposure. 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 “Treat retrieved logs as untrusted data and enforce instruction hierarchy and independent tool permissions outside the model” to address that specific condition.

D:

The proposed action belongs to the mechanism: aI recommendations are hypotheses requiring external ground truth; absent evidence is not proof of a network condition. 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 “Treat retrieved logs as untrusted data and enforce instruction hierarchy and independent tool permissions outside the model”.

Question 78

At fictional Sable Valley Power, during a certificate renewal rehearsal, the operator observes: A controller API call is occasionally slow during large inventory updates, but aggregated success logs hide its tail latency. Which targeted correction best addresses the network automation failure?

  1. Use typed input schema validation, approved resource allowlists and safe library argument interfaces rather than shell concatenation.
  2. Inject short-lived narrowly scoped secrets at runtime from a managed vault and mask them in logs and build artifacts.
  3. Capture per-request endpoint, duration, timeout class, retry attempt and status while preserving sensitive data redaction.
  4. Write semantic pyATS assertions that permit the approved intended change and reject unrelated regressions.

Explanation

Correct Answer

C:

Capture per-request endpoint, duration, timeout class, retry attempt and status while preserving sensitive data redaction. This addresses the problem because latency and retry failures require timing context and per-attempt telemetry; an aggregate success percentage is insufficient. Confirm success using: Correlated traces identify which API operation approaches the timeout threshold and whether backoff reduces the failure rate.

Incorrect Answers

A:

The offered action targets: untrusted input can cross command or configuration boundaries; validation and safe APIs prevent injection into privileged operations. The case facts point instead to: latency and retry failures require timing context and per-attempt telemetry; an aggregate success percentage is insufficient. Implement “Capture per-request endpoint, duration, timeout class, retry attempt and status while preserving sensitive data redaction” to address that specific condition.

B:

This alternative is a response to another technical cause: hardcoded secrets create persistent exposure and excessive authority; runtime secret retrieval limits both lifetime and access scope. The reported case instead depends on: latency and retry failures require timing context and per-attempt telemetry; an aggregate success percentage is insufficient. The action that directly addresses it is “Capture per-request endpoint, duration, timeout class, retry attempt and status while preserving sensitive data redaction”.

D:

The offered action targets: postdeployment validation compares expected invariants and intended deltas, not every volatile or purposely changed value. The case facts point instead to: latency and retry failures require timing context and per-attempt telemetry; an aggregate success percentage is insufficient. Implement “Capture per-request endpoint, duration, timeout class, retry attempt and status while preserving sensitive data redaction” to address that specific condition.

Question 79

At fictional Sable Valley Power, during a certificate renewal rehearsal, the operator observes: A CI pipeline logs static device admin passwords from environment variables at every run and never rotates them. What technical evidence should be required before closing this change?

  1. Centralized logs survive worker replacement and carry timestamps that correlate with device events within the accepted skew.
  2. pyATS comparison shows approved changed values while protected neighbors, interface counters or route counts remain within defined acceptance bounds.
  3. A supported image produces structured parsed data; unsupported output is reported as a test instrumentation error, not a device state failure.
  4. A token rotation test succeeds without image rebuild, and repository, image and logs contain no recoverable credentials.

Explanation

Correct Answer

D:

A token rotation test succeeds without image rebuild, and repository, image and logs contain no recoverable credentials. This directly verifies the related correction: Inject short-lived narrowly scoped secrets at runtime from a managed vault and mask them in logs and build artifacts. It checks the technical distinction: Hardcoded secrets create persistent exposure and excessive authority; runtime secret retrieval limits both lifetime and access scope.

Incorrect Answers

A:

This observation would test a different technical dependency: This directly verifies the related correction: Synchronize clocks and ship logs to a durable centralized destination with appropriate secure, reliable transport. The current issue is governed by: This directly verifies the related correction: Inject short-lived narrowly scoped secrets at runtime from a managed vault and mask them in logs and build artifacts. Its decisive check is “A token rotation test succeeds without image rebuild, and repository, image and logs contain no recoverable credentials”.

B:

The alternative verifies a different condition: 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 current case instead depends on: This directly verifies the related correction: Inject short-lived narrowly scoped secrets at runtime from a managed vault and mask them in logs and build artifacts. Confirm that “A token rotation test succeeds without image rebuild, and repository, image and logs contain no recoverable credentials”.

C:

That test belongs to another control with this basis: This directly verifies the related correction: Validate parser and platform compatibility and distinguish collection or parsing errors from actual network-state assertion failures. In the current case, the governing reason is: This directly verifies the related correction: Inject short-lived narrowly scoped secrets at runtime from a managed vault and mask them in logs and build artifacts. The direct verification is “A token rotation test succeeds without image rebuild, and repository, image and logs contain no recoverable credentials”.

Question 80

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

  1. HTTP PUT represents replacement semantics for a targeted RESTCONF resource, whereas PATCH supports partial edits under the applicable media type.
  2. Automation choice is driven by lifecycle and operational risk rather than by a single preferred programming tool.
  3. YANG distinguishes configuration intent from read-only operational state; successful config writes do not establish runtime protocol health.
  4. A network transport timeout does not prove server-side failure; blind retries of non-idempotent operations can duplicate effects.

Explanation

Correct Answer

D:

A network transport timeout does not prove server-side failure; blind retries of non-idempotent operations can duplicate effects. The corresponding repair is: Before retrying a potentially non-idempotent change, check resulting resource state or use a supported idempotency or operation key. Acceptance should show: An induced response-loss test yields one intended network object or operation and records its final state without duplicate changes.

Incorrect Answers

A:

The corresponding repair is: Choose a supported targeted PATCH or edit operation for partial changes and reserve PUT for intentionally replacing the resource representation. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Before retrying a potentially non-idempotent change, check resulting resource state or use a supported idempotency or operation key.

B:

The offered statement is true for this other mechanism: The corresponding repair is: Select the tool and deployment pattern by risk, state persistence, change scope, rollback capability and approval obligations. It does not explain the facts described here, which follow from: The corresponding repair is: Before retrying a potentially non-idempotent change, check resulting resource state or use a supported idempotency or operation key.

C:

This principle describes a separate cause: The corresponding repair is: Read intended configuration and runtime operational YANG data from their appropriate modeled resources, and write only configurable leaves. The reported condition is governed by: The corresponding repair is: Before retrying a potentially non-idempotent change, check resulting resource state or use a supported idempotency or operation key. The two mechanisms should not be conflated.