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 43

Question 420

At fictional Windward Maritime, during a GitLab deployment pipeline rehearsal, the operator observes: An inventory import creates duplicate switch records because device identity is inferred from mutable display names rather than stable identifiers. Which engineering principle explains the described system behavior?

  1. A source of truth provides desired canonical inventory, but consumers must resolve identity correctly and reconcile discrepancies.
  2. The Git index is the staging area and can be changed independently of the working tree by suitable reset modes.
  3. Git cannot automatically reconcile overlapping divergent edits; a human or reviewed tool must choose the resulting content before merge completion.
  4. Simulation usefulness depends on modeled network dependencies; an incomplete topology cannot validate omitted behaviors.

Explanation

Correct Answer

A:

A source of truth provides desired canonical inventory, but consumers must resolve identity correctly and reconcile discrepancies. The corresponding repair is: Use stable authoritative device identifiers and reconcile observed inventory to the source-of-truth records before deployment. Acceptance should show: The device registry maps one approved identity to each physical endpoint and duplicate or stale mappings are flagged.

Incorrect Answers

B:

This principle describes a separate cause: The corresponding repair is: Unstage the unintended file with an index-only reset or equivalent restore-staged operation, leaving the worktree intact. The reported condition is governed by: The corresponding repair is: Use stable authoritative device identifiers and reconcile observed inventory to the source-of-truth records before deployment. The two mechanisms should not be conflated.

C:

The corresponding repair is: Resolve the conflicting lines deliberately against the approved desired network state, run validation, then commit the merged result. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Use stable authoritative device identifiers and reconcile observed inventory to the source-of-truth records before deployment.

D:

The offered statement is true for this other mechanism: The corresponding repair is: Model the relevant links, routing peers and failure cases in CML rather than only a minimal happy-path device. It does not explain the facts described here, which follow from: The corresponding repair is: Use stable authoritative device identifiers and reconcile observed inventory to the source-of-truth records before deployment.

Question 421

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 is the appropriate response to this network automation condition?

  1. Classify authentication failures and authorization denials separately, then correct token validity or RBAC scope accordingly.
  2. Synchronize clocks and ship logs to a durable centralized destination with appropriate secure, reliable transport.
  3. Generate and store private keys in restricted secret systems and deploy only to the authorized TLS termination endpoint.
  4. Install the validated issuing CA chain in client trust stores and verify endpoint identity rather than bypassing TLS checks.

Explanation

Correct Answer

A:

Classify authentication failures and authorization denials separately, then correct token validity or RBAC scope accordingly. This addresses the problem because hTTP 401 generally signals missing or invalid authentication while 403 indicates access denied to an authenticated request. Confirm success using: The corrected job authenticates with a valid identity and has exactly the approved resource permissions, with distinct log codes for future failures.

Incorrect Answers

B:

The proposed action belongs to the mechanism: distributed troubleshooting requires durable transport and consistent time context; ephemeral local logs can be lost or misordered. 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 “Classify authentication failures and authorization denials separately, then correct token validity or RBAC scope accordingly”.

C:

The offered action targets: cA-signed certificates are public trust assertions but the associated private key must remain confidential for endpoint authentication. The case facts point instead to: hTTP 401 generally signals missing or invalid authentication while 403 indicates access denied to an authenticated request. Implement “Classify authentication failures and authorization denials separately, then correct token validity or RBAC scope accordingly” to address that specific condition.

D:

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: hTTP 401 generally signals missing or invalid authentication while 403 indicates access denied to an authenticated request. The action that directly addresses it is “Classify authentication failures and authorization denials separately, then correct token validity or RBAC scope accordingly”.

Question 422

At fictional Willowfield Hospitality, during a version-control hotfix, the operator observes: A developer accidentally stages a generated credentials fixture in an unpushed commit and needs to revise local commit history before review. What is the appropriate response to this network automation condition?

  1. Pin compatible build tool and package versions, update the lockfile and test upgrades in a separate controlled pipeline.
  2. Safely stash or commit unrelated work and check out the intended branch or detached revision in a clean worktree.
  3. Restore only the specifically reviewed historical file from the desired revision instead of replacing the whole branch state.
  4. Use an appropriate local Git reset to move the branch pointer and rebuild the unpublished commit while protecting wanted working changes.

Explanation

Correct Answer

D:

Use an appropriate local Git reset to move the branch pointer and rebuild the unpublished commit while protecting wanted working changes. This addresses the problem because git reset moves HEAD and optionally the index and worktree, making it suitable for carefully revising unpublished local history. Confirm success using: The corrected local branch no longer references the mistaken commit and preserved intended edits are recommitted after validation. Applied here, the relevant facts are: A developer accidentally stages a generated credentials fixture in an unpushed commit and needs to revise local commit history before review. The question asks what is the appropriate response to this network automation condition.

Incorrect Answers

A:

The proposed action belongs to the mechanism: unbounded dependency upgrades can introduce incompatible APIs and nondeterministic CI failures even when repository code is unchanged. Here the stated fault follows a different mechanism: git reset moves HEAD and optionally the index and worktree, making it suitable for carefully revising unpublished local history. The corrective choice is “Use an appropriate local Git reset to move the branch pointer and rebuild the unpublished commit while protecting wanted working changes”.

B:

The offered action targets: git checkout can change branch and working-tree files; uncommitted modifications must be managed to avoid accidental mixing. The case facts point instead to: git reset moves HEAD and optionally the index and worktree, making it suitable for carefully revising unpublished local history. Implement “Use an appropriate local Git reset to move the branch pointer and rebuild the unpublished commit while protecting wanted working changes” to address that specific condition.

C:

This alternative is a response to another technical cause: git can retrieve individual tracked paths from a commit; selecting file scope avoids broad branch-level rollback. The reported case instead depends on: git reset moves HEAD and optionally the index and worktree, making it suitable for carefully revising unpublished local history. The action that directly addresses it is “Use an appropriate local Git reset to move the branch pointer and rebuild the unpublished commit while protecting wanted working changes”.

Question 423

At fictional Willowfield Hospitality, during a version-control hotfix, the operator observes: A bad network automation change has already been pushed to a protected shared branch and teammates have based work on it. Which engineering principle explains the described system behavior?

  1. A GitLab pipeline exit code identifies failure, while job logs and test artifacts reveal the specific causal stage and assertion.
  2. A squash merge consolidates branch changes into a new commit, simplifying target history without preserving each source commit as a separate mainline entry.
  3. Ephemeral container writable layers are distinct from Docker managed or host-mounted persistent volumes.
  4. Git revert records an inverse patch in new history rather than moving shared branch pointers backward.

Explanation

Correct Answer

D:

Git revert records an inverse patch in new history rather than moving shared branch pointers backward. The corresponding repair is: Create a reviewed Git revert commit for the offending change and run the full network automation release tests. Acceptance should show: The target branch retains an auditable inverse commit and the published history remains intact while behavior returns to the approved state. Applied here, the relevant facts are: A bad network automation change has already been pushed to a protected shared branch and teammates have based work on it. The question asks which engineering principle explains the described system behavior.

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: Create a reviewed Git revert commit for the offending change and run the full network automation release tests.

B:

This principle describes a separate cause: The corresponding repair is: Use an approved squash merge to combine reviewed feature changes into one commit while preserving the final content. The reported condition is governed by: The corresponding repair is: Create a reviewed Git revert commit for the offending change and run the full network automation release tests. The two mechanisms should not be conflated.

C:

The corresponding repair is: Mount an appropriate persistent named volume or approved bind mount for data that must survive container recreation. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Create a reviewed Git revert commit for the offending change and run the full network automation release tests.

Question 424

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

  1. Use a shared schema validator, unit tests for boundary values and an approved-resource allowlist.
  2. Enforce pre-commit secret scans, restricted vault permissions, credential rotation and no_log controls for sensitive tasks.
  3. Introduce request budgets, jitter, retry caps and 429 rate metrics into the automation client.
  4. Document selection criteria for persistence, state, API coverage, auditability and team maintenance capacity.

Explanation

Correct Answer

C:

Introduce request budgets, jitter, retry caps and 429 rate metrics into the automation client. This prevents the recurrence because hTTP 429 signals server-enforced rate limits; API client backoff must consider shared rate budgets and Retry-After semantics. A matching immediate correction is: Respect rate-limit response headers and coordinate bounded exponential backoff with jitter under the shared API budget.

Incorrect Answers

A:

This routine guards against another mechanism: aPI clients must validate human and external inputs independently of server-side validation to avoid unsafe or unintended changes. The recurring exposure in the current case is: hTTP 429 signals server-enforced rate limits; API client backoff must consider shared rate budgets and Retry-After semantics. The matching preventive check is “Introduce request budgets, jitter, retry caps and 429 rate metrics into the automation client”.

B:

The suggested review tracks a different technical risk: automation credentials need confidentiality at rest and in output; inventory convenience does not justify committing secrets. Here the sustained control must address: hTTP 429 signals server-enforced rate limits; API client backoff must consider shared rate budgets and Retry-After semantics. Choose “Introduce request budgets, jitter, retry caps and 429 rate metrics into the automation client”.

D:

This routine guards against another mechanism: infrastructure as code, low-code workflows and custom software solve different state-lifecycle and integration needs. The recurring exposure in the current case is: hTTP 429 signals server-enforced rate limits; API client backoff must consider shared rate budgets and Retry-After semantics. The matching preventive check is “Introduce request budgets, jitter, retry caps and 429 rate metrics into the automation client”.

Question 425

During a source-of-truth integration at fictional Violet Ridge Resorts, the change record states: An engineering team patches switch interfaces manually but never updates canonical device intent, so the next automated apply undoes the fix. What mechanism is most directly responsible for these symptoms?

  1. Reverting a merge requires an explicit mainline perspective so Git knows which parent is the retained baseline.
  2. CI runners start from controlled environments; undeclared local dependencies cannot be assumed present remotely.
  3. A reliable source-of-truth workflow separates approved intent from observed device state and defines how changes flow between them.
  4. A GitLab pipeline exit code identifies failure, while job logs and test artifacts reveal the specific causal stage and assertion.

Explanation

Correct Answer

C:

A reliable source-of-truth workflow separates approved intent from observed device state and defines how changes flow between them. The corresponding repair is: Read authorized desired state from the designated source of truth and reconcile observed drift through an approved change path. Acceptance should show: Generated configs match authoritative source records and postapply compliance detects any remaining unauthorized deviation. Applied here, the relevant facts are: An engineering team patches switch interfaces manually but never updates canonical device intent, so the next automated apply undoes the fix. The question asks what mechanism is most directly responsible for these symptoms.

Incorrect Answers

A:

The corresponding repair is: Review the merge graph and select the correct mainline parent when reverting the merge, then validate the resulting tree diff. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Read authorized desired state from the designated source of truth and reconcile observed drift through an approved change path.

B:

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: Read authorized desired state from the designated source of truth and reconcile observed drift through an approved change path.

D:

The corresponding repair is: Inspect the failed job logs and classify whether build, dependency, test or environment validation failed before making a targeted fix. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Read authorized desired state from the designated source of truth and reconcile observed drift through an approved change path.

Question 426

At fictional Foxglove Aviation, an acceptance review of a certificate renewal rehearsal finds: A TLS renewal script stores the server private key in world-readable inventory files copied to every automation worker. What ongoing engineering assurance should follow the successful fix?

  1. Automate private-key permission checks, key rotation and credential scanning in certificate deployment workflows.
  2. Enforce a shared structured-event schema and test correlation queries during pipeline acceptance.
  3. Require machine-readable stage IDs and link failure summaries back to the earliest relevant stack trace.
  4. Rotate webhook credentials and monitor delivery latency, signature validation and replay protection.

Explanation

Correct Answer

A:

Automate private-key permission checks, key rotation and credential scanning in certificate deployment workflows. This prevents the recurrence because cA-signed certificates are public trust assertions but the associated private key must remain confidential for endpoint authentication. A matching immediate correction is: Generate and store private keys in restricted secret systems and deploy only to the authorized TLS termination endpoint.

Incorrect Answers

B:

This routine guards against another mechanism: an effective logging architecture uses consistent machine-readable context and common correlation fields across distributed jobs. The recurring exposure in the current case is: cA-signed certificates are public trust assertions but the associated private key must remain confidential for endpoint authentication. The matching preventive check is “Automate private-key permission checks, key rotation and credential scanning in certificate deployment workflows”.

C:

The suggested review tracks a different technical risk: downstream error messages can reflect cascaded failures; causality is established by correlating the earlier specific event and affected resource. Here the sustained control must address: cA-signed certificates are public trust assertions but the associated private key must remain confidential for endpoint authentication. Choose “Automate private-key permission checks, key rotation and credential scanning in certificate deployment workflows”.

D:

That safeguard is relevant to: webhooks are asynchronous network events; integrity, delivery acknowledgements and idempotent processing are separate reliability needs. The current failure instead follows from: cA-signed certificates are public trust assertions but the associated private key must remain confidential for endpoint authentication. Its prevention measure is “Automate private-key permission checks, key rotation and credential scanning in certificate deployment workflows”.

Question 427

During a source-of-truth integration at fictional Violet Ridge Resorts, the change record states: A GitLab job applies a network ACL and stops without confirming active data-plane connectivity for the newly allowed application. What ongoing engineering assurance should follow the successful fix?

  1. Test slow dependency startup and review Compose healthchecks for all network automation support services.
  2. Enforce unique device IDs, provenance and reconciliation reports for source-of-truth integrations.
  3. Require postchange telemetry and rollback thresholds for network pipeline release completion.
  4. Require path-limited recovery commands and postrestore diffs for surgical automation-file reversions.

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. Applied here, the relevant facts are: A GitLab job applies a network ACL and stops without confirming active data-plane connectivity for the newly allowed application. The question asks what ongoing engineering assurance should follow the successful fix.

Incorrect Answers

A:

This observation would test a different technical dependency: container start ordering does not inherently guarantee service readiness; health conditions and retries address that gap. The current issue is governed by: deployment command success is not the same as verified service success; operational checks must follow state changes. Its decisive check is “Require postchange telemetry and rollback thresholds for network pipeline release completion”.

B:

The alternative verifies a different condition: a source of truth provides desired canonical inventory, but consumers must resolve identity correctly and reconcile discrepancies. The current case instead depends on: deployment command success is not the same as verified service success; operational checks must follow state changes. Confirm that “Require postchange telemetry and rollback thresholds for network pipeline release completion”.

D:

This observation would test a different technical dependency: git can retrieve individual tracked paths from a commit; selecting file scope avoids broad branch-level rollback. The current issue is governed by: deployment command success is not the same as verified service success; operational checks must follow state changes. Its decisive check is “Require postchange telemetry and rollback thresholds for network pipeline release completion”.

Question 428

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 result most directly verifies that the proposed correction worked?

  1. Fresh runners initialize the same reviewed provider build and produce equivalent plans from the same state and configuration.
  2. Invalid IDs are rejected before any outbound request and valid values produce correctly encoded resource targets.
  3. The imported resource maps to the intended live identifier and the reviewed plan does not attempt duplicate creation or replacement.
  4. After the edit, the desired leaf is updated and every unrelated modeled sibling retains its approved value.

Explanation

Correct Answer

B:

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. Applied here, the relevant facts are: A Python script interpolates unvalidated user-provided VLAN IDs into device requests and submits values outside approved range. The question asks which result most directly verifies that the proposed correction worked.

Incorrect Answers

A:

The proposed action belongs to the mechanism: This directly verifies the related correction: Set compatible provider version constraints and commit the provider dependency lock file for reproducible runs. Here the stated fault follows a different mechanism: This directly verifies the related correction: Validate typed inputs, authorized resource scopes and ranges before constructing API requests, then encode parameters safely. The corrective choice is “Invalid IDs are rejected before any outbound request and valid values produce correctly encoded resource targets”.

C:

This alternative is a response to another technical cause: This directly verifies the related correction: Import the existing platform object into Terraform state, align its configuration and inspect a non-destructive plan. The reported 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. The action that directly addresses it is “Invalid IDs are rejected before any outbound request and valid values produce correctly encoded resource targets”.

D:

The proposed action belongs to the mechanism: This directly verifies the related correction: Choose a supported targeted PATCH or edit operation for partial changes and reserve PUT for intentionally replacing the resource representation. Here the stated fault follows a different mechanism: This directly verifies the related correction: Validate typed inputs, authorized resource scopes and ranges before constructing API requests, then encode parameters safely. The corrective choice is “Invalid IDs are rejected before any outbound request and valid values produce correctly encoded resource targets”.

Question 429

During a network policy migration at fictional Cobalt Ridge Bank, the change record states: Two network automation workers run different provider releases and produce inconsistent API requests for the same declared object. Which control best prevents this particular failure from recurring?

  1. Introduce request budgets, jitter, retry caps and 429 rate metrics into the automation client.
  2. Require representative failure-path tests before approving a low-code production integration.
  3. Test provider upgrades in a sandbox and approve lockfile changes independently of ordinary network configuration edits.
  4. Require inventory-host preview and environment-specific group-variable review in change approval.

Explanation

Correct Answer

C:

Test provider upgrades in a sandbox and approve lockfile changes independently of ordinary network configuration edits. This prevents the recurrence because terraform providers translate declarative resources into platform API operations; provider version changes can alter behavior. A matching immediate correction is: Set compatible provider version constraints and commit the provider dependency lock file for reproducible runs. Applied here, the relevant facts are: Two network automation workers run different provider releases and produce inconsistent API requests for the same declared object. The question asks which control best prevents this particular failure from recurring.

Incorrect Answers

A:

That safeguard is relevant to: hTTP 429 signals server-enforced rate limits; API client backoff must consider shared rate budgets and Retry-After semantics. The current failure instead follows from: terraform providers translate declarative resources into platform API operations; provider version changes can alter behavior. Its prevention measure is “Test provider upgrades in a sandbox and approve lockfile changes independently of ordinary network configuration edits”.

B:

This routine guards against another mechanism: low-code accelerates common supported integrations but may constrain complex branching and custom transaction semantics. The recurring exposure in the current case is: terraform providers translate declarative resources into platform API operations; provider version changes can alter behavior. The matching preventive check is “Test provider upgrades in a sandbox and approve lockfile changes independently of ordinary network configuration edits”.

D:

That safeguard is relevant to: ansible inventory groups and variable precedence determine which devices and values are targeted by a playbook. The current failure instead follows from: terraform providers translate declarative resources into platform API operations; provider version changes can alter behavior. Its prevention measure is “Test provider upgrades in a sandbox and approve lockfile changes independently of ordinary network configuration edits”.

Question 430

At fictional Amberlight Energy, an acceptance review of an AI-assisted code review finds: An incident chatbot interprets a troubleshooting question as authority to restart an OSPF process on production edge routers. Which sustainable preventive control most directly avoids a recurrence?

  1. Add explicit timeouts, result freshness metadata and partial-failure contract tests to every MCP tool.
  2. Track evidence freshness and require independent observed-state corroboration for high-impact AI advice.
  3. Tag provenance and document freshness, test poisoned retrieval cases, and gate device changes on deterministic validation.
  4. Implement tool categorization, approval records and run-as identities for every privileged network agent operation.

Explanation

Correct Answer

D:

Implement tool categorization, approval records and run-as identities for every privileged network agent operation. This prevents the recurrence because agent tool chaining can enlarge the blast radius of an ambiguous user instruction unless execution permissions are independently gated. A matching immediate correction is: Separate read-only diagnostic tools from mutating tools and require an explicit scoped approval step before any privileged operation. Applied here, the relevant facts are: An incident chatbot interprets a troubleshooting question as authority to restart an OSPF process on production edge routers. The question asks which sustainable preventive control most directly avoids a recurrence.

Incorrect Answers

A:

This routine guards against another mechanism: tool wrappers must preserve the meaning of missing, stale and failed data for the consumer agent. The recurring exposure in the current case is: agent tool chaining can enlarge the blast radius of an ambiguous user instruction unless execution permissions are independently gated. The matching preventive check is “Implement tool categorization, approval records and run-as identities for every privileged network agent operation”.

B:

The suggested review tracks a different technical risk: aI recommendations are hypotheses requiring external ground truth; absent evidence is not proof of a network condition. Here the sustained control must address: agent tool chaining can enlarge the blast radius of an ambiguous user instruction unless execution permissions are independently gated. Choose “Implement tool categorization, approval records and run-as identities for every privileged network agent operation”.

C:

That safeguard is relevant to: retrieval-augmented systems can inherit false or hostile data; source quality and technical cross-checks must precede action. The current failure instead follows from: agent tool chaining can enlarge the blast radius of an ambiguous user instruction unless execution permissions are independently gated. Its prevention measure is “Implement tool categorization, approval records and run-as identities for every privileged network agent operation”.