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 1

Question 1

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. What technical evidence should be required before closing this change?

  1. Audit logs and data-loss-prevention checks show that prompts and tool responses contain no live credentials or confidential customer payloads.
  2. The workflow reduces draft effort yet records review and successful technical tests before any proposed config reaches deployment.
  3. Two simulated tenants can query only their own device records and cross-tenant tool attempts are denied and audited.
  4. A conversational diagnostic completes safely without write access, and a proposed write remains pending until an authorized approver confirms.

Explanation

Correct Answer

C:

Two simulated tenants can query only their own device records and cross-tenant tool attempts are denied and audited. This directly verifies the related correction: Authenticate each MCP client, authorize its tool calls by tenant identity and isolate credential/session context. It checks the technical distinction: An MCP server is an integration boundary and must not treat model-selected identity strings as verified security credentials.

Incorrect Answers

A:

This observation would test a different technical dependency: 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. The current issue is governed by: This directly verifies the related correction: Authenticate each MCP client, authorize its tool calls by tenant identity and isolate credential/session context. Its decisive check is “Two simulated tenants can query only their own device records and cross-tenant tool attempts are denied and audited”.

B:

The alternative verifies a different condition: This directly verifies the related correction: Use AI assistance for bounded drafts and test generation while assigning accountable reviewers and validating facts against approved sources. The current case instead depends on: This directly verifies the related correction: Authenticate each MCP client, authorize its tool calls by tenant identity and isolate credential/session context. Confirm that “Two simulated tenants can query only their own device records and cross-tenant tool attempts are denied and audited”.

D:

This observation would test a different technical dependency: 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 current issue is governed by: This directly verifies the related correction: Authenticate each MCP client, authorize its tool calls by tenant identity and isolate credential/session context. Its decisive check is “Two simulated tenants can query only their own device records and cross-tenant tool attempts are denied and audited”.

Question 2

At fictional Coastal Meadow Labs, during a production change postcheck, the operator observes: A ticket-to-config service accepts arbitrary ACL text and passes it unvalidated into a privileged device command template. What is the appropriate response to this network automation condition?

  1. Trace correlated event IDs and earliest causal errors through the pipeline instead of treating the final propagated exception as root cause.
  2. Emit structured events with timestamp, device identity, change ID, severity, stage and outcome to the central log destination.
  3. Normalize telemetry dimensions to stable device and interface identifiers and avoid high-cardinality ephemeral labels.
  4. Use typed input schema validation, approved resource allowlists and safe library argument interfaces rather than shell concatenation.

Explanation

Correct Answer

D:

Use typed input schema validation, approved resource allowlists and safe library argument interfaces rather than shell concatenation. This addresses the problem because untrusted input can cross command or configuration boundaries; validation and safe APIs prevent injection into privileged operations. Confirm success using: Malicious metacharacter input is rejected and legitimate interface updates produce only approved structured API calls.

Incorrect Answers

A:

The proposed action belongs to the mechanism: downstream error messages can reflect cascaded failures; causality is established by correlating the earlier specific event and affected resource. Here the stated fault follows a different mechanism: untrusted input can cross command or configuration boundaries; validation and safe APIs prevent injection into privileged operations. The corrective choice is “Use typed input schema validation, approved resource allowlists and safe library argument interfaces rather than shell concatenation”.

B:

The offered action targets: an effective logging architecture uses consistent machine-readable context and common correlation fields across distributed jobs. The case facts point instead to: untrusted input can cross command or configuration boundaries; validation and safe APIs prevent injection into privileged operations. Implement “Use typed input schema validation, approved resource allowlists and safe library argument interfaces rather than shell concatenation” to address that specific condition.

C:

This alternative is a response to another technical cause: time-series cardinality grows with combinations of labels; volatile unique IDs defeat aggregation and strain metric storage. The reported case instead depends on: untrusted input can cross command or configuration boundaries; validation and safe APIs prevent injection into privileged operations. The action that directly addresses it is “Use typed input schema validation, approved resource allowlists and safe library argument interfaces rather than shell concatenation”.

Question 3

During a GitLab deployment pipeline rehearsal at fictional Seabright Learning, the change record states: A GitLab deployment job compiles automation files on the production runner using a different dependency set than unit tests used. Which explanation best matches the actual broken dependency?

  1. A reliable source-of-truth workflow separates approved intent from observed device state and defines how changes flow between them.
  2. Deployment command success is not the same as verified service success; operational checks must follow state changes.
  3. A CI build stage turns source and fixed dependencies into a traceable deployment input used by later stages.
  4. YANG defines node hierarchy, namespaces, list keys and data types; conforming JSON must preserve that structure.

Explanation

Correct Answer

C:

A CI build stage turns source and fixed dependencies into a traceable deployment input used by later stages. The corresponding repair is: Produce a reproducible versioned build artifact in the build stage and use that immutable artifact for subsequent validation and deployment. Acceptance should show: The deployed artifact checksum matches the tested build artifact and the pipeline records its originating commit.

Incorrect Answers

A:

The offered action targets: The corresponding repair is: Read authorized desired state from the designated source of truth and reconcile observed drift through an approved change path. The case facts point instead to: The corresponding repair is: Produce a reproducible versioned build artifact in the build stage and use that immutable artifact for subsequent validation and deployment. Implement “A CI build stage turns source and fixed dependencies into a traceable deployment input used by later stages” to address that specific condition.

B:

This alternative is a response to another technical cause: The corresponding repair is: Run objective-based postdeployment checks and fail or roll back the change when observed network behavior contradicts intent. The reported case instead depends on: The corresponding repair is: Produce a reproducible versioned build artifact in the build stage and use that immutable artifact for subsequent validation and deployment. The action that directly addresses it is “A CI build stage turns source and fixed dependencies into a traceable deployment input used by later stages”.

D:

The offered action targets: The corresponding repair is: Construct JSON using the published YANG container hierarchy, qualified node names and correct value types. The case facts point instead to: The corresponding repair is: Produce a reproducible versioned build artifact in the build stage and use that immutable artifact for subsequent validation and deployment. Implement “A CI build stage turns source and fixed dependencies into a traceable deployment input used by later stages” to address that specific condition.

Question 4

At fictional Violet Ridge Resorts, an acceptance review of a version-control hotfix finds: A Docker Compose stack places its internal database and externally reachable web API on an unrestricted shared network. Which observation would confirm that this exact failure is resolved?

  1. Network inspection shows the internal service reachable only to authorized app containers and public bindings limited to the approved API.
  2. The simulated nodes accept the intended configuration and protocol or connectivity assertions pass under the planned topology.
  3. Lab simulation reproduces the known routing dependency and the candidate change passes normal and failure scenarios.
  4. GitLab deployment records show the canary passed before other sites changed, and credentials cannot access unrelated workspaces.

Explanation

Correct Answer

A:

Network inspection shows the internal service reachable only to authorized app containers and public bindings limited to the approved API. This directly verifies the related correction: Use purpose-specific networks and expose only the required listener ports while keeping backend services unexposed. It checks the technical distinction: Compose networks govern container service reachability, while host port publishing determines external exposure.

Incorrect Answers

B:

The alternative verifies a different condition: 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 case instead depends on: This directly verifies the related correction: Use purpose-specific networks and expose only the required listener ports while keeping backend services unexposed. Confirm that “Network inspection shows the internal service reachable only to authorized app containers and public bindings limited to the approved API”.

C:

That test belongs to another control with this basis: This directly verifies the related correction: Model the relevant links, routing peers and failure cases in CML rather than only a minimal happy-path device. In the current case, the governing reason is: This directly verifies the related correction: Use purpose-specific networks and expose only the required listener ports while keeping backend services unexposed. The direct verification is “Network inspection shows the internal service reachable only to authorized app containers and public bindings limited to the approved API”.

D:

This observation would test a different technical dependency: This directly verifies the related correction: Deploy through bounded environment-scoped jobs with approved service credentials and staged canary or batch rollout. The current issue is governed by: This directly verifies the related correction: Use purpose-specific networks and expose only the required listener ports while keeping backend services unexposed. Its decisive check is “Network inspection shows the internal service reachable only to authorized app containers and public bindings limited to the approved API”.

Question 5

During a network policy migration at fictional Cobalt Ridge Bank, the change record states: A network automation CLI accepts an untrusted interface name and produces a malformed URL or targets a forbidden interface. Which observation would confirm that this exact failure is resolved?

  1. Invalid IDs are rejected before any outbound request and valid values produce correctly encoded resource targets.
  2. Plans for two independently configured sites show correct separate VLAN IDs or address values while sharing one reviewed module version.
  3. A GET of the specific keyed list entry shows only the authorized VLAN or interface changed, with sibling entries intact.
  4. Separate platform acceptance tests reach equivalent approved network intent on each supported operating system without invalid commands.

Explanation

Correct Answer

A:

Invalid IDs are rejected before any outbound request and valid values produce correctly encoded resource targets. This directly verifies the related correction: Validate typed inputs, authorized resource scopes and ranges before constructing API requests, then encode parameters safely. It checks the technical distinction: API clients must validate human and external inputs independently of server-side validation to avoid unsafe or unintended changes.

Incorrect Answers

B:

That test belongs to another control with this basis: This directly verifies the related correction: Extract a versioned reusable Terraform module with validated input variables for site-specific network parameters. In the current case, the governing reason is: This directly verifies the related correction: Validate typed inputs, authorized resource scopes and ranges before constructing API requests, then encode parameters safely. The direct verification is “Invalid IDs are rejected before any outbound request and valid values produce correctly encoded resource targets”.

C:

This observation would test a different technical dependency: This directly verifies the related correction: Address the exact YANG list instance using its fully encoded key values in the RESTCONF data resource path. The current issue is governed by: This directly verifies the related correction: Validate typed inputs, authorized resource scopes and ranges before constructing API requests, then encode parameters safely. Its decisive check is “Invalid IDs are rejected before any outbound request and valid values produce correctly encoded resource targets”.

D:

The alternative verifies a different condition: This directly verifies the related correction: Use inventory capability detection and platform-specific adapters behind a common validated intent model. The current case instead depends on: This directly verifies the related correction: Validate typed inputs, authorized resource scopes and ranges before constructing API requests, then encode parameters safely. Confirm that “Invalid IDs are rejected before any outbound request and valid values produce correctly encoded resource targets”.

Question 6

During a telemetry quality investigation at fictional Foxglove Aviation, the change record states: A new network controller presents a certificate from a private CA and clients fail TLS handshakes because the CA is not trusted. What ongoing engineering assurance should follow the successful fix?

  1. Collect bounded latency histograms, timeout reason labels and retry budgets for critical controller calls.
  2. Add typed error classification and separate authorization and authentication runbooks to API clients.
  3. Monitor certificate expirations and trust-chain changes with automated predeployment verification.
  4. Define subscription-path ownership, freshness objectives and collector loss alarms for critical operational signals.

Explanation

Correct Answer

C:

Monitor certificate expirations and trust-chain changes with automated predeployment verification. This prevents the recurrence because tLS server validation depends on trusted issuer chains and hostname identity; bypassing verification defeats server authentication. A matching immediate correction is: Install the validated issuing CA chain in client trust stores and verify endpoint identity rather than bypassing TLS checks.

Incorrect Answers

A:

That safeguard is relevant to: latency and retry failures require timing context and per-attempt telemetry; an aggregate success percentage is insufficient. The current failure instead follows from: tLS server validation depends on trusted issuer chains and hostname identity; bypassing verification defeats server authentication. Its prevention measure is “Monitor certificate expirations and trust-chain changes with automated predeployment verification”.

B:

This routine guards against another mechanism: hTTP 401 generally signals missing or invalid authentication while 403 indicates access denied to an authenticated request. The recurring exposure in the current case is: tLS server validation depends on trusted issuer chains and hostname identity; bypassing verification defeats server authentication. The matching preventive check is “Monitor certificate expirations and trust-chain changes with automated predeployment verification”.

D:

That safeguard is relevant to: model-driven telemetry publishes structured device state using subscribed paths and collection modes rather than relying only on slow polling. The current failure instead follows from: tLS server validation depends on trusted issuer chains and hostname identity; bypassing verification defeats server authentication. Its prevention measure is “Monitor certificate expirations and trust-chain changes with automated predeployment verification”.

Question 7

While investigating a reproducible simulation for fictional Windward Maritime, the team reports: A team needs to validate an interface-renaming playbook but cannot safely run experimental changes against a shared campus network. What mechanism is most directly responsible for these symptoms?

  1. A source of truth provides desired canonical inventory, but consumers must resolve identity correctly and reconcile discrepancies.
  2. CML supports topology-based device and protocol simulation for safe early integration tests without touching live infrastructure.
  3. A cherry-picked commit does not automatically bring every ancestor or dependent change from its original branch.
  4. Git checkout can change branch and working-tree files; uncommitted modifications must be managed to avoid accidental mixing.

Explanation

Correct Answer

B:

CML supports topology-based device and protocol simulation for safe early integration tests without touching live infrastructure. The corresponding repair is: Build a representative topology in Cisco Modeling Labs and execute the automation against simulated devices before live release. Acceptance should show: The simulated nodes accept the intended configuration and protocol or connectivity assertions pass under the planned topology.

Incorrect Answers

A:

This principle describes a separate cause: The corresponding repair is: Use stable authoritative device identifiers and reconcile observed inventory to the source-of-truth records before deployment. The reported condition is governed by: The corresponding repair is: Build a representative topology in Cisco Modeling Labs and execute the automation against simulated devices before live release. The two mechanisms should not be conflated.

C:

The offered statement is true for this other mechanism: The corresponding repair is: Identify the prerequisite commits and cherry-pick a minimal compatible sequence or adapt the patch for the target baseline. It does not explain the facts described here, which follow from: The corresponding repair is: Build a representative topology in Cisco Modeling Labs and execute the automation against simulated devices before live release.

D:

This principle describes a separate cause: The corresponding repair is: Safely stash or commit unrelated work and check out the intended branch or detached revision in a clean worktree. The reported condition is governed by: The corresponding repair is: Build a representative topology in Cisco Modeling Labs and execute the automation against simulated devices before live release. The two mechanisms should not be conflated.

Question 8

At fictional Seabright Learning, an acceptance review of a reproducible simulation finds: A developer needs one last-known-good YANG mapping file but checks out an entire outdated branch over current production code. What is the appropriate response to this network automation condition?

  1. Model the relevant links, routing peers and failure cases in CML rather than only a minimal happy-path device.
  2. Validate leaf type and range constraints and include every mandatory keyed-list attribute in the encoded configuration.
  3. Use an approved squash merge to combine reviewed feature changes into one commit while preserving the final content.
  4. Restore only the specifically reviewed historical file from the desired revision instead of replacing the whole branch state.

Explanation

Correct Answer

D:

Restore only the specifically reviewed historical file from the desired revision instead of replacing the whole branch state. This addresses the problem because git can retrieve individual tracked paths from a commit; selecting file scope avoids broad branch-level rollback. Confirm success using: Only the selected file matches the approved historical content, and unrelated working files remain unchanged.

Incorrect Answers

A:

The proposed action belongs to the mechanism: simulation usefulness depends on modeled network dependencies; an incomplete topology cannot validate omitted behaviors. Here the stated fault follows a different mechanism: git can retrieve individual tracked paths from a commit; selecting file scope avoids broad branch-level rollback. The corrective choice is “Restore only the specifically reviewed historical file from the desired revision instead of replacing the whole branch state”.

B:

That action addresses another technical layer: YANG and JSON schema validation check data types, allowable ranges and required keyed-list fields; this is distinct from successfully completing a later deployment or workflow step. It does not correct this specific failure, which is explained by: git can retrieve individual tracked paths from a commit; selecting file scope avoids broad branch-level rollback. The case-matched action is “Restore only the specifically reviewed historical file from the desired revision instead of replacing the whole branch state”.

C:

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 can retrieve individual tracked paths from a commit; selecting file scope avoids broad branch-level rollback. The action that directly addresses it is “Restore only the specifically reviewed historical file from the desired revision instead of replacing the whole branch state”.

Question 9

While investigating a telemetry quality investigation for fictional Sable Valley Power, the team reports: A network change job logs HTTP 403 after authenticating with a valid token, but operations repeatedly rotate the password instead of fixing authorization. What should the team add to its network automation operating process?

  1. Add typed error classification and separate authorization and authentication runbooks to API clients.
  2. Rotate webhook credentials and monitor delivery latency, signature validation and replay protection.
  3. Include cross-tenant and privilege-escalation negative tests in API CI and audit privileged access decisions.
  4. Enforce a shared structured-event schema and test correlation queries during pipeline acceptance.

Explanation

Correct Answer

A:

Add typed error classification and separate authorization and authentication runbooks to API clients. This prevents the recurrence because hTTP 401 generally signals missing or invalid authentication while 403 indicates access denied to an authenticated request. A matching immediate correction is: Classify authentication failures and authorization denials separately, then correct token validity or RBAC scope accordingly.

Incorrect Answers

B:

This alternative is a response to another technical cause: webhooks are asynchronous network events; integrity, delivery acknowledgements and idempotent processing are separate reliability needs. The reported case instead depends on: hTTP 401 generally signals missing or invalid authentication while 403 indicates access denied to an authenticated request. The action that directly addresses it is “Add typed error classification and separate authorization and authentication runbooks to API clients”.

C:

The proposed action belongs to the mechanism: authentication proves identity but each network resource action requires separate policy-based authorization controls. Here the stated fault follows a different mechanism: hTTP 401 generally signals missing or invalid authentication while 403 indicates access denied to an authenticated request. The corrective choice is “Add typed error classification and separate authorization and authentication runbooks to API clients”.

D:

The offered action targets: an effective logging architecture uses consistent machine-readable context and common correlation fields across distributed jobs. The case facts point instead to: hTTP 401 generally signals missing or invalid authentication while 403 indicates access denied to an authenticated request. Implement “Add typed error classification and separate authorization and authentication runbooks to API clients” to address that specific condition.

Question 10

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

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

Explanation

Correct Answer

A:

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

Incorrect Answers

B:

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

C:

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

D:

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