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 10

Question 90

At fictional Amberlight Energy, an acceptance review of an AI-assisted code review finds: A generated Ansible task uses a nonexistent Cisco module parameter yet passes a superficial prose review by the engineer. Which engineering principle explains the described system behavior?

  1. Prompt injection attempts to convert lower-trust retrieved content into high-priority instructions across an AI-agent trust boundary.
  2. Typed MCP tool schemas improve interoperability but server-side validation remains necessary even for a well-formed client call.
  3. Generative systems can propose plausible-looking but incorrect commands; independent executable validation is required for safe infrastructure changes.
  4. Conversation memory is not authoritative network state; stale context and scope leakage create wrong-target operational risk.

Explanation

Correct Answer

C:

Generative systems can propose plausible-looking but incorrect commands; independent executable validation is required for safe infrastructure changes. The corresponding repair is: Subject AI-suggested changes to schema and unit tests, simulated network execution, policy checks and human change approval. Acceptance should show: Invalid module parameters or destructive unrelated changes fail the predeployment gates and never reach production devices.

Incorrect Answers

A:

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: Subject AI-suggested changes to schema and unit tests, simulated network execution, policy checks and human change approval.

B:

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: Subject AI-suggested changes to schema and unit tests, simulated network execution, policy checks and human change approval. The two mechanisms should not be conflated.

D:

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: Subject AI-suggested changes to schema and unit tests, simulated network execution, policy checks and human change approval.

Question 91

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 explanation best matches the actual broken dependency?

  1. Prompt injection attempts to convert lower-trust retrieved content into high-priority instructions across an AI-agent trust boundary.
  2. Generative systems can propose plausible-looking but incorrect commands; independent executable validation is required for safe infrastructure changes.
  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

D:

Typed MCP tool schemas improve interoperability but server-side validation remains necessary even for a well-formed client call. The corresponding repair is: Define typed, validated tool arguments with explicit device allowlists and reject invalid or unauthorized inputs at the server boundary. Acceptance should show: Malformed IDs and cross-tenant requests are rejected predictably while approved tool calls return scoped data.

Incorrect Answers

A:

This alternative is a response to another technical cause: The corresponding repair is: Treat retrieved logs as untrusted data and enforce instruction hierarchy and independent tool permissions outside the model. The reported case instead depends on: The corresponding repair is: Define typed, validated tool arguments with explicit device allowlists and reject invalid or unauthorized inputs at the server boundary. The action that directly addresses it is “Typed MCP tool schemas improve interoperability but server-side validation remains necessary even for a well-formed client call”.

B:

The proposed action belongs to the mechanism: The corresponding repair is: Subject AI-suggested changes to schema and unit tests, simulated network execution, policy checks and human change approval. Here the stated fault follows a different mechanism: The corresponding repair is: Define typed, validated tool arguments with explicit device allowlists and reject invalid or unauthorized inputs at the server boundary. The corrective choice is “Typed MCP tool schemas improve interoperability but server-side validation remains necessary even for a well-formed client call”.

C:

The offered action targets: The corresponding repair is: Use AI assistance for bounded drafts and test generation while assigning accountable reviewers and validating facts against approved sources. The case facts point instead to: The corresponding repair is: Define typed, validated tool arguments with explicit device allowlists and reject invalid or unauthorized inputs at the server boundary. Implement “Typed MCP tool schemas improve interoperability but server-side validation remains necessary even for a well-formed client call” to address that specific condition.

Question 92

At fictional Sunrise Aeronautics, during an AI-assisted code review, the operator observes: An AI chat assistant translates free-text "fix routing" into unbounded commands rather than requiring a precise change proposal. What ongoing engineering assurance should follow the successful fix?

  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. Test parameter bounds, tenant authorization and injection input against each FastMCP exposed operation.
  4. Require deterministic schema validation, diff preview and affirmative approval for any mutating conversational action.

Explanation

Correct Answer

D:

Require deterministic schema validation, diff preview and affirmative approval for any mutating conversational action. This prevents the recurrence because lLMs are useful for language interpretation but the execution boundary should accept validated structured intents, not arbitrary prose. A matching immediate correction is: Convert user requests into a typed proposed intent with explicit targets, preconditions and a separate human-approved execution path.

Incorrect Answers

A:

The suggested review tracks a different technical risk: aI recommendations are hypotheses requiring external ground truth; absent evidence is not proof of a network condition. Here the sustained control must address: lLMs are useful for language interpretation but the execution boundary should accept validated structured intents, not arbitrary prose. Choose “Require deterministic schema validation, diff preview and affirmative approval for any mutating conversational action”.

B:

That safeguard is relevant to: generative systems can propose plausible-looking but incorrect commands; independent executable validation is required for safe infrastructure changes. The current failure instead follows from: lLMs are useful for language interpretation but the execution boundary should accept validated structured intents, not arbitrary prose. Its prevention measure is “Require deterministic schema validation, diff preview and affirmative approval for any mutating conversational action”.

C:

This routine guards against another mechanism: typed MCP tool schemas improve interoperability but server-side validation remains necessary even for a well-formed client call. The recurring exposure in the current case is: lLMs are useful for language interpretation but the execution boundary should accept validated structured intents, not arbitrary prose. The matching preventive check is “Require deterministic schema validation, diff preview and affirmative approval for any mutating conversational action”.

Question 93

While investigating a FastMCP security review for fictional Elmcrest Theatre, the team reports: An MCP agent sends malformed VLAN filters and the tool silently falls back to querying every tenant's configuration. What ongoing engineering assurance should follow the successful fix?

  1. Test parameter bounds, tenant authorization and injection input against each FastMCP exposed operation.
  2. Require provenance review, software composition analysis and approved dependencies for generated network automation components.
  3. Red-team retrieval inputs and enforce hard tool allowlists and approvals independent of prompt wording.
  4. Expire cached network context, confirm target scope and revalidate resources before agent actions.

Explanation

Correct Answer

A:

Test parameter bounds, tenant authorization and injection input against each FastMCP exposed operation. This prevents the recurrence because typed MCP tool schemas improve interoperability but server-side validation remains necessary even for a well-formed client call. A matching immediate correction is: Define typed, validated tool arguments with explicit device allowlists and reject invalid or unauthorized inputs at the server boundary.

Incorrect Answers

B:

This routine guards against another mechanism: aI-generated code may embed third-party patterns or dependencies; tool output is not automatically cleared of licensing obligations. The recurring exposure in the current case is: typed MCP tool schemas improve interoperability but server-side validation remains necessary even for a well-formed client call. The matching preventive check is “Test parameter bounds, tenant authorization and injection input against each FastMCP exposed operation”.

C:

The suggested review tracks a different technical risk: prompt injection attempts to convert lower-trust retrieved content into high-priority instructions across an AI-agent trust boundary. Here the sustained control must address: typed MCP tool schemas improve interoperability but server-side validation remains necessary even for a well-formed client call. Choose “Test parameter bounds, tenant authorization and injection input against each FastMCP exposed operation”.

D:

That safeguard is relevant to: conversation memory is not authoritative network state; stale context and scope leakage create wrong-target operational risk. The current failure instead follows from: typed MCP tool schemas improve interoperability but server-side validation remains necessary even for a well-formed client call. Its prevention measure is “Test parameter bounds, tenant authorization and injection input against each FastMCP exposed operation”.

Question 94

At fictional Northshore Cloud, an acceptance review of an inventory reconciliation finds: A VLAN RESTCONF update targets the entire list collection rather than the keyed VLAN instance, altering more entries than intended. Which engineering principle explains the described system behavior?

  1. RESTCONF exposes list entries through resource identifiers determined by the keys declared in the YANG model.
  2. Robust batch automation isolates errors at the per-resource boundary and retains auditable partial outcomes.
  3. Terraform state tracks managed resource associations; concurrent writes without locking can corrupt effective desired-state coordination.
  4. An access-token lifecycle and authorization scope are distinct concerns; repeated reuse of expired or insufficient tokens cannot resolve them.

Explanation

Correct Answer

A:

RESTCONF exposes list entries through resource identifiers determined by the keys declared in the YANG model. The corresponding repair is: Address the exact YANG list instance using its fully encoded key values in the RESTCONF data resource path. Acceptance should show: A GET of the specific keyed list entry shows only the authorized VLAN or interface changed, with sibling entries intact. Applied here, the relevant facts are: A VLAN RESTCONF update targets the entire list collection rather than the keyed VLAN instance, altering more entries than intended. The question asks which engineering principle explains the described system behavior.

Incorrect Answers

B:

The corresponding repair is: Handle per-target HTTP, parsing and retryable exceptions and persist a failure summary without misreporting completed targets. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Address the exact YANG list instance using its fully encoded key values in the RESTCONF data resource path.

C:

The offered statement is true for this other mechanism: The corresponding repair is: Configure a shared protected Terraform state backend with supported locking and serialize competing applies against the same state. It does not explain the facts described here, which follow from: The corresponding repair is: Address the exact YANG list instance using its fully encoded key values in the RESTCONF data resource path.

D:

This principle describes a separate cause: The corresponding repair is: Use the supported token refresh flow with secret storage and distinguish unauthenticated 401 from authorized-but-forbidden 403 responses. The reported condition is governed by: The corresponding repair is: Address the exact YANG list instance using its fully encoded key values in the RESTCONF data resource path. The two mechanisms should not be conflated.

Question 95

While investigating a reproducible simulation for fictional Windward Maritime, the team reports: A team needs to validate an interface-renaming playbook but cannot safely run experimental changes against a shared campus network. What should the team add to its network automation operating process?

  1. Document backup, ownership and retention policies for every persistent Compose volume.
  2. Use protected environments, least-privilege deploy tokens and progressive rollout approval conditions.
  3. Set protected branch merge policies and link the squash commit to the reviewed change request.
  4. Maintain versioned representative CML topologies as mandatory preproduction test fixtures.

Explanation

Correct Answer

D:

Maintain versioned representative CML topologies as mandatory preproduction test fixtures. This prevents the recurrence because cML supports topology-based device and protocol simulation for safe early integration tests without touching live infrastructure. A matching immediate correction is: Build a representative topology in Cisco Modeling Labs and execute the automation against simulated devices before live release.

Incorrect Answers

A:

The proposed action belongs to the mechanism: ephemeral container writable layers are distinct from Docker managed or host-mounted persistent volumes. Here the stated fault follows a different mechanism: cML supports topology-based device and protocol simulation for safe early integration tests without touching live infrastructure. The corrective choice is “Maintain versioned representative CML topologies as mandatory preproduction test fixtures”.

B:

The offered action targets: a deployment stage should enforce release scope and approval, not merely execute a command with unrestricted infrastructure access. The case facts point instead to: cML supports topology-based device and protocol simulation for safe early integration tests without touching live infrastructure. Implement “Maintain versioned representative CML topologies as mandatory preproduction test fixtures” to address that specific condition.

C:

This alternative is a response to another technical cause: a squash merge consolidates branch changes into a new commit, simplifying target history without preserving each source commit as a separate mainline entry. The reported case instead depends on: cML supports topology-based device and protocol simulation for safe early integration tests without touching live infrastructure. The action that directly addresses it is “Maintain versioned representative CML topologies as mandatory preproduction test fixtures”.

Question 96

While investigating a reproducible simulation for fictional Windward Maritime, the team reports: A team wants one traceable release change from a noisy experiment branch, but a standard merge preserves temporary debugging commits in main history. Which targeted correction best addresses the network automation failure?

  1. Use an approved squash merge to combine reviewed feature changes into one commit while preserving the final content.
  2. Run objective-based postdeployment checks and fail or roll back the change when observed network behavior contradicts intent.
  3. Deploy through bounded environment-scoped jobs with approved service credentials and staged canary or batch rollout.
  4. Construct JSON using the published YANG container hierarchy, qualified node names and correct value types.

Explanation

Correct Answer

A:

Use an approved squash merge to combine reviewed feature changes into one commit while preserving the final content. This addresses the problem because a squash merge consolidates branch changes into a new commit, simplifying target history without preserving each source commit as a separate mainline entry. Confirm success using: The protected target branch contains one reviewed release commit whose diff matches the approved feature changes.

Incorrect Answers

B:

This alternative is a response to another technical cause: deployment command success is not the same as verified service success; operational checks must follow state changes. The reported case instead depends on: a squash merge consolidates branch changes into a new commit, simplifying target history without preserving each source commit as a separate mainline entry. The action that directly addresses it is “Use an approved squash merge to combine reviewed feature changes into one commit while preserving the final content”.

C:

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: a squash merge consolidates branch changes into a new commit, simplifying target history without preserving each source commit as a separate mainline entry. The corrective choice is “Use an approved squash merge to combine reviewed feature changes into one commit while preserving the final content”.

D:

The offered action targets: yANG defines node hierarchy, namespaces, list keys and data types; conforming JSON must preserve that structure. The case facts point instead to: a squash merge consolidates branch changes into a new commit, simplifying target history without preserving each source commit as a separate mainline entry. Implement “Use an approved squash merge to combine reviewed feature changes into one commit while preserving the final content” to address that specific condition.

Question 97

During a network policy migration at fictional Cobalt Ridge Bank, the change record states: A configuration collector overloads a shared Cisco API budget during a morning audit and starves other authorized automation. Which implementation action best meets the observed technical requirement?

  1. Choose a supported targeted PATCH or edit operation for partial changes and reserve PUT for intentionally replacing the resource representation.
  2. Use inventory capability detection and platform-specific adapters behind a common validated intent model.
  3. Read intended configuration and runtime operational YANG data from their appropriate modeled resources, and write only configurable leaves.
  4. Respect rate-limit response headers and coordinate bounded exponential backoff with jitter under the shared API budget.

Explanation

Correct Answer

D:

Respect rate-limit response headers and coordinate bounded exponential backoff with jitter under the shared API budget. This addresses the problem because hTTP 429 signals server-enforced rate limits; API client backoff must consider shared rate budgets and Retry-After semantics. Confirm success using: Simulated 429 responses result in delayed, bounded retries and the caller recovers without a retry storm.

Incorrect Answers

A:

This alternative is a response to another technical cause: hTTP PUT represents replacement semantics for a targeted RESTCONF resource, whereas PATCH supports partial edits under the applicable media type. The reported case instead depends on: hTTP 429 signals server-enforced rate limits; API client backoff must consider shared rate budgets and Retry-After semantics. The action that directly addresses it is “Respect rate-limit response headers and coordinate bounded exponential backoff with jitter under the shared API budget”.

B:

The proposed action belongs to the mechanism: cross-platform automation benefits from a shared intent model but must translate differences in native device APIs and models. Here the stated fault follows a different mechanism: hTTP 429 signals server-enforced rate limits; API client backoff must consider shared rate budgets and Retry-After semantics. The corrective choice is “Respect rate-limit response headers and coordinate bounded exponential backoff with jitter under the shared API budget”.

C:

The offered action targets: yANG distinguishes configuration intent from read-only operational state; successful config writes do not establish runtime protocol health. The case facts point instead to: hTTP 429 signals server-enforced rate limits; API client backoff must consider shared rate budgets and Retry-After semantics. Implement “Respect rate-limit response headers and coordinate bounded exponential backoff with jitter under the shared API budget” to address that specific condition.

Question 98

During a production change postcheck at fictional Marble Bay Software, the change record states: A network automation service connects to an API by IP address while the new certificate only contains its DNS service name. Which observation would confirm that this exact failure is resolved?

  1. A supported image produces structured parsed data; unsupported output is reported as a test instrumentation error, not a device state failure.
  2. A timeline of stage logs identifies the first failing API or schema operation and confirms the targeted repair removes it.
  3. Correlated traces identify which API operation approaches the timeout threshold and whether backoff reduces the failure rate.
  4. TLS validation succeeds for the intended hostname and fails for unexpected names without disabling verification.

Explanation

Correct Answer

D:

TLS validation succeeds for the intended hostname and fails for unexpected names without disabling verification. This directly verifies the related correction: Use an approved DNS endpoint covered by the certificate SAN or reissue a certificate with correct service identities. It checks the technical distinction: Modern TLS clients validate the connection name against certificate subject alternative names, not merely that a CA issued the cert.

Incorrect Answers

A:

The alternative verifies a different condition: This directly verifies the related correction: Validate parser and platform compatibility and distinguish collection or parsing errors from actual network-state assertion failures. The current case instead depends on: This directly verifies the related correction: Use an approved DNS endpoint covered by the certificate SAN or reissue a certificate with correct service identities. Confirm that “TLS validation succeeds for the intended hostname and fails for unexpected names without disabling verification”.

B:

That test belongs to another control with this basis: This directly verifies the related correction: Trace correlated event IDs and earliest causal errors through the pipeline instead of treating the final propagated exception as root cause. In the current case, the governing reason is: 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 direct verification is “TLS validation succeeds for the intended hostname and fails for unexpected names without disabling verification”.

C:

This observation would test a different technical dependency: This directly verifies the related correction: Capture per-request endpoint, duration, timeout class, retry attempt and status while preserving sensitive data redaction. The current issue is governed by: This directly verifies the related correction: Use an approved DNS endpoint covered by the certificate SAN or reissue a certificate with correct service identities. Its decisive check is “TLS validation succeeds for the intended hostname and fails for unexpected names without disabling verification”.

Question 99

At fictional Violet Ridge Resorts, an acceptance review of a version-control hotfix finds: A network parsing pipeline runs under a clean container and raises ModuleNotFoundError for a local-only tool used by the scripts. What ongoing engineering assurance should follow the successful fix?

  1. Set protected branch merge policies and link the squash commit to the reviewed change request.
  2. Require path-limited recovery commands and postrestore diffs for surgical automation-file reversions.
  3. Run clean-environment dependency installation tests and enforce dependency lockfile review.
  4. Add merge topology review and a dry-run diff approval for complex revert operations.

Explanation

Correct Answer

C:

Run clean-environment dependency installation tests and enforce dependency lockfile review. This prevents the recurrence because cI runners start from controlled environments; undeclared local dependencies cannot be assumed present remotely. A matching immediate correction is: Declare and lock the required dependency in the build manifest and install it in the pipeline's reproducible environment.

Incorrect Answers

A:

That safeguard is relevant to: a squash merge consolidates branch changes into a new commit, simplifying target history without preserving each source commit as a separate mainline entry. The current failure instead follows from: cI runners start from controlled environments; undeclared local dependencies cannot be assumed present remotely. Its prevention measure is “Run clean-environment dependency installation tests and enforce dependency lockfile review”.

B:

This routine guards against another mechanism: git can retrieve individual tracked paths from a commit; selecting file scope avoids broad branch-level rollback. The recurring exposure in the current case is: cI runners start from controlled environments; undeclared local dependencies cannot be assumed present remotely. The matching preventive check is “Run clean-environment dependency installation tests and enforce dependency lockfile review”.

D:

That safeguard is relevant to: reverting a merge requires an explicit mainline perspective so Git knows which parent is the retained baseline. The current failure instead follows from: cI runners start from controlled environments; undeclared local dependencies cannot be assumed present remotely. Its prevention measure is “Run clean-environment dependency installation tests and enforce dependency lockfile review”.

Question 100

At fictional Willowfield Hospitality, during a version-control hotfix, the operator observes: A bad network automation change has already been pushed to a protected shared branch and teammates have based work on it. What technical evidence should be required before closing this change?

  1. The payload validates against the YANG schema and the RESTCONF server accepts the exact intended interface resource.
  2. The maintenance branch contains the intended patch without unrelated feature commits and passes the target release tests.
  3. Only the selected file matches the approved historical content, and unrelated working files remain unchanged.
  4. The target branch retains an auditable inverse commit and the published history remains intact while behavior returns to the approved state.

Explanation

Correct Answer

D:

The target branch retains an auditable inverse commit and the published history remains intact while behavior returns to the approved state. This directly verifies the related correction: Create a reviewed Git revert commit for the offending change and run the full network automation release tests. It checks the technical distinction: Git revert records an inverse patch in new history rather than moving shared branch pointers backward.

Incorrect Answers

A:

This observation would test a different technical dependency: This directly verifies the related correction: Construct JSON using the published YANG container hierarchy, qualified node names and correct value types. The current issue is governed by: This directly verifies the related correction: Create a reviewed Git revert commit for the offending change and run the full network automation release tests. Its decisive check is “The target branch retains an auditable inverse commit and the published history remains intact while behavior returns to the approved state”.

B:

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: Create a reviewed Git revert commit for the offending change and run the full network automation release tests. Confirm that “The target branch retains an auditable inverse commit and the published history remains intact while behavior returns to the approved state”.

C:

That test belongs to another control with this basis: This directly verifies the related correction: Restore only the specifically reviewed historical file from the desired revision instead of replacing the whole branch state. In the current case, the governing reason is: This directly verifies the related correction: Create a reviewed Git revert commit for the offending change and run the full network automation release tests. The direct verification is “The target branch retains an auditable inverse commit and the published history remains intact while behavior returns to the approved state”.