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 3

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

Question 21

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. What ongoing engineering assurance should follow the successful fix?

  1. Require validated backups, staged batches and executable rollback procedures in approved network playbooks.
  2. Design resource-state reconciliation and safe retry policies for all create and job-submission requests.
  3. Record per-platform model support and gate model-specific deploy steps on device capability checks.
  4. Publish tested module releases, enforce variable validation, and review module version upgrades across environments.

Explanation

Correct Answer

A:

Require validated backups, staged batches and executable rollback procedures in approved network playbooks. This prevents the recurrence because safe network automation separates preflight, controlled deployment, verification and recovery instead of assuming all endpoints will succeed. A matching immediate correction is: Perform per-device reachability and capability prechecks, capture backups, and stop or roll back on failed postchecks.

Incorrect Answers

B:

This routine guards against another mechanism: a network transport timeout does not prove server-side failure; blind retries of non-idempotent operations can duplicate effects. The recurring exposure in the current case is: safe network automation separates preflight, controlled deployment, verification and recovery instead of assuming all endpoints will succeed. The matching preventive check is “Require validated backups, staged batches and executable rollback procedures in approved network playbooks”.

C:

The suggested review tracks a different technical risk: model-driven APIs are available only for modules and revisions implemented by the device software, not by the client library alone. Here the sustained control must address: safe network automation separates preflight, controlled deployment, verification and recovery instead of assuming all endpoints will succeed. Choose “Require validated backups, staged batches and executable rollback procedures in approved network playbooks”.

D:

That safeguard is relevant to: terraform modules support repeated declarative resource patterns while typed inputs isolate deployment-specific configuration. The current failure instead follows from: safe network automation separates preflight, controlled deployment, verification and recovery instead of assuming all endpoints will succeed. Its prevention measure is “Require validated backups, staged batches and executable rollback procedures in approved network playbooks”.

Question 22

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 ongoing engineering assurance should follow the successful fix?

  1. Measure ingress rate, queue depth, drop rate and end-to-end sample latency with capacity alerts.
  2. Maintain tested parser/device version matrices and fail clearly when collection contracts change.
  3. Require machine-readable stage IDs and link failure summaries back to the earliest relevant stack trace.
  4. Monitor certificate expirations and trust-chain changes with automated predeployment verification.

Explanation

Correct Answer

B:

Maintain tested parser/device version matrices and fail clearly when collection contracts change. This prevents the recurrence because model-driven test tools depend on supported device schemas and parser versions; missing parsed data is not proof of missing network function. A matching immediate correction is: Validate parser and platform compatibility and distinguish collection or parsing errors from actual network-state assertion failures.

Incorrect Answers

A:

This routine guards against another mechanism: streaming telemetry pipelines have collectors, transports, ingestion queues and storage capacity that can fail independently of device subscriptions. The recurring exposure in the current case is: model-driven test tools depend on supported device schemas and parser versions; missing parsed data is not proof of missing network function. The matching preventive check is “Maintain tested parser/device version matrices and fail clearly when collection contracts change”.

C:

That safeguard is relevant to: downstream error messages can reflect cascaded failures; causality is established by correlating the earlier specific event and affected resource. The current failure instead follows from: model-driven test tools depend on supported device schemas and parser versions; missing parsed data is not proof of missing network function. Its prevention measure is “Maintain tested parser/device version matrices and fail clearly when collection contracts change”.

D:

This routine guards against another mechanism: tLS server validation depends on trusted issuer chains and hostname identity; bypassing verification defeats server authentication. The recurring exposure in the current case is: model-driven test tools depend on supported device schemas and parser versions; missing parsed data is not proof of missing network function. The matching preventive check is “Maintain tested parser/device version matrices and fail clearly when collection contracts change”.

Question 23

At fictional Cobalt Ridge Bank, an acceptance review of a campus API automation rollout finds: A controller script issues interface changes using a module namespace unavailable on a branch router's installed version. Which targeted correction best addresses the network automation failure?

  1. Configure a shared protected Terraform state backend with supported locking and serialize competing applies against the same state.
  2. Use the supported token refresh flow with secret storage and distinguish unauthenticated 401 from authorized-but-forbidden 403 responses.
  3. Select the tool and deployment pattern by risk, state persistence, change scope, rollback capability and approval obligations.
  4. Discover supported YANG modules or capabilities before using module-specific RESTCONF data paths, and branch for supported models.

Explanation

Correct Answer

D:

Discover supported YANG modules or capabilities before using module-specific RESTCONF data paths, and branch for supported models. This addresses the problem because model-driven APIs are available only for modules and revisions implemented by the device software, not by the client library alone. Confirm success using: The preflight confirms the required module and revision per target, or marks incompatible devices without making changes.

Incorrect Answers

A:

The proposed action belongs to the mechanism: terraform state tracks managed resource associations; concurrent writes without locking can corrupt effective desired-state coordination. Here the stated fault follows a different mechanism: model-driven APIs are available only for modules and revisions implemented by the device software, not by the client library alone. The corrective choice is “Discover supported YANG modules or capabilities before using module-specific RESTCONF data paths, and branch for supported models”.

B:

The offered action targets: an access-token lifecycle and authorization scope are distinct concerns; repeated reuse of expired or insufficient tokens cannot resolve them. The case facts point instead to: model-driven APIs are available only for modules and revisions implemented by the device software, not by the client library alone. Implement “Discover supported YANG modules or capabilities before using module-specific RESTCONF data paths, and branch for supported models” to address that specific condition.

C:

This alternative is a response to another technical cause: automation choice is driven by lifecycle and operational risk rather than by a single preferred programming tool. The reported case instead depends on: model-driven APIs are available only for modules and revisions implemented by the device software, not by the client library alone. The action that directly addresses it is “Discover supported YANG modules or capabilities before using module-specific RESTCONF data paths, and branch for supported models”.

Question 24

At fictional Windward Maritime, during a GitLab deployment pipeline rehearsal, the operator observes: A GitLab pipeline starts network integration tests before the virtual lab nodes have completed booting and connectivity checks. Which targeted correction best addresses the network automation failure?

  1. Cherry-pick the specific reviewed hotfix commit into the target maintenance branch and test the resulting change.
  2. Provision the CML topology reproducibly and wait for all required node readiness conditions before tests begin.
  3. Inspect the failed job logs and classify whether build, dependency, test or environment validation failed before making a targeted fix.
  4. Pin compatible build tool and package versions, update the lockfile and test upgrades in a separate controlled pipeline.

Explanation

Correct Answer

B:

Provision the CML topology reproducibly and wait for all required node readiness conditions before tests begin. This addresses the problem because a reproducible simulation needs controlled topology definitions and readiness gates to avoid timing-dependent false failures. Confirm success using: The pipeline consistently reaches a ready test topology and records the versioned lab definition and run results.

Incorrect Answers

A:

The offered action targets: git cherry-pick applies the change introduced by selected commit(s) onto the current branch, creating new history in that branch. The case facts point instead to: a reproducible simulation needs controlled topology definitions and readiness gates to avoid timing-dependent false failures. Implement “Provision the CML topology reproducibly and wait for all required node readiness conditions before tests begin” to address that specific condition.

C:

The proposed action belongs to the mechanism: a GitLab pipeline exit code identifies failure, while job logs and test artifacts reveal the specific causal stage and assertion. Here the stated fault follows a different mechanism: a reproducible simulation needs controlled topology definitions and readiness gates to avoid timing-dependent false failures. The corrective choice is “Provision the CML topology reproducibly and wait for all required node readiness conditions before tests begin”.

D:

The offered action targets: unbounded dependency upgrades can introduce incompatible APIs and nondeterministic CI failures even when repository code is unchanged. The case facts point instead to: a reproducible simulation needs controlled topology definitions and readiness gates to avoid timing-dependent false failures. Implement “Provision the CML topology reproducibly and wait for all required node readiness conditions before tests begin” to address that specific condition.

Question 25

During a conversational network agent pilot at fictional Westlake Biomedicine, the change record states: An LLM invents a controller API path not documented in the deployed Cisco software and presents it as a certain fix. Which targeted correction best addresses the network automation failure?

  1. Issue read-only scoped identity credentials for diagnostic agents and place separate approval boundaries around mutating tools.
  2. Require citation to a compatible authoritative reference and fail closed or escalate when command syntax or device version is uncertain.
  3. Return structured success and error states with source timestamps and bounded API timeouts rather than silently substituting empty values.
  4. Treat retrieved logs as untrusted data and enforce instruction hierarchy and independent tool permissions outside the model.

Explanation

Correct Answer

B:

Require citation to a compatible authoritative reference and fail closed or escalate when command syntax or device version is uncertain. This addresses the problem because model fluency is not evidence of device capability; uncertain technical recommendations require explicit verification before action. Confirm success using: The assistant identifies missing version evidence and withholds unverified commands instead of fabricating supported APIs.

Incorrect Answers

A:

This alternative is a response to another technical cause: the model is not a reliable security principal; tool identities and server-side authorization bound the damage of agent errors. The reported case instead depends on: model fluency is not evidence of device capability; uncertain technical recommendations require explicit verification before action. The action that directly addresses it is “Require citation to a compatible authoritative reference and fail closed or escalate when command syntax or device version is uncertain”.

C:

The offered action targets: tool wrappers must preserve the meaning of missing, stale and failed data for the consumer agent. The case facts point instead to: model fluency is not evidence of device capability; uncertain technical recommendations require explicit verification before action. Implement “Require citation to a compatible authoritative reference and fail closed or escalate when command syntax or device version is uncertain” to address that specific condition.

D:

This alternative is a response to another technical cause: prompt injection attempts to convert lower-trust retrieved content into high-priority instructions across an AI-agent trust boundary. The reported case instead depends on: model fluency is not evidence of device capability; uncertain technical recommendations require explicit verification before action. The action that directly addresses it is “Require citation to a compatible authoritative reference and fail closed or escalate when command syntax or device version is uncertain”.

Question 26

At fictional Cobalt Ridge Bank, an acceptance review of a campus API automation rollout finds: A configuration orchestrator launches a second identical device-change operation when the first asynchronous submission has not yet been acknowledged. What should the team add to its network automation operating process?

  1. Require representative failure-path tests before approving a low-code production integration.
  2. Design resource-state reconciliation and safe retry policies for all create and job-submission requests.
  3. Validate request headers, YANG schemas and sample GET/PATCH transactions in a lab before device-wide rollout.
  4. Require remote state access controls, locking verification and serialized deployment jobs for shared workspaces.

Explanation

Correct Answer

B:

Design resource-state reconciliation and safe retry policies for all create and job-submission requests. This prevents the recurrence because a network transport timeout does not prove server-side failure; blind retries of non-idempotent operations can duplicate effects. A matching immediate correction is: Before retrying a potentially non-idempotent change, check resulting resource state or use a supported idempotency or operation key.

Incorrect Answers

A:

The proposed action belongs to the mechanism: low-code accelerates common supported integrations but may constrain complex branching and custom transaction semantics. Here the stated fault follows a different mechanism: a network transport timeout does not prove server-side failure; blind retries of non-idempotent operations can duplicate effects. The corrective choice is “Design resource-state reconciliation and safe retry policies for all create and job-submission requests”.

C:

This alternative is a response to another technical cause: rESTCONF manipulates YANG-defined resources over HTTP; both resource paths and payload media encoding must match the model. The reported case instead depends on: a network transport timeout does not prove server-side failure; blind retries of non-idempotent operations can duplicate effects. The action that directly addresses it is “Design resource-state reconciliation and safe retry policies for all create and job-submission requests”.

D:

The proposed action belongs to the mechanism: terraform state tracks managed resource associations; concurrent writes without locking can corrupt effective desired-state coordination. Here the stated fault follows a different mechanism: a network transport timeout does not prove server-side failure; blind retries of non-idempotent operations can duplicate effects. The corrective choice is “Design resource-state reconciliation and safe retry policies for all create and job-submission requests”.

Question 27

During a source-of-truth integration at fictional Violet Ridge Resorts, the change record states: A network automation release branch merges conflicting inventory files and a hurried commit leaves both incompatible configuration blocks in place. What underlying technical distinction accounts for this failure?

  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. Deployment command success is not the same as verified service success; operational checks must follow state changes.
  4. Git cannot automatically reconcile overlapping divergent edits; a human or reviewed tool must choose the resulting content before merge completion.

Explanation

Correct Answer

D:

Git cannot automatically reconcile overlapping divergent edits; a human or reviewed tool must choose the resulting content before merge completion. The corresponding repair is: Resolve the conflicting lines deliberately against the approved desired network state, run validation, then commit the merged result. Acceptance should show: The merged file has no conflict markers, passes schema tests and retains the intended requirements from both branches.

Incorrect Answers

A:

The offered statement is true for this other mechanism: The corresponding repair is: Inspect the failed job logs and classify whether build, dependency, test or environment validation failed before making a targeted fix. It does not explain the facts described here, which follow from: The corresponding repair is: Resolve the conflicting lines deliberately against the approved desired network state, run validation, then commit the merged result.

B:

This principle describes a separate cause: The corresponding repair is: Deploy through bounded environment-scoped jobs with approved service credentials and staged canary or batch rollout. The reported condition is governed by: The corresponding repair is: Resolve the conflicting lines deliberately against the approved desired network state, run validation, then commit the merged result. The two mechanisms should not be conflated.

C:

The corresponding repair is: Run objective-based postdeployment checks and fail or roll back the change when observed network behavior contradicts intent. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Resolve the conflicting lines deliberately against the approved desired network state, run validation, then commit the merged result.

Question 28

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

  1. Replace non-idempotent shell appends with the platform-aware Ansible network configuration module and explicit desired interface state.
  2. Handle per-target HTTP, parsing and retryable exceptions and persist a failure summary without misreporting completed targets.
  3. Extract a versioned reusable Terraform module with validated input variables for site-specific network parameters.
  4. Follow the API's documented cursor or Link continuation until exhaustion, merging results while protecting against repeated cursors.

Explanation

Correct Answer

B:

Handle per-target HTTP, parsing and retryable exceptions and persist a failure summary without misreporting completed targets. This addresses the problem because robust batch automation isolates errors at the per-resource boundary and retains auditable partial outcomes. Confirm success using: The job records successes and failures by device, retries only supported transient cases, and does not claim full success when any target fails.

Incorrect Answers

A:

This alternative is a response to another technical cause: ansible's desired-state-aware network modules compare declared configuration with device state before determining required changes. The reported case instead depends on: robust batch automation isolates errors at the per-resource boundary and retains auditable partial outcomes. The action that directly addresses it is “Handle per-target HTTP, parsing and retryable exceptions and persist a failure summary without misreporting completed targets”.

C:

The offered action targets: terraform modules support repeated declarative resource patterns while typed inputs isolate deployment-specific configuration. The case facts point instead to: robust batch automation isolates errors at the per-resource boundary and retains auditable partial outcomes. Implement “Handle per-target HTTP, parsing and retryable exceptions and persist a failure summary without misreporting completed targets” to address that specific condition.

D:

This alternative is a response to another technical cause: many platform APIs paginate large result sets; the first HTTP success response may contain only a subset. The reported case instead depends on: robust batch automation isolates errors at the per-resource boundary and retains auditable partial outcomes. The action that directly addresses it is “Handle per-target HTTP, parsing and retryable exceptions and persist a failure summary without misreporting completed targets”.

Question 29

While investigating a FastMCP security review for fictional Elmcrest Theatre, the team reports: A retrieved configuration note includes a disguised URL that would leak network inventory if the agent automatically opens it. What technical evidence should be required before closing this change?

  1. The review artifact identifies dependencies, licenses and any material code reuse concerns before the release is approved.
  2. Test reports expose false positives, false negatives and unsupported recommendations before approval for a broader network scope.
  3. A simulated malicious tool response cannot trigger outbound requests to unapproved destinations or reveal hidden credentials.
  4. The assistant outputs a reviewable structured plan and no device mutation occurs until the scoped proposal is approved.

Explanation

Correct Answer

C:

A simulated malicious tool response cannot trigger outbound requests to unapproved destinations or reveal hidden credentials. This directly verifies the related correction: Restrict tool egress to approved destinations and never grant untrusted retrieved text authority to choose exfiltration endpoints. It checks the technical distinction: Tool results are untrusted external input; unrestricted outbound connectivity turns an injected instruction into a data-exfiltration path.

Incorrect Answers

A:

The alternative verifies a different condition: This directly verifies the related correction: Review generated code provenance, included dependencies and organizational IP policy before accepting it into the repository. The current case instead depends on: This directly verifies the related correction: Restrict tool egress to approved destinations and never grant untrusted retrieved text authority to choose exfiltration endpoints. Confirm that “A simulated malicious tool response cannot trigger outbound requests to unapproved destinations or reveal hidden credentials”.

B:

That test belongs to another control with this basis: This directly verifies the related correction: Evaluate the agent on a representative labeled test set with difficult, adversarial and negative cases, measuring factual error and unsafe-action rates. In the current case, the governing reason is: This directly verifies the related correction: Restrict tool egress to approved destinations and never grant untrusted retrieved text authority to choose exfiltration endpoints. The direct verification is “A simulated malicious tool response cannot trigger outbound requests to unapproved destinations or reveal hidden credentials”.

D:

The alternative verifies a different condition: This directly verifies the related correction: Convert user requests into a typed proposed intent with explicit targets, preconditions and a separate human-approved execution path. The current case instead depends on: This directly verifies the related correction: Restrict tool egress to approved destinations and never grant untrusted retrieved text authority to choose exfiltration endpoints. Confirm that “A simulated malicious tool response cannot trigger outbound requests to unapproved destinations or reveal hidden credentials”.

Question 30

While investigating an AI recommendation accuracy study for fictional Sunrise Aeronautics, the team reports: A conversational network assistant is permitted to run a harmless ping but then automatically chains into an unapproved ACL modification. What acceptance check would prove the intended behavior was restored?

  1. Audit logs and data-loss-prevention checks show that prompts and tool responses contain no live credentials or confidential customer payloads.
  2. A simulated malicious tool response cannot trigger outbound requests to unapproved destinations or reveal hidden credentials.
  3. A conversational diagnostic completes safely without write access, and a proposed write remains pending until an authorized approver confirms.
  4. A poisoned-source test yields a flagged uncertainty or validated official-source citation instead of an unsafe configuration recommendation.

Explanation

Correct Answer

C:

A conversational diagnostic completes safely without write access, and a proposed write remains pending until an authorized approver confirms. This directly verifies the related correction: Separate read-only diagnostic tools from mutating tools and require an explicit scoped approval step before any privileged operation. It checks the technical distinction: Agent tool chaining can enlarge the blast radius of an ambiguous user instruction unless execution permissions are independently gated.

Incorrect Answers

A:

That test belongs to another control with this basis: This directly verifies the related correction: Sanitize inputs and use an approved private or contractually controlled AI service without exposing secrets or regulated network data. In the current case, the governing reason is: This directly verifies the related correction: Separate read-only diagnostic tools from mutating tools and require an explicit scoped approval step before any privileged operation. The direct verification is “A conversational diagnostic completes safely without write access, and a proposed write remains pending until an authorized approver confirms”.

B:

This observation would test a different technical dependency: This directly verifies the related correction: Restrict tool egress to approved destinations and never grant untrusted retrieved text authority to choose exfiltration endpoints. The current issue is governed by: This directly verifies the related correction: Separate read-only diagnostic tools from mutating tools and require an explicit scoped approval step before any privileged operation. Its decisive check is “A conversational diagnostic completes safely without write access, and a proposed write remains pending until an authorized approver confirms”.

D:

That test belongs to another control with this basis: This directly verifies the related correction: Ground actionable recommendations in trusted versioned technical references and reject unsupported or conflicting retrieved claims. In the current case, the governing reason is: This directly verifies the related correction: Separate read-only diagnostic tools from mutating tools and require an explicit scoped approval step before any privileged operation. The direct verification is “A conversational diagnostic completes safely without write access, and a proposed write remains pending until an authorized approver confirms”.