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 53

Question 520

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 engineer change first to resolve this specific issue?

  1. Treat retrieved logs as untrusted data and enforce instruction hierarchy and independent tool permissions outside the model.
  2. Check AI conclusions against fresh independent device and controller evidence with explicit freshness and confidence rules.
  3. Require citation to a compatible authoritative reference and fail closed or escalate when command syntax or device version is uncertain.
  4. Authenticate each MCP client, authorize its tool calls by tenant identity and isolate credential/session context.

Explanation

Correct Answer

A:

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. Applied here, the relevant facts are: A network incident log contains attacker-controlled text saying ignore safety checks and run a destructive router command, and the agent obeys it. The question asks what should the engineer change first to resolve this specific issue.

Incorrect Answers

B:

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”.

C:

The offered action targets: model fluency is not evidence of device capability; uncertain technical recommendations require explicit verification before action. 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:

This alternative is a response to another technical cause: an MCP server is an integration boundary and must not treat model-selected identity strings as verified security credentials. 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 “Treat retrieved logs as untrusted data and enforce instruction hierarchy and independent tool permissions outside the model”.

Question 521

While investigating a network policy migration for fictional Cedarbridge Care Systems, the team reports: A Cisco management API returns 202 Accepted for a network provisioning job but the caller reports success before the job completes. What technical evidence should be required before closing this change?

  1. The job records successes and failures by device, retries only supported transient cases, and does not claim full success when any target fails.
  2. The preflight confirms the required module and revision per target, or marks incompatible devices without making changes.
  3. A simulated nonresponsive endpoint times out within the declared bound and produces a per-device failure record without blocking others.
  4. The change record captures the final completed task status and verifies resulting network configuration rather than only the HTTP submission response.

Explanation

Correct Answer

D:

The change record captures the final completed task status and verifies resulting network configuration rather than only the HTTP submission response. This directly verifies the related correction: Poll the returned operation resource with bounded intervals and timeout until a terminal success or failure state is observed. It checks the technical distinction: HTTP 202 signals accepted asynchronous processing, not completion of the requested configuration change.

Incorrect Answers

A:

The alternative verifies a different condition: This directly verifies the related correction: Handle per-target HTTP, parsing and retryable exceptions and persist a failure summary without misreporting completed targets. The current case instead depends on: This directly verifies the related correction: Poll the returned operation resource with bounded intervals and timeout until a terminal success or failure state is observed. Confirm that “The change record captures the final completed task status and verifies resulting network configuration rather than only the HTTP submission response”.

B:

That test belongs to another control with this basis: This directly verifies the related correction: Discover supported YANG modules or capabilities before using module-specific RESTCONF data paths, and branch for supported models. In the current case, the governing reason is: This directly verifies the related correction: Poll the returned operation resource with bounded intervals and timeout until a terminal success or failure state is observed. The direct verification is “The change record captures the final completed task status and verifies resulting network configuration rather than only the HTTP submission response”.

C:

This observation would test a different technical dependency: This directly verifies the related correction: Set explicit connect and read timeouts and catch the resulting exceptions so the worker can report and continue safely. The current issue is governed by: This directly verifies the related correction: Poll the returned operation resource with bounded intervals and timeout until a terminal success or failure state is observed. Its decisive check is “The change record captures the final completed task status and verifies resulting network configuration rather than only the HTTP submission response”.

Question 522

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. What mechanism is most directly responsible for these symptoms?

  1. pyATS can learn and compare device operational state to detect unintended network effects beyond text config diffs.
  2. An effective logging architecture uses consistent machine-readable context and common correlation fields across distributed jobs.
  3. Streaming telemetry pipelines have collectors, transports, ingestion queues and storage capacity that can fail independently of device subscriptions.
  4. Latency and retry failures require timing context and per-attempt telemetry; an aggregate success percentage is insufficient.

Explanation

Correct Answer

B:

An effective logging architecture uses consistent machine-readable context and common correlation fields across distributed jobs. The corresponding repair is: Emit structured events with timestamp, device identity, change ID, severity, stage and outcome to the central log destination. Acceptance should show: An incident query joins all deployment events by change ID and identifies the failed device and pipeline stage. Applied here, the relevant facts are: A batch router update logs identical generic success messages for every device and gives incident responders no affected-host context. The question asks what mechanism is most directly responsible for these symptoms.

Incorrect Answers

A:

The offered statement is true for this other mechanism: The corresponding repair is: Capture structured prechange operational state with pyATS, apply the change, then compare relevant postchange state and assert expected invariants. It does not explain the facts described here, which follow from: The corresponding repair is: Emit structured events with timestamp, device identity, change ID, severity, stage and outcome to the central log destination.

C:

The corresponding repair is: Introduce bounded buffering, backpressure monitoring and horizontal ingestion capacity with visible gap or loss reporting. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Emit structured events with timestamp, device identity, change ID, severity, stage and outcome to the central log destination.

D:

The offered statement is true for this other mechanism: The corresponding repair is: Capture per-request endpoint, duration, timeout class, retry attempt and status while preserving sensitive data redaction. It does not explain the facts described here, which follow from: The corresponding repair is: Emit structured events with timestamp, device identity, change ID, severity, stage and outcome to the central log destination.

Question 523

During a network policy migration at fictional Cobalt Ridge Bank, the change record states: A network automation CLI accepts an untrusted interface name and produces a malformed URL or targets a forbidden interface. 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. Terraform compares configuration, recorded state and provider observations to compute a proposed change set before apply.
  3. Model-driven APIs are available only for modules and revisions implemented by the device software, not by the client library alone.
  4. API clients must validate human and external inputs independently of server-side validation to avoid unsafe or unintended changes.

Explanation

Correct Answer

D:

API clients must validate human and external inputs independently of server-side validation to avoid unsafe or unintended changes. The corresponding repair is: Validate typed inputs, authorized resource scopes and ranges before constructing API requests, then encode parameters safely. Acceptance should show: Invalid IDs are rejected before any outbound request and valid values produce correctly encoded resource targets.

Incorrect Answers

A:

This principle describes a separate cause: The corresponding repair is: Choose a supported targeted PATCH or edit operation for partial changes and reserve PUT for intentionally replacing the resource representation. The reported condition is governed by: The corresponding repair is: Validate typed inputs, authorized resource scopes and ranges before constructing API requests, then encode parameters safely. The two mechanisms should not be conflated.

B:

The corresponding repair is: Refresh managed state and review a generated Terraform plan before applying only the intended network changes. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Validate typed inputs, authorized resource scopes and ranges before constructing API requests, then encode parameters safely.

C:

The offered statement is true for this other mechanism: The corresponding repair is: Discover supported YANG modules or capabilities before using module-specific RESTCONF data paths, and branch for supported models. It does not explain the facts described here, which follow from: The corresponding repair is: Validate typed inputs, authorized resource scopes and ranges before constructing API requests, then encode parameters safely.

Question 524

At fictional Cedarbridge Care Systems, during a campus API automation rollout, the operator observes: A Python script interpolates unvalidated user-provided VLAN IDs into device requests and submits values outside approved range. Which engineering principle explains the described system behavior?

  1. Cross-platform automation benefits from a shared intent model but must translate differences in native device APIs and models.
  2. API clients must validate human and external inputs independently of server-side validation to avoid unsafe or unintended changes.
  3. HTTP PUT represents replacement semantics for a targeted RESTCONF resource, whereas PATCH supports partial edits under the applicable media type.
  4. Low-code accelerates common supported integrations but may constrain complex branching and custom transaction semantics.

Explanation

Correct Answer

B:

API clients must validate human and external inputs independently of server-side validation to avoid unsafe or unintended changes. The corresponding repair is: Validate typed inputs, authorized resource scopes and ranges before constructing API requests, then encode parameters safely. Acceptance should show: Invalid IDs are rejected before any outbound request and valid values produce correctly encoded resource targets. Applied here, the relevant facts are: A Python script interpolates unvalidated user-provided VLAN IDs into device requests and submits values outside approved range. The question asks which engineering principle explains the described system behavior.

Incorrect Answers

A:

The corresponding repair is: Use inventory capability detection and platform-specific adapters behind a common validated intent model. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Validate typed inputs, authorized resource scopes and ranges before constructing API requests, then encode parameters safely.

C:

This principle describes a separate cause: The corresponding repair is: Choose a supported targeted PATCH or edit operation for partial changes and reserve PUT for intentionally replacing the resource representation. The reported condition is governed by: The corresponding repair is: Validate typed inputs, authorized resource scopes and ranges before constructing API requests, then encode parameters safely. The two mechanisms should not be conflated.

D:

The corresponding repair is: Match workflow complexity, vendor connector capability and error recovery needs to low-code or custom application design after a capability pilot. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Validate typed inputs, authorized resource scopes and ranges before constructing API requests, then encode parameters safely.

Question 525

While investigating a network policy migration for fictional Cedarbridge Care Systems, the team reports: A RESTCONF PATCH request sends a bare CLI string as JSON and the IOS XE server rejects it as malformed model data. What ongoing engineering assurance should follow the successful fix?

  1. Exercise representative 4xx, 5xx, timeout and malformed-payload cases in contract tests before scheduling batches.
  2. Require validated backups, staged batches and executable rollback procedures in approved network playbooks.
  3. Add multi-page integration tests and monitor continuation tokens and retrieved counts on every scheduled inventory run.
  4. Validate request headers, YANG schemas and sample GET/PATCH transactions in a lab before device-wide rollout.

Explanation

Correct Answer

D:

Validate request headers, YANG schemas and sample GET/PATCH transactions in a lab before device-wide rollout. This prevents the recurrence because rESTCONF manipulates YANG-defined resources over HTTP; both resource paths and payload media encoding must match the model. A matching immediate correction is: Build the request body from the correct YANG data node and use application/yang-data+json with valid RESTCONF resource paths.

Incorrect Answers

A:

That safeguard is relevant to: robust batch automation isolates errors at the per-resource boundary and retains auditable partial outcomes. The current failure instead follows from: rESTCONF manipulates YANG-defined resources over HTTP; both resource paths and payload media encoding must match the model. Its prevention measure is “Validate request headers, YANG schemas and sample GET/PATCH transactions in a lab before device-wide rollout”.

B:

This routine guards against another mechanism: safe network automation separates preflight, controlled deployment, verification and recovery instead of assuming all endpoints will succeed. The recurring exposure in the current case is: rESTCONF manipulates YANG-defined resources over HTTP; both resource paths and payload media encoding must match the model. The matching preventive check is “Validate request headers, YANG schemas and sample GET/PATCH transactions in a lab before device-wide rollout”.

C:

The suggested review tracks a different technical risk: many platform APIs paginate large result sets; the first HTTP success response may contain only a subset. Here the sustained control must address: rESTCONF manipulates YANG-defined resources over HTTP; both resource paths and payload media encoding must match the model. Choose “Validate request headers, YANG schemas and sample GET/PATCH transactions in a lab before device-wide rollout”.

Question 526

At fictional Violet Ridge Resorts, an acceptance review of a version-control hotfix finds: A support operator attempts to inspect a historical release while untracked temporary config overlays contaminate the working directory. Which result most directly verifies that the proposed correction worked?

  1. The merged file has no conflict markers, passes schema tests and retains the intended requirements from both branches.
  2. The protected target branch contains one reviewed release commit whose diff matches the approved feature changes.
  3. GitLab deployment records show the canary passed before other sites changed, and credentials cannot access unrelated workspaces.
  4. The working tree reports the intended revision and no uncommitted cross-branch edits before test execution.

Explanation

Correct Answer

D:

The working tree reports the intended revision and no uncommitted cross-branch edits before test execution. This directly verifies the related correction: Safely stash or commit unrelated work and check out the intended branch or detached revision in a clean worktree. It checks the technical distinction: Git checkout can change branch and working-tree files; uncommitted modifications must be managed to avoid accidental mixing. Applied here, the relevant facts are: A support operator attempts to inspect a historical release while untracked temporary config overlays contaminate the working directory. The question asks which result most directly verifies that the proposed correction worked.

Incorrect Answers

A:

This alternative is a response to another technical cause: This directly verifies the related correction: Resolve the conflicting lines deliberately against the approved desired network state, run validation, then commit the merged result. The reported case instead depends on: This directly verifies the related correction: Safely stash or commit unrelated work and check out the intended branch or detached revision in a clean worktree. The action that directly addresses it is “The working tree reports the intended revision and no uncommitted cross-branch edits before test execution”.

B:

The proposed action belongs to the mechanism: This directly verifies the related correction: Use an approved squash merge to combine reviewed feature changes into one commit while preserving the final content. Here the stated fault follows a different mechanism: This directly verifies the related correction: Safely stash or commit unrelated work and check out the intended branch or detached revision in a clean worktree. The corrective choice is “The working tree reports the intended revision and no uncommitted cross-branch edits before test execution”.

C:

The offered action targets: This directly verifies the related correction: Deploy through bounded environment-scoped jobs with approved service credentials and staged canary or batch rollout. The case facts point instead to: This directly verifies the related correction: Safely stash or commit unrelated work and check out the intended branch or detached revision in a clean worktree. Implement “The working tree reports the intended revision and no uncommitted cross-branch edits before test execution” to address that specific condition.

Question 527

During a GitLab deployment pipeline rehearsal at fictional Seabright Learning, the change record states: An engineer adds every file to the index, including a generated device backup that must not be included in a Git commit. Which control best prevents this particular failure from recurring?

  1. Add secret scanning and explicit staged-diff review before committing automation changes.
  2. Generate payload fixtures from reviewed YANG modules and test schema validation before any live update.
  3. Promote immutable build artifacts between GitLab stages instead of rebuilding from moving branches.
  4. Use reproducible lockfiles, container digest pinning and scheduled compatibility tests before updating dependencies.

Explanation

Correct Answer

A:

Add secret scanning and explicit staged-diff review before committing automation changes. This prevents the recurrence because the Git index is the staging area and can be changed independently of the working tree by suitable reset modes. A matching immediate correction is: Unstage the unintended file with an index-only reset or equivalent restore-staged operation, leaving the worktree intact. Applied here, the relevant facts are: An engineer adds every file to the index, including a generated device backup that must not be included in a Git commit. The question asks which control best prevents this particular failure from recurring.

Incorrect Answers

B:

That safeguard is relevant to: yANG defines node hierarchy, namespaces, list keys and data types; conforming JSON must preserve that structure. The current failure instead follows from: the Git index is the staging area and can be changed independently of the working tree by suitable reset modes. Its prevention measure is “Add secret scanning and explicit staged-diff review before committing automation changes”.

C:

This routine guards against another mechanism: a CI build stage turns source and fixed dependencies into a traceable deployment input used by later stages. The recurring exposure in the current case is: the Git index is the staging area and can be changed independently of the working tree by suitable reset modes. The matching preventive check is “Add secret scanning and explicit staged-diff review before committing automation changes”.

D:

The suggested review tracks a different technical risk: unbounded dependency upgrades can introduce incompatible APIs and nondeterministic CI failures even when repository code is unchanged. Here the sustained control must address: the Git index is the staging area and can be changed independently of the working tree by suitable reset modes. Choose “Add secret scanning and explicit staged-diff review before committing automation changes”.

Question 528

During a production change postcheck at fictional Marble Bay Software, the change record states: An internal network automation API checks that users are logged in but does not verify which device groups they are permitted to change. Which engineering principle explains the described system behavior?

  1. CA-signed certificates are public trust assertions but the associated private key must remain confidential for endpoint authentication.
  2. Latency and retry failures require timing context and per-attempt telemetry; an aggregate success percentage is insufficient.
  3. HTTP 401 generally signals missing or invalid authentication while 403 indicates access denied to an authenticated request.
  4. Authentication proves identity but each network resource action requires separate policy-based authorization controls.

Explanation

Correct Answer

D:

Authentication proves identity but each network resource action requires separate policy-based authorization controls. The corresponding repair is: Enforce server-side per-resource authorization using authenticated identity and approved tenant or device scope. Acceptance should show: Cross-tenant modification attempts are rejected with a denial and approved users can change only authorized resources.

Incorrect Answers

A:

That test belongs to another control with this basis: The corresponding repair is: Generate and store private keys in restricted secret systems and deploy only to the authorized TLS termination endpoint. In the current case, the governing reason is: The corresponding repair is: Enforce server-side per-resource authorization using authenticated identity and approved tenant or device scope. The direct verification is “Authentication proves identity but each network resource action requires separate policy-based authorization controls”.

B:

This observation would test a different technical dependency: The corresponding repair is: Capture per-request endpoint, duration, timeout class, retry attempt and status while preserving sensitive data redaction. The current issue is governed by: The corresponding repair is: Enforce server-side per-resource authorization using authenticated identity and approved tenant or device scope. Its decisive check is “Authentication proves identity but each network resource action requires separate policy-based authorization controls”.

C:

The alternative verifies a different condition: The corresponding repair is: Classify authentication failures and authorization denials separately, then correct token validity or RBAC scope accordingly. The current case instead depends on: The corresponding repair is: Enforce server-side per-resource authorization using authenticated identity and approved tenant or device scope. Confirm that “Authentication proves identity but each network resource action requires separate policy-based authorization controls”.

Question 529

At fictional Westlake Biomedicine, an acceptance review of a FastMCP security review finds: An AI assistant suggests that a particular VLAN is unused, but it bases the claim on incomplete cached controller telemetry. Which sustainable preventive control most directly avoids a recurrence?

  1. Track evidence freshness and require independent observed-state corroboration for high-impact AI advice.
  2. Mark generated code for extra negative tests and prohibit bypassing deployment gates based on model confidence.
  3. Red-team retrieval inputs and enforce hard tool allowlists and approvals independent of prompt wording.
  4. Review FastMCP tool schemas, allowed methods, output redaction and per-device access before agent connection.

Explanation

Correct Answer

A:

Track evidence freshness and require independent observed-state corroboration for high-impact AI advice. This prevents the recurrence because aI recommendations are hypotheses requiring external ground truth; absent evidence is not proof of a network condition. A matching immediate correction is: Check AI conclusions against fresh independent device and controller evidence with explicit freshness and confidence rules. Applied here, the relevant facts are: An AI assistant suggests that a particular VLAN is unused, but it bases the claim on incomplete cached controller telemetry. The question asks which sustainable preventive control most directly avoids a recurrence.

Incorrect Answers

B:

The suggested review tracks a different technical risk: generative systems can propose plausible-looking but incorrect commands; independent executable validation is required for safe infrastructure changes. Here the sustained control must address: aI recommendations are hypotheses requiring external ground truth; absent evidence is not proof of a network condition. Choose “Track evidence freshness and require independent observed-state corroboration for high-impact AI advice”.

C:

That safeguard is relevant to: prompt injection attempts to convert lower-trust retrieved content into high-priority instructions across an AI-agent trust boundary. The current failure instead follows from: aI recommendations are hypotheses requiring external ground truth; absent evidence is not proof of a network condition. Its prevention measure is “Track evidence freshness and require independent observed-state corroboration for high-impact AI advice”.

D:

This routine guards against another mechanism: an MCP server publishes structured tools and resources to clients; safe network use requires explicit least-privilege tool definitions. The recurring exposure in the current case is: aI recommendations are hypotheses requiring external ground truth; absent evidence is not proof of a network condition. The matching preventive check is “Track evidence freshness and require independent observed-state corroboration for high-impact AI advice”.

Question 530

During a production change postcheck at fictional Marble Bay Software, the change record states: An engineer approves an OSPF automation change after configuration diff alone even though neighbor states have changed unexpectedly. Which control best prevents this particular failure from recurring?

  1. Collect bounded latency histograms, timeout reason labels and retry budgets for critical controller calls.
  2. Add typed error classification and separate authorization and authentication runbooks to API clients.
  3. Version baseline snapshots and specify per-feature allowed changes rather than requiring exact equality for volatile counters.
  4. Require least-privilege service identities, secret scans, expiration alerts and rotation rehearsal.

Explanation

Correct Answer

C:

Version baseline snapshots and specify per-feature allowed changes rather than requiring exact equality for volatile counters. This prevents the recurrence because pyATS can learn and compare device operational state to detect unintended network effects beyond text config diffs. A matching immediate correction is: Capture structured prechange operational state with pyATS, apply the change, then compare relevant postchange state and assert expected invariants.

Incorrect Answers

A:

The alternative verifies a different condition: latency and retry failures require timing context and per-attempt telemetry; an aggregate success percentage is insufficient. The current case instead depends on: pyATS can learn and compare device operational state to detect unintended network effects beyond text config diffs. Confirm that “Version baseline snapshots and specify per-feature allowed changes rather than requiring exact equality for volatile counters”.

B:

That test belongs to another control with this basis: hTTP 401 generally signals missing or invalid authentication while 403 indicates access denied to an authenticated request. In the current case, the governing reason is: pyATS can learn and compare device operational state to detect unintended network effects beyond text config diffs. The direct verification is “Version baseline snapshots and specify per-feature allowed changes rather than requiring exact equality for volatile counters”.

D:

The alternative verifies a different condition: hardcoded secrets create persistent exposure and excessive authority; runtime secret retrieval limits both lifetime and access scope. The current case instead depends on: pyATS can learn and compare device operational state to detect unintended network effects beyond text config diffs. Confirm that “Version baseline snapshots and specify per-feature allowed changes rather than requiring exact equality for volatile counters”.