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 60

Question 590

While investigating an AI recommendation accuracy study for fictional Sunrise Aeronautics, the team reports: An AI assistant recommends deleting the running VLAN configuration to fix an unrelated RESTCONF authentication failure. What is the appropriate response to this network automation condition?

  1. Subject AI-suggested changes to schema and unit tests, simulated network execution, policy checks and human change approval.
  2. Expose narrowly scoped typed read-only FastMCP tools for approved device and status fields with controlled access.
  3. Issue read-only scoped identity credentials for diagnostic agents and place separate approval boundaries around mutating tools.
  4. Ground actionable recommendations in trusted versioned technical references and reject unsupported or conflicting retrieved claims.

Explanation

Correct Answer

A:

Subject AI-suggested changes to schema and unit tests, simulated network execution, policy checks and human change approval. This addresses the problem because generative systems can propose plausible-looking but incorrect commands; independent executable validation is required for safe infrastructure changes. Confirm success using: Invalid module parameters or destructive unrelated changes fail the predeployment gates and never reach production devices. Applied here, the relevant facts are: An AI assistant recommends deleting the running VLAN configuration to fix an unrelated RESTCONF authentication failure. The question asks what is the appropriate response to this network automation condition.

Incorrect Answers

B:

The offered action targets: an MCP server publishes structured tools and resources to clients; safe network use requires explicit least-privilege tool definitions. The case facts point instead to: generative systems can propose plausible-looking but incorrect commands; independent executable validation is required for safe infrastructure changes. Implement “Subject AI-suggested changes to schema and unit tests, simulated network execution, policy checks and human change approval” to address that specific condition.

C:

This alternative is a response to another technical cause: the model is not a reliable security principal; tool identities and server-side authorization bound the damage of agent errors. The reported case instead depends on: generative systems can propose plausible-looking but incorrect commands; independent executable validation is required for safe infrastructure changes. The action that directly addresses it is “Subject AI-suggested changes to schema and unit tests, simulated network execution, policy checks and human change approval”.

D:

The proposed action belongs to the mechanism: retrieval-augmented systems can inherit false or hostile data; source quality and technical cross-checks must precede action. Here the stated fault follows a different mechanism: generative systems can propose plausible-looking but incorrect commands; independent executable validation is required for safe infrastructure changes. The corrective choice is “Subject AI-suggested changes to schema and unit tests, simulated network execution, policy checks and human change approval”.

Question 591

At fictional Westlake Biomedicine, an acceptance review of a FastMCP security review finds: A team forbids all AI support for routine test scaffolding even though repetitive documentation work consumes scarce engineering time. Which observation would confirm that this exact failure is resolved?

  1. The workflow reduces draft effort yet records review and successful technical tests before any proposed config reaches deployment.
  2. A tool listing shows bounded operations and calls return only authorized network telemetry without configuration mutations.
  3. The assistant identifies missing version evidence and withholds unverified commands instead of fabricating supported APIs.
  4. Agent tool traces distinguish timeout, authorization and partial-data failures from genuine empty network results.

Explanation

Correct Answer

A:

The workflow reduces draft effort yet records review and successful technical tests before any proposed config reaches deployment. This directly verifies the related correction: Use AI assistance for bounded drafts and test generation while assigning accountable reviewers and validating facts against approved sources. It checks the technical distinction: AI can accelerate low-risk preparation, but speed benefits must be balanced against hallucination, privacy and review obligations. Applied here, the relevant facts are: A team forbids all AI support for routine test scaffolding even though repetitive documentation work consumes scarce engineering time. The question asks which observation would confirm that this exact failure is resolved.

Incorrect Answers

B:

This observation would test a different technical dependency: This directly verifies the related correction: Expose narrowly scoped typed read-only FastMCP tools for approved device and status fields with controlled access. The current issue is governed by: This directly verifies the related correction: Use AI assistance for bounded drafts and test generation while assigning accountable reviewers and validating facts against approved sources. Its decisive check is “The workflow reduces draft effort yet records review and successful technical tests before any proposed config reaches deployment”.

C:

The alternative verifies a different condition: 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. The current case instead depends on: This directly verifies the related correction: Use AI assistance for bounded drafts and test generation while assigning accountable reviewers and validating facts against approved sources. Confirm that “The workflow reduces draft effort yet records review and successful technical tests before any proposed config reaches deployment”.

D:

That test belongs to another control with this basis: 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. In the current case, the governing reason is: This directly verifies the related correction: Use AI assistance for bounded drafts and test generation while assigning accountable reviewers and validating facts against approved sources. The direct verification is “The workflow reduces draft effort yet records review and successful technical tests before any proposed config reaches deployment”.

Question 592

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. Which implementation action best meets the observed technical requirement?

  1. Inspect the failed job logs and classify whether build, dependency, test or environment validation failed before making a targeted fix.
  2. Use an appropriate local Git reset to move the branch pointer and rebuild the unpublished commit while protecting wanted working changes.
  3. Construct JSON using the published YANG container hierarchy, qualified node names and correct value types.
  4. Use stable authoritative device identifiers and reconcile observed inventory to the source-of-truth records before deployment.

Explanation

Correct Answer

A:

Inspect the failed job logs and classify whether build, dependency, test or environment validation failed before making a targeted fix. This addresses the problem because a GitLab pipeline exit code identifies failure, while job logs and test artifacts reveal the specific causal stage and assertion. Confirm success using: A repaired pipeline has a documented root cause and passes the originally failing test without bypassing safety gates. Applied here, the relevant facts are: A pipeline status shows red due to a failed inventory schema validation stage, yet the automation team assumes the controller was unreachable. The question asks which implementation action best meets the observed technical requirement.

Incorrect Answers

B:

The proposed action belongs to the mechanism: git reset moves HEAD and optionally the index and worktree, making it suitable for carefully revising unpublished local history. Here the stated fault follows a different mechanism: a GitLab pipeline exit code identifies failure, while job logs and test artifacts reveal the specific causal stage and assertion. The corrective choice is “Inspect the failed job logs and classify whether build, dependency, test or environment validation failed before making a targeted fix”.

C:

The offered action targets: yANG defines node hierarchy, namespaces, list keys and data types; conforming JSON must preserve that structure. The case facts point instead to: a GitLab pipeline exit code identifies failure, while job logs and test artifacts reveal the specific causal stage and assertion. Implement “Inspect the failed job logs and classify whether build, dependency, test or environment validation failed before making a targeted fix” to address that specific condition.

D:

This alternative is a response to another technical cause: a source of truth provides desired canonical inventory, but consumers must resolve identity correctly and reconcile discrepancies. The reported case instead depends on: a GitLab pipeline exit code identifies failure, while job logs and test artifacts reveal the specific causal stage and assertion. The action that directly addresses it is “Inspect the failed job logs and classify whether build, dependency, test or environment validation failed before making a targeted fix”.

Question 593

While investigating an AI recommendation accuracy study for fictional Sunrise Aeronautics, the team reports: A conversational network assistant is permitted to run a harmless ping but then automatically chains into an unapproved ACL modification. Which implementation action best meets the observed technical requirement?

  1. Separate read-only diagnostic tools from mutating tools and require an explicit scoped approval step before any privileged operation.
  2. Expose narrowly scoped typed read-only FastMCP tools for approved device and status fields with controlled access.
  3. Review generated code provenance, included dependencies and organizational IP policy before accepting it into the repository.
  4. Restrict tool egress to approved destinations and never grant untrusted retrieved text authority to choose exfiltration endpoints.

Explanation

Correct Answer

A:

Separate read-only diagnostic tools from mutating tools and require an explicit scoped approval step before any privileged operation. This addresses the problem because agent tool chaining can enlarge the blast radius of an ambiguous user instruction unless execution permissions are independently gated. Confirm success using: A conversational diagnostic completes safely without write access, and a proposed write remains pending until an authorized approver confirms. Applied here, the relevant facts are: A conversational network assistant is permitted to run a harmless ping but then automatically chains into an unapproved ACL modification. The question asks which implementation action best meets the observed technical requirement.

Incorrect Answers

B:

The offered action targets: an MCP server publishes structured tools and resources to clients; safe network use requires explicit least-privilege tool definitions. The case facts point instead to: agent tool chaining can enlarge the blast radius of an ambiguous user instruction unless execution permissions are independently gated. Implement “Separate read-only diagnostic tools from mutating tools and require an explicit scoped approval step before any privileged operation” to address that specific condition.

C:

This alternative is a response to another technical cause: aI-generated code may embed third-party patterns or dependencies; tool output is not automatically cleared of licensing obligations. The reported case instead depends on: agent tool chaining can enlarge the blast radius of an ambiguous user instruction unless execution permissions are independently gated. The action that directly addresses it is “Separate read-only diagnostic tools from mutating tools and require an explicit scoped approval step before any privileged operation”.

D:

The proposed action belongs to the mechanism: tool results are untrusted external input; unrestricted outbound connectivity turns an injected instruction into a data-exfiltration path. Here the stated fault follows a different mechanism: agent tool chaining can enlarge the blast radius of an ambiguous user instruction unless execution permissions are independently gated. The corrective choice is “Separate read-only diagnostic tools from mutating tools and require an explicit scoped approval step before any privileged operation”.

Question 594

At fictional Thornwick Health Trust, during a remote branch provisioning pilot, the operator observes: A temporary inventory update is built as a large Terraform module even though the required API operation is an ephemeral read-only query. What technical evidence should be required before closing this change?

  1. The design review shows the chosen approach fits the resource lifecycle, state ownership and change frequency without redundant infrastructure code.
  2. The imported resource maps to the intended live identifier and the reviewed plan does not attempt duplicate creation or replacement.
  3. The change record captures the final completed task status and verifies resulting network configuration rather than only the HTTP submission response.
  4. The second apply waits or fails safely on an active lock, and state reflects one consistent resource graph after the approved deployment.

Explanation

Correct Answer

A:

The design review shows the chosen approach fits the resource lifecycle, state ownership and change frequency without redundant infrastructure code. This directly verifies the related correction: Choose a supported declarative IaC framework for persistent desired configuration and targeted scripts for bounded imperative queries or integrations. It checks the technical distinction: Infrastructure as code, low-code workflows and custom software solve different state-lifecycle and integration needs.

Incorrect Answers

B:

This observation would test a different technical dependency: This directly verifies the related correction: Import the existing platform object into Terraform state, align its configuration and inspect a non-destructive plan. The current issue is governed by: This directly verifies the related correction: Choose a supported declarative IaC framework for persistent desired configuration and targeted scripts for bounded imperative queries or integrations. Its decisive check is “The design review shows the chosen approach fits the resource lifecycle, state ownership and change frequency without redundant infrastructure code”.

C:

The alternative verifies a different condition: This directly verifies the related correction: Poll the returned operation resource with bounded intervals and timeout until a terminal success or failure state is observed. The current case instead depends on: This directly verifies the related correction: Choose a supported declarative IaC framework for persistent desired configuration and targeted scripts for bounded imperative queries or integrations. Confirm that “The design review shows the chosen approach fits the resource lifecycle, state ownership and change frequency without redundant infrastructure code”.

D:

That test belongs to another control with this basis: This directly verifies the related correction: Configure a shared protected Terraform state backend with supported locking and serialize competing applies against the same state. In the current case, the governing reason is: This directly verifies the related correction: Choose a supported declarative IaC framework for persistent desired configuration and targeted scripts for bounded imperative queries or integrations. The direct verification is “The design review shows the chosen approach fits the resource lifecycle, state ownership and change frequency without redundant infrastructure code”.

Question 595

At fictional Violet Ridge Resorts, an acceptance review of a version-control hotfix finds: A Docker Compose stack places its internal database and externally reachable web API on an unrestricted shared network. What should the engineer change first to resolve this specific issue?

  1. Safely stash or commit unrelated work and check out the intended branch or detached revision in a clean worktree.
  2. Make deployment depend on successful prevalidation jobs for schema, policy, simulation and approval checks.
  3. Use purpose-specific networks and expose only the required listener ports while keeping backend services unexposed.
  4. Pin compatible build tool and package versions, update the lockfile and test upgrades in a separate controlled pipeline.

Explanation

Correct Answer

C:

Use purpose-specific networks and expose only the required listener ports while keeping backend services unexposed. This addresses the problem because compose networks govern container service reachability, while host port publishing determines external exposure. Confirm success using: Network inspection shows the internal service reachable only to authorized app containers and public bindings limited to the approved API.

Incorrect Answers

A:

This alternative is a response to another technical cause: git checkout can change branch and working-tree files; uncommitted modifications must be managed to avoid accidental mixing. The reported case instead depends on: compose networks govern container service reachability, while host port publishing determines external exposure. The action that directly addresses it is “Use purpose-specific networks and expose only the required listener ports while keeping backend services unexposed”.

B:

The proposed action belongs to the mechanism: prevalidation is a safety boundary before changing network state, separate from checks after a change completes. Here the stated fault follows a different mechanism: compose networks govern container service reachability, while host port publishing determines external exposure. The corrective choice is “Use purpose-specific networks and expose only the required listener ports while keeping backend services unexposed”.

D:

This alternative is a response to another technical cause: unbounded dependency upgrades can introduce incompatible APIs and nondeterministic CI failures even when repository code is unchanged. The reported case instead depends on: compose networks govern container service reachability, while host port publishing determines external exposure. The action that directly addresses it is “Use purpose-specific networks and expose only the required listener ports while keeping backend services unexposed”.

Question 596

At fictional Sable Valley Power, during a certificate renewal rehearsal, the operator observes: A telemetry dashboard polls SNMP every minute for a rapidly changing interface queue and fails to capture short congestion spikes. Which explanation best matches the actual broken dependency?

  1. Model-driven telemetry publishes structured device state using subscribed paths and collection modes rather than relying only on slow polling.
  2. Webhooks are asynchronous network events; integrity, delivery acknowledgements and idempotent processing are separate reliability needs.
  3. TLS server validation depends on trusted issuer chains and hostname identity; bypassing verification defeats server authentication.
  4. Untrusted input can cross command or configuration boundaries; validation and safe APIs prevent injection into privileged operations.

Explanation

Correct Answer

A:

Model-driven telemetry publishes structured device state using subscribed paths and collection modes rather than relying only on slow polling. The corresponding repair is: Configure suitable model-driven telemetry subscriptions for the relevant paths at a collection interval appropriate to the signal. Acceptance should show: The collector receives timestamped updates for the requested YANG paths and captures brief changes within its approved delay budget.

Incorrect Answers

B:

The offered action targets: The corresponding repair is: Authenticate webhook delivery and implement bounded retries with deduplication or delivery-state accounting. The case facts point instead to: The corresponding repair is: Configure suitable model-driven telemetry subscriptions for the relevant paths at a collection interval appropriate to the signal. Implement “Model-driven telemetry publishes structured device state using subscribed paths and collection modes rather than relying only on slow polling” to address that specific condition.

C:

This alternative is a response to another technical cause: The corresponding repair is: Install the validated issuing CA chain in client trust stores and verify endpoint identity rather than bypassing TLS checks. The reported case instead depends on: The corresponding repair is: Configure suitable model-driven telemetry subscriptions for the relevant paths at a collection interval appropriate to the signal. The action that directly addresses it is “Model-driven telemetry publishes structured device state using subscribed paths and collection modes rather than relying only on slow polling”.

D:

The proposed action belongs to the mechanism: The corresponding repair is: Use typed input schema validation, approved resource allowlists and safe library argument interfaces rather than shell concatenation. Here the stated fault follows a different mechanism: The corresponding repair is: Configure suitable model-driven telemetry subscriptions for the relevant paths at a collection interval appropriate to the signal. The corrective choice is “Model-driven telemetry publishes structured device state using subscribed paths and collection modes rather than relying only on slow polling”.

Question 597

During a source-of-truth integration at fictional Violet Ridge Resorts, the change record states: A GitLab job applies a network ACL and stops without confirming active data-plane connectivity for the newly allowed application. What mechanism is most directly responsible for these symptoms?

  1. A cherry-picked commit does not automatically bring every ancestor or dependent change from its original branch.
  2. Simulation usefulness depends on modeled network dependencies; an incomplete topology cannot validate omitted behaviors.
  3. Deployment command success is not the same as verified service success; operational checks must follow state changes.
  4. The Git index is the staging area and can be changed independently of the working tree by suitable reset modes.

Explanation

Correct Answer

C:

Deployment command success is not the same as verified service success; operational checks must follow state changes. The corresponding repair is: Run objective-based postdeployment checks and fail or roll back the change when observed network behavior contradicts intent. Acceptance should show: The postvalidation stage confirms routes, adjacency and connectivity or triggers the documented recovery workflow with evidence. Applied here, the relevant facts are: A GitLab job applies a network ACL and stops without confirming active data-plane connectivity for the newly allowed application. The question asks what mechanism is most directly responsible for these symptoms.

Incorrect Answers

A:

That test belongs to another control with this basis: The corresponding repair is: Identify the prerequisite commits and cherry-pick a minimal compatible sequence or adapt the patch for the target baseline. In the current case, the governing reason is: The corresponding repair is: Run objective-based postdeployment checks and fail or roll back the change when observed network behavior contradicts intent. The direct verification is “Deployment command success is not the same as verified service success; operational checks must follow state changes”.

B:

This observation would test a different technical dependency: The corresponding repair is: Model the relevant links, routing peers and failure cases in CML rather than only a minimal happy-path device. The current issue is governed by: The corresponding repair is: Run objective-based postdeployment checks and fail or roll back the change when observed network behavior contradicts intent. Its decisive check is “Deployment command success is not the same as verified service success; operational checks must follow state changes”.

D:

That test belongs to another control with this basis: The corresponding repair is: Unstage the unintended file with an index-only reset or equivalent restore-staged operation, leaving the worktree intact. In the current case, the governing reason is: The corresponding repair is: Run objective-based postdeployment checks and fail or roll back the change when observed network behavior contradicts intent. The direct verification is “Deployment command success is not the same as verified service success; operational checks must follow state changes”.

Question 598

During a production change postcheck at fictional Marble Bay Software, the change record states: Branch controllers send syslog with inconsistent clocks and the SOC cannot order a sequence of ACL policy events. Which observation would confirm that this exact failure is resolved?

  1. Centralized logs survive worker replacement and carry timestamps that correlate with device events within the accepted skew.
  2. A token rotation test succeeds without image rebuild, and repository, image and logs contain no recoverable credentials.
  3. pyATS comparison shows approved changed values while protected neighbors, interface counters or route counts remain within defined acceptance bounds.
  4. TLS validation succeeds for the intended hostname and fails for unexpected names without disabling verification.

Explanation

Correct Answer

A:

Centralized logs survive worker replacement and carry timestamps that correlate with device events within the accepted skew. This directly verifies the related correction: Synchronize clocks and ship logs to a durable centralized destination with appropriate secure, reliable transport. It checks the technical distinction: Distributed troubleshooting requires durable transport and consistent time context; ephemeral local logs can be lost or misordered.

Incorrect Answers

B:

The alternative verifies a different condition: This directly verifies the related correction: Inject short-lived narrowly scoped secrets at runtime from a managed vault and mask them in logs and build artifacts. The current case instead depends on: This directly verifies the related correction: Synchronize clocks and ship logs to a durable centralized destination with appropriate secure, reliable transport. Confirm that “Centralized logs survive worker replacement and carry timestamps that correlate with device events within the accepted skew”.

C:

That test belongs to another control with this basis: This directly verifies the related correction: Capture structured prechange operational state with pyATS, apply the change, then compare relevant postchange state and assert expected invariants. In the current case, the governing reason is: This directly verifies the related correction: Synchronize clocks and ship logs to a durable centralized destination with appropriate secure, reliable transport. The direct verification is “Centralized logs survive worker replacement and carry timestamps that correlate with device events within the accepted skew”.

D:

This observation would test a different technical dependency: This directly verifies the related correction: Use an approved DNS endpoint covered by the certificate SAN or reissue a certificate with correct service identities. The current issue is governed by: This directly verifies the related correction: Synchronize clocks and ship logs to a durable centralized destination with appropriate secure, reliable transport. Its decisive check is “Centralized logs survive worker replacement and carry timestamps that correlate with device events within the accepted skew”.

Question 599

During a remote branch provisioning pilot at fictional Northshore Cloud, the change record states: A team declares an existing production VLAN as a new Terraform resource and an apply attempts to create a duplicate object. What underlying technical distinction accounts for this failure?

  1. Terraform configuration alone does not establish ownership of an already-existing platform object; state import binds it to a resource address.
  2. RESTCONF manipulates YANG-defined resources over HTTP; both resource paths and payload media encoding must match the model.
  3. Infrastructure as code, low-code workflows and custom software solve different state-lifecycle and integration needs.
  4. RESTCONF exposes list entries through resource identifiers determined by the keys declared in the YANG model.

Explanation

Correct Answer

A:

Terraform configuration alone does not establish ownership of an already-existing platform object; state import binds it to a resource address. The corresponding repair is: Import the existing platform object into Terraform state, align its configuration and inspect a non-destructive plan. Acceptance should show: The imported resource maps to the intended live identifier and the reviewed plan does not attempt duplicate creation or replacement. Applied here, the relevant facts are: A team declares an existing production VLAN as a new Terraform resource and an apply attempts to create a duplicate object. The question asks what underlying technical distinction accounts for this failure.

Incorrect Answers

B:

The offered statement is true for this other mechanism: The corresponding repair is: Build the request body from the correct YANG data node and use application/yang-data+json with valid RESTCONF resource paths. It does not explain the facts described here, which follow from: The corresponding repair is: Import the existing platform object into Terraform state, align its configuration and inspect a non-destructive plan.

C:

This principle describes a separate cause: The corresponding repair is: Choose a supported declarative IaC framework for persistent desired configuration and targeted scripts for bounded imperative queries or integrations. The reported condition is governed by: The corresponding repair is: Import the existing platform object into Terraform state, align its configuration and inspect a non-destructive plan. The two mechanisms should not be conflated.

D:

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: Import the existing platform object into Terraform state, align its configuration and inspect a non-destructive plan.

Question 600

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 targeted correction best addresses the network automation failure?

  1. Enforce server-side per-resource authorization using authenticated identity and approved tenant or device scope.
  2. Generate and store private keys in restricted secret systems and deploy only to the authorized TLS termination endpoint.
  3. Trace correlated event IDs and earliest causal errors through the pipeline instead of treating the final propagated exception as root cause.
  4. Introduce bounded buffering, backpressure monitoring and horizontal ingestion capacity with visible gap or loss reporting.

Explanation

Correct Answer

D:

Introduce bounded buffering, backpressure monitoring and horizontal ingestion capacity with visible gap or loss reporting. This addresses the problem because streaming telemetry pipelines have collectors, transports, ingestion queues and storage capacity that can fail independently of device subscriptions. Confirm success using: Load tests show telemetry consumers keeping up with target throughput or explicitly signaling lost samples without presenting false continuity. 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 targeted correction best addresses the network automation failure.

Incorrect Answers

A:

The offered action targets: authentication proves identity but each network resource action requires separate policy-based authorization controls. The case facts point instead to: streaming telemetry pipelines have collectors, transports, ingestion queues and storage capacity that can fail independently of device subscriptions. Implement “Introduce bounded buffering, backpressure monitoring and horizontal ingestion capacity with visible gap or loss reporting” to address that specific condition.

B:

This alternative is a response to another technical cause: cA-signed certificates are public trust assertions but the associated private key must remain confidential for endpoint authentication. The reported case instead depends on: streaming telemetry pipelines have collectors, transports, ingestion queues and storage capacity that can fail independently of device subscriptions. The action that directly addresses it is “Introduce bounded buffering, backpressure monitoring and horizontal ingestion capacity with visible gap or loss reporting”.

C:

The proposed action belongs to the mechanism: downstream error messages can reflect cascaded failures; causality is established by correlating the earlier specific event and affected resource. Here the stated fault follows a different mechanism: streaming telemetry pipelines have collectors, transports, ingestion queues and storage capacity that can fail independently of device subscriptions. The corrective choice is “Introduce bounded buffering, backpressure monitoring and horizontal ingestion capacity with visible gap or loss reporting”.