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 21

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

Question 201

At fictional Willowfield Hospitality, during a version-control hotfix, the operator observes: A developer accidentally stages a generated credentials fixture in an unpushed commit and needs to revise local commit history before review. Which control best prevents this particular failure from recurring?

  1. Test slow dependency startup and review Compose healthchecks for all network automation support services.
  2. Control source updates through review and schedule automated drift detection after deployment.
  3. Forbid destructive reset on shared branches and require review of soft, mixed and hard reset effects.
  4. Promote immutable build artifacts between GitLab stages instead of rebuilding from moving branches.

Explanation

Correct Answer

C:

Forbid destructive reset on shared branches and require review of soft, mixed and hard reset effects. This prevents the recurrence because git reset moves HEAD and optionally the index and worktree, making it suitable for carefully revising unpublished local history. A matching immediate correction is: Use an appropriate local Git reset to move the branch pointer and rebuild the unpublished commit while protecting wanted working changes.

Incorrect Answers

A:

That safeguard is relevant to: container start ordering does not inherently guarantee service readiness; health conditions and retries address that gap. The current failure instead follows from: git reset moves HEAD and optionally the index and worktree, making it suitable for carefully revising unpublished local history. Its prevention measure is “Forbid destructive reset on shared branches and require review of soft, mixed and hard reset effects”.

B:

This routine guards against another mechanism: a reliable source-of-truth workflow separates approved intent from observed device state and defines how changes flow between them. The recurring exposure in the current case is: git reset moves HEAD and optionally the index and worktree, making it suitable for carefully revising unpublished local history. The matching preventive check is “Forbid destructive reset on shared branches and require review of soft, mixed and hard reset effects”.

D:

That safeguard is relevant to: a CI build stage turns source and fixed dependencies into a traceable deployment input used by later stages. The current failure instead follows from: git reset moves HEAD and optionally the index and worktree, making it suitable for carefully revising unpublished local history. Its prevention measure is “Forbid destructive reset on shared branches and require review of soft, mixed and hard reset effects”.

Question 202

At fictional Willowfield Hospitality, during a version-control hotfix, the operator observes: A GitLab job is marked failed after a network policy unit test, but the operator reruns deployment without inspecting the failing assertion. What mechanism is most directly responsible for these symptoms?

  1. Git revert records an inverse patch in new history rather than moving shared branch pointers backward.
  2. A GitLab pipeline exit code identifies failure, while job logs and test artifacts reveal the specific causal stage and assertion.
  3. Reverting a merge requires an explicit mainline perspective so Git knows which parent is the retained baseline.
  4. Prevalidation is a safety boundary before changing network state, separate from checks after a change completes.

Explanation

Correct Answer

B:

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. Applied here, the relevant facts are: A GitLab job is marked failed after a network policy unit test, but the operator reruns deployment without inspecting the failing assertion. The question asks what mechanism is most directly responsible for these symptoms.

Incorrect Answers

A:

This principle describes a separate cause: The corresponding repair is: Create a reviewed Git revert commit for the offending change and run the full network automation release tests. 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.

C:

The offered statement is true for this other mechanism: The corresponding repair is: Review the merge graph and select the correct mainline parent when reverting the merge, then validate the resulting tree diff. 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.

D:

This principle describes a separate cause: The corresponding repair is: Make deployment depend on successful prevalidation jobs for schema, policy, simulation and approval checks. 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.

Question 203

While investigating an AI recommendation accuracy study for fictional Sunrise Aeronautics, the team reports: An AI assistant recommends deleting the running VLAN configuration to fix an unrelated RESTCONF authentication failure. Which engineering principle explains the described system behavior?

  1. Tool wrappers must preserve the meaning of missing, stale and failed data for the consumer agent.
  2. Conversation memory is not authoritative network state; stale context and scope leakage create wrong-target operational risk.
  3. Generative systems can propose plausible-looking but incorrect commands; independent executable validation is required for safe infrastructure changes.
  4. High aggregate answer accuracy can hide safety-critical errors; validation must measure behavior on representative failure modes.

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. Applied here, the relevant facts are: An AI assistant recommends deleting the running VLAN configuration to fix an unrelated RESTCONF authentication failure. The question asks which engineering principle explains the described system behavior.

Incorrect Answers

A:

The corresponding repair is: Return structured success and error states with source timestamps and bounded API timeouts rather than silently substituting empty values. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Subject AI-suggested changes to schema and unit tests, simulated network execution, policy checks and human change approval.

B:

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.

D:

The corresponding repair is: Evaluate the agent on a representative labeled test set with difficult, adversarial and negative cases, measuring factual error and unsafe-action rates. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Subject AI-suggested changes to schema and unit tests, simulated network execution, policy checks and human change approval.

Question 204

While investigating an automation service security audit for fictional Coastal Meadow Labs, the team reports: During a fabric-wide link flap, a subscriber's ingestion queue overflows while dashboards continue displaying incomplete metrics as if current. What should the engineer change first to resolve this specific issue?

  1. Authenticate webhook delivery and implement bounded retries with deduplication or delivery-state accounting.
  2. Use an approved DNS endpoint covered by the certificate SAN or reissue a certificate with correct service identities.
  3. Introduce bounded buffering, backpressure monitoring and horizontal ingestion capacity with visible gap or loss reporting.
  4. Synchronize clocks and ship logs to a durable centralized destination with appropriate secure, reliable transport.

Explanation

Correct Answer

C:

Introduce bounded buffering, backpressure monitoring and horizontal ingestion capacity with visible gap or loss reporting. This addresses the problem because streaming telemetry pipelines have collectors, transports, ingestion queues and storage capacity that can fail independently of device subscriptions. Confirm success using: Load tests show telemetry consumers keeping up with target throughput or explicitly signaling lost samples without presenting false continuity.

Incorrect Answers

A:

The offered action targets: webhooks are asynchronous network events; integrity, delivery acknowledgements and idempotent processing are separate reliability needs. The case facts point instead to: streaming telemetry pipelines have collectors, transports, ingestion queues and storage capacity that can fail independently of device subscriptions. Implement “Introduce bounded buffering, backpressure monitoring and horizontal ingestion capacity with visible gap or loss reporting” to address that specific condition.

B:

This alternative is a response to another technical cause: modern TLS clients validate the connection name against certificate subject alternative names, not merely that a CA issued the cert. The reported case instead depends on: streaming telemetry pipelines have collectors, transports, ingestion queues and storage capacity that can fail independently of device subscriptions. The action that directly addresses it is “Introduce bounded buffering, backpressure monitoring and horizontal ingestion capacity with visible gap or loss reporting”.

D:

The offered action targets: distributed troubleshooting requires durable transport and consistent time context; ephemeral local logs can be lost or misordered. The case facts point instead to: streaming telemetry pipelines have collectors, transports, ingestion queues and storage capacity that can fail independently of device subscriptions. Implement “Introduce bounded buffering, backpressure monitoring and horizontal ingestion capacity with visible gap or loss reporting” to address that specific condition.

Question 205

At fictional Violet Ridge Resorts, an acceptance review of a version-control hotfix finds: An engineer must port one approved RESTCONF bug fix to an older support branch without incorporating unrelated commits. What is the appropriate response to this network automation condition?

  1. Construct JSON using the published YANG container hierarchy, qualified node names and correct value types.
  2. Cherry-pick the specific reviewed hotfix commit into the target maintenance branch and test the resulting change.
  3. Review the merge graph and select the correct mainline parent when reverting the merge, then validate the resulting tree diff.
  4. Use an approved squash merge to combine reviewed feature changes into one commit while preserving the final content.

Explanation

Correct Answer

B:

Cherry-pick the specific reviewed hotfix commit into the target maintenance branch and test the resulting change. This addresses the problem because git cherry-pick applies the change introduced by selected commit(s) onto the current branch, creating new history in that branch. Confirm success using: The maintenance branch contains the intended patch without unrelated feature commits and passes the target release tests.

Incorrect Answers

A:

This alternative is a response to another technical cause: yANG defines node hierarchy, namespaces, list keys and data types; conforming JSON must preserve that structure. The reported case instead depends on: git cherry-pick applies the change introduced by selected commit(s) onto the current branch, creating new history in that branch. The action that directly addresses it is “Cherry-pick the specific reviewed hotfix commit into the target maintenance branch and test the resulting change”.

C:

The offered action targets: reverting a merge requires an explicit mainline perspective so Git knows which parent is the retained baseline. The case facts point instead to: git cherry-pick applies the change introduced by selected commit(s) onto the current branch, creating new history in that branch. Implement “Cherry-pick the specific reviewed hotfix commit into the target maintenance branch and test the resulting change” to address that specific condition.

D:

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: git cherry-pick applies the change introduced by selected commit(s) onto the current branch, creating new history in that branch. The action that directly addresses it is “Cherry-pick the specific reviewed hotfix commit into the target maintenance branch and test the resulting change”.

Question 206

During a production change postcheck at fictional Marble Bay Software, the change record states: An internal network automation API checks that users are logged in but does not verify which device groups they are permitted to change. Which implementation action best meets the observed technical requirement?

  1. Classify authentication failures and authorization denials separately, then correct token validity or RBAC scope accordingly.
  2. Enforce server-side per-resource authorization using authenticated identity and approved tenant or device scope.
  3. Validate parser and platform compatibility and distinguish collection or parsing errors from actual network-state assertion failures.
  4. Capture structured prechange operational state with pyATS, apply the change, then compare relevant postchange state and assert expected invariants.

Explanation

Correct Answer

B:

Enforce server-side per-resource authorization using authenticated identity and approved tenant or device scope. This addresses the problem because authentication proves identity but each network resource action requires separate policy-based authorization controls. Confirm success using: Cross-tenant modification attempts are rejected with a denial and approved users can change only authorized resources.

Incorrect Answers

A:

The alternative verifies a different condition: hTTP 401 generally signals missing or invalid authentication while 403 indicates access denied to an authenticated request. The current case instead depends on: authentication proves identity but each network resource action requires separate policy-based authorization controls. Confirm that “Enforce server-side per-resource authorization using authenticated identity and approved tenant or device scope”.

C:

This observation would test a different technical dependency: model-driven test tools depend on supported device schemas and parser versions; missing parsed data is not proof of missing network function. The current issue is governed by: authentication proves identity but each network resource action requires separate policy-based authorization controls. Its decisive check is “Enforce server-side per-resource authorization using authenticated identity and approved tenant or device scope”.

D:

The alternative verifies a different condition: pyATS can learn and compare device operational state to detect unintended network effects beyond text config diffs. The current case instead depends on: authentication proves identity but each network resource action requires separate policy-based authorization controls. Confirm that “Enforce server-side per-resource authorization using authenticated identity and approved tenant or device scope”.

Question 207

During a remote branch provisioning pilot at fictional Northshore Cloud, the change record states: One device returns a 503 response and the Python batch raises an uncaught exception, abandoning configuration for all other approved targets. What ongoing engineering assurance should follow the successful fix?

  1. Require representative failure-path tests before approving a low-code production integration.
  2. Enforce pre-commit secret scans, restricted vault permissions, credential rotation and no_log controls for sensitive tasks.
  3. Exercise representative 4xx, 5xx, timeout and malformed-payload cases in contract tests before scheduling batches.
  4. Add check-mode previews and a second-run idempotence assertion to the network playbook CI gate.

Explanation

Correct Answer

C:

Exercise representative 4xx, 5xx, timeout and malformed-payload cases in contract tests before scheduling batches. This prevents the recurrence because robust batch automation isolates errors at the per-resource boundary and retains auditable partial outcomes. A matching immediate correction is: Handle per-target HTTP, parsing and retryable exceptions and persist a failure summary without misreporting completed targets.

Incorrect Answers

A:

That safeguard is relevant to: low-code accelerates common supported integrations but may constrain complex branching and custom transaction semantics. The current failure instead follows from: robust batch automation isolates errors at the per-resource boundary and retains auditable partial outcomes. Its prevention measure is “Exercise representative 4xx, 5xx, timeout and malformed-payload cases in contract tests before scheduling batches”.

B:

This routine guards against another mechanism: automation credentials need confidentiality at rest and in output; inventory convenience does not justify committing secrets. The recurring exposure in the current case is: robust batch automation isolates errors at the per-resource boundary and retains auditable partial outcomes. The matching preventive check is “Exercise representative 4xx, 5xx, timeout and malformed-payload cases in contract tests before scheduling batches”.

D:

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: robust batch automation isolates errors at the per-resource boundary and retains auditable partial outcomes. Its prevention measure is “Exercise representative 4xx, 5xx, timeout and malformed-payload cases in contract tests before scheduling batches”.

Question 208

While investigating an AI recommendation accuracy study for fictional Sunrise Aeronautics, the team reports: An AI assistant recommends deleting the running VLAN configuration to fix an unrelated RESTCONF authentication failure. What technical evidence should be required before closing this change?

  1. Malformed IDs and cross-tenant requests are rejected predictably while approved tool calls return scoped data.
  2. Invalid module parameters or destructive unrelated changes fail the predeployment gates and never reach production devices.
  3. The validation crosschecks observed interface or VLAN state before accepting a proposed operation and flags missing telemetry as uncertainty.
  4. Two simulated tenants can query only their own device records and cross-tenant tool attempts are denied and audited.

Explanation

Correct Answer

B:

Invalid module parameters or destructive unrelated changes fail the predeployment gates and never reach production devices. This directly verifies the related correction: Subject AI-suggested changes to schema and unit tests, simulated network execution, policy checks and human change approval. It checks the technical distinction: Generative systems can propose plausible-looking but incorrect commands; independent executable validation is required for safe infrastructure changes. Applied here, the relevant facts are: An AI assistant recommends deleting the running VLAN configuration to fix an unrelated RESTCONF authentication failure. The question asks what technical evidence should be required before closing this change.

Incorrect Answers

A:

This observation would test a different technical dependency: This directly verifies the related correction: Define typed, validated tool arguments with explicit device allowlists and reject invalid or unauthorized inputs at the server boundary. The current issue is governed by: This directly verifies the related correction: Subject AI-suggested changes to schema and unit tests, simulated network execution, policy checks and human change approval. Its decisive check is “Invalid module parameters or destructive unrelated changes fail the predeployment gates and never reach production devices”.

C:

That test belongs to another control with this basis: This directly verifies the related correction: Check AI conclusions against fresh independent device and controller evidence with explicit freshness and confidence rules. In the current case, the governing reason is: This directly verifies the related correction: Subject AI-suggested changes to schema and unit tests, simulated network execution, policy checks and human change approval. The direct verification is “Invalid module parameters or destructive unrelated changes fail the predeployment gates and never reach production devices”.

D:

This observation would test a different technical dependency: This directly verifies the related correction: Authenticate each MCP client, authorize its tool calls by tenant identity and isolate credential/session context. The current issue is governed by: This directly verifies the related correction: Subject AI-suggested changes to schema and unit tests, simulated network execution, policy checks and human change approval. Its decisive check is “Invalid module parameters or destructive unrelated changes fail the predeployment gates and never reach production devices”.

Question 209

During an AI recommendation accuracy study at fictional Amberlight Energy, the change record states: An AI recommendation service is approved after only a few successful demos and then misses unsafe configuration proposals in production. What should the team add to its network automation operating process?

  1. Maintain a versioned adversarial evaluation suite and block regressions in unsafe recommendation rates.
  2. Test parameter bounds, tenant authorization and injection input against each FastMCP exposed operation.
  3. Enforce identity binding, tenant-isolated caches and tool-level audit and RBAC tests for MCP services.
  4. Tag provenance and document freshness, test poisoned retrieval cases, and gate device changes on deterministic validation.

Explanation

Correct Answer

A:

Maintain a versioned adversarial evaluation suite and block regressions in unsafe recommendation rates. This prevents the recurrence because high aggregate answer accuracy can hide safety-critical errors; validation must measure behavior on representative failure modes. A matching immediate correction is: Evaluate the agent on a representative labeled test set with difficult, adversarial and negative cases, measuring factual error and unsafe-action rates.

Incorrect Answers

B:

The offered action targets: typed MCP tool schemas improve interoperability but server-side validation remains necessary even for a well-formed client call. The case facts point instead to: high aggregate answer accuracy can hide safety-critical errors; validation must measure behavior on representative failure modes. Implement “Maintain a versioned adversarial evaluation suite and block regressions in unsafe recommendation rates” to address that specific condition.

C:

This alternative is a response to another technical cause: an MCP server is an integration boundary and must not treat model-selected identity strings as verified security credentials. The reported case instead depends on: high aggregate answer accuracy can hide safety-critical errors; validation must measure behavior on representative failure modes. The action that directly addresses it is “Maintain a versioned adversarial evaluation suite and block regressions in unsafe recommendation rates”.

D:

The proposed action belongs to the mechanism: retrieval-augmented systems can inherit false or hostile data; source quality and technical cross-checks must precede action. Here the stated fault follows a different mechanism: high aggregate answer accuracy can hide safety-critical errors; validation must measure behavior on representative failure modes. The corrective choice is “Maintain a versioned adversarial evaluation suite and block regressions in unsafe recommendation rates”.

Question 210

At fictional Cedarbridge Care Systems, during a campus API automation rollout, the operator observes: A VLAN deployment continues after half the switches fail connectivity tests, creating an incomplete campus rollout. Which explanation best matches the actual broken dependency?

  1. Safe network automation separates preflight, controlled deployment, verification and recovery instead of assuming all endpoints will succeed.
  2. YANG distinguishes configuration intent from read-only operational state; successful config writes do not establish runtime protocol health.
  3. A network transport timeout does not prove server-side failure; blind retries of non-idempotent operations can duplicate effects.
  4. HTTP 429 signals server-enforced rate limits; API client backoff must consider shared rate budgets and Retry-After semantics.

Explanation

Correct Answer

A:

Safe network automation separates preflight, controlled deployment, verification and recovery instead of assuming all endpoints will succeed. The corresponding repair is: Perform per-device reachability and capability prechecks, capture backups, and stop or roll back on failed postchecks. Acceptance should show: A failed device causes a controlled halt and restoration, and successful devices pass their intended config comparisons. Applied here, the relevant facts are: A VLAN deployment continues after half the switches fail connectivity tests, creating an incomplete campus rollout. The question asks which explanation best matches the actual broken dependency.

Incorrect Answers

B:

This alternative is a response to another technical cause: The corresponding repair is: Read intended configuration and runtime operational YANG data from their appropriate modeled resources, and write only configurable leaves. The reported case instead depends on: The corresponding repair is: Perform per-device reachability and capability prechecks, capture backups, and stop or roll back on failed postchecks. The action that directly addresses it is “Safe network automation separates preflight, controlled deployment, verification and recovery instead of assuming all endpoints will succeed”.

C:

The proposed action belongs to the mechanism: The corresponding repair is: Before retrying a potentially non-idempotent change, check resulting resource state or use a supported idempotency or operation key. Here the stated fault follows a different mechanism: The corresponding repair is: Perform per-device reachability and capability prechecks, capture backups, and stop or roll back on failed postchecks. The corrective choice is “Safe network automation separates preflight, controlled deployment, verification and recovery instead of assuming all endpoints will succeed”.

D:

The offered action targets: The corresponding repair is: Respect rate-limit response headers and coordinate bounded exponential backoff with jitter under the shared API budget. The case facts point instead to: The corresponding repair is: Perform per-device reachability and capability prechecks, capture backups, and stop or roll back on failed postchecks. Implement “Safe network automation separates preflight, controlled deployment, verification and recovery instead of assuming all endpoints will succeed” to address that specific condition.