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 2

Question 10

At fictional Sable Valley Power, during a certificate renewal rehearsal, the operator observes: A CI pipeline logs static device admin passwords from environment variables at every run and never rotates them. Which targeted correction best addresses the network automation failure?

  1. Inject short-lived narrowly scoped secrets at runtime from a managed vault and mask them in logs and build artifacts.
  2. Emit structured events with timestamp, device identity, change ID, severity, stage and outcome to the central log destination.
  3. Introduce bounded buffering, backpressure monitoring and horizontal ingestion capacity with visible gap or loss reporting.
  4. Classify authentication failures and authorization denials separately, then correct token validity or RBAC scope accordingly.

Explanation

Correct Answer

A:

Inject short-lived narrowly scoped secrets at runtime from a managed vault and mask them in logs and build artifacts. This addresses the problem because hardcoded secrets create persistent exposure and excessive authority; runtime secret retrieval limits both lifetime and access scope. Confirm success using: A token rotation test succeeds without image rebuild, and repository, image and logs contain no recoverable credentials.

Incorrect Answers

B:

The proposed action belongs to the mechanism: an effective logging architecture uses consistent machine-readable context and common correlation fields across distributed jobs. Here the stated fault follows a different mechanism: hardcoded secrets create persistent exposure and excessive authority; runtime secret retrieval limits both lifetime and access scope. The corrective choice is “Inject short-lived narrowly scoped secrets at runtime from a managed vault and mask them in logs and build artifacts”.

C:

The offered action targets: streaming telemetry pipelines have collectors, transports, ingestion queues and storage capacity that can fail independently of device subscriptions. The case facts point instead to: hardcoded secrets create persistent exposure and excessive authority; runtime secret retrieval limits both lifetime and access scope. Implement “Inject short-lived narrowly scoped secrets at runtime from a managed vault and mask them in logs and build artifacts” to address that specific condition.

D:

This alternative is a response to another technical cause: hTTP 401 generally signals missing or invalid authentication while 403 indicates access denied to an authenticated request. The reported case instead depends on: hardcoded secrets create persistent exposure and excessive authority; runtime secret retrieval limits both lifetime and access scope. The action that directly addresses it is “Inject short-lived narrowly scoped secrets at runtime from a managed vault and mask them in logs and build artifacts”.

Question 11

While investigating a FastMCP security review for fictional Elmcrest Theatre, the team reports: A service integrator copies model-generated code into a commercial network product without reviewing third-party dependency or attribution terms. What mechanism is most directly responsible for these symptoms?

  1. AI-generated code may embed third-party patterns or dependencies; tool output is not automatically cleared of licensing obligations.
  2. Agent tool chaining can enlarge the blast radius of an ambiguous user instruction unless execution permissions are independently gated.
  3. Retrieval-augmented systems can inherit false or hostile data; source quality and technical cross-checks must precede action.
  4. An MCP server publishes structured tools and resources to clients; safe network use requires explicit least-privilege tool definitions.

Explanation

Correct Answer

A:

AI-generated code may embed third-party patterns or dependencies; tool output is not automatically cleared of licensing obligations. The corresponding repair is: Review generated code provenance, included dependencies and organizational IP policy before accepting it into the repository. Acceptance should show: The review artifact identifies dependencies, licenses and any material code reuse concerns before the release is approved.

Incorrect Answers

B:

The offered statement is true for this other mechanism: The corresponding repair is: Separate read-only diagnostic tools from mutating tools and require an explicit scoped approval step before any privileged operation. It does not explain the facts described here, which follow from: The corresponding repair is: Review generated code provenance, included dependencies and organizational IP policy before accepting it into the repository.

C:

This principle describes a separate cause: The corresponding repair is: Ground actionable recommendations in trusted versioned technical references and reject unsupported or conflicting retrieved claims. The reported condition is governed by: The corresponding repair is: Review generated code provenance, included dependencies and organizational IP policy before accepting it into the repository. The two mechanisms should not be conflated.

D:

The corresponding repair is: Expose narrowly scoped typed read-only FastMCP tools for approved device and status fields with controlled access. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Review generated code provenance, included dependencies and organizational IP policy before accepting it into the repository.

Question 12

At fictional Coastal Meadow Labs, during a production change postcheck, the operator observes: A network rollback reports a timeout, but earlier job logs clearly show the wrong controller endpoint was configured. What ongoing engineering assurance should follow the successful fix?

  1. Review telemetry label schemas, retention and cardinality budgets before enabling new collectors.
  2. Require machine-readable stage IDs and link failure summaries back to the earliest relevant stack trace.
  3. Automate private-key permission checks, key rotation and credential scanning in certificate deployment workflows.
  4. Version baseline snapshots and specify per-feature allowed changes rather than requiring exact equality for volatile counters.

Explanation

Correct Answer

B:

Require machine-readable stage IDs and link failure summaries back to the earliest relevant stack trace. This prevents the recurrence because downstream error messages can reflect cascaded failures; causality is established by correlating the earlier specific event and affected resource. A matching immediate correction is: Trace correlated event IDs and earliest causal errors through the pipeline instead of treating the final propagated exception as root cause.

Incorrect Answers

A:

That safeguard is relevant to: time-series cardinality grows with combinations of labels; volatile unique IDs defeat aggregation and strain metric storage. The current failure instead follows from: downstream error messages can reflect cascaded failures; causality is established by correlating the earlier specific event and affected resource. Its prevention measure is “Require machine-readable stage IDs and link failure summaries back to the earliest relevant stack trace”.

C:

The suggested review tracks a different technical risk: cA-signed certificates are public trust assertions but the associated private key must remain confidential for endpoint authentication. Here the sustained control must address: downstream error messages can reflect cascaded failures; causality is established by correlating the earlier specific event and affected resource. Choose “Require machine-readable stage IDs and link failure summaries back to the earliest relevant stack trace”.

D:

That safeguard is relevant to: pyATS can learn and compare device operational state to detect unintended network effects beyond text config diffs. The current failure instead follows from: downstream error messages can reflect cascaded failures; causality is established by correlating the earlier specific event and affected resource. Its prevention measure is “Require machine-readable stage IDs and link failure summaries back to the earliest relevant stack trace”.

Question 13

At fictional Seabright Learning, an acceptance review of a reproducible simulation finds: A developer cherry-picks a small Terraform resource fix without its prerequisite helper update, and the maintenance pipeline cannot import a function. Which sustainable preventive control most directly avoids a recurrence?

  1. Review Compose network boundaries and port mappings with security tests before any deployment.
  2. Test slow dependency startup and review Compose healthchecks for all network automation support services.
  3. Add dependency-impact review and target-branch CI validation to hotfix backport procedures.
  4. Maintain versioned representative CML topologies as mandatory preproduction test fixtures.

Explanation

Correct Answer

C:

Add dependency-impact review and target-branch CI validation to hotfix backport procedures. This prevents the recurrence because a cherry-picked commit does not automatically bring every ancestor or dependent change from its original branch. A matching immediate correction is: Identify the prerequisite commits and cherry-pick a minimal compatible sequence or adapt the patch for the target baseline.

Incorrect Answers

A:

This routine guards against another mechanism: compose networks govern container service reachability, while host port publishing determines external exposure. The recurring exposure in the current case is: a cherry-picked commit does not automatically bring every ancestor or dependent change from its original branch. The matching preventive check is “Add dependency-impact review and target-branch CI validation to hotfix backport procedures”.

B:

The suggested review tracks a different technical risk: container start ordering does not inherently guarantee service readiness; health conditions and retries address that gap. Here the sustained control must address: a cherry-picked commit does not automatically bring every ancestor or dependent change from its original branch. Choose “Add dependency-impact review and target-branch CI validation to hotfix backport procedures”.

D:

This routine guards against another mechanism: cML supports topology-based device and protocol simulation for safe early integration tests without touching live infrastructure. The recurring exposure in the current case is: a cherry-picked commit does not automatically bring every ancestor or dependent change from its original branch. The matching preventive check is “Add dependency-impact review and target-branch CI validation to hotfix backport procedures”.

Question 14

During a remote branch provisioning pilot at fictional Northshore Cloud, the change record states: Two automation jobs modify the same Cisco network resource inventory from separate local Terraform state files, each unaware of the other's last apply. Which sustainable preventive control most directly avoids a recurrence?

  1. Exercise representative 4xx, 5xx, timeout and malformed-payload cases in contract tests before scheduling batches.
  2. Add check-mode previews and a second-run idempotence assertion to the network playbook CI gate.
  3. Require representative failure-path tests before approving a low-code production integration.
  4. Require remote state access controls, locking verification and serialized deployment jobs for shared workspaces.

Explanation

Correct Answer

D:

Require remote state access controls, locking verification and serialized deployment jobs for shared workspaces. This prevents the recurrence because terraform state tracks managed resource associations; concurrent writes without locking can corrupt effective desired-state coordination. A matching immediate correction is: Configure a shared protected Terraform state backend with supported locking and serialize competing applies against the same state.

Incorrect Answers

A:

The suggested review tracks a different technical risk: robust batch automation isolates errors at the per-resource boundary and retains auditable partial outcomes. Here the sustained control must address: terraform state tracks managed resource associations; concurrent writes without locking can corrupt effective desired-state coordination. Choose “Require remote state access controls, locking verification and serialized deployment jobs for shared workspaces”.

B:

That safeguard is relevant to: ansible's desired-state-aware network modules compare declared configuration with device state before determining required changes. The current failure instead follows from: terraform state tracks managed resource associations; concurrent writes without locking can corrupt effective desired-state coordination. Its prevention measure is “Require remote state access controls, locking verification and serialized deployment jobs for shared workspaces”.

C:

This routine guards against another mechanism: low-code accelerates common supported integrations but may constrain complex branching and custom transaction semantics. The recurring exposure in the current case is: terraform state tracks managed resource associations; concurrent writes without locking can corrupt effective desired-state coordination. The matching preventive check is “Require remote state access controls, locking verification and serialized deployment jobs for shared workspaces”.

Question 15

At fictional Elmcrest Theatre, during a conversational network agent pilot, the operator observes: An AI agent ranks an attacker-supplied forum snippet above current Cisco documentation and recommends disabling TLS verification. What mechanism is most directly responsible for these symptoms?

  1. AI can accelerate low-risk preparation, but speed benefits must be balanced against hallucination, privacy and review obligations.
  2. LLMs are useful for language interpretation but the execution boundary should accept validated structured intents, not arbitrary prose.
  3. Retrieval-augmented systems can inherit false or hostile data; source quality and technical cross-checks must precede action.
  4. An MCP server is an integration boundary and must not treat model-selected identity strings as verified security credentials.

Explanation

Correct Answer

C:

Retrieval-augmented systems can inherit false or hostile data; source quality and technical cross-checks must precede action. The corresponding repair is: Ground actionable recommendations in trusted versioned technical references and reject unsupported or conflicting retrieved claims. Acceptance should show: A poisoned-source test yields a flagged uncertainty or validated official-source citation instead of an unsafe configuration recommendation.

Incorrect Answers

A:

That test belongs to another control with this basis: The corresponding repair is: Use AI assistance for bounded drafts and test generation while assigning accountable reviewers and validating facts against approved sources. In the current case, the governing reason is: The corresponding repair is: Ground actionable recommendations in trusted versioned technical references and reject unsupported or conflicting retrieved claims. The direct verification is “Retrieval-augmented systems can inherit false or hostile data; source quality and technical cross-checks must precede action”.

B:

This observation would test a different technical dependency: The corresponding repair is: Convert user requests into a typed proposed intent with explicit targets, preconditions and a separate human-approved execution path. The current issue is governed by: The corresponding repair is: Ground actionable recommendations in trusted versioned technical references and reject unsupported or conflicting retrieved claims. Its decisive check is “Retrieval-augmented systems can inherit false or hostile data; source quality and technical cross-checks must precede action”.

D:

That test belongs to another control with this basis: The corresponding repair is: Authenticate each MCP client, authorize its tool calls by tenant identity and isolate credential/session context. In the current case, the governing reason is: The corresponding repair is: Ground actionable recommendations in trusted versioned technical references and reject unsupported or conflicting retrieved claims. The direct verification is “Retrieval-augmented systems can inherit false or hostile data; source quality and technical cross-checks must precede action”.

Question 16

During a telemetry quality investigation at fictional Foxglove Aviation, the change record states: A webhook collector loses device-change notifications during transient outages because the sender has no retry or acknowledgement tracking. What is the appropriate response to this network automation condition?

  1. Authenticate webhook delivery and implement bounded retries with deduplication or delivery-state accounting.
  2. Normalize telemetry dimensions to stable device and interface identifiers and avoid high-cardinality ephemeral labels.
  3. Install the validated issuing CA chain in client trust stores and verify endpoint identity rather than bypassing TLS checks.
  4. Capture per-request endpoint, duration, timeout class, retry attempt and status while preserving sensitive data redaction.

Explanation

Correct Answer

A:

Authenticate webhook delivery and implement bounded retries with deduplication or delivery-state accounting. This addresses the problem because webhooks are asynchronous network events; integrity, delivery acknowledgements and idempotent processing are separate reliability needs. Confirm success using: A simulated receiver outage results in eventual one-time processing or an explicit recorded dead-letter failure without accepting forged requests.

Incorrect Answers

B:

The proposed action belongs to the mechanism: time-series cardinality grows with combinations of labels; volatile unique IDs defeat aggregation and strain metric storage. Here the stated fault follows a different mechanism: webhooks are asynchronous network events; integrity, delivery acknowledgements and idempotent processing are separate reliability needs. The corrective choice is “Authenticate webhook delivery and implement bounded retries with deduplication or delivery-state accounting”.

C:

The offered action targets: tLS server validation depends on trusted issuer chains and hostname identity; bypassing verification defeats server authentication. The case facts point instead to: webhooks are asynchronous network events; integrity, delivery acknowledgements and idempotent processing are separate reliability needs. Implement “Authenticate webhook delivery and implement bounded retries with deduplication or delivery-state accounting” to address that specific condition.

D:

This alternative is a response to another technical cause: latency and retry failures require timing context and per-attempt telemetry; an aggregate success percentage is insufficient. The reported case instead depends on: webhooks are asynchronous network events; integrity, delivery acknowledgements and idempotent processing are separate reliability needs. The action that directly addresses it is “Authenticate webhook delivery and implement bounded retries with deduplication or delivery-state accounting”.

Question 17

While investigating an inventory reconciliation for fictional Thornwick Health Trust, the team reports: An engineer places region-specific ACL variables in a global inventory file, and the wrong region receives the restricted network policy. Which result most directly verifies that the proposed correction worked?

  1. Fresh runners initialize the same reviewed provider build and produce equivalent plans from the same state and configuration.
  2. The design review shows the chosen approach fits the resource lifecycle, state ownership and change frequency without redundant infrastructure code.
  3. The dry-run host list and collected post-change configurations show that only the approved group received the new OSPF or ACL policy.
  4. After the edit, the desired leaf is updated and every unrelated modeled sibling retains its approved value.

Explanation

Correct Answer

C:

The dry-run host list and collected post-change configurations show that only the approved group received the new OSPF or ACL policy. This directly verifies the related correction: Separate inventory groups and group variables by approved device scope, then constrain the play to the intended group. It checks the technical distinction: Ansible inventory groups and variable precedence determine which devices and values are targeted by a playbook.

Incorrect Answers

A:

The proposed action belongs to the mechanism: This directly verifies the related correction: Set compatible provider version constraints and commit the provider dependency lock file for reproducible runs. Here the stated fault follows a different mechanism: This directly verifies the related correction: Separate inventory groups and group variables by approved device scope, then constrain the play to the intended group. The corrective choice is “The dry-run host list and collected post-change configurations show that only the approved group received the new OSPF or ACL policy”.

B:

The offered action targets: This directly verifies the related correction: Choose a supported declarative IaC framework for persistent desired configuration and targeted scripts for bounded imperative queries or integrations. The case facts point instead to: This directly verifies the related correction: Separate inventory groups and group variables by approved device scope, then constrain the play to the intended group. Implement “The dry-run host list and collected post-change configurations show that only the approved group received the new OSPF or ACL policy” to address that specific condition.

D:

The proposed action belongs to the mechanism: This directly verifies the related correction: Choose a supported targeted PATCH or edit operation for partial changes and reserve PUT for intentionally replacing the resource representation. Here the stated fault follows a different mechanism: This directly verifies the related correction: Separate inventory groups and group variables by approved device scope, then constrain the play to the intended group. The corrective choice is “The dry-run host list and collected post-change configurations show that only the approved group received the new OSPF or ACL policy”.

Question 18

While investigating a telemetry quality investigation for fictional Sable Valley Power, the team reports: A team exports a controller certificate and private key into a public GitLab job artifact to simplify deployment. Which engineering principle explains the described system behavior?

  1. Authentication proves identity but each network resource action requires separate policy-based authorization controls.
  2. CA-signed certificates are public trust assertions but the associated private key must remain confidential for endpoint authentication.
  3. Distributed troubleshooting requires durable transport and consistent time context; ephemeral local logs can be lost or misordered.
  4. Time-series cardinality grows with combinations of labels; volatile unique IDs defeat aggregation and strain metric storage.

Explanation

Correct Answer

B:

CA-signed certificates are public trust assertions but the associated private key must remain confidential for endpoint authentication. The corresponding repair is: Generate and store private keys in restricted secret systems and deploy only to the authorized TLS termination endpoint. Acceptance should show: Permission checks and artifact scans show no exposed private keys, while the service presents the renewed trusted certificate.

Incorrect Answers

A:

The offered statement is true for this other mechanism: The corresponding repair is: Enforce server-side per-resource authorization using authenticated identity and approved tenant or device scope. It does not explain the facts described here, which follow from: The corresponding repair is: Generate and store private keys in restricted secret systems and deploy only to the authorized TLS termination endpoint.

C:

The corresponding repair is: Synchronize clocks and ship logs to a durable centralized destination with appropriate secure, reliable transport. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Generate and store private keys in restricted secret systems and deploy only to the authorized TLS termination endpoint.

D:

The offered statement is true for this other mechanism: The corresponding repair is: Normalize telemetry dimensions to stable device and interface identifiers and avoid high-cardinality ephemeral labels. It does not explain the facts described here, which follow from: The corresponding repair is: Generate and store private keys in restricted secret systems and deploy only to the authorized TLS termination endpoint.

Question 19

While investigating a source-of-truth integration for fictional Willowfield Hospitality, the team reports: A Terraform apply starts before policy lint and network simulation checks, allowing an invalid ACL to reach live devices. Which sustainable preventive control most directly avoids a recurrence?

  1. Promote immutable build artifacts between GitLab stages instead of rebuilding from moving branches.
  2. Control source updates through review and schedule automated drift detection after deployment.
  3. Add explicit GitLab stage dependencies and enforce nonoptional predeploy validation checks.
  4. Set protected branch merge policies and link the squash commit to the reviewed change request.

Explanation

Correct Answer

C:

Add explicit GitLab stage dependencies and enforce nonoptional predeploy validation checks. This prevents the recurrence because prevalidation is a safety boundary before changing network state, separate from checks after a change completes. A matching immediate correction is: Make deployment depend on successful prevalidation jobs for schema, policy, simulation and approval checks.

Incorrect Answers

A:

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: prevalidation is a safety boundary before changing network state, separate from checks after a change completes. The matching preventive check is “Add explicit GitLab stage dependencies and enforce nonoptional predeploy validation checks”.

B:

The suggested review tracks a different technical risk: a reliable source-of-truth workflow separates approved intent from observed device state and defines how changes flow between them. Here the sustained control must address: prevalidation is a safety boundary before changing network state, separate from checks after a change completes. Choose “Add explicit GitLab stage dependencies and enforce nonoptional predeploy validation checks”.

D:

This routine guards against another 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 recurring exposure in the current case is: prevalidation is a safety boundary before changing network state, separate from checks after a change completes. The matching preventive check is “Add explicit GitLab stage dependencies and enforce nonoptional predeploy validation checks”.

Question 20

At fictional Thornwick Health Trust, during a remote branch provisioning pilot, the operator observes: An engineer builds a RESTCONF URI without a required interface-list key and receives a resource-not-found or ambiguous-target error. 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. Derive endpoint templates from the published YANG list keys and reject unkeyed destructive list updates.
  4. Exercise representative 4xx, 5xx, timeout and malformed-payload cases in contract tests before scheduling batches.

Explanation

Correct Answer

C:

Derive endpoint templates from the published YANG list keys and reject unkeyed destructive list updates. This prevents the recurrence because rESTCONF exposes list entries through resource identifiers determined by the keys declared in the YANG model. A matching immediate correction is: Address the exact YANG list instance using its fully encoded key values in the RESTCONF data resource path.

Incorrect Answers

A:

The proposed action belongs to the mechanism: infrastructure as code, low-code workflows and custom software solve different state-lifecycle and integration needs. Here the stated fault follows a different mechanism: rESTCONF exposes list entries through resource identifiers determined by the keys declared in the YANG model. The corrective choice is “Derive endpoint templates from the published YANG list keys and reject unkeyed destructive list updates”.

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: rESTCONF exposes list entries through resource identifiers determined by the keys declared in the YANG model. Implement “Derive endpoint templates from the published YANG list keys and reject unkeyed destructive list updates” to address that specific condition.

D:

The proposed action belongs to the mechanism: robust batch automation isolates errors at the per-resource boundary and retains auditable partial outcomes. Here the stated fault follows a different mechanism: rESTCONF exposes list entries through resource identifiers determined by the keys declared in the YANG model. The corrective choice is “Derive endpoint templates from the published YANG list keys and reject unkeyed destructive list updates”.