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 20

Question 190

At fictional Thornwick Health Trust, during a remote branch provisioning pilot, the operator observes: A branch office deployment reuses a fixed IP addressing string embedded in a shared network module and conflicts with another region. What underlying technical distinction accounts for this failure?

  1. Automation choice is driven by lifecycle and operational risk rather than by a single preferred programming tool.
  2. Robust batch automation isolates errors at the per-resource boundary and retains auditable partial outcomes.
  3. Terraform modules support repeated declarative resource patterns while typed inputs isolate deployment-specific configuration.
  4. HTTP 202 signals accepted asynchronous processing, not completion of the requested configuration change.

Explanation

Correct Answer

C:

Terraform modules support repeated declarative resource patterns while typed inputs isolate deployment-specific configuration. The corresponding repair is: Extract a versioned reusable Terraform module with validated input variables for site-specific network parameters. Acceptance should show: Plans for two independently configured sites show correct separate VLAN IDs or address values while sharing one reviewed module version.

Incorrect Answers

A:

This principle describes a separate cause: The corresponding repair is: Select the tool and deployment pattern by risk, state persistence, change scope, rollback capability and approval obligations. The reported condition is governed by: The corresponding repair is: Extract a versioned reusable Terraform module with validated input variables for site-specific network parameters. The two mechanisms should not be conflated.

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: Extract a versioned reusable Terraform module with validated input variables for site-specific network parameters.

D:

That statement describes a separate technical dependency: An HTTP 202 response indicates accepted asynchronous work; a separate completion status is needed to prove the requested device change actually finished. The present problem is governed by: The corresponding repair is: Extract a versioned reusable Terraform module with validated input variables for site-specific network parameters. The applicable explanation is “Terraform modules support repeated declarative resource patterns while typed inputs isolate deployment-specific configuration”.

Question 191

While investigating an automation service security audit for fictional Coastal Meadow Labs, the team reports: An automation platform relies solely on local volatile logs, and the incident evidence disappears when a deployment container restarts. Which engineering principle explains the described system behavior?

  1. Distributed troubleshooting requires durable transport and consistent time context; ephemeral local logs can be lost or misordered.
  2. Streaming telemetry pipelines have collectors, transports, ingestion queues and storage capacity that can fail independently of device subscriptions.
  3. Model-driven test tools depend on supported device schemas and parser versions; missing parsed data is not proof of missing network function.
  4. Downstream error messages can reflect cascaded failures; causality is established by correlating the earlier specific event and affected resource.

Explanation

Correct Answer

A:

Distributed troubleshooting requires durable transport and consistent time context; ephemeral local logs can be lost or misordered. The corresponding repair is: Synchronize clocks and ship logs to a durable centralized destination with appropriate secure, reliable transport. Acceptance should show: Centralized logs survive worker replacement and carry timestamps that correlate with device events within the accepted skew. Applied here, the relevant facts are: An automation platform relies solely on local volatile logs, and the incident evidence disappears when a deployment container restarts. The question asks which engineering principle explains the described system behavior.

Incorrect Answers

B:

The offered statement is true for this other mechanism: The corresponding repair is: Introduce bounded buffering, backpressure monitoring and horizontal ingestion capacity with visible gap or loss reporting. It does not explain the facts described here, which follow from: The corresponding repair is: Synchronize clocks and ship logs to a durable centralized destination with appropriate secure, reliable transport.

C:

This principle describes a separate cause: The corresponding repair is: Validate parser and platform compatibility and distinguish collection or parsing errors from actual network-state assertion failures. The reported condition is governed by: The corresponding repair is: Synchronize clocks and ship logs to a durable centralized destination with appropriate secure, reliable transport. The two mechanisms should not be conflated.

D:

The corresponding repair is: Trace correlated event IDs and earliest causal errors through the pipeline instead of treating the final propagated exception as root cause. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Synchronize clocks and ship logs to a durable centralized destination with appropriate secure, reliable transport.

Question 192

At fictional Westlake Biomedicine, an acceptance review of a FastMCP security review finds: An internal FastMCP server trusts a caller-supplied user name and gives any connected chat agent access to all device telemetry. What acceptance check would prove the intended behavior was restored?

  1. Two simulated tenants can query only their own device records and cross-tenant tool attempts are denied and audited.
  2. The workflow reduces draft effort yet records review and successful technical tests before any proposed config reaches deployment.
  3. A site-context switch triggers a fresh scoped lookup and proposed actions reference currently authorized device identifiers.
  4. Injection test logs are summarized as evidence but never cause unauthorized configuration or secret-retrieval tool calls.

Explanation

Correct Answer

A:

Two simulated tenants can query only their own device records and cross-tenant tool attempts are denied and audited. This directly verifies the related correction: Authenticate each MCP client, authorize its tool calls by tenant identity and isolate credential/session context. It checks the technical distinction: An MCP server is an integration boundary and must not treat model-selected identity strings as verified security credentials. Applied here, the relevant facts are: An internal FastMCP server trusts a caller-supplied user name and gives any connected chat agent access to all device telemetry. The question asks what acceptance check would prove the intended behavior was restored.

Incorrect Answers

B:

This observation would test a different technical dependency: This directly verifies the related correction: Use AI assistance for bounded drafts and test generation while assigning accountable reviewers and validating facts against approved sources. The current issue is governed by: This directly verifies the related correction: Authenticate each MCP client, authorize its tool calls by tenant identity and isolate credential/session context. Its decisive check is “Two simulated tenants can query only their own device records and cross-tenant tool attempts are denied and audited”.

C:

The alternative verifies a different condition: This directly verifies the related correction: Bind current request context to fresh authorized inventory and explicit tenant or device selection before tool calls. The current case instead depends on: This directly verifies the related correction: Authenticate each MCP client, authorize its tool calls by tenant identity and isolate credential/session context. Confirm that “Two simulated tenants can query only their own device records and cross-tenant tool attempts are denied and audited”.

D:

That test belongs to another control with this basis: This directly verifies the related correction: Treat retrieved logs as untrusted data and enforce instruction hierarchy and independent tool permissions outside the model. In the current case, the governing reason is: This directly verifies the related correction: Authenticate each MCP client, authorize its tool calls by tenant identity and isolate credential/session context. The direct verification is “Two simulated tenants can query only their own device records and cross-tenant tool attempts are denied and audited”.

Question 193

While investigating an AI recommendation accuracy study for fictional Sunrise Aeronautics, the team reports: A read-only network troubleshooting agent runs under a global administrator token and can delete production device configurations. Which explanation best matches the actual broken dependency?

  1. The model is not a reliable security principal; tool identities and server-side authorization bound the damage of agent errors.
  2. Model fluency is not evidence of device capability; uncertain technical recommendations require explicit verification before action.
  3. AI-generated code may embed third-party patterns or dependencies; tool output is not automatically cleared of licensing obligations.
  4. Generative systems can propose plausible-looking but incorrect commands; independent executable validation is required for safe infrastructure changes.

Explanation

Correct Answer

A:

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

Incorrect Answers

B:

The proposed action belongs to the mechanism: The corresponding repair is: Require citation to a compatible authoritative reference and fail closed or escalate when command syntax or device version is uncertain. Here the stated fault follows a different mechanism: The corresponding repair is: Issue read-only scoped identity credentials for diagnostic agents and place separate approval boundaries around mutating tools. The corrective choice is “The model is not a reliable security principal; tool identities and server-side authorization bound the damage of agent errors”.

C:

The offered action targets: The corresponding repair is: Review generated code provenance, included dependencies and organizational IP policy before accepting it into the repository. The case facts point instead to: The corresponding repair is: Issue read-only scoped identity credentials for diagnostic agents and place separate approval boundaries around mutating tools. Implement “The model is not a reliable security principal; tool identities and server-side authorization bound the damage of agent errors” to address that specific condition.

D:

This alternative is a response to another technical cause: The corresponding repair is: Subject AI-suggested changes to schema and unit tests, simulated network execution, policy checks and human change approval. The reported case instead depends on: The corresponding repair is: Issue read-only scoped identity credentials for diagnostic agents and place separate approval boundaries around mutating tools. The action that directly addresses it is “The model is not a reliable security principal; tool identities and server-side authorization bound the damage of agent errors”.

Question 194

During a source-of-truth integration at fictional Violet Ridge Resorts, the change record states: A pipeline status shows red due to a failed inventory schema validation stage, yet the automation team assumes the controller was unreachable. Which engineering principle explains the described system behavior?

  1. A GitLab pipeline exit code identifies failure, while job logs and test artifacts reveal the specific causal stage and assertion.
  2. A deployment stage should enforce release scope and approval, not merely execute a command with unrestricted infrastructure access.
  3. CML supports topology-based device and protocol simulation for safe early integration tests without touching live infrastructure.
  4. Git checkout can change branch and working-tree files; uncommitted modifications must be managed to avoid accidental mixing.

Explanation

Correct Answer

A:

A GitLab pipeline exit code identifies failure, while job logs and test artifacts reveal the specific causal stage and assertion. The corresponding repair is: Inspect the failed job logs and classify whether build, dependency, test or environment validation failed before making a targeted fix. Acceptance should show: A repaired pipeline has a documented root cause and passes the originally failing test without bypassing safety gates.

Incorrect Answers

B:

The offered statement is true for this other mechanism: The corresponding repair is: Deploy through bounded environment-scoped jobs with approved service credentials and staged canary or batch rollout. It does not explain the facts described here, which follow from: The corresponding repair is: Inspect the failed job logs and classify whether build, dependency, test or environment validation failed before making a targeted fix.

C:

This principle describes a separate cause: The corresponding repair is: Build a representative topology in Cisco Modeling Labs and execute the automation against simulated devices before live release. The reported condition is governed by: The corresponding repair is: Inspect the failed job logs and classify whether build, dependency, test or environment validation failed before making a targeted fix. The two mechanisms should not be conflated.

D:

The corresponding repair is: Safely stash or commit unrelated work and check out the intended branch or detached revision in a clean worktree. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Inspect the failed job logs and classify whether build, dependency, test or environment validation failed before making a targeted fix.

Question 195

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 implementation action best meets the observed technical requirement?

  1. Unstage the unintended file with an index-only reset or equivalent restore-staged operation, leaving the worktree intact.
  2. Review the merge graph and select the correct mainline parent when reverting the merge, then validate the resulting tree diff.
  3. Deploy through bounded environment-scoped jobs with approved service credentials and staged canary or batch rollout.
  4. Mount an appropriate persistent named volume or approved bind mount for data that must survive container recreation.

Explanation

Correct Answer

A:

Unstage the unintended file with an index-only reset or equivalent restore-staged operation, leaving the worktree intact. This addresses the problem because the Git index is the staging area and can be changed independently of the working tree by suitable reset modes. Confirm success using: The next commit excludes the file, while the local copy remains available for secure handling or deletion. 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 implementation action best meets the observed technical requirement.

Incorrect Answers

B:

This alternative is a response to another technical cause: reverting a merge requires an explicit mainline perspective so Git knows which parent is the retained baseline. The reported case instead depends on: the Git index is the staging area and can be changed independently of the working tree by suitable reset modes. The action that directly addresses it is “Unstage the unintended file with an index-only reset or equivalent restore-staged operation, leaving the worktree intact”.

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: the Git index is the staging area and can be changed independently of the working tree by suitable reset modes. The corrective choice is “Unstage the unintended file with an index-only reset or equivalent restore-staged operation, leaving the worktree intact”.

D:

The offered action targets: ephemeral container writable layers are distinct from Docker managed or host-mounted persistent volumes. The case facts point instead to: the Git index is the staging area and can be changed independently of the working tree by suitable reset modes. Implement “Unstage the unintended file with an index-only reset or equivalent restore-staged operation, leaving the worktree intact” to address that specific condition.

Question 196

At fictional Foxglove Aviation, an acceptance review of a certificate renewal rehearsal finds: A network health job fails when command output format changes but the runner incorrectly interprets a parser exception as failed OSPF state. What mechanism is most directly responsible for these symptoms?

  1. Time-series cardinality grows with combinations of labels; volatile unique IDs defeat aggregation and strain metric storage.
  2. Model-driven test tools depend on supported device schemas and parser versions; missing parsed data is not proof of missing network function.
  3. Untrusted input can cross command or configuration boundaries; validation and safe APIs prevent injection into privileged operations.
  4. Hardcoded secrets create persistent exposure and excessive authority; runtime secret retrieval limits both lifetime and access scope.

Explanation

Correct Answer

B:

Model-driven test tools depend on supported device schemas and parser versions; missing parsed data is not proof of missing network function. The corresponding repair is: Validate parser and platform compatibility and distinguish collection or parsing errors from actual network-state assertion failures. Acceptance should show: A supported image produces structured parsed data; unsupported output is reported as a test instrumentation error, not a device state failure.

Incorrect Answers

A:

This principle describes a separate cause: The corresponding repair is: Normalize telemetry dimensions to stable device and interface identifiers and avoid high-cardinality ephemeral labels. The reported condition is governed by: The corresponding repair is: Validate parser and platform compatibility and distinguish collection or parsing errors from actual network-state assertion failures. The two mechanisms should not be conflated.

C:

The offered statement is true for this other mechanism: The corresponding repair is: Use typed input schema validation, approved resource allowlists and safe library argument interfaces rather than shell concatenation. It does not explain the facts described here, which follow from: The corresponding repair is: Validate parser and platform compatibility and distinguish collection or parsing errors from actual network-state assertion failures.

D:

This principle describes a separate cause: The corresponding repair is: Inject short-lived narrowly scoped secrets at runtime from a managed vault and mask them in logs and build artifacts. The reported condition is governed by: The corresponding repair is: Validate parser and platform compatibility and distinguish collection or parsing errors from actual network-state assertion failures. The two mechanisms should not be conflated.

Question 197

During a telemetry quality investigation at fictional Foxglove Aviation, the change record states: A new network controller presents a certificate from a private CA and clients fail TLS handshakes because the CA is not trusted. Which targeted correction best addresses the network automation failure?

  1. Install the validated issuing CA chain in client trust stores and verify endpoint identity rather than bypassing TLS checks.
  2. Configure suitable model-driven telemetry subscriptions for the relevant paths at a collection interval appropriate to the signal.
  3. Capture structured prechange operational state with pyATS, apply the change, then compare relevant postchange state and assert expected invariants.
  4. Introduce bounded buffering, backpressure monitoring and horizontal ingestion capacity with visible gap or loss reporting.

Explanation

Correct Answer

A:

Install the validated issuing CA chain in client trust stores and verify endpoint identity rather than bypassing TLS checks. This addresses the problem because tLS server validation depends on trusted issuer chains and hostname identity; bypassing verification defeats server authentication. Confirm success using: Clients establish a verified TLS session to the expected controller hostname with a valid certificate chain.

Incorrect Answers

B:

The offered action targets: model-driven telemetry publishes structured device state using subscribed paths and collection modes rather than relying only on slow polling. The case facts point instead to: tLS server validation depends on trusted issuer chains and hostname identity; bypassing verification defeats server authentication. Implement “Install the validated issuing CA chain in client trust stores and verify endpoint identity rather than bypassing TLS checks” to address that specific condition.

C:

This alternative is a response to another technical cause: pyATS can learn and compare device operational state to detect unintended network effects beyond text config diffs. The reported case instead depends on: tLS server validation depends on trusted issuer chains and hostname identity; bypassing verification defeats server authentication. The action that directly addresses it is “Install the validated issuing CA chain in client trust stores and verify endpoint identity rather than bypassing TLS checks”.

D:

The proposed action belongs to the mechanism: streaming telemetry pipelines have collectors, transports, ingestion queues and storage capacity that can fail independently of device subscriptions. Here the stated fault follows a different mechanism: tLS server validation depends on trusted issuer chains and hostname identity; bypassing verification defeats server authentication. The corrective choice is “Install the validated issuing CA chain in client trust stores and verify endpoint identity rather than bypassing TLS checks”.

Question 198

At fictional Sable Valley Power, during a certificate renewal rehearsal, the operator observes: A telemetry dashboard polls SNMP every minute for a rapidly changing interface queue and fails to capture short congestion spikes. Which result most directly verifies that the proposed correction worked?

  1. The corrected job authenticates with a valid identity and has exactly the approved resource permissions, with distinct log codes for future failures.
  2. A supported image produces structured parsed data; unsupported output is reported as a test instrumentation error, not a device state failure.
  3. A token rotation test succeeds without image rebuild, and repository, image and logs contain no recoverable credentials.
  4. The collector receives timestamped updates for the requested YANG paths and captures brief changes within its approved delay budget.

Explanation

Correct Answer

D:

The collector receives timestamped updates for the requested YANG paths and captures brief changes within its approved delay budget. This directly verifies the related correction: Configure suitable model-driven telemetry subscriptions for the relevant paths at a collection interval appropriate to the signal. It checks the technical distinction: Model-driven telemetry publishes structured device state using subscribed paths and collection modes rather than relying only on slow polling.

Incorrect Answers

A:

The offered action targets: This directly verifies the related correction: Classify authentication failures and authorization denials separately, then correct token validity or RBAC scope accordingly. The case facts point instead to: This directly verifies the related correction: Configure suitable model-driven telemetry subscriptions for the relevant paths at a collection interval appropriate to the signal. Implement “The collector receives timestamped updates for the requested YANG paths and captures brief changes within its approved delay budget” to address that specific condition.

B:

This alternative is a response to another technical cause: This directly verifies the related correction: Validate parser and platform compatibility and distinguish collection or parsing errors from actual network-state assertion failures. The reported case instead depends on: This directly verifies the related correction: Configure suitable model-driven telemetry subscriptions for the relevant paths at a collection interval appropriate to the signal. The action that directly addresses it is “The collector receives timestamped updates for the requested YANG paths and captures brief changes within its approved delay budget”.

C:

The proposed action belongs to the mechanism: 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. Here the stated fault follows a different mechanism: This directly verifies the related correction: Configure suitable model-driven telemetry subscriptions for the relevant paths at a collection interval appropriate to the signal. The corrective choice is “The collector receives timestamped updates for the requested YANG paths and captures brief changes within its approved delay budget”.

Question 199

At fictional Elmcrest Theatre, during a conversational network agent pilot, the operator observes: A generated network change says a link is down because one collector stream has missing data, while device operational state is healthy. What should the team add to its network automation operating process?

  1. Track evidence freshness and require independent observed-state corroboration for high-impact AI advice.
  2. Review scopes per AI tool, segregate read/write services and require explicit elevated-change approvals.
  3. Adopt AI data-classification rules, approved endpoints and automatic prompt redaction checks for developer workflows.
  4. Use egress firewall allowlists, response sanitization, credential isolation and canary tests against tool-output injection.

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.

Incorrect Answers

B:

The proposed action belongs to the mechanism: the model is not a reliable security principal; tool identities and server-side authorization bound the damage of agent errors. Here the stated fault follows a different mechanism: aI recommendations are hypotheses requiring external ground truth; absent evidence is not proof of a network condition. The corrective choice is “Track evidence freshness and require independent observed-state corroboration for high-impact AI advice”.

C:

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: aI recommendations are hypotheses requiring external ground truth; absent evidence is not proof of a network condition. Implement “Track evidence freshness and require independent observed-state corroboration for high-impact AI advice” to address that specific condition.

D:

This alternative is a response to another technical cause: tool results are untrusted external input; unrestricted outbound connectivity turns an injected instruction into a data-exfiltration path. The reported case instead depends on: aI recommendations are hypotheses requiring external ground truth; absent evidence is not proof of a network condition. The action that directly addresses it is “Track evidence freshness and require independent observed-state corroboration for high-impact AI advice”.

Question 200

At fictional Thornwick Health Trust, during a remote branch provisioning pilot, the operator observes: A temporary inventory update is built as a large Terraform module even though the required API operation is an ephemeral read-only query. What should the team add to its network automation operating process?

  1. Document selection criteria for persistence, state, API coverage, auditability and team maintenance capacity.
  2. Require validated backups, staged batches and executable rollback procedures in approved network playbooks.
  3. Design resource-state reconciliation and safe retry policies for all create and job-submission requests.
  4. Add multi-page integration tests and monitor continuation tokens and retrieved counts on every scheduled inventory run.

Explanation

Correct Answer

A:

Document selection criteria for persistence, state, API coverage, auditability and team maintenance capacity. This prevents the recurrence because infrastructure as code, low-code workflows and custom software solve different state-lifecycle and integration needs. A matching immediate correction is: Choose a supported declarative IaC framework for persistent desired configuration and targeted scripts for bounded imperative queries or integrations.

Incorrect Answers

B:

The offered action targets: safe network automation separates preflight, controlled deployment, verification and recovery instead of assuming all endpoints will succeed. The case facts point instead to: infrastructure as code, low-code workflows and custom software solve different state-lifecycle and integration needs. Implement “Document selection criteria for persistence, state, API coverage, auditability and team maintenance capacity” to address that specific condition.

C:

This alternative is a response to another technical cause: a network transport timeout does not prove server-side failure; blind retries of non-idempotent operations can duplicate effects. The reported case instead depends on: infrastructure as code, low-code workflows and custom software solve different state-lifecycle and integration needs. The action that directly addresses it is “Document selection criteria for persistence, state, API coverage, auditability and team maintenance capacity”.

D:

The proposed action belongs to the mechanism: many platform APIs paginate large result sets; the first HTTP success response may contain only a subset. Here the stated fault follows a different mechanism: infrastructure as code, low-code workflows and custom software solve different state-lifecycle and integration needs. The corrective choice is “Document selection criteria for persistence, state, API coverage, auditability and team maintenance capacity”.