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 4

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

Question 31

During a network policy migration at fictional Cobalt Ridge Bank, the change record states: A switch management project applies new ACLs without taking pre-change configuration backups and cannot restore a known-good policy after errors. Which engineering principle explains the described system behavior?

  1. Safe network automation separates preflight, controlled deployment, verification and recovery instead of assuming all endpoints will succeed.
  2. Terraform state tracks managed resource associations; concurrent writes without locking can corrupt effective desired-state coordination.
  3. Low-code accelerates common supported integrations but may constrain complex branching and custom transaction semantics.
  4. Cross-platform automation benefits from a shared intent model but must translate differences in native device APIs and models.

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.

Incorrect Answers

B:

The corresponding repair is: Configure a shared protected Terraform state backend with supported locking and serialize competing applies against the same state. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Perform per-device reachability and capability prechecks, capture backups, and stop or roll back on failed postchecks.

C:

The offered statement is true for this other mechanism: The corresponding repair is: Match workflow complexity, vendor connector capability and error recovery needs to low-code or custom application design after a capability pilot. It does not explain the facts described here, which follow from: The corresponding repair is: Perform per-device reachability and capability prechecks, capture backups, and stop or roll back on failed postchecks.

D:

This principle describes a separate cause: The corresponding repair is: Use inventory capability detection and platform-specific adapters behind a common validated intent model. The reported condition is governed by: The corresponding repair is: Perform per-device reachability and capability prechecks, capture backups, and stop or roll back on failed postchecks. The two mechanisms should not be conflated.

Question 32

At fictional Sable Valley Power, during a certificate renewal rehearsal, the operator observes: A configuration service posts failure webhooks without authentication and receivers accept forged network-change alerts. Which implementation action best meets the observed technical requirement?

  1. Generate and store private keys in restricted secret systems and deploy only to the authorized TLS termination endpoint.
  2. Enforce server-side per-resource authorization using authenticated identity and approved tenant or device scope.
  3. Install the validated issuing CA chain in client trust stores and verify endpoint identity rather than bypassing TLS checks.
  4. Authenticate webhook delivery and implement bounded retries with deduplication or delivery-state accounting.

Explanation

Correct Answer

D:

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. Applied here, the relevant facts are: A configuration service posts failure webhooks without authentication and receivers accept forged network-change alerts. The question asks which implementation action best meets the observed technical requirement.

Incorrect Answers

A:

The proposed action belongs to the mechanism: cA-signed certificates are public trust assertions but the associated private key must remain confidential for endpoint authentication. 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”.

B:

The offered action targets: authentication proves identity but each network resource action requires separate policy-based authorization controls. 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.

C:

This alternative is a response to another technical cause: tLS server validation depends on trusted issuer chains and hostname identity; bypassing verification defeats server authentication. 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 33

At fictional Windward Maritime, during a GitLab deployment pipeline rehearsal, the operator observes: A GitLab network release uses an overly privileged runner that applies Terraform changes to unauthorized production workspaces. What technical evidence should be required before closing this change?

  1. The payload validates against the YANG schema and the RESTCONF server accepts the exact intended interface resource.
  2. The simulated nodes accept the intended configuration and protocol or connectivity assertions pass under the planned topology.
  3. GitLab deployment records show the canary passed before other sites changed, and credentials cannot access unrelated workspaces.
  4. The Compose deployment starts required backends and the worker reaches ready state even when a dependency starts slowly.

Explanation

Correct Answer

C:

GitLab deployment records show the canary passed before other sites changed, and credentials cannot access unrelated workspaces. This directly verifies the related correction: Deploy through bounded environment-scoped jobs with approved service credentials and staged canary or batch rollout. It checks the technical distinction: A deployment stage should enforce release scope and approval, not merely execute a command with unrestricted infrastructure access.

Incorrect Answers

A:

That test belongs to another control with this basis: This directly verifies the related correction: Construct JSON using the published YANG container hierarchy, qualified node names and correct value types. In the current case, the governing reason is: This directly verifies the related correction: Deploy through bounded environment-scoped jobs with approved service credentials and staged canary or batch rollout. The direct verification is “GitLab deployment records show the canary passed before other sites changed, and credentials cannot access unrelated workspaces”.

B:

This observation would test a different technical dependency: This directly verifies the related correction: Build a representative topology in Cisco Modeling Labs and execute the automation against simulated devices before live release. The current issue is governed by: This directly verifies the related correction: Deploy through bounded environment-scoped jobs with approved service credentials and staged canary or batch rollout. Its decisive check is “GitLab deployment records show the canary passed before other sites changed, and credentials cannot access unrelated workspaces”.

D:

That test belongs to another control with this basis: This directly verifies the related correction: Define service dependencies with appropriate health checks and resilient application startup or retry behavior. In the current case, the governing reason is: This directly verifies the related correction: Deploy through bounded environment-scoped jobs with approved service credentials and staged canary or batch rollout. The direct verification is “GitLab deployment records show the canary passed before other sites changed, and credentials cannot access unrelated workspaces”.

Question 34

During a network policy migration at fictional Cobalt Ridge Bank, the change record states: A configuration collector overloads a shared Cisco API budget during a morning audit and starves other authorized automation. What acceptance check would prove the intended behavior was restored?

  1. Invalid IDs are rejected before any outbound request and valid values produce correctly encoded resource targets.
  2. Simulated 429 responses result in delayed, bounded retries and the caller recovers without a retry storm.
  3. A proof of concept demonstrates all required conditional paths, audit fields and rollback needs using the selected approach.
  4. A simulated nonresponsive endpoint times out within the declared bound and produces a per-device failure record without blocking others.

Explanation

Correct Answer

B:

Simulated 429 responses result in delayed, bounded retries and the caller recovers without a retry storm. This directly verifies the related correction: Respect rate-limit response headers and coordinate bounded exponential backoff with jitter under the shared API budget. It checks the technical distinction: HTTP 429 signals server-enforced rate limits; API client backoff must consider shared rate budgets and Retry-After semantics.

Incorrect Answers

A:

This observation would test a different technical dependency: This directly verifies the related correction: Validate typed inputs, authorized resource scopes and ranges before constructing API requests, then encode parameters safely. The current issue is governed by: This directly verifies the related correction: Respect rate-limit response headers and coordinate bounded exponential backoff with jitter under the shared API budget. Its decisive check is “Simulated 429 responses result in delayed, bounded retries and the caller recovers without a retry storm”.

C:

That test belongs to another control with this basis: This directly verifies the related correction: Match workflow complexity, vendor connector capability and error recovery needs to low-code or custom application design after a capability pilot. In the current case, the governing reason is: This directly verifies the related correction: Respect rate-limit response headers and coordinate bounded exponential backoff with jitter under the shared API budget. The direct verification is “Simulated 429 responses result in delayed, bounded retries and the caller recovers without a retry storm”.

D:

This observation would test a different technical dependency: This directly verifies the related correction: Set explicit connect and read timeouts and catch the resulting exceptions so the worker can report and continue safely. The current issue is governed by: This directly verifies the related correction: Respect rate-limit response headers and coordinate bounded exponential backoff with jitter under the shared API budget. Its decisive check is “Simulated 429 responses result in delayed, bounded retries and the caller recovers without a retry storm”.

Question 35

During a GitLab deployment pipeline rehearsal at fictional Seabright Learning, the change record states: A developer sends an interface configuration as a flat JSON object without the model container and module prefix expected by the RESTCONF endpoint. Which implementation action best meets the observed technical requirement?

  1. Use an approved squash merge to combine reviewed feature changes into one commit while preserving the final content.
  2. Deploy through bounded environment-scoped jobs with approved service credentials and staged canary or batch rollout.
  3. Cherry-pick the specific reviewed hotfix commit into the target maintenance branch and test the resulting change.
  4. Construct JSON using the published YANG container hierarchy, qualified node names and correct value types.

Explanation

Correct Answer

D:

Construct JSON using the published YANG container hierarchy, qualified node names and correct value types. This addresses the problem because yANG defines node hierarchy, namespaces, list keys and data types; conforming JSON must preserve that structure. Confirm success using: The payload validates against the YANG schema and the RESTCONF server accepts the exact intended interface resource.

Incorrect Answers

A:

The proposed action belongs to the mechanism: a squash merge consolidates branch changes into a new commit, simplifying target history without preserving each source commit as a separate mainline entry. Here the stated fault follows a different mechanism: yANG defines node hierarchy, namespaces, list keys and data types; conforming JSON must preserve that structure. The corrective choice is “Construct JSON using the published YANG container hierarchy, qualified node names and correct value types”.

B:

The offered action targets: a deployment stage should enforce release scope and approval, not merely execute a command with unrestricted infrastructure access. The case facts point instead to: yANG defines node hierarchy, namespaces, list keys and data types; conforming JSON must preserve that structure. Implement “Construct JSON using the published YANG container hierarchy, qualified node names and correct value types” to address that specific condition.

C:

This alternative is a response to another technical cause: git cherry-pick applies the change introduced by selected commit(s) onto the current branch, creating new history in that branch. The reported case instead depends on: yANG defines node hierarchy, namespaces, list keys and data types; conforming JSON must preserve that structure. The action that directly addresses it is “Construct JSON using the published YANG container hierarchy, qualified node names and correct value types”.

Question 36

At fictional Cedarbridge Care Systems, during a campus API automation rollout, the operator observes: A Python script interpolates unvalidated user-provided VLAN IDs into device requests and submits values outside approved range. Which targeted correction best addresses the network automation failure?

  1. Build the request body from the correct YANG data node and use application/yang-data+json with valid RESTCONF resource paths.
  2. Set compatible provider version constraints and commit the provider dependency lock file for reproducible runs.
  3. Validate typed inputs, authorized resource scopes and ranges before constructing API requests, then encode parameters safely.
  4. Extract a versioned reusable Terraform module with validated input variables for site-specific network parameters.

Explanation

Correct Answer

C:

Validate typed inputs, authorized resource scopes and ranges before constructing API requests, then encode parameters safely. This addresses the problem because aPI clients must validate human and external inputs independently of server-side validation to avoid unsafe or unintended changes. Confirm success using: Invalid IDs are rejected before any outbound request and valid values produce correctly encoded resource targets.

Incorrect Answers

A:

The offered action targets: rESTCONF manipulates YANG-defined resources over HTTP; both resource paths and payload media encoding must match the model. The case facts point instead to: aPI clients must validate human and external inputs independently of server-side validation to avoid unsafe or unintended changes. Implement “Validate typed inputs, authorized resource scopes and ranges before constructing API requests, then encode parameters safely” to address that specific condition.

B:

This alternative is a response to another technical cause: terraform providers translate declarative resources into platform API operations; provider version changes can alter behavior. The reported case instead depends on: aPI clients must validate human and external inputs independently of server-side validation to avoid unsafe or unintended changes. The action that directly addresses it is “Validate typed inputs, authorized resource scopes and ranges before constructing API requests, then encode parameters safely”.

D:

The offered action targets: terraform modules support repeated declarative resource patterns while typed inputs isolate deployment-specific configuration. The case facts point instead to: aPI clients must validate human and external inputs independently of server-side validation to avoid unsafe or unintended changes. Implement “Validate typed inputs, authorized resource scopes and ranges before constructing API requests, then encode parameters safely” to address that specific condition.

Question 37

During a GitLab deployment pipeline rehearsal at fictional Seabright Learning, the change record states: A controller-integration container loses its collected audit results whenever the Compose project is recreated. Which sustainable preventive control most directly avoids a recurrence?

  1. Document backup, ownership and retention policies for every persistent Compose volume.
  2. Generate payload fixtures from reviewed YANG modules and test schema validation before any live update.
  3. Use protected environments, least-privilege deploy tokens and progressive rollout approval conditions.
  4. Maintain versioned representative CML topologies as mandatory preproduction test fixtures.

Explanation

Correct Answer

A:

Document backup, ownership and retention policies for every persistent Compose volume. This prevents the recurrence because ephemeral container writable layers are distinct from Docker managed or host-mounted persistent volumes. A matching immediate correction is: Mount an appropriate persistent named volume or approved bind mount for data that must survive container recreation.

Incorrect Answers

B:

The suggested review tracks a different technical risk: yANG defines node hierarchy, namespaces, list keys and data types; conforming JSON must preserve that structure. Here the sustained control must address: ephemeral container writable layers are distinct from Docker managed or host-mounted persistent volumes. Choose “Document backup, ownership and retention policies for every persistent Compose volume”.

C:

That safeguard is relevant to: a deployment stage should enforce release scope and approval, not merely execute a command with unrestricted infrastructure access. The current failure instead follows from: ephemeral container writable layers are distinct from Docker managed or host-mounted persistent volumes. Its prevention measure is “Document backup, ownership and retention policies for every persistent Compose volume”.

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: ephemeral container writable layers are distinct from Docker managed or host-mounted persistent volumes. The matching preventive check is “Document backup, ownership and retention policies for every persistent Compose volume”.

Question 38

At fictional Willowfield Hospitality, during a version-control hotfix, the operator observes: A pipeline declares success when configuration API calls return 200 despite OSPF sessions remaining down on edge routers. What should the team add to its network automation operating process?

  1. Test slow dependency startup and review Compose healthchecks for all network automation support services.
  2. Include negative tests for out-of-range values, missing keys and incorrect scalar types in model-driven build gates.
  3. Require postchange telemetry and rollback thresholds for network pipeline release completion.
  4. Use protected environments, least-privilege deploy tokens and progressive rollout approval conditions.

Explanation

Correct Answer

C:

Require postchange telemetry and rollback thresholds for network pipeline release completion. This prevents the recurrence because deployment command success is not the same as verified service success; operational checks must follow state changes. A matching immediate correction is: Run objective-based postdeployment checks and fail or roll back the change when observed network behavior contradicts intent.

Incorrect Answers

A:

The proposed action belongs to the mechanism: container start ordering does not inherently guarantee service readiness; health conditions and retries address that gap. Here the stated fault follows a different mechanism: deployment command success is not the same as verified service success; operational checks must follow state changes. The corrective choice is “Require postchange telemetry and rollback thresholds for network pipeline release completion”.

B:

The offered action targets: model-based configuration encoding is constrained by YANG leaf types, ranges and required list keys, not arbitrary YAML structure. The case facts point instead to: deployment command success is not the same as verified service success; operational checks must follow state changes. Implement “Require postchange telemetry and rollback thresholds for network pipeline release completion” to address that specific condition.

D:

The proposed action belongs to the mechanism: a deployment stage should enforce release scope and approval, not merely execute a command with unrestricted infrastructure access. Here the stated fault follows a different mechanism: deployment command success is not the same as verified service success; operational checks must follow state changes. The corrective choice is “Require postchange telemetry and rollback thresholds for network pipeline release completion”.

Question 39

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. What mechanism is most directly responsible for these symptoms?

  1. CI runners start from controlled environments; undeclared local dependencies cannot be assumed present remotely.
  2. A GitLab pipeline exit code identifies failure, while job logs and test artifacts reveal the specific causal stage and assertion.
  3. Prevalidation is a safety boundary before changing network state, separate from checks after a change completes.
  4. A reproducible simulation needs controlled topology definitions and readiness gates to avoid timing-dependent false failures.

Explanation

Correct Answer

D:

A reproducible simulation needs controlled topology definitions and readiness gates to avoid timing-dependent false failures. The corresponding repair is: Provision the CML topology reproducibly and wait for all required node readiness conditions before tests begin. Acceptance should show: The pipeline consistently reaches a ready test topology and records the versioned lab definition and run results.

Incorrect Answers

A:

The offered statement is true for this other mechanism: The corresponding repair is: Declare and lock the required dependency in the build manifest and install it in the pipeline's reproducible environment. It does not explain the facts described here, which follow from: The corresponding repair is: Provision the CML topology reproducibly and wait for all required node readiness conditions before tests begin.

B:

This principle describes a separate cause: 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 reported condition is governed by: The corresponding repair is: Provision the CML topology reproducibly and wait for all required node readiness conditions before tests begin. The two mechanisms should not be conflated.

C:

The corresponding repair is: Make deployment depend on successful prevalidation jobs for schema, policy, simulation and approval checks. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Provision the CML topology reproducibly and wait for all required node readiness conditions before tests begin.

Question 40

At fictional Elmcrest Theatre, during a conversational network agent pilot, the operator observes: A multi-tenant MCP endpoint reuses a cached privileged token between separate customer sessions, exposing one site's inventory to another. Which targeted correction best addresses the network automation failure?

  1. Authenticate each MCP client, authorize its tool calls by tenant identity and isolate credential/session context.
  2. Review generated code provenance, included dependencies and organizational IP policy before accepting it into the repository.
  3. Issue read-only scoped identity credentials for diagnostic agents and place separate approval boundaries around mutating tools.
  4. Subject AI-suggested changes to schema and unit tests, simulated network execution, policy checks and human change approval.

Explanation

Correct Answer

A:

Authenticate each MCP client, authorize its tool calls by tenant identity and isolate credential/session context. This addresses the problem because an MCP server is an integration boundary and must not treat model-selected identity strings as verified security credentials. Confirm success using: Two simulated tenants can query only their own device records and cross-tenant tool attempts are denied and audited.

Incorrect Answers

B:

The proposed action belongs to the mechanism: aI-generated code may embed third-party patterns or dependencies; tool output is not automatically cleared of licensing obligations. Here the stated fault follows a different mechanism: an MCP server is an integration boundary and must not treat model-selected identity strings as verified security credentials. The corrective choice is “Authenticate each MCP client, authorize its tool calls by tenant identity and isolate credential/session context”.

C:

The offered action targets: the model is not a reliable security principal; tool identities and server-side authorization bound the damage of agent errors. The case facts point instead to: an MCP server is an integration boundary and must not treat model-selected identity strings as verified security credentials. Implement “Authenticate each MCP client, authorize its tool calls by tenant identity and isolate credential/session context” to address that specific condition.

D:

This alternative is a response to another technical cause: generative systems can propose plausible-looking but incorrect commands; independent executable validation is required for safe infrastructure changes. The reported case instead depends on: an MCP server is an integration boundary and must not treat model-selected identity strings as verified security credentials. The action that directly addresses it is “Authenticate each MCP client, authorize its tool calls by tenant identity and isolate credential/session context”.