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 27

Question 260

During a production change postcheck at fictional Marble Bay Software, the change record states: A gNMI telemetry collector cannot process bursty device messages and drops interface counters without reporting any gaps. Which sustainable preventive control most directly avoids a recurrence?

  1. Measure ingress rate, queue depth, drop rate and end-to-end sample latency with capacity alerts.
  2. Automate private-key permission checks, key rotation and credential scanning in certificate deployment workflows.
  3. Rotate webhook credentials and monitor delivery latency, signature validation and replay protection.
  4. Version baseline snapshots and specify per-feature allowed changes rather than requiring exact equality for volatile counters.

Explanation

Correct Answer

A:

Measure ingress rate, queue depth, drop rate and end-to-end sample latency with capacity alerts. This prevents the recurrence because streaming telemetry pipelines have collectors, transports, ingestion queues and storage capacity that can fail independently of device subscriptions. A matching immediate correction is: Introduce bounded buffering, backpressure monitoring and horizontal ingestion capacity with visible gap or loss reporting. Applied here, the relevant facts are: A gNMI telemetry collector cannot process bursty device messages and drops interface counters without reporting any gaps. The question asks which sustainable preventive control most directly avoids a recurrence.

Incorrect Answers

B:

That safeguard is relevant to: cA-signed certificates are public trust assertions but the associated private key must remain confidential for endpoint authentication. The current failure instead follows from: streaming telemetry pipelines have collectors, transports, ingestion queues and storage capacity that can fail independently of device subscriptions. Its prevention measure is “Measure ingress rate, queue depth, drop rate and end-to-end sample latency with capacity alerts”.

C:

This routine guards against another mechanism: webhooks are asynchronous network events; integrity, delivery acknowledgements and idempotent processing are separate reliability needs. The recurring exposure in the current case is: streaming telemetry pipelines have collectors, transports, ingestion queues and storage capacity that can fail independently of device subscriptions. The matching preventive check is “Measure ingress rate, queue depth, drop rate and end-to-end sample latency with capacity alerts”.

D:

The suggested review tracks a different technical risk: pyATS can learn and compare device operational state to detect unintended network effects beyond text config diffs. Here the sustained control must address: streaming telemetry pipelines have collectors, transports, ingestion queues and storage capacity that can fail independently of device subscriptions. Choose “Measure ingress rate, queue depth, drop rate and end-to-end sample latency with capacity alerts”.

Question 261

During a production change postcheck at fictional Marble Bay Software, the change record states: A network automation service connects to an API by IP address while the new certificate only contains its DNS service name. What underlying technical distinction accounts for this failure?

  1. Modern TLS clients validate the connection name against certificate subject alternative names, not merely that a CA issued the cert.
  2. Hardcoded secrets create persistent exposure and excessive authority; runtime secret retrieval limits both lifetime and access scope.
  3. HTTP 401 generally signals missing or invalid authentication while 403 indicates access denied to an authenticated request.
  4. Postdeployment validation compares expected invariants and intended deltas, not every volatile or purposely changed value.

Explanation

Correct Answer

A:

Modern TLS clients validate the connection name against certificate subject alternative names, not merely that a CA issued the cert. The corresponding repair is: Use an approved DNS endpoint covered by the certificate SAN or reissue a certificate with correct service identities. Acceptance should show: TLS validation succeeds for the intended hostname and fails for unexpected names without disabling verification. Applied here, the relevant facts are: A network automation service connects to an API by IP address while the new certificate only contains its DNS service name. The question asks what underlying technical distinction accounts for this failure.

Incorrect Answers

B:

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: Use an approved DNS endpoint covered by the certificate SAN or reissue a certificate with correct service identities. The two mechanisms should not be conflated.

C:

The corresponding repair is: Classify authentication failures and authorization denials separately, then correct token validity or RBAC scope accordingly. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Use an approved DNS endpoint covered by the certificate SAN or reissue a certificate with correct service identities.

D:

The offered statement is true for this other mechanism: The corresponding repair is: Write semantic pyATS assertions that permit the approved intended change and reject unrelated regressions. It does not explain the facts described here, which follow from: The corresponding repair is: Use an approved DNS endpoint covered by the certificate SAN or reissue a certificate with correct service identities.

Question 262

At fictional Sunrise Aeronautics, during an AI-assisted code review, the operator observes: An AI chat assistant translates free-text "fix routing" into unbounded commands rather than requiring a precise change proposal. What mechanism is most directly responsible for these symptoms?

  1. AI can accelerate low-risk preparation, but speed benefits must be balanced against hallucination, privacy and review obligations.
  2. Model fluency is not evidence of device capability; uncertain technical recommendations require explicit verification before action.
  3. Typed MCP tool schemas improve interoperability but server-side validation remains necessary even for a well-formed client call.
  4. LLMs are useful for language interpretation but the execution boundary should accept validated structured intents, not arbitrary prose.

Explanation

Correct Answer

D:

LLMs are useful for language interpretation but the execution boundary should accept validated structured intents, not arbitrary prose. The corresponding repair is: Convert user requests into a typed proposed intent with explicit targets, preconditions and a separate human-approved execution path. Acceptance should show: The assistant outputs a reviewable structured plan and no device mutation occurs until the scoped proposal is approved.

Incorrect Answers

A:

This principle describes a separate cause: The corresponding repair is: Use AI assistance for bounded drafts and test generation while assigning accountable reviewers and validating facts against approved sources. The reported condition is governed by: The corresponding repair is: Convert user requests into a typed proposed intent with explicit targets, preconditions and a separate human-approved execution path. The two mechanisms should not be conflated.

B:

The corresponding repair is: Require citation to a compatible authoritative reference and fail closed or escalate when command syntax or device version is uncertain. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Convert user requests into a typed proposed intent with explicit targets, preconditions and a separate human-approved execution path.

C:

The offered statement is true for this other mechanism: The corresponding repair is: Define typed, validated tool arguments with explicit device allowlists and reject invalid or unauthorized inputs at the server boundary. It does not explain the facts described here, which follow from: The corresponding repair is: Convert user requests into a typed proposed intent with explicit targets, preconditions and a separate human-approved execution path.

Question 263

At fictional Coastal Meadow Labs, during a production change postcheck, the operator observes: A BGP peering project legitimately changes neighbor count while a baseline assertion requires exact old inventory values. Which sustainable preventive control most directly avoids a recurrence?

  1. Monitor clock skew, log forwarding errors and collector persistence capacity.
  2. Rotate webhook credentials and monitor delivery latency, signature validation and replay protection.
  3. Monitor certificate expirations and trust-chain changes with automated predeployment verification.
  4. Review change-specific expected route and adjacency deltas alongside baseline safety invariants in test cases.

Explanation

Correct Answer

D:

Review change-specific expected route and adjacency deltas alongside baseline safety invariants in test cases. This prevents the recurrence because postdeployment validation compares expected invariants and intended deltas, not every volatile or purposely changed value. A matching immediate correction is: Write semantic pyATS assertions that permit the approved intended change and reject unrelated regressions.

Incorrect Answers

A:

The suggested review tracks a different technical risk: distributed troubleshooting requires durable transport and consistent time context; ephemeral local logs can be lost or misordered. Here the sustained control must address: postdeployment validation compares expected invariants and intended deltas, not every volatile or purposely changed value. Choose “Review change-specific expected route and adjacency deltas alongside baseline safety invariants in test cases”.

B:

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: postdeployment validation compares expected invariants and intended deltas, not every volatile or purposely changed value. Its prevention measure is “Review change-specific expected route and adjacency deltas alongside baseline safety invariants in test cases”.

C:

This routine guards against another mechanism: tLS server validation depends on trusted issuer chains and hostname identity; bypassing verification defeats server authentication. The recurring exposure in the current case is: postdeployment validation compares expected invariants and intended deltas, not every volatile or purposely changed value. The matching preventive check is “Review change-specific expected route and adjacency deltas alongside baseline safety invariants in test cases”.

Question 264

At fictional Westlake Biomedicine, an acceptance review of a FastMCP security review finds: An AI assistant suggests that a particular VLAN is unused, but it bases the claim on incomplete cached controller telemetry. What mechanism is most directly responsible for these symptoms?

  1. Tool results are untrusted external input; unrestricted outbound connectivity turns an injected instruction into a data-exfiltration path.
  2. AI recommendations are hypotheses requiring external ground truth; absent evidence is not proof of a network condition.
  3. AI can accelerate low-risk preparation, but speed benefits must be balanced against hallucination, privacy and review obligations.
  4. The model is not a reliable security principal; tool identities and server-side authorization bound the damage of agent errors.

Explanation

Correct Answer

B:

AI recommendations are hypotheses requiring external ground truth; absent evidence is not proof of a network condition. The corresponding repair is: Check AI conclusions against fresh independent device and controller evidence with explicit freshness and confidence rules. Acceptance should show: The validation crosschecks observed interface or VLAN state before accepting a proposed operation and flags missing telemetry as uncertainty.

Incorrect Answers

A:

The offered statement is true for this other mechanism: The corresponding repair is: Restrict tool egress to approved destinations and never grant untrusted retrieved text authority to choose exfiltration endpoints. It does not explain the facts described here, which follow from: The corresponding repair is: Check AI conclusions against fresh independent device and controller evidence with explicit freshness and confidence rules.

C:

The corresponding repair is: Use AI assistance for bounded drafts and test generation while assigning accountable reviewers and validating facts against approved sources. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Check AI conclusions against fresh independent device and controller evidence with explicit freshness and confidence rules.

D:

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: Check AI conclusions against fresh independent device and controller evidence with explicit freshness and confidence rules.

Question 265

While investigating a reproducible simulation for fictional Windward Maritime, the team reports: A team wants one traceable release change from a noisy experiment branch, but a standard merge preserves temporary debugging commits in main history. What underlying technical distinction accounts for this failure?

  1. A squash merge consolidates branch changes into a new commit, simplifying target history without preserving each source commit as a separate mainline entry.
  2. Unbounded dependency upgrades can introduce incompatible APIs and nondeterministic CI failures even when repository code is unchanged.
  3. Simulation usefulness depends on modeled network dependencies; an incomplete topology cannot validate omitted behaviors.
  4. YANG defines node hierarchy, namespaces, list keys and data types; conforming JSON must preserve that structure.

Explanation

Correct Answer

A:

A squash merge consolidates branch changes into a new commit, simplifying target history without preserving each source commit as a separate mainline entry. The corresponding repair is: Use an approved squash merge to combine reviewed feature changes into one commit while preserving the final content. Acceptance should show: The protected target branch contains one reviewed release commit whose diff matches the approved feature changes. Applied here, the relevant facts are: A team wants one traceable release change from a noisy experiment branch, but a standard merge preserves temporary debugging commits in main history. The question asks what underlying technical distinction accounts for this failure.

Incorrect Answers

B:

The corresponding repair is: Pin compatible build tool and package versions, update the lockfile and test upgrades in a separate controlled pipeline. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Use an approved squash merge to combine reviewed feature changes into one commit while preserving the final content.

C:

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 an approved squash merge to combine reviewed feature changes into one commit while preserving the final content.

D:

This principle describes a separate cause: The corresponding repair is: Construct JSON using the published YANG container hierarchy, qualified node names and correct value types. The reported condition is governed by: The corresponding repair is: Use an approved squash merge to combine reviewed feature changes into one commit while preserving the final content. The two mechanisms should not be conflated.

Question 266

During a source-of-truth integration at fictional Violet Ridge Resorts, the change record states: A network automation release branch merges conflicting inventory files and a hurried commit leaves both incompatible configuration blocks in place. Which sustainable preventive control most directly avoids a recurrence?

  1. Control source updates through review and schedule automated drift detection after deployment.
  2. Forbid destructive reset on shared branches and require review of soft, mixed and hard reset effects.
  3. Require merge-request review and parse or lint validation after conflicts in network automation files.
  4. Record source commit IDs, test cross-branch compatibility and review cherry-pick conflict resolutions.

Explanation

Correct Answer

C:

Require merge-request review and parse or lint validation after conflicts in network automation files. This prevents the recurrence because git cannot automatically reconcile overlapping divergent edits; a human or reviewed tool must choose the resulting content before merge completion. A matching immediate correction is: Resolve the conflicting lines deliberately against the approved desired network state, run validation, then commit the merged result.

Incorrect Answers

A:

The suggested review tracks a different technical risk: a reliable source-of-truth workflow separates approved intent from observed device state and defines how changes flow between them. Here the sustained control must address: git cannot automatically reconcile overlapping divergent edits; a human or reviewed tool must choose the resulting content before merge completion. Choose “Require merge-request review and parse or lint validation after conflicts in network automation files”.

B:

That safeguard is relevant to: git reset moves HEAD and optionally the index and worktree, making it suitable for carefully revising unpublished local history. The current failure instead follows from: git cannot automatically reconcile overlapping divergent edits; a human or reviewed tool must choose the resulting content before merge completion. Its prevention measure is “Require merge-request review and parse or lint validation after conflicts in network automation files”.

D:

The suggested review tracks a different technical risk: git cherry-pick applies the change introduced by selected commit(s) onto the current branch, creating new history in that branch. Here the sustained control must address: git cannot automatically reconcile overlapping divergent edits; a human or reviewed tool must choose the resulting content before merge completion. Choose “Require merge-request review and parse or lint validation after conflicts in network automation files”.

Question 267

At fictional Coastal Meadow Labs, during a production change postcheck, the operator observes: A network rollback reports a timeout, but earlier job logs clearly show the wrong controller endpoint was configured. Which result most directly verifies that the proposed correction worked?

  1. A timeline of stage logs identifies the first failing API or schema operation and confirms the targeted repair removes it.
  2. Load tests show telemetry consumers keeping up with target throughput or explicitly signaling lost samples without presenting false continuity.
  3. Centralized logs survive worker replacement and carry timestamps that correlate with device events within the accepted skew.
  4. Permission checks and artifact scans show no exposed private keys, while the service presents the renewed trusted certificate.

Explanation

Correct Answer

A:

A timeline of stage logs identifies the first failing API or schema operation and confirms the targeted repair removes it. 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. It checks the technical distinction: Downstream error messages can reflect cascaded failures; causality is established by correlating the earlier specific event and affected resource.

Incorrect Answers

B:

This alternative is a response to another technical cause: This directly verifies the related correction: Introduce bounded buffering, backpressure monitoring and horizontal ingestion capacity with visible gap or loss reporting. The reported case instead depends on: 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 action that directly addresses it is “A timeline of stage logs identifies the first failing API or schema operation and confirms the targeted repair removes it”.

C:

The proposed action belongs to the mechanism: This directly verifies the related correction: Synchronize clocks and ship logs to a durable centralized destination with appropriate secure, reliable transport. Here the stated fault follows a different mechanism: 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 corrective choice is “A timeline of stage logs identifies the first failing API or schema operation and confirms the targeted repair removes it”.

D:

The offered action targets: This directly verifies the related correction: Generate and store private keys in restricted secret systems and deploy only to the authorized TLS termination endpoint. The case facts point instead to: 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. Implement “A timeline of stage logs identifies the first failing API or schema operation and confirms the targeted repair removes it” to address that specific condition.

Question 268

During an AI recommendation accuracy study at fictional Amberlight Energy, the change record states: An automation team needs to let a network assistant query inventory, but its MCP server returns entire unrestricted controller API objects. Which explanation best matches the actual broken dependency?

  1. Generative systems can propose plausible-looking but incorrect commands; independent executable validation is required for safe infrastructure changes.
  2. An MCP server publishes structured tools and resources to clients; safe network use requires explicit least-privilege tool definitions.
  3. AI can accelerate low-risk preparation, but speed benefits must be balanced against hallucination, privacy and review obligations.
  4. AI recommendations are hypotheses requiring external ground truth; absent evidence is not proof of a network condition.

Explanation

Correct Answer

B:

An MCP server publishes structured tools and resources to clients; safe network use requires explicit least-privilege tool definitions. The corresponding repair is: Expose narrowly scoped typed read-only FastMCP tools for approved device and status fields with controlled access. Acceptance should show: A tool listing shows bounded operations and calls return only authorized network telemetry without configuration mutations.

Incorrect Answers

A:

This alternative is a response to another technical cause: The corresponding repair is: Subject AI-suggested changes to schema and unit tests, simulated network execution, policy checks and human change approval. The reported case instead depends on: The corresponding repair is: Expose narrowly scoped typed read-only FastMCP tools for approved device and status fields with controlled access. The action that directly addresses it is “An MCP server publishes structured tools and resources to clients; safe network use requires explicit least-privilege tool definitions”.

C:

The offered action targets: The corresponding repair is: Use AI assistance for bounded drafts and test generation while assigning accountable reviewers and validating facts against approved sources. The case facts point instead to: The corresponding repair is: Expose narrowly scoped typed read-only FastMCP tools for approved device and status fields with controlled access. Implement “An MCP server publishes structured tools and resources to clients; safe network use requires explicit least-privilege tool definitions” to address that specific condition.

D:

This alternative is a response to another technical cause: The corresponding repair is: Check AI conclusions against fresh independent device and controller evidence with explicit freshness and confidence rules. The reported case instead depends on: The corresponding repair is: Expose narrowly scoped typed read-only FastMCP tools for approved device and status fields with controlled access. The action that directly addresses it is “An MCP server publishes structured tools and resources to clients; safe network use requires explicit least-privilege tool definitions”.

Question 269

While investigating a network policy migration for fictional Cedarbridge Care Systems, the team reports: A Python script retries a POST creating a network object after an ambiguous timeout and creates a duplicate because the first request already succeeded. What should the engineer change first to resolve this specific issue?

  1. Before retrying a potentially non-idempotent change, check resulting resource state or use a supported idempotency or operation key.
  2. Replace non-idempotent shell appends with the platform-aware Ansible network configuration module and explicit desired interface state.
  3. Move credentials into a protected secret store or Ansible Vault and suppress sensitive task output while keeping access narrowly scoped.
  4. Notify a handler only when the associated configuration task reports a real change, and apply the restart once if necessary.

Explanation

Correct Answer

A:

Before retrying a potentially non-idempotent change, check resulting resource state or use a supported idempotency or operation key. This addresses the problem because a network transport timeout does not prove server-side failure; blind retries of non-idempotent operations can duplicate effects. Confirm success using: An induced response-loss test yields one intended network object or operation and records its final state without duplicate changes.

Incorrect Answers

B:

The offered action targets: ansible's desired-state-aware network modules compare declared configuration with device state before determining required changes. The case facts point instead to: a network transport timeout does not prove server-side failure; blind retries of non-idempotent operations can duplicate effects. Implement “Before retrying a potentially non-idempotent change, check resulting resource state or use a supported idempotency or operation key” to address that specific condition.

C:

This alternative is a response to another technical cause: automation credentials need confidentiality at rest and in output; inventory convenience does not justify committing secrets. The reported case instead depends on: a network transport timeout does not prove server-side failure; blind retries of non-idempotent operations can duplicate effects. The action that directly addresses it is “Before retrying a potentially non-idempotent change, check resulting resource state or use a supported idempotency or operation key”.

D:

The proposed action belongs to the mechanism: ansible handlers are triggered by changed tasks and coalesce notifications, separating configuration checks from disruptive service actions. Here the stated fault follows a different mechanism: a network transport timeout does not prove server-side failure; blind retries of non-idempotent operations can duplicate effects. The corrective choice is “Before retrying a potentially non-idempotent change, check resulting resource state or use a supported idempotency or operation key”.

Question 270

While investigating an inventory reconciliation for fictional Thornwick Health Trust, the team reports: A network provisioning system assumes every device family exposes identical Terraform provider resources and cannot fulfill a mixed-platform request. What ongoing engineering assurance should follow the successful fix?

  1. Design resource-state reconciliation and safe retry policies for all create and job-submission requests.
  2. Require validated backups, staged batches and executable rollback procedures in approved network playbooks.
  3. Record per-platform model support and gate model-specific deploy steps on device capability checks.
  4. Maintain a tested platform compatibility matrix and versioned adapter contracts for each device family.

Explanation

Correct Answer

D:

Maintain a tested platform compatibility matrix and versioned adapter contracts for each device family. This prevents the recurrence because cross-platform automation benefits from a shared intent model but must translate differences in native device APIs and models. A matching immediate correction is: Use inventory capability detection and platform-specific adapters behind a common validated intent model.

Incorrect Answers

A:

That safeguard is relevant to: a network transport timeout does not prove server-side failure; blind retries of non-idempotent operations can duplicate effects. The current failure instead follows from: cross-platform automation benefits from a shared intent model but must translate differences in native device APIs and models. Its prevention measure is “Maintain a tested platform compatibility matrix and versioned adapter contracts for each device family”.

B:

This routine guards against another mechanism: safe network automation separates preflight, controlled deployment, verification and recovery instead of assuming all endpoints will succeed. The recurring exposure in the current case is: cross-platform automation benefits from a shared intent model but must translate differences in native device APIs and models. The matching preventive check is “Maintain a tested platform compatibility matrix and versioned adapter contracts for each device family”.

C:

The suggested review tracks a different technical risk: model-driven APIs are available only for modules and revisions implemented by the device software, not by the client library alone. Here the sustained control must address: cross-platform automation benefits from a shared intent model but must translate differences in native device APIs and models. Choose “Maintain a tested platform compatibility matrix and versioned adapter contracts for each device family”.