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 17

Question 160

During an AI recommendation accuracy study at fictional Amberlight Energy, the change record states: A developer sends internal Cisco API bearer tokens and customer inventory records to an unapproved hosted LLM to generate a Terraform module. Which observation would confirm that this exact failure is resolved?

  1. A poisoned-source test yields a flagged uncertainty or validated official-source citation instead of an unsafe configuration recommendation.
  2. Malformed IDs and cross-tenant requests are rejected predictably while approved tool calls return scoped data.
  3. A site-context switch triggers a fresh scoped lookup and proposed actions reference currently authorized device identifiers.
  4. Audit logs and data-loss-prevention checks show that prompts and tool responses contain no live credentials or confidential customer payloads.

Explanation

Correct Answer

D:

Audit logs and data-loss-prevention checks show that prompts and tool responses contain no live credentials or confidential customer payloads. This directly verifies the related correction: Sanitize inputs and use an approved private or contractually controlled AI service without exposing secrets or regulated network data. It checks the technical distinction: AI-assisted code tools may process submitted data outside the intended trust boundary, creating privacy and intellectual-property exposure. Applied here, the relevant facts are: A developer sends internal Cisco API bearer tokens and customer inventory records to an unapproved hosted LLM to generate a Terraform module. The question asks which observation would confirm that this exact failure is resolved.

Incorrect Answers

A:

This observation would test a different technical dependency: This directly verifies the related correction: Ground actionable recommendations in trusted versioned technical references and reject unsupported or conflicting retrieved claims. The current issue is governed by: This directly verifies the related correction: Sanitize inputs and use an approved private or contractually controlled AI service without exposing secrets or regulated network data. Its decisive check is “Audit logs and data-loss-prevention checks show that prompts and tool responses contain no live credentials or confidential customer payloads”.

B:

The alternative verifies a different condition: This directly verifies the related correction: Define typed, validated tool arguments with explicit device allowlists and reject invalid or unauthorized inputs at the server boundary. The current case instead depends on: This directly verifies the related correction: Sanitize inputs and use an approved private or contractually controlled AI service without exposing secrets or regulated network data. Confirm that “Audit logs and data-loss-prevention checks show that prompts and tool responses contain no live credentials or confidential customer payloads”.

C:

That test belongs to another control with this basis: This directly verifies the related correction: Bind current request context to fresh authorized inventory and explicit tenant or device selection before tool calls. In the current case, the governing reason is: This directly verifies the related correction: Sanitize inputs and use an approved private or contractually controlled AI service without exposing secrets or regulated network data. The direct verification is “Audit logs and data-loss-prevention checks show that prompts and tool responses contain no live credentials or confidential customer payloads”.

Question 161

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. Which engineering principle explains the described system behavior?

  1. Git cannot automatically reconcile overlapping divergent edits; a human or reviewed tool must choose the resulting content before merge completion.
  2. YANG defines node hierarchy, namespaces, list keys and data types; conforming JSON must preserve that structure.
  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

B:

YANG defines node hierarchy, namespaces, list keys and data types; conforming JSON must preserve that structure. The corresponding repair is: Construct JSON using the published YANG container hierarchy, qualified node names and correct value types. Acceptance should show: The payload validates against the YANG schema and the RESTCONF server accepts the exact intended interface resource.

Incorrect Answers

A:

The corresponding repair is: Resolve the conflicting lines deliberately against the approved desired network state, run validation, then commit the merged result. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Construct JSON using the published YANG container hierarchy, qualified node names and correct value types.

C:

This principle describes a separate cause: The corresponding repair is: Run objective-based postdeployment checks and fail or roll back the change when observed network behavior contradicts intent. The reported condition is governed by: The corresponding repair is: Construct JSON using the published YANG container hierarchy, qualified node names and correct value types. The two mechanisms should not be conflated.

D:

The corresponding repair is: Unstage the unintended file with an index-only reset or equivalent restore-staged operation, leaving the worktree intact. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Construct JSON using the published YANG container hierarchy, qualified node names and correct value types.

Question 162

While investigating a network policy migration for fictional Cedarbridge Care Systems, the team reports: A generalized automation assumes every switch supports the same vendor YANG augmentation and fails against older IOS XE images. Which explanation best matches the actual broken dependency?

  1. Infrastructure as code, low-code workflows and custom software solve different state-lifecycle and integration needs.
  2. Ansible's desired-state-aware network modules compare declared configuration with device state before determining required changes.
  3. Model-driven APIs are available only for modules and revisions implemented by the device software, not by the client library alone.
  4. Terraform configuration alone does not establish ownership of an already-existing platform object; state import binds it to a resource address.

Explanation

Correct Answer

C:

Model-driven APIs are available only for modules and revisions implemented by the device software, not by the client library alone. The corresponding repair is: Discover supported YANG modules or capabilities before using module-specific RESTCONF data paths, and branch for supported models. Acceptance should show: The preflight confirms the required module and revision per target, or marks incompatible devices without making changes.

Incorrect Answers

A:

The offered action targets: The corresponding repair is: Choose a supported declarative IaC framework for persistent desired configuration and targeted scripts for bounded imperative queries or integrations. The case facts point instead to: The corresponding repair is: Discover supported YANG modules or capabilities before using module-specific RESTCONF data paths, and branch for supported models. Implement “Model-driven APIs are available only for modules and revisions implemented by the device software, not by the client library alone” to address that specific condition.

B:

This alternative is a response to another technical cause: The corresponding repair is: Replace non-idempotent shell appends with the platform-aware Ansible network configuration module and explicit desired interface state. The reported case instead depends on: The corresponding repair is: Discover supported YANG modules or capabilities before using module-specific RESTCONF data paths, and branch for supported models. The action that directly addresses it is “Model-driven APIs are available only for modules and revisions implemented by the device software, not by the client library alone”.

D:

The offered action targets: The corresponding repair is: Import the existing platform object into Terraform state, align its configuration and inspect a non-destructive plan. The case facts point instead to: The corresponding repair is: Discover supported YANG modules or capabilities before using module-specific RESTCONF data paths, and branch for supported models. Implement “Model-driven APIs are available only for modules and revisions implemented by the device software, not by the client library alone” to address that specific condition.

Question 163

During a source-of-truth integration at fictional Violet Ridge Resorts, the change record states: A local branch includes a mistaken last commit with invalid Terraform test output, and no one else has fetched the commit. What should the engineer change first to resolve this specific issue?

  1. Use an approved squash merge to combine reviewed feature changes into one commit while preserving the final content.
  2. Use an appropriate local Git reset to move the branch pointer and rebuild the unpublished commit while protecting wanted working changes.
  3. Model the relevant links, routing peers and failure cases in CML rather than only a minimal happy-path device.
  4. Identify the prerequisite commits and cherry-pick a minimal compatible sequence or adapt the patch for the target baseline.

Explanation

Correct Answer

B:

Use an appropriate local Git reset to move the branch pointer and rebuild the unpublished commit while protecting wanted working changes. This addresses the problem because git reset moves HEAD and optionally the index and worktree, making it suitable for carefully revising unpublished local history. Confirm success using: The corrected local branch no longer references the mistaken commit and preserved intended edits are recommitted after validation.

Incorrect Answers

A:

This alternative is a response to another technical cause: a squash merge consolidates branch changes into a new commit, simplifying target history without preserving each source commit as a separate mainline entry. The reported case instead depends on: git reset moves HEAD and optionally the index and worktree, making it suitable for carefully revising unpublished local history. The action that directly addresses it is “Use an appropriate local Git reset to move the branch pointer and rebuild the unpublished commit while protecting wanted working changes”.

C:

The offered action targets: simulation usefulness depends on modeled network dependencies; an incomplete topology cannot validate omitted behaviors. The case facts point instead to: git reset moves HEAD and optionally the index and worktree, making it suitable for carefully revising unpublished local history. Implement “Use an appropriate local Git reset to move the branch pointer and rebuild the unpublished commit while protecting wanted working changes” to address that specific condition.

D:

This alternative is a response to another technical cause: a cherry-picked commit does not automatically bring every ancestor or dependent change from its original branch. The reported case instead depends on: git reset moves HEAD and optionally the index and worktree, making it suitable for carefully revising unpublished local history. The action that directly addresses it is “Use an appropriate local Git reset to move the branch pointer and rebuild the unpublished commit while protecting wanted working changes”.

Question 164

At fictional Willowfield Hospitality, during a version-control hotfix, the operator observes: A pipeline declares success when configuration API calls return 200 despite OSPF sessions remaining down on edge routers. What underlying technical distinction accounts for this failure?

  1. A source of truth provides desired canonical inventory, but consumers must resolve identity correctly and reconcile discrepancies.
  2. A GitLab pipeline exit code identifies failure, while job logs and test artifacts reveal the specific causal stage and assertion.
  3. CI runners start from controlled environments; undeclared local dependencies cannot be assumed present remotely.
  4. Deployment command success is not the same as verified service success; operational checks must follow state changes.

Explanation

Correct Answer

D:

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.

Incorrect Answers

A:

The corresponding repair is: Use stable authoritative device identifiers and reconcile observed inventory to the source-of-truth records before deployment. That explanation applies to a different technical failure. Here the controlling principle is: The corresponding repair is: Run objective-based postdeployment checks and fail or roll back the change when observed network behavior contradicts intent.

B:

The offered statement is true for this other mechanism: The corresponding repair is: Inspect the failed job logs and classify whether build, dependency, test or environment validation failed before making a targeted fix. It does not explain the facts described here, which follow from: The corresponding repair is: Run objective-based postdeployment checks and fail or roll back the change when observed network behavior contradicts intent.

C:

This principle describes a separate cause: The corresponding repair is: Declare and lock the required dependency in the build manifest and install it in the pipeline's reproducible environment. The reported condition 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. The two mechanisms should not be conflated.

Question 165

While investigating a source-of-truth integration for fictional Willowfield Hospitality, the team reports: A network engineer switches branches with uncommitted interface edits, then mistakenly tests a mixture of two feature versions. Which explanation best matches the actual broken dependency?

  1. Git checkout can change branch and working-tree files; uncommitted modifications must be managed to avoid accidental mixing.
  2. A reliable source-of-truth workflow separates approved intent from observed device state and defines how changes flow between them.
  3. A GitLab pipeline exit code identifies failure, while job logs and test artifacts reveal the specific causal stage and assertion.
  4. A source of truth provides desired canonical inventory, but consumers must resolve identity correctly and reconcile discrepancies.

Explanation

Correct Answer

A:

Git checkout can change branch and working-tree files; uncommitted modifications must be managed to avoid accidental mixing. The corresponding repair is: Safely stash or commit unrelated work and check out the intended branch or detached revision in a clean worktree. Acceptance should show: The working tree reports the intended revision and no uncommitted cross-branch edits before test execution.

Incorrect Answers

B:

This alternative is a response to another technical cause: The corresponding repair is: Read authorized desired state from the designated source of truth and reconcile observed drift through an approved change path. The reported case instead depends on: The corresponding repair is: Safely stash or commit unrelated work and check out the intended branch or detached revision in a clean worktree. The action that directly addresses it is “Git checkout can change branch and working-tree files; uncommitted modifications must be managed to avoid accidental mixing”.

C:

The proposed action belongs to the mechanism: The corresponding repair is: Inspect the failed job logs and classify whether build, dependency, test or environment validation failed before making a targeted fix. Here the stated fault follows a different mechanism: The corresponding repair is: Safely stash or commit unrelated work and check out the intended branch or detached revision in a clean worktree. The corrective choice is “Git checkout can change branch and working-tree files; uncommitted modifications must be managed to avoid accidental mixing”.

D:

The offered action targets: The corresponding repair is: Use stable authoritative device identifiers and reconcile observed inventory to the source-of-truth records before deployment. The case facts point instead to: The corresponding repair is: Safely stash or commit unrelated work and check out the intended branch or detached revision in a clean worktree. Implement “Git checkout can change branch and working-tree files; uncommitted modifications must be managed to avoid accidental mixing” to address that specific condition.

Question 166

At fictional Cobalt Ridge Bank, an acceptance review of a campus API automation rollout finds: A management automation forces a routing process reload on each inventory polling cycle, causing avoidable control-plane interruptions. What is the appropriate response to this network automation condition?

  1. Set explicit connect and read timeouts and catch the resulting exceptions so the worker can report and continue safely.
  2. Set compatible provider version constraints and commit the provider dependency lock file for reproducible runs.
  3. Notify a handler only when the associated configuration task reports a real change, and apply the restart once if necessary.
  4. Import the existing platform object into Terraform state, align its configuration and inspect a non-destructive plan.

Explanation

Correct Answer

C:

Notify a handler only when the associated configuration task reports a real change, and apply the restart once if necessary. This addresses the problem because ansible handlers are triggered by changed tasks and coalesce notifications, separating configuration checks from disruptive service actions. Confirm success using: Unchanged reruns cause no service restart, while an approved changed configuration invokes its handler exactly once.

Incorrect Answers

A:

This alternative is a response to another technical cause: python HTTP clients do not guarantee a useful bounded response time unless the caller configures explicit timeouts. The reported case instead depends on: ansible handlers are triggered by changed tasks and coalesce notifications, separating configuration checks from disruptive service actions. The action that directly addresses it is “Notify a handler only when the associated configuration task reports a real change, and apply the restart once if necessary”.

B:

The proposed action belongs to the mechanism: terraform providers translate declarative resources into platform API operations; provider version changes can alter behavior. Here the stated fault follows a different mechanism: ansible handlers are triggered by changed tasks and coalesce notifications, separating configuration checks from disruptive service actions. The corrective choice is “Notify a handler only when the associated configuration task reports a real change, and apply the restart once if necessary”.

D:

This alternative is a response to another technical cause: terraform configuration alone does not establish ownership of an already-existing platform object; state import binds it to a resource address. The reported case instead depends on: ansible handlers are triggered by changed tasks and coalesce notifications, separating configuration checks from disruptive service actions. The action that directly addresses it is “Notify a handler only when the associated configuration task reports a real change, and apply the restart once if necessary”.

Question 167

During a GitLab deployment pipeline rehearsal at fictional Seabright Learning, the change record states: A controller-integration container loses its collected audit results whenever the Compose project is recreated. Which explanation best matches the actual broken dependency?

  1. A reliable source-of-truth workflow separates approved intent from observed device state and defines how changes flow between them.
  2. A cherry-picked commit does not automatically bring every ancestor or dependent change from its original branch.
  3. A GitLab pipeline exit code identifies failure, while job logs and test artifacts reveal the specific causal stage and assertion.
  4. Ephemeral container writable layers are distinct from Docker managed or host-mounted persistent volumes.

Explanation

Correct Answer

D:

Ephemeral container writable layers are distinct from Docker managed or host-mounted persistent volumes. The corresponding repair is: Mount an appropriate persistent named volume or approved bind mount for data that must survive container recreation. Acceptance should show: A recreated container reads the expected persistent audit or inventory records from the configured volume.

Incorrect Answers

A:

The proposed action belongs to the mechanism: The corresponding repair is: Read authorized desired state from the designated source of truth and reconcile observed drift through an approved change path. Here the stated fault follows a different mechanism: The corresponding repair is: Mount an appropriate persistent named volume or approved bind mount for data that must survive container recreation. The corrective choice is “Ephemeral container writable layers are distinct from Docker managed or host-mounted persistent volumes”.

B:

The offered action targets: The corresponding repair is: Identify the prerequisite commits and cherry-pick a minimal compatible sequence or adapt the patch for the target baseline. The case facts point instead to: The corresponding repair is: Mount an appropriate persistent named volume or approved bind mount for data that must survive container recreation. Implement “Ephemeral container writable layers are distinct from Docker managed or host-mounted persistent volumes” to address that specific condition.

C:

This alternative is a response to another technical cause: The corresponding repair is: Inspect the failed job logs and classify whether build, dependency, test or environment validation failed before making a targeted fix. The reported case instead depends on: The corresponding repair is: Mount an appropriate persistent named volume or approved bind mount for data that must survive container recreation. The action that directly addresses it is “Ephemeral container writable layers are distinct from Docker managed or host-mounted persistent volumes”.

Question 168

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. Which sustainable preventive control most directly avoids a recurrence?

  1. Maintain a tested platform compatibility matrix and versioned adapter contracts for each device family.
  2. Review handler notification conditions and test unchanged and changed execution paths before production scheduling.
  3. Design resource-state reconciliation and safe retry policies for all create and job-submission requests.
  4. Require a policy-reviewed plan artifact and a clean post-change plan in the automated change workflow.

Explanation

Correct Answer

C:

Design resource-state reconciliation and safe retry policies for all create and job-submission requests. This prevents the recurrence because a network transport timeout does not prove server-side failure; blind retries of non-idempotent operations can duplicate effects. A matching immediate correction is: Before retrying a potentially non-idempotent change, check resulting resource state or use a supported idempotency or operation key. Applied here, the relevant facts are: A Python script retries a POST creating a network object after an ambiguous timeout and creates a duplicate because the first request already succeeded. The question asks which sustainable preventive control most directly avoids a recurrence.

Incorrect Answers

A:

That safeguard is relevant to: cross-platform automation benefits from a shared intent model but must translate differences in native device APIs and models. The current failure instead follows from: a network transport timeout does not prove server-side failure; blind retries of non-idempotent operations can duplicate effects. Its prevention measure is “Design resource-state reconciliation and safe retry policies for all create and job-submission requests”.

B:

This routine guards against another mechanism: ansible handlers are triggered by changed tasks and coalesce notifications, separating configuration checks from disruptive service actions. The recurring exposure in the current case is: a network transport timeout does not prove server-side failure; blind retries of non-idempotent operations can duplicate effects. The matching preventive check is “Design resource-state reconciliation and safe retry policies for all create and job-submission requests”.

D:

That safeguard is relevant to: terraform compares configuration, recorded state and provider observations to compute a proposed change set before apply. The current failure instead follows from: a network transport timeout does not prove server-side failure; blind retries of non-idempotent operations can duplicate effects. Its prevention measure is “Design resource-state reconciliation and safe retry policies for all create and job-submission requests”.

Question 169

At fictional Seabright Learning, an acceptance review of a reproducible simulation finds: A deployment stage targets all routers at once despite an approved plan to canary one site before fleet rollout. Which engineering principle explains the described system behavior?

  1. CML supports topology-based device and protocol simulation for safe early integration tests without touching live infrastructure.
  2. Unbounded dependency upgrades can introduce incompatible APIs and nondeterministic CI failures even when repository code is unchanged.
  3. A deployment stage should enforce release scope and approval, not merely execute a command with unrestricted infrastructure access.
  4. Ephemeral container writable layers are distinct from Docker managed or host-mounted persistent volumes.

Explanation

Correct Answer

C:

A deployment stage should enforce release scope and approval, not merely execute a command with unrestricted infrastructure access. The corresponding repair is: Deploy through bounded environment-scoped jobs with approved service credentials and staged canary or batch rollout. Acceptance should show: GitLab deployment records show the canary passed before other sites changed, and credentials cannot access unrelated workspaces. Applied here, the relevant facts are: A deployment stage targets all routers at once despite an approved plan to canary one site before fleet rollout. The question asks which engineering principle explains the described system behavior.

Incorrect Answers

A:

This principle describes a separate cause: The corresponding repair is: Build a representative topology in Cisco Modeling Labs and execute the automation against simulated devices before live release. The reported condition is governed by: The corresponding repair is: Deploy through bounded environment-scoped jobs with approved service credentials and staged canary or batch rollout. The two mechanisms should not be conflated.

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: Deploy through bounded environment-scoped jobs with approved service credentials and staged canary or batch rollout.

D:

This principle describes a separate cause: The corresponding repair is: Mount an appropriate persistent named volume or approved bind mount for data that must survive container recreation. The reported condition is governed by: The corresponding repair is: Deploy through bounded environment-scoped jobs with approved service credentials and staged canary or batch rollout. The two mechanisms should not be conflated.

Question 170

At fictional Cedarbridge Care Systems, during a campus API automation rollout, the operator observes: A Meraki dashboard integration treats HTTP 429 as permanent failure and immediately resubmits hundreds of calls in a tight loop. Which observation would confirm that this exact failure is resolved?

  1. Invalid IDs are rejected before any outbound request and valid values produce correctly encoded resource targets.
  2. A proof of concept demonstrates all required conditional paths, audit fields and rollback needs using the selected approach.
  3. Simulated 429 responses result in delayed, bounded retries and the caller recovers without a retry storm.
  4. The dry-run host list and collected post-change configurations show that only the approved group received the new OSPF or ACL policy.

Explanation

Correct Answer

C:

Simulated 429 responses result in delayed, bounded retries and the caller recovers without a retry storm. This directly verifies the related correction: Respect rate-limit response headers and coordinate bounded exponential backoff with jitter under the shared API budget. It checks the technical distinction: HTTP 429 signals server-enforced rate limits; API client backoff must consider shared rate budgets and Retry-After semantics. Applied here, the relevant facts are: A Meraki dashboard integration treats HTTP 429 as permanent failure and immediately resubmits hundreds of calls in a tight loop. The question asks which observation would confirm that this exact failure is resolved.

Incorrect Answers

A:

The alternative verifies a different condition: This directly verifies the related correction: Validate typed inputs, authorized resource scopes and ranges before constructing API requests, then encode parameters safely. The current case instead depends on: This directly verifies the related correction: Respect rate-limit response headers and coordinate bounded exponential backoff with jitter under the shared API budget. Confirm that “Simulated 429 responses result in delayed, bounded retries and the caller recovers without a retry storm”.

B:

That test belongs to another control with this basis: This directly verifies the related correction: Match workflow complexity, vendor connector capability and error recovery needs to low-code or custom application design after a capability pilot. In the current case, the governing reason is: This directly verifies the related correction: Respect rate-limit response headers and coordinate bounded exponential backoff with jitter under the shared API budget. The direct verification is “Simulated 429 responses result in delayed, bounded retries and the caller recovers without a retry storm”.

D:

The alternative verifies a different condition: This directly verifies the related correction: Separate inventory groups and group variables by approved device scope, then constrain the play to the intended group. The current case instead depends on: This directly verifies the related correction: Respect rate-limit response headers and coordinate bounded exponential backoff with jitter under the shared API budget. Confirm that “Simulated 429 responses result in delayed, bounded retries and the caller recovers without a retry storm”.