100% Latest & Updated Cisco 350-901 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 60
Two controllers show conflicting VLAN settings after simultaneous pipelines wrote infrastructure state. Independently, reviewers flag this potentially unsafe practice for assessment: 'Run forced replacement on all resources whenever a drift alert appears'. Which verification addresses that practice without assuming it caused the incident?
- Review lock records and pipeline serialization
- Compare plan diff and controller readback for suspected drift
- Keep writable local state files on every engineer laptop
- Audit backend encryption and access control
Explanation
Correct Answer
B:Destructive blanket refresh is not a safe reconciliation plan. The intended behavior is: State is not proof the live controller still matches it.
Incorrect Answers
A:This checks prevent parallel mutations, not the named failure. Concurrent writes can corrupt tracked resource relationships.
C:Divergent snapshots can overwrite one another.
D:This checks protect sensitive state, not the named failure. State may contain endpoint identifiers and secrets.
Question 61
A data-center team manages tenant VLAN resources with Terraform and needs predictable approval of any changes. The specific implementation objective is to model the smallest managed object. Which configuration best meets the stated requirement?
- Run terraform apply automatically on every unreviewed feature push
- Ignore a plan marked destroy-and-create because the name remains unchanged
- Define only the intended network resource and its required dependencies
- Use state file presence as sole evidence that clients can reach the VLAN
Explanation
Correct Answer
C:Fine-grained state limits unintended side effects.
Incorrect Answers
A:Unreviewed infrastructure changes threaten production.
B:Resource identity and connectivity may be disrupted.
D:Tracking metadata is not packet-level validation.
Question 62
A data-center team manages tenant VLAN resources with Terraform and needs predictable approval of any changes. The specific implementation objective is to review change effects first. Which design action is most appropriate for this case?
- Model the whole controller inventory as one frequently replaced object
- Use state file presence as sole evidence that clients can reach the VLAN
- Require a human-reviewed terraform plan before applying network changes
- Ignore a plan marked destroy-and-create because the name remains unchanged
Explanation
Correct Answer
C:A plan reveals creates, updates and replacements.
Incorrect Answers
A:Giant resource scope increases replacement blast radius.
B:Tracking metadata is not packet-level validation.
D:Resource identity and connectivity may be disrupted.
Question 63
A data-center team manages tenant VLAN resources with Terraform and needs predictable approval of any changes. The specific implementation objective is to avoid destructive replacements. What should the engineer implement for this specific objective?
- Investigate why lifecycle or provider schema indicates resource replacement
- Model the whole controller inventory as one frequently replaced object
- Use state file presence as sole evidence that clients can reach the VLAN
- Run terraform apply automatically on every unreviewed feature push
Explanation
Correct Answer
A:Unexpected replacements may interrupt attached services.
Incorrect Answers
B:Giant resource scope increases replacement blast radius.
C:Tracking metadata is not packet-level validation.
D:Unreviewed infrastructure changes threaten production.
Question 64
A data-center team manages tenant VLAN resources with Terraform and needs predictable approval of any changes. The specific implementation objective is to validate deployed state. Which adjustment would satisfy this particular constraint?
- Check the target controller objects and service reachability after apply
- Ignore a plan marked destroy-and-create because the name remains unchanged
- Model the whole controller inventory as one frequently replaced object
- Run terraform apply automatically on every unreviewed feature push
Explanation
Correct Answer
A:Success status does not guarantee network behavior.
Incorrect Answers
B:Resource identity and connectivity may be disrupted.
C:Giant resource scope increases replacement blast radius.
D:Unreviewed infrastructure changes threaten production.
Question 65
A data-center team manages tenant VLAN resources with Terraform and needs predictable approval of any changes. The deployment plan must both (1) model the smallest managed object and (2) avoid destructive replacements. Which TWO actions together satisfy those requirements? Choose TWO.
- Ignore a plan marked destroy-and-create because the name remains unchanged
- Define only the intended network resource and its required dependencies
- Use state file presence as sole evidence that clients can reach the VLAN
- Investigate why lifecycle or provider schema indicates resource replacement
- Run terraform apply automatically on every unreviewed feature push
Explanation
Correct Answers
B:Fine-grained state limits unintended side effects.
D:Unexpected replacements may interrupt attached services.
Incorrect Answers
A:Resource identity and connectivity may be disrupted.
C:Tracking metadata is not packet-level validation.
E:Unreviewed infrastructure changes threaten production.
Question 66
A data-center team manages tenant VLAN resources with Terraform and needs predictable approval of any changes. Three conditions must be met: (1) model the smallest managed object; (2) review change effects first; and (3) validate deployed state. Which THREE actions form the narrowest complete plan? Choose THREE.
- Use state file presence as sole evidence that clients can reach the VLAN
- Model the whole controller inventory as one frequently replaced object
- Require a human-reviewed terraform plan before applying network changes
- Run terraform apply automatically on every unreviewed feature push
- Define only the intended network resource and its required dependencies
- Check the target controller objects and service reachability after apply
Explanation
Correct Answers
C:A plan reveals creates, updates and replacements.
E:Fine-grained state limits unintended side effects.
F:Success status does not guarantee network behavior.
Incorrect Answers
A:Tracking metadata is not packet-level validation.
B:Giant resource scope increases replacement blast radius.
D:Unreviewed infrastructure changes threaten production.
Question 67
A planned VLAN change would delete an unrelated trunk because the resource definition was replaced rather than updated. Independently, reviewers flag this potentially unsafe practice for assessment: 'Model the whole controller inventory as one frequently replaced object'. Which inspection most directly evaluates that practice?
- Compare controller operational status and application probes
- Ignore a plan marked destroy-and-create because the name remains unchanged
- Review plan action codes and required replacements
- Inspect resource addresses and dependency graph
Explanation
Correct Answer
D:Giant resource scope increases replacement blast radius. The intended behavior is: Fine-grained state limits unintended side effects.
Incorrect Answers
A:This checks validate deployed state, not the named failure. Success status does not guarantee network behavior.
B:Resource identity and connectivity may be disrupted.
C:This checks review change effects first, not the named failure. A plan reveals creates, updates and replacements.
Question 68
A planned VLAN change would delete an unrelated trunk because the resource definition was replaced rather than updated. Independently, reviewers flag this potentially unsafe practice for assessment: 'Run terraform apply automatically on every unreviewed feature push'. What diagnostic evidence should first be collected to assess that practice?
- Inspect plan replace triggers and referenced dependencies
- Review plan action codes and required replacements
- Compare controller operational status and application probes
- Model the whole controller inventory as one frequently replaced object
Explanation
Correct Answer
B:Unreviewed infrastructure changes threaten production. The intended behavior is: A plan reveals creates, updates and replacements.
Incorrect Answers
A:This checks avoid destructive replacements, not the named failure. Unexpected replacements may interrupt attached services.
C:This checks validate deployed state, not the named failure. Success status does not guarantee network behavior.
D:Giant resource scope increases replacement blast radius.
Question 69
A planned VLAN change would delete an unrelated trunk because the resource definition was replaced rather than updated. Independently, reviewers flag this potentially unsafe practice for assessment: 'Ignore a plan marked destroy-and-create because the name remains unchanged'. Which focused check best tests this specific assumption?
- Inspect plan replace triggers and referenced dependencies
- Use state file presence as sole evidence that clients can reach the VLAN
- Inspect resource addresses and dependency graph
- Review plan action codes and required replacements
Explanation
Correct Answer
A:Resource identity and connectivity may be disrupted. The intended behavior is: Unexpected replacements may interrupt attached services.
Incorrect Answers
B:Tracking metadata is not packet-level validation.
C:This checks model the smallest managed object, not the named failure. Fine-grained state limits unintended side effects.
D:This checks review change effects first, not the named failure. A plan reveals creates, updates and replacements.
Question 70
A planned VLAN change would delete an unrelated trunk because the resource definition was replaced rather than updated. Independently, reviewers flag this potentially unsafe practice for assessment: 'Use state file presence as sole evidence that clients can reach the VLAN'. Which verification addresses that practice without assuming it caused the incident?
- Inspect plan replace triggers and referenced dependencies
- Inspect resource addresses and dependency graph
- Run terraform apply automatically on every unreviewed feature push
- Compare controller operational status and application probes
Explanation
Correct Answer
D:Tracking metadata is not packet-level validation. The intended behavior is: Success status does not guarantee network behavior.
Incorrect Answers
A:This checks avoid destructive replacements, not the named failure. Unexpected replacements may interrupt attached services.
B:This checks model the smallest managed object, not the named failure. Fine-grained state limits unintended side effects.
C:Unreviewed infrastructure changes threaten production.
Designing, Deploying, and Managing Network Automation Systems (350-901) Practice Tests