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 28

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”.

Question 271

At fictional Marble Bay Software, an acceptance review of an automation service security audit finds: A GitLab network apply fails, and the team examines the final generic nonzero exit message rather than the earlier invalid YANG schema traceback. What mechanism is most directly responsible for these symptoms?

  1. Distributed troubleshooting requires durable transport and consistent time context; ephemeral local logs can be lost or misordered.
  2. Hardcoded secrets create persistent exposure and excessive authority; runtime secret retrieval limits both lifetime and access scope.
  3. Downstream error messages can reflect cascaded failures; causality is established by correlating the earlier specific event and affected resource.
  4. Model-driven telemetry publishes structured device state using subscribed paths and collection modes rather than relying only on slow polling.

Explanation

Correct Answer

C:

Downstream error messages can reflect cascaded failures; causality is established by correlating the earlier specific event and affected resource. The corresponding repair is: Trace correlated event IDs and earliest causal errors through the pipeline instead of treating the final propagated exception as root cause. Acceptance should show: A timeline of stage logs identifies the first failing API or schema operation and confirms the targeted repair removes it.

Incorrect Answers

A:

This principle describes a separate cause: The corresponding repair is: Synchronize clocks and ship logs to a durable centralized destination with appropriate secure, reliable transport. The reported condition is governed by: The corresponding repair is: Trace correlated event IDs and earliest causal errors through the pipeline instead of treating the final propagated exception as root cause. The two mechanisms should not be conflated.

B:

The corresponding repair is: Inject short-lived narrowly scoped secrets at runtime from a managed vault and mask them in logs and build artifacts. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Trace correlated event IDs and earliest causal errors through the pipeline instead of treating the final propagated exception as root cause.

D:

This principle describes a separate cause: The corresponding repair is: Configure suitable model-driven telemetry subscriptions for the relevant paths at a collection interval appropriate to the signal. The reported condition is governed by: The corresponding repair is: Trace correlated event IDs and earliest causal errors through the pipeline instead of treating the final propagated exception as root cause. The two mechanisms should not be conflated.

Question 272

During a GitLab deployment pipeline rehearsal at fictional Seabright Learning, the change record states: A developer sends an interface configuration as a flat JSON object without the model container and module prefix expected by the RESTCONF endpoint. What acceptance check would prove the intended behavior was restored?

  1. A deliberately invalid network change blocks before deploy and a valid change reaches the deployment stage only after passing gates.
  2. The Compose deployment starts required backends and the worker reaches ready state even when a dependency starts slowly.
  3. The target branch retains an auditable inverse commit and the published history remains intact while behavior returns to the approved state.
  4. The payload validates against the YANG schema and the RESTCONF server accepts the exact intended interface resource.

Explanation

Correct Answer

D:

The payload validates against the YANG schema and the RESTCONF server accepts the exact intended interface resource. This directly verifies the related correction: Construct JSON using the published YANG container hierarchy, qualified node names and correct value types. It checks the technical distinction: YANG defines node hierarchy, namespaces, list keys and data types; conforming JSON must preserve that structure.

Incorrect Answers

A:

The alternative verifies a different condition: This directly verifies the related correction: Make deployment depend on successful prevalidation jobs for schema, policy, simulation and approval checks. The current case instead depends on: This directly verifies the related correction: Construct JSON using the published YANG container hierarchy, qualified node names and correct value types. Confirm that “The payload validates against the YANG schema and the RESTCONF server accepts the exact intended interface resource”.

B:

That test belongs to another control with this basis: This directly verifies the related correction: Define service dependencies with appropriate health checks and resilient application startup or retry behavior. In the current case, the governing reason is: This directly verifies the related correction: Construct JSON using the published YANG container hierarchy, qualified node names and correct value types. The direct verification is “The payload validates against the YANG schema and the RESTCONF server accepts the exact intended interface resource”.

C:

This observation would test a different technical dependency: 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 issue is governed by: This directly verifies the related correction: Construct JSON using the published YANG container hierarchy, qualified node names and correct value types. Its decisive check is “The payload validates against the YANG schema and the RESTCONF server accepts the exact intended interface resource”.

Question 273

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

  1. Retain build/test artifacts and require root-cause notes rather than waiving failed predeployment checks.
  2. Maintain versioned representative CML topologies as mandatory preproduction test fixtures.
  3. Use reproducible lockfiles, container digest pinning and scheduled compatibility tests before updating dependencies.
  4. Set protected branch merge policies and link the squash commit to the reviewed change request.

Explanation

Correct Answer

D:

Set protected branch merge policies and link the squash commit to the reviewed change request. This prevents the recurrence because a squash merge consolidates branch changes into a new commit, simplifying target history without preserving each source commit as a separate mainline entry. A matching immediate correction is: Use an approved squash merge to combine reviewed feature changes into one commit while preserving the final content. 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 ongoing engineering assurance should follow the successful fix.

Incorrect Answers

A:

That safeguard is relevant to: a GitLab pipeline exit code identifies failure, while job logs and test artifacts reveal the specific causal stage and assertion. The current failure instead follows from: a squash merge consolidates branch changes into a new commit, simplifying target history without preserving each source commit as a separate mainline entry. Its prevention measure is “Set protected branch merge policies and link the squash commit to the reviewed change request”.

B:

This routine guards against another mechanism: cML supports topology-based device and protocol simulation for safe early integration tests without touching live infrastructure. The recurring exposure in the current case is: a squash merge consolidates branch changes into a new commit, simplifying target history without preserving each source commit as a separate mainline entry. The matching preventive check is “Set protected branch merge policies and link the squash commit to the reviewed change request”.

C:

The suggested review tracks a different technical risk: unbounded dependency upgrades can introduce incompatible APIs and nondeterministic CI failures even when repository code is unchanged. Here the sustained control must address: a squash merge consolidates branch changes into a new commit, simplifying target history without preserving each source commit as a separate mainline entry. Choose “Set protected branch merge policies and link the squash commit to the reviewed change request”.

Question 274

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. What should the engineer change first to resolve this specific issue?

  1. Move credentials into a protected secret store or Ansible Vault and suppress sensitive task output while keeping access narrowly scoped.
  2. Replace non-idempotent shell appends with the platform-aware Ansible network configuration module and explicit desired interface state.
  3. Use inventory capability detection and platform-specific adapters behind a common validated intent model.
  4. Read intended configuration and runtime operational YANG data from their appropriate modeled resources, and write only configurable leaves.

Explanation

Correct Answer

D:

Read intended configuration and runtime operational YANG data from their appropriate modeled resources, and write only configurable leaves. This addresses the problem because yANG distinguishes configuration intent from read-only operational state; successful config writes do not establish runtime protocol health. Confirm success using: The verification compares the authorized modeled configuration with separate operational neighbor or counter results after deployment.

Incorrect Answers

A:

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: yANG distinguishes configuration intent from read-only operational state; successful config writes do not establish runtime protocol health. The action that directly addresses it is “Read intended configuration and runtime operational YANG data from their appropriate modeled resources, and write only configurable leaves”.

B:

The proposed action belongs to the mechanism: ansible's desired-state-aware network modules compare declared configuration with device state before determining required changes. Here the stated fault follows a different mechanism: yANG distinguishes configuration intent from read-only operational state; successful config writes do not establish runtime protocol health. The corrective choice is “Read intended configuration and runtime operational YANG data from their appropriate modeled resources, and write only configurable leaves”.

C:

The offered action targets: cross-platform automation benefits from a shared intent model but must translate differences in native device APIs and models. The case facts point instead to: yANG distinguishes configuration intent from read-only operational state; successful config writes do not establish runtime protocol health. Implement “Read intended configuration and runtime operational YANG data from their appropriate modeled resources, and write only configurable leaves” to address that specific condition.

Question 275

During a source-of-truth integration at fictional Violet Ridge Resorts, the change record states: A pipeline status shows red due to a failed inventory schema validation stage, yet the automation team assumes the controller was unreachable. What ongoing engineering assurance should follow the successful fix?

  1. Review topology fidelity against production design and include adverse link or neighbor failures in CML tests.
  2. Enforce unique device IDs, provenance and reconciliation reports for source-of-truth integrations.
  3. Retain build/test artifacts and require root-cause notes rather than waiving failed predeployment checks.
  4. Review Compose network boundaries and port mappings with security tests before any deployment.

Explanation

Correct Answer

C:

Retain build/test artifacts and require root-cause notes rather than waiving failed predeployment checks. This prevents the recurrence because a GitLab pipeline exit code identifies failure, while job logs and test artifacts reveal the specific causal stage and assertion. A matching immediate correction is: Inspect the failed job logs and classify whether build, dependency, test or environment validation failed before making a targeted fix.

Incorrect Answers

A:

The suggested review tracks a different technical risk: simulation usefulness depends on modeled network dependencies; an incomplete topology cannot validate omitted behaviors. Here the sustained control must address: a GitLab pipeline exit code identifies failure, while job logs and test artifacts reveal the specific causal stage and assertion. Choose “Retain build/test artifacts and require root-cause notes rather than waiving failed predeployment checks”.

B:

That safeguard is relevant to: a source of truth provides desired canonical inventory, but consumers must resolve identity correctly and reconcile discrepancies. The current failure instead follows from: a GitLab pipeline exit code identifies failure, while job logs and test artifacts reveal the specific causal stage and assertion. Its prevention measure is “Retain build/test artifacts and require root-cause notes rather than waiving failed predeployment checks”.

D:

The suggested review tracks a different technical risk: compose networks govern container service reachability, while host port publishing determines external exposure. Here the sustained control must address: a GitLab pipeline exit code identifies failure, while job logs and test artifacts reveal the specific causal stage and assertion. Choose “Retain build/test artifacts and require root-cause notes rather than waiving failed predeployment checks”.

Question 276

While investigating a telemetry quality investigation for fictional Sable Valley Power, the team reports: A pyATS test script uses a command parser for an unsupported IOS XE release and reports a missing field as a network outage. Which control best prevents this particular failure from recurring?

  1. Maintain tested parser/device version matrices and fail clearly when collection contracts change.
  2. Monitor certificate expirations and trust-chain changes with automated predeployment verification.
  3. Measure ingress rate, queue depth, drop rate and end-to-end sample latency with capacity alerts.
  4. Monitor clock skew, log forwarding errors and collector persistence capacity.

Explanation

Correct Answer

A:

Maintain tested parser/device version matrices and fail clearly when collection contracts change. This prevents the recurrence because model-driven test tools depend on supported device schemas and parser versions; missing parsed data is not proof of missing network function. A matching immediate correction is: Validate parser and platform compatibility and distinguish collection or parsing errors from actual network-state assertion failures. Applied here, the relevant facts are: A pyATS test script uses a command parser for an unsupported IOS XE release and reports a missing field as a network outage. The question asks which control best prevents this particular failure from recurring.

Incorrect Answers

B:

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: model-driven test tools depend on supported device schemas and parser versions; missing parsed data is not proof of missing network function. The matching preventive check is “Maintain tested parser/device version matrices and fail clearly when collection contracts change”.

C:

The suggested review tracks a different technical risk: streaming telemetry pipelines have collectors, transports, ingestion queues and storage capacity that can fail independently of device subscriptions. Here the sustained control must address: model-driven test tools depend on supported device schemas and parser versions; missing parsed data is not proof of missing network function. Choose “Maintain tested parser/device version matrices and fail clearly when collection contracts change”.

D:

That safeguard is relevant to: distributed troubleshooting requires durable transport and consistent time context; ephemeral local logs can be lost or misordered. The current failure instead follows from: model-driven test tools depend on supported device schemas and parser versions; missing parsed data is not proof of missing network function. Its prevention measure is “Maintain tested parser/device version matrices and fail clearly when collection contracts change”.

Question 277

During a conversational network agent pilot at fictional Westlake Biomedicine, the change record states: An AI network diagnostic tool receives a malicious API description instructing it to send secrets to an external webhook. Which targeted correction best addresses the network automation failure?

  1. Return structured success and error states with source timestamps and bounded API timeouts rather than silently substituting empty values.
  2. Use AI assistance for bounded drafts and test generation while assigning accountable reviewers and validating facts against approved sources.
  3. Expose narrowly scoped typed read-only FastMCP tools for approved device and status fields with controlled access.
  4. Restrict tool egress to approved destinations and never grant untrusted retrieved text authority to choose exfiltration endpoints.

Explanation

Correct Answer

D:

Restrict tool egress to approved destinations and never grant untrusted retrieved text authority to choose exfiltration endpoints. This addresses the problem because tool results are untrusted external input; unrestricted outbound connectivity turns an injected instruction into a data-exfiltration path. Confirm success using: A simulated malicious tool response cannot trigger outbound requests to unapproved destinations or reveal hidden credentials.

Incorrect Answers

A:

This principle describes a separate cause: tool wrappers must preserve the meaning of missing, stale and failed data for the consumer agent. The reported condition is governed by: tool results are untrusted external input; unrestricted outbound connectivity turns an injected instruction into a data-exfiltration path. The two mechanisms should not be conflated.

B:

aI can accelerate low-risk preparation, but speed benefits must be balanced against hallucination, privacy and review obligations. That explanation applies to a different technical failure. Here the controlling principle is: tool results are untrusted external input; unrestricted outbound connectivity turns an injected instruction into a data-exfiltration path.

C:

The offered statement is true for this other mechanism: an MCP server publishes structured tools and resources to clients; safe network use requires explicit least-privilege tool definitions. It does not explain the facts described here, which follow from: tool results are untrusted external input; unrestricted outbound connectivity turns an injected instruction into a data-exfiltration path.

Question 278

During a GitLab deployment pipeline rehearsal at fictional Seabright Learning, the change record states: A GitLab deployment job compiles automation files on the production runner using a different dependency set than unit tests used. What should the engineer change first to resolve this specific issue?

  1. Produce a reproducible versioned build artifact in the build stage and use that immutable artifact for subsequent validation and deployment.
  2. Use an approved squash merge to combine reviewed feature changes into one commit while preserving the final content.
  3. Restore only the specifically reviewed historical file from the desired revision instead of replacing the whole branch state.
  4. Unstage the unintended file with an index-only reset or equivalent restore-staged operation, leaving the worktree intact.

Explanation

Correct Answer

A:

Produce a reproducible versioned build artifact in the build stage and use that immutable artifact for subsequent validation and deployment. This addresses the problem because a CI build stage turns source and fixed dependencies into a traceable deployment input used by later stages. Confirm success using: The deployed artifact checksum matches the tested build artifact and the pipeline records its originating commit.

Incorrect Answers

B:

The offered action targets: a squash merge consolidates branch changes into a new commit, simplifying target history without preserving each source commit as a separate mainline entry. The case facts point instead to: a CI build stage turns source and fixed dependencies into a traceable deployment input used by later stages. Implement “Produce a reproducible versioned build artifact in the build stage and use that immutable artifact for subsequent validation and deployment” to address that specific condition.

C:

This alternative is a response to another technical cause: git can retrieve individual tracked paths from a commit; selecting file scope avoids broad branch-level rollback. The reported case instead depends on: a CI build stage turns source and fixed dependencies into a traceable deployment input used by later stages. The action that directly addresses it is “Produce a reproducible versioned build artifact in the build stage and use that immutable artifact for subsequent validation and deployment”.

D:

The proposed action belongs to the mechanism: the Git index is the staging area and can be changed independently of the working tree by suitable reset modes. Here the stated fault follows a different mechanism: a CI build stage turns source and fixed dependencies into a traceable deployment input used by later stages. The corrective choice is “Produce a reproducible versioned build artifact in the build stage and use that immutable artifact for subsequent validation and deployment”.

Question 279

At fictional Sunrise Aeronautics, during an AI-assisted code review, the operator observes: A Python FastMCP service exposes a broad execute-command tool to an agent that only needs interface status snapshots. Which sustainable preventive control most directly avoids a recurrence?

  1. Track evidence freshness and require independent observed-state corroboration for high-impact AI advice.
  2. Review FastMCP tool schemas, allowed methods, output redaction and per-device access before agent connection.
  3. Require provenance review, software composition analysis and approved dependencies for generated network automation components.
  4. Mark generated code for extra negative tests and prohibit bypassing deployment gates based on model confidence.

Explanation

Correct Answer

B:

Review FastMCP tool schemas, allowed methods, output redaction and per-device access before agent connection. This prevents the recurrence because an MCP server publishes structured tools and resources to clients; safe network use requires explicit least-privilege tool definitions. A matching immediate correction is: Expose narrowly scoped typed read-only FastMCP tools for approved device and status fields with controlled access.

Incorrect Answers

A:

That safeguard is relevant to: aI recommendations are hypotheses requiring external ground truth; absent evidence is not proof of a network condition. The current failure instead follows from: an MCP server publishes structured tools and resources to clients; safe network use requires explicit least-privilege tool definitions. Its prevention measure is “Review FastMCP tool schemas, allowed methods, output redaction and per-device access before agent connection”.

C:

The suggested review tracks a different technical risk: aI-generated code may embed third-party patterns or dependencies; tool output is not automatically cleared of licensing obligations. Here the sustained control must address: an MCP server publishes structured tools and resources to clients; safe network use requires explicit least-privilege tool definitions. Choose “Review FastMCP tool schemas, allowed methods, output redaction and per-device access before agent connection”.

D:

That safeguard is relevant to: generative systems can propose plausible-looking but incorrect commands; independent executable validation is required for safe infrastructure changes. The current failure instead follows from: an MCP server publishes structured tools and resources to clients; safe network use requires explicit least-privilege tool definitions. Its prevention measure is “Review FastMCP tool schemas, allowed methods, output redaction and per-device access before agent connection”.

Question 280

While investigating a source-of-truth integration for fictional Willowfield Hospitality, the team reports: A lab test succeeds only because the CML topology omits an actual branch transit link where routing loops occur. What ongoing engineering assurance should follow the successful fix?

  1. Generate payload fixtures from reviewed YANG modules and test schema validation before any live update.
  2. Require path-limited recovery commands and postrestore diffs for surgical automation-file reversions.
  3. Add dependency-impact review and target-branch CI validation to hotfix backport procedures.
  4. Review topology fidelity against production design and include adverse link or neighbor failures in CML tests.

Explanation

Correct Answer

D:

Review topology fidelity against production design and include adverse link or neighbor failures in CML tests. This prevents the recurrence because simulation usefulness depends on modeled network dependencies; an incomplete topology cannot validate omitted behaviors. A matching immediate correction is: Model the relevant links, routing peers and failure cases in CML rather than only a minimal happy-path device.

Incorrect Answers

A:

This routine guards against another mechanism: yANG defines node hierarchy, namespaces, list keys and data types; conforming JSON must preserve that structure. The recurring exposure in the current case is: simulation usefulness depends on modeled network dependencies; an incomplete topology cannot validate omitted behaviors. The matching preventive check is “Review topology fidelity against production design and include adverse link or neighbor failures in CML tests”.

B:

The suggested review tracks a different technical risk: git can retrieve individual tracked paths from a commit; selecting file scope avoids broad branch-level rollback. Here the sustained control must address: simulation usefulness depends on modeled network dependencies; an incomplete topology cannot validate omitted behaviors. Choose “Review topology fidelity against production design and include adverse link or neighbor failures in CML tests”.

C:

That safeguard is relevant to: a cherry-picked commit does not automatically bring every ancestor or dependent change from its original branch. The current failure instead follows from: simulation usefulness depends on modeled network dependencies; an incomplete topology cannot validate omitted behaviors. Its prevention measure is “Review topology fidelity against production design and include adverse link or neighbor failures in CML tests”.