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 30

Question 290

While investigating an inventory reconciliation for fictional Thornwick Health Trust, the team reports: Parallel infrastructure pipelines apply conflicting ACL changes because state locking was disabled in a shared backend. What should the engineer change first to resolve this specific issue?

  1. Use the supported token refresh flow with secret storage and distinguish unauthenticated 401 from authorized-but-forbidden 403 responses.
  2. Respect rate-limit response headers and coordinate bounded exponential backoff with jitter under the shared API budget.
  3. Configure a shared protected Terraform state backend with supported locking and serialize competing applies against the same state.
  4. Discover supported YANG modules or capabilities before using module-specific RESTCONF data paths, and branch for supported models.

Explanation

Correct Answer

C:

Configure a shared protected Terraform state backend with supported locking and serialize competing applies against the same state. This addresses the problem because terraform state tracks managed resource associations; concurrent writes without locking can corrupt effective desired-state coordination. Confirm success using: The second apply waits or fails safely on an active lock, and state reflects one consistent resource graph after the approved deployment. Applied here, the relevant facts are: Parallel infrastructure pipelines apply conflicting ACL changes because state locking was disabled in a shared backend. The question asks what should the engineer change first to resolve this specific issue.

Incorrect Answers

A:

The proposed action belongs to the mechanism: an access-token lifecycle and authorization scope are distinct concerns; repeated reuse of expired or insufficient tokens cannot resolve them. Here the stated fault follows a different mechanism: terraform state tracks managed resource associations; concurrent writes without locking can corrupt effective desired-state coordination. The corrective choice is “Configure a shared protected Terraform state backend with supported locking and serialize competing applies against the same state”.

B:

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: terraform state tracks managed resource associations; concurrent writes without locking can corrupt effective desired-state coordination. Implement “Configure a shared protected Terraform state backend with supported locking and serialize competing applies against the same state” to address that specific condition.

D:

The proposed action belongs to the mechanism: model-driven APIs are available only for modules and revisions implemented by the device software, not by the client library alone. Here the stated fault follows a different mechanism: terraform state tracks managed resource associations; concurrent writes without locking can corrupt effective desired-state coordination. The corrective choice is “Configure a shared protected Terraform state backend with supported locking and serialize competing applies against the same state”.

Question 291

During a remote branch provisioning pilot at fictional Northshore Cloud, the change record states: A playbook selects the entire production inventory even though a new OSPF policy is approved only for one distribution switch group. What technical evidence should be required before closing this change?

  1. The verification compares the authorized modeled configuration with separate operational neighbor or counter results after deployment.
  2. An induced response-loss test yields one intended network object or operation and records its final state without duplicate changes.
  3. The job records successes and failures by device, retries only supported transient cases, and does not claim full success when any target fails.
  4. The dry-run host list and collected post-change configurations show that only the approved group received the new OSPF or ACL policy.

Explanation

Correct Answer

D:

The dry-run host list and collected post-change configurations show that only the approved group received the new OSPF or ACL policy. This directly verifies the related correction: Separate inventory groups and group variables by approved device scope, then constrain the play to the intended group. It checks the technical distinction: Ansible inventory groups and variable precedence determine which devices and values are targeted by a playbook. Applied here, the relevant facts are: A playbook selects the entire production inventory even though a new OSPF policy is approved only for one distribution switch group. The question asks what technical evidence should be required before closing this change.

Incorrect Answers

A:

That test belongs to another control with this basis: This directly verifies the related correction: Read intended configuration and runtime operational YANG data from their appropriate modeled resources, and write only configurable leaves. In the current case, the governing reason is: This directly verifies the related correction: Separate inventory groups and group variables by approved device scope, then constrain the play to the intended group. The direct verification is “The dry-run host list and collected post-change configurations show that only the approved group received the new OSPF or ACL policy”.

B:

This observation would test a different technical dependency: This directly verifies the related correction: Before retrying a potentially non-idempotent change, check resulting resource state or use a supported idempotency or operation key. The current issue is governed by: This directly verifies the related correction: Separate inventory groups and group variables by approved device scope, then constrain the play to the intended group. Its decisive check is “The dry-run host list and collected post-change configurations show that only the approved group received the new OSPF or ACL policy”.

C:

The alternative verifies a different condition: This directly verifies the related correction: Handle per-target HTTP, parsing and retryable exceptions and persist a failure summary without misreporting completed targets. The current case instead depends on: This directly verifies the related correction: Separate inventory groups and group variables by approved device scope, then constrain the play to the intended group. Confirm that “The dry-run host list and collected post-change configurations show that only the approved group received the new OSPF or ACL policy”.

Question 292

At fictional Northshore Cloud, an acceptance review of an inventory reconciliation finds: A Python network maintenance loop calls requests.get without a timeout and blocks indefinitely when a switch management plane stops responding. Which control best prevents this particular failure from recurring?

  1. Require inventory-host preview and environment-specific group-variable review in change approval.
  2. Add timeout fault injection and per-target execution deadlines to the network automation test suite.
  3. Add multi-page integration tests and monitor continuation tokens and retrieved counts on every scheduled inventory run.
  4. Use an ownership register and import verification when onboarding manually created resources to IaC management.

Explanation

Correct Answer

B:

Add timeout fault injection and per-target execution deadlines to the network automation test suite. This prevents the recurrence because python HTTP clients do not guarantee a useful bounded response time unless the caller configures explicit timeouts. A matching immediate correction is: Set explicit connect and read timeouts and catch the resulting exceptions so the worker can report and continue safely.

Incorrect Answers

A:

This routine guards against another mechanism: ansible inventory groups and variable precedence determine which devices and values are targeted by a playbook. The recurring exposure in the current case is: python HTTP clients do not guarantee a useful bounded response time unless the caller configures explicit timeouts. The matching preventive check is “Add timeout fault injection and per-target execution deadlines to the network automation test suite”.

C:

That safeguard is relevant to: many platform APIs paginate large result sets; the first HTTP success response may contain only a subset. The current failure instead follows from: python HTTP clients do not guarantee a useful bounded response time unless the caller configures explicit timeouts. Its prevention measure is “Add timeout fault injection and per-target execution deadlines to the network automation test suite”.

D:

This routine guards against another mechanism: terraform configuration alone does not establish ownership of an already-existing platform object; state import binds it to a resource address. The recurring exposure in the current case is: python HTTP clients do not guarantee a useful bounded response time unless the caller configures explicit timeouts. The matching preventive check is “Add timeout fault injection and per-target execution deadlines to the network automation test suite”.

Question 293

During a telemetry quality investigation at fictional Foxglove Aviation, the change record states: A long-lived bot token with global network administrator privileges is embedded in a Docker image used for development and production. Which engineering principle explains the described system behavior?

  1. Time-series cardinality grows with combinations of labels; volatile unique IDs defeat aggregation and strain metric storage.
  2. Hardcoded secrets create persistent exposure and excessive authority; runtime secret retrieval limits both lifetime and access scope.
  3. Webhooks are asynchronous network events; integrity, delivery acknowledgements and idempotent processing are separate reliability needs.
  4. Model-driven test tools depend on supported device schemas and parser versions; missing parsed data is not proof of missing network function.

Explanation

Correct Answer

B:

Hardcoded secrets create persistent exposure and excessive authority; runtime secret retrieval limits both lifetime and access scope. The corresponding repair is: Inject short-lived narrowly scoped secrets at runtime from a managed vault and mask them in logs and build artifacts. Acceptance should show: A token rotation test succeeds without image rebuild, and repository, image and logs contain no recoverable credentials.

Incorrect Answers

A:

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: Inject short-lived narrowly scoped secrets at runtime from a managed vault and mask them in logs and build artifacts.

C:

This principle describes a separate cause: The corresponding repair is: Authenticate webhook delivery and implement bounded retries with deduplication or delivery-state accounting. The reported condition is governed by: 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 two mechanisms should not be conflated.

D:

The corresponding repair is: Validate parser and platform compatibility and distinguish collection or parsing errors from actual network-state assertion failures. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Inject short-lived narrowly scoped secrets at runtime from a managed vault and mask them in logs and build artifacts.

Question 294

During a remote branch provisioning pilot at fictional Northshore Cloud, the change record states: One device returns a 503 response and the Python batch raises an uncaught exception, abandoning configuration for all other approved targets. Which engineering principle explains the described system behavior?

  1. Model-driven APIs are available only for modules and revisions implemented by the device software, not by the client library alone.
  2. Robust batch automation isolates errors at the per-resource boundary and retains auditable partial outcomes.
  3. RESTCONF exposes list entries through resource identifiers determined by the keys declared in the YANG model.
  4. Automation choice is driven by lifecycle and operational risk rather than by a single preferred programming tool.

Explanation

Correct Answer

B:

Robust batch automation isolates errors at the per-resource boundary and retains auditable partial outcomes. The corresponding repair is: Handle per-target HTTP, parsing and retryable exceptions and persist a failure summary without misreporting completed targets. Acceptance should show: The job records successes and failures by device, retries only supported transient cases, and does not claim full success when any target fails.

Incorrect Answers

A:

The offered statement is true for this other mechanism: The corresponding repair is: Discover supported YANG modules or capabilities before using module-specific RESTCONF data paths, and branch for supported models. It does not explain the facts described here, which follow from: The corresponding repair is: Handle per-target HTTP, parsing and retryable exceptions and persist a failure summary without misreporting completed targets.

C:

The corresponding repair is: Address the exact YANG list instance using its fully encoded key values in the RESTCONF data resource path. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Handle per-target HTTP, parsing and retryable exceptions and persist a failure summary without misreporting completed targets.

D:

The offered statement is true for this other mechanism: The corresponding repair is: Select the tool and deployment pattern by risk, state persistence, change scope, rollback capability and approval obligations. It does not explain the facts described here, which follow from: The corresponding repair is: Handle per-target HTTP, parsing and retryable exceptions and persist a failure summary without misreporting completed targets.

Question 295

While investigating an inventory reconciliation for fictional Thornwick Health Trust, the team reports: An engineer reads a configuration datastore and concludes an OSPF adjacency is healthy even though the operational state shows no neighbor. Which explanation best matches the actual broken dependency?

  1. YANG distinguishes configuration intent from read-only operational state; successful config writes do not establish runtime protocol health.
  2. An access-token lifecycle and authorization scope are distinct concerns; repeated reuse of expired or insufficient tokens cannot resolve them.
  3. Terraform providers translate declarative resources into platform API operations; provider version changes can alter behavior.
  4. Terraform configuration alone does not establish ownership of an already-existing platform object; state import binds it to a resource address.

Explanation

Correct Answer

A:

YANG distinguishes configuration intent from read-only operational state; successful config writes do not establish runtime protocol health. The corresponding repair is: Read intended configuration and runtime operational YANG data from their appropriate modeled resources, and write only configurable leaves. Acceptance should show: The verification compares the authorized modeled configuration with separate operational neighbor or counter results after deployment.

Incorrect Answers

B:

The proposed action belongs to the mechanism: The corresponding repair is: Use the supported token refresh flow with secret storage and distinguish unauthenticated 401 from authorized-but-forbidden 403 responses. Here the stated fault follows a different mechanism: The corresponding repair is: Read intended configuration and runtime operational YANG data from their appropriate modeled resources, and write only configurable leaves. The corrective choice is “YANG distinguishes configuration intent from read-only operational state; successful config writes do not establish runtime protocol health”.

C:

The offered action targets: The corresponding repair is: Set compatible provider version constraints and commit the provider dependency lock file for reproducible runs. The case facts point instead to: The corresponding repair is: Read intended configuration and runtime operational YANG data from their appropriate modeled resources, and write only configurable leaves. Implement “YANG distinguishes configuration intent from read-only operational state; successful config writes do not establish runtime protocol health” to address that specific condition.

D:

This alternative is a response to another technical cause: The corresponding repair is: Import the existing platform object into Terraform state, align its configuration and inspect a non-destructive plan. The reported case instead depends on: The corresponding repair is: Read intended configuration and runtime operational YANG data from their appropriate modeled resources, and write only configurable leaves. The action that directly addresses it is “YANG distinguishes configuration intent from read-only operational state; successful config writes do not establish runtime protocol health”.

Question 296

At fictional Windward Maritime, during a GitLab deployment pipeline rehearsal, the operator observes: A teammate wants to compare one previous inventory template but accidentally resets unrelated new workflow files to older versions. Which sustainable preventive control most directly avoids a recurrence?

  1. Add merge topology review and a dry-run diff approval for complex revert operations.
  2. Record source commit IDs, test cross-branch compatibility and review cherry-pick conflict resolutions.
  3. Version lab topology artifacts and run automated readiness verification before configuration tests.
  4. Require path-limited recovery commands and postrestore diffs for surgical automation-file reversions.

Explanation

Correct Answer

D:

Require path-limited recovery commands and postrestore diffs for surgical automation-file reversions. This prevents the recurrence because git can retrieve individual tracked paths from a commit; selecting file scope avoids broad branch-level rollback. A matching immediate correction is: Restore only the specifically reviewed historical file from the desired revision instead of replacing the whole branch state.

Incorrect Answers

A:

The suggested review tracks a different technical risk: reverting a merge requires an explicit mainline perspective so Git knows which parent is the retained baseline. Here the sustained control must address: git can retrieve individual tracked paths from a commit; selecting file scope avoids broad branch-level rollback. Choose “Require path-limited recovery commands and postrestore diffs for surgical automation-file reversions”.

B:

That safeguard is relevant to: git cherry-pick applies the change introduced by selected commit(s) onto the current branch, creating new history in that branch. The current failure instead follows from: git can retrieve individual tracked paths from a commit; selecting file scope avoids broad branch-level rollback. Its prevention measure is “Require path-limited recovery commands and postrestore diffs for surgical automation-file reversions”.

C:

This routine guards against another mechanism: a reproducible simulation needs controlled topology definitions and readiness gates to avoid timing-dependent false failures. The recurring exposure in the current case is: git can retrieve individual tracked paths from a commit; selecting file scope avoids broad branch-level rollback. The matching preventive check is “Require path-limited recovery commands and postrestore diffs for surgical automation-file reversions”.

Question 297

While investigating a FastMCP security review for fictional Elmcrest Theatre, the team reports: A user switches sites in the same session, but the assistant carries the earlier site's tenant scope into a new API query. What underlying technical distinction accounts for this failure?

  1. The model is not a reliable security principal; tool identities and server-side authorization bound the damage of agent errors.
  2. AI-generated code may embed third-party patterns or dependencies; tool output is not automatically cleared of licensing obligations.
  3. Retrieval-augmented systems can inherit false or hostile data; source quality and technical cross-checks must precede action.
  4. Conversation memory is not authoritative network state; stale context and scope leakage create wrong-target operational risk.

Explanation

Correct Answer

D:

Conversation memory is not authoritative network state; stale context and scope leakage create wrong-target operational risk. The corresponding repair is: Bind current request context to fresh authorized inventory and explicit tenant or device selection before tool calls. Acceptance should show: A site-context switch triggers a fresh scoped lookup and proposed actions reference currently authorized device identifiers.

Incorrect Answers

A:

The offered statement is true for this other mechanism: The corresponding repair is: Issue read-only scoped identity credentials for diagnostic agents and place separate approval boundaries around mutating tools. It does not explain the facts described here, which follow from: The corresponding repair is: Bind current request context to fresh authorized inventory and explicit tenant or device selection before tool calls.

B:

This principle describes a separate cause: The corresponding repair is: Review generated code provenance, included dependencies and organizational IP policy before accepting it into the repository. The reported condition is governed by: The corresponding repair is: Bind current request context to fresh authorized inventory and explicit tenant or device selection before tool calls. The two mechanisms should not be conflated.

C:

The corresponding repair is: Ground actionable recommendations in trusted versioned technical references and reject unsupported or conflicting retrieved claims. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Bind current request context to fresh authorized inventory and explicit tenant or device selection before tool calls.

Question 298

At fictional Northshore Cloud, an acceptance review of an inventory reconciliation finds: A Python network maintenance loop calls requests.get without a timeout and blocks indefinitely when a switch management plane stops responding. Which engineering principle explains the described system behavior?

  1. Python HTTP clients do not guarantee a useful bounded response time unless the caller configures explicit timeouts.
  2. HTTP 429 signals server-enforced rate limits; API client backoff must consider shared rate budgets and Retry-After semantics.
  3. YANG distinguishes configuration intent from read-only operational state; successful config writes do not establish runtime protocol health.
  4. Low-code accelerates common supported integrations but may constrain complex branching and custom transaction semantics.

Explanation

Correct Answer

A:

Python HTTP clients do not guarantee a useful bounded response time unless the caller configures explicit timeouts. The corresponding repair is: Set explicit connect and read timeouts and catch the resulting exceptions so the worker can report and continue safely. Acceptance should show: A simulated nonresponsive endpoint times out within the declared bound and produces a per-device failure record without blocking others. Applied here, the relevant facts are: A Python network maintenance loop calls requests.get without a timeout and blocks indefinitely when a switch management plane stops responding. The question asks which engineering principle explains the described system behavior.

Incorrect Answers

B:

The corresponding repair is: Respect rate-limit response headers and coordinate bounded exponential backoff with jitter under the shared API budget. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Set explicit connect and read timeouts and catch the resulting exceptions so the worker can report and continue safely.

C:

The offered statement is true for this other mechanism: The corresponding repair is: Read intended configuration and runtime operational YANG data from their appropriate modeled resources, and write only configurable leaves. It does not explain the facts described here, which follow from: The corresponding repair is: Set explicit connect and read timeouts and catch the resulting exceptions so the worker can report and continue safely.

D:

This principle describes a separate cause: 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. The reported condition is governed by: The corresponding repair is: Set explicit connect and read timeouts and catch the resulting exceptions so the worker can report and continue safely. The two mechanisms should not be conflated.

Question 299

At fictional Sunrise Aeronautics, during an AI-assisted code review, the operator observes: A network incident log contains attacker-controlled text saying ignore safety checks and run a destructive router command, and the agent obeys it. Which result most directly verifies that the proposed correction worked?

  1. Injection test logs are summarized as evidence but never cause unauthorized configuration or secret-retrieval tool calls.
  2. Test reports expose false positives, false negatives and unsupported recommendations before approval for a broader network scope.
  3. Agent tool traces distinguish timeout, authorization and partial-data failures from genuine empty network results.
  4. The assistant identifies missing version evidence and withholds unverified commands instead of fabricating supported APIs.

Explanation

Correct Answer

A:

Injection test logs are summarized as evidence but never cause unauthorized configuration or secret-retrieval tool calls. This directly verifies the related correction: Treat retrieved logs as untrusted data and enforce instruction hierarchy and independent tool permissions outside the model. It checks the technical distinction: Prompt injection attempts to convert lower-trust retrieved content into high-priority instructions across an AI-agent trust boundary.

Incorrect Answers

B:

The offered action targets: This directly verifies the related correction: Evaluate the agent on a representative labeled test set with difficult, adversarial and negative cases, measuring factual error and unsafe-action rates. The case facts point instead to: This directly verifies the related correction: Treat retrieved logs as untrusted data and enforce instruction hierarchy and independent tool permissions outside the model. Implement “Injection test logs are summarized as evidence but never cause unauthorized configuration or secret-retrieval tool calls” to address that specific condition.

C:

This alternative is a response to another technical cause: This directly verifies the related correction: Return structured success and error states with source timestamps and bounded API timeouts rather than silently substituting empty values. The reported case instead depends on: This directly verifies the related correction: Treat retrieved logs as untrusted data and enforce instruction hierarchy and independent tool permissions outside the model. The action that directly addresses it is “Injection test logs are summarized as evidence but never cause unauthorized configuration or secret-retrieval tool calls”.

D:

The proposed action belongs to the mechanism: This directly verifies the related correction: Require citation to a compatible authoritative reference and fail closed or escalate when command syntax or device version is uncertain. Here the stated fault follows a different mechanism: This directly verifies the related correction: Treat retrieved logs as untrusted data and enforce instruction hierarchy and independent tool permissions outside the model. The corrective choice is “Injection test logs are summarized as evidence but never cause unauthorized configuration or secret-retrieval tool calls”.

Question 300

While investigating a reproducible simulation for fictional Windward Maritime, the team reports: A YANG-driven script uses a generic key name that is not in the device's supported schema, causing server-side validation rejection. Which targeted correction best addresses the network automation failure?

  1. Define service dependencies with appropriate health checks and resilient application startup or retry behavior.
  2. Inspect the failed job logs and classify whether build, dependency, test or environment validation failed before making a targeted fix.
  3. Run objective-based postdeployment checks and fail or roll back the change when observed network behavior contradicts intent.
  4. Construct JSON using the published YANG container hierarchy, qualified node names and correct value types.

Explanation

Correct Answer

D:

Construct JSON using the published YANG container hierarchy, qualified node names and correct value types. This addresses the problem because yANG defines node hierarchy, namespaces, list keys and data types; conforming JSON must preserve that structure. Confirm success using: The payload validates against the YANG schema and the RESTCONF server accepts the exact intended interface resource. Applied here, the relevant facts are: A YANG-driven script uses a generic key name that is not in the device's supported schema, causing server-side validation rejection. The question asks which targeted correction best addresses the network automation failure.

Incorrect Answers

A:

The offered action targets: container start ordering does not inherently guarantee service readiness; health conditions and retries address that gap. The case facts point instead to: yANG defines node hierarchy, namespaces, list keys and data types; conforming JSON must preserve that structure. Implement “Construct JSON using the published YANG container hierarchy, qualified node names and correct value types” to address that specific condition.

B:

This alternative is a response to another technical cause: a GitLab pipeline exit code identifies failure, while job logs and test artifacts reveal the specific causal stage and assertion. The reported case instead depends on: yANG defines node hierarchy, namespaces, list keys and data types; conforming JSON must preserve that structure. The action that directly addresses it is “Construct JSON using the published YANG container hierarchy, qualified node names and correct value types”.

C:

The proposed action belongs to the mechanism: deployment command success is not the same as verified service success; operational checks must follow state changes. Here the stated fault follows a different mechanism: yANG defines node hierarchy, namespaces, list keys and data types; conforming JSON must preserve that structure. The corrective choice is “Construct JSON using the published YANG container hierarchy, qualified node names and correct value types”.