Cisco 350-601 Practice Test 99
Question 980
Two operators run Terraform on one fabric and overwrite each other's state when remote locking is absent. The observed failure is: unreconciled or concurrently modified state can trigger unintended replacement or lost configuration. What should the engineer do to recover and validate the service?
- The controlled remediation is to give all operators an unlocked local copy of the same shared state.
- The controlled remediation is to delete the state file to make Terraform forget the running infrastructure.
- The controlled remediation is to apply every plan without checking destructive changes.
- The controlled remediation is to restore accurate state tracking and locked workflows, then approve only an expected plan.
Explanation
Correct Answer
D:Terraform compares declared configuration with tracked state; safe operations depend on accurate state and coordination. Validate against Terraform plan diff, resource identifiers, locked state backend and verified current infrastructure.
Incorrect Answers
A:Give all operators an unlocked local copy of the same shared state. This would not reliably restore service after the stated fault. Unreconciled or concurrently modified state can trigger unintended replacement or lost configuration. The controlled recovery is to restore accurate state tracking and locked workflows, then approve only an expected plan.
B:Delete the state file to make Terraform forget the running infrastructure. This would not reliably restore service after the stated fault. Unreconciled or concurrently modified state can trigger unintended replacement or lost configuration. The controlled recovery is to restore accurate state tracking and locked workflows, then approve only an expected plan.
C:Apply every plan without checking destructive changes. This would not reliably restore service after the stated fault. Unreconciled or concurrently modified state can trigger unintended replacement or lost configuration. The controlled recovery is to restore accurate state tracking and locked workflows, then approve only an expected plan.
Question 981
A network administrator changes an ACI contract manually but the source-controlled Terraform configuration does not reflect it. Which operator action best meets this technical requirement?
- Compare provider readback with Terraform plan and decide whether to reconcile the drift into code or restore desired state.
- Purge all configuration history to hide unmanaged changes.
- Ignore provider readback and treat state as infallible.
- Force a global destroy whenever a single managed attribute changes.
Explanation
Correct Answer
A:This directly addresses Terraform drift detection because infrastructure drift occurs when actual resources diverge from tracked declarative desired state. Confirm the change against plan changes, current provider resource values, Git change history and approved policy intent.
Incorrect Answers
B:Blindly applying stale configuration can overwrite an intentionally approved emergency change. The relevant correction is to compare provider readback with Terraform plan and decide whether to reconcile the drift into code or restore desired state.
C:Ignore provider readback and treat state as infallible. The proposed change targets the wrong mechanism or lacks essential validation. Infrastructure drift occurs when actual resources diverge from tracked declarative desired state. Relevant evidence is plan changes, current provider resource values, Git change history and approved policy intent.
D:Blindly applying stale configuration can overwrite an intentionally approved emergency change. The appropriate action remains to compare provider readback with Terraform plan and decide whether to reconcile the drift into code or restore desired state.
Question 982
A network administrator changes an ACI contract manually but the source-controlled Terraform configuration does not reflect it. Which collection of observations most directly tests the suspected cause?
- A dashboard snapshot detached from actual target configuration and logs.
- Plan changes, current provider resource values, Git change history and approved policy intent.
- An old CI job name without run records or configuration diffs.
- A saved script file that has never been executed or tested.
Explanation
Correct Answer
B:These observations test the actual Terraform drift detection mechanism rather than a superficial management status. Infrastructure drift occurs when actual resources diverge from tracked declarative desired state.
Incorrect Answers
A:A dashboard snapshot detached from actual target configuration and logs. This information cannot independently verify Terraform drift detection. The decisive records instead include plan changes, current provider resource values, Git change history and approved policy intent. Infrastructure drift occurs when actual resources diverge from tracked declarative desired state.
C:An old CI job name without run records or configuration diffs. This information cannot independently verify Terraform drift detection. The decisive records instead include plan changes, current provider resource values, Git change history and approved policy intent. Infrastructure drift occurs when actual resources diverge from tracked declarative desired state.
D:A saved script file that has never been executed or tested. This information cannot independently verify Terraform drift detection. The decisive records instead include plan changes, current provider resource values, Git change history and approved policy intent. Infrastructure drift occurs when actual resources diverge from tracked declarative desired state.
Question 983
A network administrator changes an ACI contract manually but the source-controlled Terraform configuration does not reflect it. Which statement most accurately explains this scenario?
- The existence of a state file proves all remote resources match desired state.
- An HTTP 200 connection proves the intended device state was changed correctly.
- Infrastructure drift occurs when actual resources diverge from tracked declarative desired state.
- Cloud or on-box automation removes the need to validate inputs and outcomes.
Explanation
Correct Answer
C:Validation depends on plan changes, current provider resource values, Git change history and approved policy intent. This explains why the most appropriate response is to compare provider readback with Terraform plan and decide whether to reconcile the drift into code or restore desired state.
Incorrect Answers
A:The existence of a state file proves all remote resources match desired state. This is an incorrect generalization for Terraform drift detection. The applicable technical behavior is that infrastructure drift occurs when actual resources diverge from tracked declarative desired state. The operator should verify plan changes, current provider resource values, Git change history and approved policy intent.
B:An HTTP 200 connection proves the intended device state was changed correctly. This is an incorrect generalization for Terraform drift detection. The applicable technical behavior is that infrastructure drift occurs when actual resources diverge from tracked declarative desired state. The operator should verify plan changes, current provider resource values, Git change history and approved policy intent.
D:Cloud or on-box automation removes the need to validate inputs and outcomes. This is an incorrect generalization for Terraform drift detection. The applicable technical behavior is that infrastructure drift occurs when actual resources diverge from tracked declarative desired state. The operator should verify plan changes, current provider resource values, Git change history and approved policy intent.
Question 984
A network administrator changes an ACI contract manually but the source-controlled Terraform configuration does not reflect it. Assume an engineer instead chooses to purge all configuration history to hide unmanaged changes. What is the principal technical consequence of the mistaken choice?
- Reviewing a Terraform plan makes correct configuration objects disappear.
- Using a dry-run test inherently disables every network management API.
- Storing execution logs causes the original script to use invalid parameters.
- Blindly applying stale configuration can overwrite an intentionally approved emergency change.
Explanation
Correct Answer
D:The proper corrective action is to compare provider readback with Terraform plan and decide whether to reconcile the drift into code or restore desired state. That is the direct consequence of choosing the misleading shortcut.
Incorrect Answers
A:This does not explain the actual Terraform drift detection defect after the shortcut. The meaningful failure is that blindly applying stale configuration can overwrite an intentionally approved emergency change.
B:This does not explain the actual Terraform drift detection defect after the shortcut. The relevant evidence is plan changes, current provider resource values, Git change history and approved policy intent.
C:This does not explain the actual Terraform drift detection defect after the shortcut. Storing execution logs causes the original script to use invalid parameters.
Question 985
A network administrator changes an ACI contract manually but the source-controlled Terraform configuration does not reflect it. The observed failure is: blindly applying stale configuration can overwrite an intentionally approved emergency change. What should the engineer do to recover and validate the service?
- Review drift ownership, update source of truth or safely revert change and verify the resulting plan.
- Ignore provider readback and treat state as infallible.
- Force a global destroy whenever a single managed attribute changes.
- Purge all configuration history to hide unmanaged changes.
Explanation
Correct Answer
A:Validate against plan changes, current provider resource values, Git change history and approved policy intent. This addresses the observable fault while preserving a check of the expected result.
Incorrect Answers
B:Ignore provider readback and treat state as infallible. This would not reliably restore service after the stated fault. Blindly applying stale configuration can overwrite an intentionally approved emergency change. The controlled recovery is to review drift ownership, update source of truth or safely revert change and verify the resulting plan.
C:Force a global destroy whenever a single managed attribute changes. This would not reliably restore service after the stated fault. Blindly applying stale configuration can overwrite an intentionally approved emergency change. The controlled recovery is to review drift ownership, update source of truth or safely revert change and verify the resulting plan.
D:Purge all configuration history to hide unmanaged changes. This would not reliably restore service after the stated fault. Blindly applying stale configuration can overwrite an intentionally approved emergency change. The controlled recovery is to review drift ownership, update source of truth or safely revert change and verify the resulting plan.
Question 986
A periodic infrastructure-as-code check identifies that a Nexus object differs from the last applied declarative policy. Which next step should the data center engineer select?
- On this affected device, the engineer should ignore provider readback and treat state as infallible.
- On this affected device, the engineer should compare provider readback with Terraform plan and decide whether to reconcile the drift into code or restore desired state.
- On this affected device, the engineer should force a global destroy whenever a single managed attribute changes.
- On this affected device, the engineer should purge all configuration history to hide unmanaged changes.
Explanation
Correct Answer
B:This directly addresses Terraform drift detection because infrastructure drift occurs when actual resources diverge from tracked declarative desired state.
Incorrect Answers
A:Ignore provider readback and treat state as infallible. The proposed change targets the wrong mechanism or lacks essential validation. Infrastructure drift occurs when actual resources diverge from tracked declarative desired state. Relevant evidence is plan changes, current provider resource values, Git change history and approved policy intent.
C:Blindly applying stale configuration can overwrite an intentionally approved emergency change. Force a global destroy whenever a single managed attribute changes.
D:Blindly applying stale configuration can overwrite an intentionally approved emergency change. In the given case, a periodic infrastructure-as-code check identifies that a Nexus object differs from the last applied declarative policy.
Question 987
A periodic infrastructure-as-code check identifies that a Nexus object differs from the last applied declarative policy. Which diagnostic record would most strongly confirm the result?
- For this deployment, examine an API endpoint returning HTML instead of validated inventory or outcome.
- For this deployment, examine a dashboard snapshot detached from actual target configuration and logs.
- For this deployment, examine plan changes, current provider resource values, Git change history and approved policy intent.
- For this deployment, examine an old CI job name without run records or configuration diffs.
Explanation
Correct Answer
C:These observations test the actual Terraform drift detection mechanism rather than a superficial management status. They should be checked after compare provider readback with Terraform plan and decide whether to reconcile the drift into code or restore desired state.
Incorrect Answers
A:An API endpoint returning HTML instead of validated inventory or outcome. This information cannot independently verify Terraform drift detection. The decisive records instead include plan changes, current provider resource values, Git change history and approved policy intent. Infrastructure drift occurs when actual resources diverge from tracked declarative desired state.
B:A dashboard snapshot detached from actual target configuration and logs. This information cannot independently verify Terraform drift detection. The decisive records instead include plan changes, current provider resource values, Git change history and approved policy intent. Infrastructure drift occurs when actual resources diverge from tracked declarative desired state.
D:An old CI job name without run records or configuration diffs. This information cannot independently verify Terraform drift detection. The decisive records instead include plan changes, current provider resource values, Git change history and approved policy intent. Infrastructure drift occurs when actual resources diverge from tracked declarative desired state.
Question 988
A periodic infrastructure-as-code check identifies that a Nexus object differs from the last applied declarative policy. Which platform concept should guide the engineer’s assessment?
- For this condition, the applicable principle is that cloud or on-box automation removes the need to validate inputs and outcomes.
- For this condition, the applicable principle is that the existence of a state file proves all remote resources match desired state.
- For this condition, the applicable principle is that one initial successful run guarantees all later automation remains correct.
- For this condition, the applicable principle is that infrastructure drift occurs when actual resources diverge from tracked declarative desired state.
Explanation
Correct Answer
D:Validation depends on plan changes, current provider resource values, Git change history and approved policy intent.
Incorrect Answers
A:Cloud or on-box automation removes the need to validate inputs and outcomes. This is an incorrect generalization for Terraform drift detection. The applicable technical behavior is that infrastructure drift occurs when actual resources diverge from tracked declarative desired state. The operator should verify plan changes, current provider resource values, Git change history and approved policy intent.
B:The existence of a state file proves all remote resources match desired state. This is an incorrect generalization for Terraform drift detection. The applicable technical behavior is that infrastructure drift occurs when actual resources diverge from tracked declarative desired state. The operator should verify plan changes, current provider resource values, Git change history and approved policy intent.
C:One initial successful run guarantees all later automation remains correct. This is an incorrect generalization for Terraform drift detection. The applicable technical behavior is that infrastructure drift occurs when actual resources diverge from tracked declarative desired state. The operator should verify plan changes, current provider resource values, Git change history and approved policy intent.
Question 989
A periodic infrastructure-as-code check identifies that a Nexus object differs from the last applied declarative policy. Assume an engineer instead chooses to purge all configuration history to hide unmanaged changes. Which root-cause observation follows from that incorrect change?
- The resulting defect is that blindly applying stale configuration can overwrite an intentionally approved emergency change.
- The resulting defect is that storing execution logs causes the original script to use invalid parameters.
- The resulting defect is that verifying server policy references is the reason the missing references occurred.
- The resulting defect is that using a dry-run test inherently disables every network management API.
Explanation
Correct Answer
A:The proper corrective action is to compare provider readback with Terraform plan and decide whether to reconcile the drift into code or restore desired state. Infrastructure drift occurs when actual resources diverge from tracked declarative desired state.
Incorrect Answers
B:This does not explain the actual Terraform drift detection defect after the shortcut. In the given case, a periodic infrastructure-as-code check identifies that a Nexus object differs from the last applied declarative policy.
C:This does not explain the actual Terraform drift detection defect after the shortcut. Verifying server policy references is the reason the missing references occurred.
D:This does not explain the actual Terraform drift detection defect after the shortcut. Using a dry-run test inherently disables every network management API.
Question 990
A periodic infrastructure-as-code check identifies that a Nexus object differs from the last applied declarative policy. The observed failure is: blindly applying stale configuration can overwrite an intentionally approved emergency change. Which recovery action addresses the underlying technical fault?
- The controlled remediation is to force a global destroy whenever a single managed attribute changes.
- The controlled remediation is to review drift ownership, update source of truth or safely revert change and verify the resulting plan.
- The controlled remediation is to purge all configuration history to hide unmanaged changes.
- The controlled remediation is to ignore provider readback and treat state as infallible.
Explanation
Correct Answer
B:Validate against plan changes, current provider resource values, Git change history and approved policy intent. Infrastructure drift occurs when actual resources diverge from tracked declarative desired state.
Incorrect Answers
A:Force a global destroy whenever a single managed attribute changes. This would not reliably restore service after the stated fault. Blindly applying stale configuration can overwrite an intentionally approved emergency change. The controlled recovery is to review drift ownership, update source of truth or safely revert change and verify the resulting plan.
C:Purge all configuration history to hide unmanaged changes. This would not reliably restore service after the stated fault. Blindly applying stale configuration can overwrite an intentionally approved emergency change. The controlled recovery is to review drift ownership, update source of truth or safely revert change and verify the resulting plan.
D:Ignore provider readback and treat state as infallible. This would not reliably restore service after the stated fault. Blindly applying stale configuration can overwrite an intentionally approved emergency change. The controlled recovery is to review drift ownership, update source of truth or safely revert change and verify the resulting plan.