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 11

Question 100

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. 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 maintenance branch contains the intended patch without unrelated feature commits and passes the target release tests.
  3. Only the selected file matches the approved historical content, and unrelated working files remain unchanged.
  4. The target branch retains an auditable inverse commit and the published history remains intact while behavior returns to the approved state.

Explanation

Correct Answer

D:

The target branch retains an auditable inverse commit and the published history remains intact while behavior returns to the approved state. This directly verifies the related correction: Create a reviewed Git revert commit for the offending change and run the full network automation release tests. It checks the technical distinction: Git revert records an inverse patch in new history rather than moving shared branch pointers backward.

Incorrect Answers

A:

This observation would test a different technical dependency: This directly verifies the related correction: Construct JSON using the published YANG container hierarchy, qualified node names and correct value types. The current issue is governed by: This directly verifies the related correction: Create a reviewed Git revert commit for the offending change and run the full network automation release tests. Its decisive check is “The target branch retains an auditable inverse commit and the published history remains intact while behavior returns to the approved state”.

B:

The alternative verifies a different condition: This directly verifies the related correction: Cherry-pick the specific reviewed hotfix commit into the target maintenance branch and test the resulting change. The current case instead depends on: This directly verifies the related correction: Create a reviewed Git revert commit for the offending change and run the full network automation release tests. Confirm that “The target branch retains an auditable inverse commit and the published history remains intact while behavior returns to the approved state”.

C:

That test belongs to another control with this basis: This directly verifies the related correction: Restore only the specifically reviewed historical file from the desired revision instead of replacing the whole branch state. In the current case, the governing reason is: This directly verifies the related correction: Create a reviewed Git revert commit for the offending change and run the full network automation release tests. The direct verification is “The target branch retains an auditable inverse commit and the published history remains intact while behavior returns to the approved state”.

Question 101

While investigating a telemetry quality investigation for fictional Sable Valley Power, the team reports: A time-series database stores each raw API request ID as a permanent metric label, causing explosive series cardinality. What should the team add to its network automation operating process?

  1. Rotate webhook credentials and monitor delivery latency, signature validation and replay protection.
  2. Monitor certificate expirations and trust-chain changes with automated predeployment verification.
  3. Review telemetry label schemas, retention and cardinality budgets before enabling new collectors.
  4. Review change-specific expected route and adjacency deltas alongside baseline safety invariants in test cases.

Explanation

Correct Answer

C:

Review telemetry label schemas, retention and cardinality budgets before enabling new collectors. This prevents the recurrence because time-series cardinality grows with combinations of labels; volatile unique IDs defeat aggregation and strain metric storage. A matching immediate correction is: Normalize telemetry dimensions to stable device and interface identifiers and avoid high-cardinality ephemeral labels.

Incorrect Answers

A:

The proposed action belongs to the mechanism: webhooks are asynchronous network events; integrity, delivery acknowledgements and idempotent processing are separate reliability needs. Here the stated fault follows a different mechanism: time-series cardinality grows with combinations of labels; volatile unique IDs defeat aggregation and strain metric storage. The corrective choice is “Review telemetry label schemas, retention and cardinality budgets before enabling new collectors”.

B:

The offered action targets: tLS server validation depends on trusted issuer chains and hostname identity; bypassing verification defeats server authentication. The case facts point instead to: time-series cardinality grows with combinations of labels; volatile unique IDs defeat aggregation and strain metric storage. Implement “Review telemetry label schemas, retention and cardinality budgets before enabling new collectors” to address that specific condition.

D:

The proposed action belongs to the mechanism: postdeployment validation compares expected invariants and intended deltas, not every volatile or purposely changed value. Here the stated fault follows a different mechanism: time-series cardinality grows with combinations of labels; volatile unique IDs defeat aggregation and strain metric storage. The corrective choice is “Review telemetry label schemas, retention and cardinality budgets before enabling new collectors”.

Question 102

At fictional Sunrise Aeronautics, during an AI-assisted code review, the operator observes: A network assistant scores well on easy inventory questions but fails when simulated device logs contain conflicting routing states. What mechanism is most directly responsible for these symptoms?

  1. An MCP server publishes structured tools and resources to clients; safe network use requires explicit least-privilege tool definitions.
  2. High aggregate answer accuracy can hide safety-critical errors; validation must measure behavior on representative failure modes.
  3. Tool results are untrusted external input; unrestricted outbound connectivity turns an injected instruction into a data-exfiltration path.
  4. An MCP server is an integration boundary and must not treat model-selected identity strings as verified security credentials.

Explanation

Correct Answer

B:

High aggregate answer accuracy can hide safety-critical errors; validation must measure behavior on representative failure modes. The corresponding repair is: Evaluate the agent on a representative labeled test set with difficult, adversarial and negative cases, measuring factual error and unsafe-action rates. Acceptance should show: Test reports expose false positives, false negatives and unsupported recommendations before approval for a broader network scope. Applied here, the relevant facts are: A network assistant scores well on easy inventory questions but fails when simulated device logs contain conflicting routing states. The question asks what mechanism is most directly responsible for these symptoms.

Incorrect Answers

A:

The offered statement is true for this other mechanism: The corresponding repair is: Expose narrowly scoped typed read-only FastMCP tools for approved device and status fields with controlled access. It does not explain the facts described here, which follow from: The corresponding repair is: Evaluate the agent on a representative labeled test set with difficult, adversarial and negative cases, measuring factual error and unsafe-action rates.

C:

The corresponding repair is: Restrict tool egress to approved destinations and never grant untrusted retrieved text authority to choose exfiltration endpoints. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Evaluate the agent on a representative labeled test set with difficult, adversarial and negative cases, measuring factual error and unsafe-action rates.

D:

The offered statement is true for this other mechanism: The corresponding repair is: Authenticate each MCP client, authorize its tool calls by tenant identity and isolate credential/session context. It does not explain the facts described here, which follow from: The corresponding repair is: Evaluate the agent on a representative labeled test set with difficult, adversarial and negative cases, measuring factual error and unsafe-action rates.

Question 103

At fictional Thornwick Health Trust, during a remote branch provisioning pilot, the operator observes: A playbook prints bearer tokens in verbose task output while provisioning switch access lists across multiple sites. Which observation would confirm that this exact failure is resolved?

  1. Repository scans and run logs reveal no plain credentials, and the playbook authenticates with approved secret retrieval.
  2. The imported resource maps to the intended live identifier and the reviewed plan does not attempt duplicate creation or replacement.
  3. Fresh runners initialize the same reviewed provider build and produce equivalent plans from the same state and configuration.
  4. The integration refreshes an expired token once when permitted, does not leak credentials and reports genuine 403 denials accurately.

Explanation

Correct Answer

A:

Repository scans and run logs reveal no plain credentials, and the playbook authenticates with approved secret retrieval. This directly verifies the related correction: Move credentials into a protected secret store or Ansible Vault and suppress sensitive task output while keeping access narrowly scoped. It checks the technical distinction: Automation credentials need confidentiality at rest and in output; inventory convenience does not justify committing secrets.

Incorrect Answers

B:

The alternative verifies a different condition: This directly verifies the related correction: Import the existing platform object into Terraform state, align its configuration and inspect a non-destructive plan. The current case instead depends on: This directly verifies the related correction: Move credentials into a protected secret store or Ansible Vault and suppress sensitive task output while keeping access narrowly scoped. Confirm that “Repository scans and run logs reveal no plain credentials, and the playbook authenticates with approved secret retrieval”.

C:

That test belongs to another control with this basis: This directly verifies the related correction: Set compatible provider version constraints and commit the provider dependency lock file for reproducible runs. In the current case, the governing reason is: This directly verifies the related correction: Move credentials into a protected secret store or Ansible Vault and suppress sensitive task output while keeping access narrowly scoped. The direct verification is “Repository scans and run logs reveal no plain credentials, and the playbook authenticates with approved secret retrieval”.

D:

This observation would test a different technical dependency: This directly verifies the related correction: Use the supported token refresh flow with secret storage and distinguish unauthenticated 401 from authorized-but-forbidden 403 responses. The current issue is governed by: This directly verifies the related correction: Move credentials into a protected secret store or Ansible Vault and suppress sensitive task output while keeping access narrowly scoped. Its decisive check is “Repository scans and run logs reveal no plain credentials, and the playbook authenticates with approved secret retrieval”.

Question 104

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. Which observation would confirm that this exact failure is resolved?

  1. Generated configs match authoritative source records and postapply compliance detects any remaining unauthorized deviation.
  2. The protected target branch contains one reviewed release commit whose diff matches the approved feature changes.
  3. A recreated container reads the expected persistent audit or inventory records from the configured volume.
  4. The target branch retains an auditable inverse commit and the published history remains intact while behavior returns to the approved state.

Explanation

Correct Answer

A:

Generated configs match authoritative source records and postapply compliance detects any remaining unauthorized deviation. This directly verifies the related correction: Read authorized desired state from the designated source of truth and reconcile observed drift through an approved change path. It checks the technical distinction: A reliable source-of-truth workflow separates approved intent from observed device state and defines how changes flow between them.

Incorrect Answers

B:

That test belongs to another control with this basis: This directly verifies the related correction: Use an approved squash merge to combine reviewed feature changes into one commit while preserving the final content. In the current case, the governing reason is: This directly verifies the related correction: Read authorized desired state from the designated source of truth and reconcile observed drift through an approved change path. The direct verification is “Generated configs match authoritative source records and postapply compliance detects any remaining unauthorized deviation”.

C:

This observation would test a different technical dependency: This directly verifies the related correction: Mount an appropriate persistent named volume or approved bind mount for data that must survive container recreation. The current issue is governed by: This directly verifies the related correction: Read authorized desired state from the designated source of truth and reconcile observed drift through an approved change path. Its decisive check is “Generated configs match authoritative source records and postapply compliance detects any remaining unauthorized deviation”.

D:

The alternative verifies a different condition: This directly verifies the related correction: Create a reviewed Git revert commit for the offending change and run the full network automation release tests. The current case instead depends on: This directly verifies the related correction: Read authorized desired state from the designated source of truth and reconcile observed drift through an approved change path. Confirm that “Generated configs match authoritative source records and postapply compliance detects any remaining unauthorized deviation”.

Question 105

During a conversational network agent pilot at fictional Westlake Biomedicine, the change record states: An LLM invents a controller API path not documented in the deployed Cisco software and presents it as a certain fix. Which 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. Require provenance review, software composition analysis and approved dependencies for generated network automation components.
  3. Enforce identity binding, tenant-isolated caches and tool-level audit and RBAC tests for MCP services.
  4. Use retrieval provenance, platform compatibility checks and refusal or escalation criteria for low-confidence device instructions.

Explanation

Correct Answer

D:

Use retrieval provenance, platform compatibility checks and refusal or escalation criteria for low-confidence device instructions. This prevents the recurrence because model fluency is not evidence of device capability; uncertain technical recommendations require explicit verification before action. A matching immediate correction is: Require citation to a compatible authoritative reference and fail closed or escalate when command syntax or device version is uncertain.

Incorrect Answers

A:

That safeguard is relevant to: tool wrappers must preserve the meaning of missing, stale and failed data for the consumer agent. The current failure instead follows from: model fluency is not evidence of device capability; uncertain technical recommendations require explicit verification before action. Its prevention measure is “Use retrieval provenance, platform compatibility checks and refusal or escalation criteria for low-confidence device instructions”.

B:

This routine guards against another mechanism: aI-generated code may embed third-party patterns or dependencies; tool output is not automatically cleared of licensing obligations. The recurring exposure in the current case is: model fluency is not evidence of device capability; uncertain technical recommendations require explicit verification before action. The matching preventive check is “Use retrieval provenance, platform compatibility checks and refusal or escalation criteria for low-confidence device instructions”.

C:

The suggested review tracks a different technical risk: an MCP server is an integration boundary and must not treat model-selected identity strings as verified security credentials. Here the sustained control must address: model fluency is not evidence of device capability; uncertain technical recommendations require explicit verification before action. Choose “Use retrieval provenance, platform compatibility checks and refusal or escalation criteria for low-confidence device instructions”.

Question 106

At fictional Foxglove Aviation, an acceptance review of a certificate renewal rehearsal finds: A network health job fails when command output format changes but the runner incorrectly interprets a parser exception as failed OSPF state. What technical evidence should be required before closing this change?

  1. A supported image produces structured parsed data; unsupported output is reported as a test instrumentation error, not a device state failure.
  2. A timeline of stage logs identifies the first failing API or schema operation and confirms the targeted repair removes it.
  3. Cross-tenant modification attempts are rejected with a denial and approved users can change only authorized resources.
  4. TLS validation succeeds for the intended hostname and fails for unexpected names without disabling verification.

Explanation

Correct Answer

A:

A supported image produces structured parsed data; unsupported output is reported as a test instrumentation error, not a device state failure. This directly verifies the related correction: Validate parser and platform compatibility and distinguish collection or parsing errors from actual network-state assertion failures. It checks the technical distinction: Model-driven test tools depend on supported device schemas and parser versions; missing parsed data is not proof of missing network function.

Incorrect Answers

B:

The alternative verifies a different condition: This directly verifies the related correction: Trace correlated event IDs and earliest causal errors through the pipeline instead of treating the final propagated exception as root cause. The current case instead depends on: This directly verifies the related correction: Validate parser and platform compatibility and distinguish collection or parsing errors from actual network-state assertion failures. Confirm that “A supported image produces structured parsed data; unsupported output is reported as a test instrumentation error, not a device state failure”.

C:

That test belongs to another control with this basis: This directly verifies the related correction: Enforce server-side per-resource authorization using authenticated identity and approved tenant or device scope. In the current case, the governing reason is: This directly verifies the related correction: Validate parser and platform compatibility and distinguish collection or parsing errors from actual network-state assertion failures. The direct verification is “A supported image produces structured parsed data; unsupported output is reported as a test instrumentation error, not a device state failure”.

D:

This observation would test a different technical dependency: This directly verifies the related correction: Use an approved DNS endpoint covered by the certificate SAN or reissue a certificate with correct service identities. The current issue is governed by: This directly verifies the related correction: Validate parser and platform compatibility and distinguish collection or parsing errors from actual network-state assertion failures. Its decisive check is “A supported image produces structured parsed data; unsupported output is reported as a test instrumentation error, not a device state failure”.

Question 107

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 underlying technical distinction accounts for this failure?

  1. pyATS can learn and compare device operational state to detect unintended network effects beyond text config diffs.
  2. HTTP 401 generally signals missing or invalid authentication while 403 indicates access denied to an authenticated request.
  3. Hardcoded secrets create persistent exposure and excessive authority; runtime secret retrieval limits both lifetime and access scope.
  4. Time-series cardinality grows with combinations of labels; volatile unique IDs defeat aggregation and strain metric storage.

Explanation

Correct Answer

B:

HTTP 401 generally signals missing or invalid authentication while 403 indicates access denied to an authenticated request. The corresponding repair is: Classify authentication failures and authorization denials separately, then correct token validity or RBAC scope accordingly. Acceptance should show: The corrected job authenticates with a valid identity and has exactly the approved resource permissions, with distinct log codes for future failures.

Incorrect Answers

A:

The corresponding repair is: Capture structured prechange operational state with pyATS, apply the change, then compare relevant postchange state and assert expected invariants. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Classify authentication failures and authorization denials separately, then correct token validity or RBAC scope accordingly.

C:

This principle describes a separate cause: The corresponding repair is: Inject short-lived narrowly scoped secrets at runtime from a managed vault and mask them in logs and build artifacts. The reported condition is governed by: The corresponding repair is: Classify authentication failures and authorization denials separately, then correct token validity or RBAC scope accordingly. The two mechanisms should not be conflated.

D:

The corresponding repair is: Normalize telemetry dimensions to stable device and interface identifiers and avoid high-cardinality ephemeral labels. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Classify authentication failures and authorization denials separately, then correct token validity or RBAC scope accordingly.

Question 108

While investigating a network policy migration for fictional Cedarbridge Care Systems, the team reports: An engineer pushes a Terraform change to production without reviewing a plan, unexpectedly replacing a live network object instead of editing it. Which engineering principle explains the described system behavior?

  1. Terraform compares configuration, recorded state and provider observations to compute a proposed change set before apply.
  2. Model-driven APIs are available only for modules and revisions implemented by the device software, not by the client library alone.
  3. Low-code accelerates common supported integrations but may constrain complex branching and custom transaction semantics.
  4. RESTCONF exposes list entries through resource identifiers determined by the keys declared in the YANG model.

Explanation

Correct Answer

A:

Terraform compares configuration, recorded state and provider observations to compute a proposed change set before apply. The corresponding repair is: Refresh managed state and review a generated Terraform plan before applying only the intended network changes. Acceptance should show: The approved plan identifies the precise create, update and destroy operations, and a follow-up plan shows no unintended drift. Applied here, the relevant facts are: An engineer pushes a Terraform change to production without reviewing a plan, unexpectedly replacing a live network object instead of editing it. The question asks which engineering principle explains the described system behavior.

Incorrect Answers

B:

This principle describes a separate cause: The corresponding repair is: Discover supported YANG modules or capabilities before using module-specific RESTCONF data paths, and branch for supported models. The reported condition is governed by: The corresponding repair is: Refresh managed state and review a generated Terraform plan before applying only the intended network changes. The two mechanisms should not be conflated.

C:

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. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Refresh managed state and review a generated Terraform plan before applying only the intended network changes.

D:

The offered statement is true for this other mechanism: The corresponding repair is: Address the exact YANG list instance using its fully encoded key values in the RESTCONF data resource path. It does not explain the facts described here, which follow from: The corresponding repair is: Refresh managed state and review a generated Terraform plan before applying only the intended network changes.

Question 109

At fictional Thornwick Health Trust, during a remote branch provisioning pilot, the operator observes: An engineer builds a RESTCONF URI without a required interface-list key and receives a resource-not-found or ambiguous-target error. Which targeted correction best addresses the network automation failure?

  1. Extract a versioned reusable Terraform module with validated input variables for site-specific network parameters.
  2. Address the exact YANG list instance using its fully encoded key values in the RESTCONF data resource path.
  3. Respect rate-limit response headers and coordinate bounded exponential backoff with jitter under the shared API budget.
  4. Match workflow complexity, vendor connector capability and error recovery needs to low-code or custom application design after a capability pilot.

Explanation

Correct Answer

B:

Address the exact YANG list instance using its fully encoded key values in the RESTCONF data resource path. This addresses the problem because rESTCONF exposes list entries through resource identifiers determined by the keys declared in the YANG model. Confirm success using: A GET of the specific keyed list entry shows only the authorized VLAN or interface changed, with sibling entries intact.

Incorrect Answers

A:

This alternative is a response to another technical cause: terraform modules support repeated declarative resource patterns while typed inputs isolate deployment-specific configuration. The reported case instead depends on: rESTCONF exposes list entries through resource identifiers determined by the keys declared in the YANG model. The action that directly addresses it is “Address the exact YANG list instance using its fully encoded key values in the RESTCONF data resource path”.

C:

The offered action targets: hTTP 429 signals server-enforced rate limits; API client backoff must consider shared rate budgets and Retry-After semantics. The case facts point instead to: rESTCONF exposes list entries through resource identifiers determined by the keys declared in the YANG model. Implement “Address the exact YANG list instance using its fully encoded key values in the RESTCONF data resource path” to address that specific condition.

D:

This alternative is a response to another technical cause: low-code accelerates common supported integrations but may constrain complex branching and custom transaction semantics. The reported case instead depends on: rESTCONF exposes list entries through resource identifiers determined by the keys declared in the YANG model. The action that directly addresses it is “Address the exact YANG list instance using its fully encoded key values in the RESTCONF data resource path”.

Question 110

While investigating a reproducible simulation for fictional Windward Maritime, the team reports: A CI experiment stages a temporary secret-test file but needs to keep it locally while excluding it from the next commit. Which control best prevents this particular failure from recurring?

  1. Run clean-environment dependency installation tests and enforce dependency lockfile review.
  2. Add secret scanning and explicit staged-diff review before committing automation changes.
  3. Use protected environments, least-privilege deploy tokens and progressive rollout approval conditions.
  4. Require postchange telemetry and rollback thresholds for network pipeline release completion.

Explanation

Correct Answer

B:

Add secret scanning and explicit staged-diff review before committing automation changes. This prevents the recurrence because the Git index is the staging area and can be changed independently of the working tree by suitable reset modes. A matching immediate correction is: Unstage the unintended file with an index-only reset or equivalent restore-staged operation, leaving the worktree intact.

Incorrect Answers

A:

The suggested review tracks a different technical risk: cI runners start from controlled environments; undeclared local dependencies cannot be assumed present remotely. Here the sustained control must address: the Git index is the staging area and can be changed independently of the working tree by suitable reset modes. Choose “Add secret scanning and explicit staged-diff review before committing automation changes”.

C:

This routine guards against another mechanism: a deployment stage should enforce release scope and approval, not merely execute a command with unrestricted infrastructure access. The recurring exposure in the current case is: the Git index is the staging area and can be changed independently of the working tree by suitable reset modes. The matching preventive check is “Add secret scanning and explicit staged-diff review before committing automation changes”.

D:

The suggested review tracks a different technical risk: deployment command success is not the same as verified service success; operational checks must follow state changes. Here the sustained control must address: the Git index is the staging area and can be changed independently of the working tree by suitable reset modes. Choose “Add secret scanning and explicit staged-diff review before committing automation changes”.