Cisco 350-601 Practice Test 98
Question 970
A network workflow written in PowerShell fails to parse a JSON API response and treats an error field as valid inventory. The observed failure is: ignoring HTTP and schema errors can make automation act on absent or misleading inventory. Which remediation most directly restores the intended behavior?
- The controlled remediation is to hard-code successful output regardless of server response.
- The controlled remediation is to correct request signing or token flow and response handling, then validate the actual target objects.
- The controlled remediation is to assume any HTML login page is a valid JSON inventory result.
- The controlled remediation is to place API secrets in a publicly readable script repository.
Explanation
Correct Answer
B:Validate against powerShell request headers, HTTP error codes, parsed JSON properties and verified inventory count. PowerShell can orchestrate management REST APIs but must handle authentication, serialization and error conditions.
Incorrect Answers
A:Hard-code successful output regardless of server response. This would not reliably restore service after the stated fault. Ignoring HTTP and schema errors can make automation act on absent or misleading inventory. The controlled recovery is to correct request signing or token flow and response handling, then validate the actual target objects.
C:Assume any HTML login page is a valid JSON inventory result. This would not reliably restore service after the stated fault. Ignoring HTTP and schema errors can make automation act on absent or misleading inventory. The controlled recovery is to correct request signing or token flow and response handling, then validate the actual target objects.
D:Place API secrets in a publicly readable script repository. This would not reliably restore service after the stated fault. Ignoring HTTP and schema errors can make automation act on absent or misleading inventory. The controlled recovery is to correct request signing or token flow and response handling, then validate the actual target objects.
Question 971
A Terraform apply wants to recreate an existing NX-OS network object because its state file is out of sync. Which configuration decision MOST directly resolves the issue?
- Delete the state file to make Terraform forget the running infrastructure.
- Apply every plan without checking destructive changes.
- Review Terraform plan and state reconciliation, using approved state locking and import procedures before apply.
- Give all operators an unlocked local copy of the same shared state.
Explanation
Correct Answer
C:This directly addresses Terraform planning and state because Terraform compares declared configuration with tracked state; safe operations depend on accurate state and coordination. Confirm the change against Terraform plan diff, resource identifiers, locked state backend and verified current infrastructure.
Incorrect Answers
A:Unreconciled or concurrently modified state can trigger unintended replacement or lost configuration. The relevant correction is to review Terraform plan and state reconciliation, using approved state locking and import procedures before apply.
B:Apply every plan without checking destructive changes. The proposed change targets the wrong mechanism or lacks essential validation. Terraform compares declared configuration with tracked state; safe operations depend on accurate state and coordination. Relevant evidence is Terraform plan diff, resource identifiers, locked state backend and verified current infrastructure.
D:Unreconciled or concurrently modified state can trigger unintended replacement or lost configuration. The appropriate action remains to review Terraform plan and state reconciliation, using approved state locking and import procedures before apply.
Question 972
A Terraform apply wants to recreate an existing NX-OS network object because its state file is out of sync. What should the engineer inspect to confirm the actual state?
- A successful SSH session without script output, API responses or resulting state.
- A saved script file that has never been executed or tested.
- An API endpoint returning HTML instead of validated inventory or outcome.
- Terraform plan diff, resource identifiers, locked state backend and verified current infrastructure.
Explanation
Correct Answer
D:These observations test the actual Terraform planning and state mechanism rather than a superficial management status. Terraform compares declared configuration with tracked state; safe operations depend on accurate state and coordination.
Incorrect Answers
A:This information cannot independently verify Terraform planning and state. The decisive records instead include Terraform plan diff, resource identifiers, locked state backend and verified current infrastructure.
B:This information cannot independently verify Terraform planning and state. Terraform compares declared configuration with tracked state; safe operations depend on accurate state and coordination.
C:This information cannot independently verify Terraform planning and state. An API endpoint returning HTML instead of validated inventory or outcome.
Question 973
A Terraform apply wants to recreate an existing NX-OS network object because its state file is out of sync. What technical behavior underlies the correct decision?
- Terraform compares declared configuration with tracked state; safe operations depend on accurate state and coordination.
- An HTTP 200 connection proves the intended device state was changed correctly.
- One initial successful run guarantees all later automation remains correct.
- A script saved on a controller always runs successfully on every target.
Explanation
Correct Answer
A:Validation depends on Terraform plan diff, resource identifiers, locked state backend and verified current infrastructure. This explains why the most appropriate response is to review Terraform plan and state reconciliation, using approved state locking and import procedures before apply.
Incorrect Answers
B:An HTTP 200 connection proves the intended device state was changed correctly. This is an incorrect generalization for Terraform planning and state. The applicable technical behavior is that Terraform compares declared configuration with tracked state; safe operations depend on accurate state and coordination. The operator should verify Terraform plan diff, resource identifiers, locked state backend and verified current infrastructure.
C:One initial successful run guarantees all later automation remains correct. This is an incorrect generalization for Terraform planning and state. The applicable technical behavior is that Terraform compares declared configuration with tracked state; safe operations depend on accurate state and coordination. The operator should verify Terraform plan diff, resource identifiers, locked state backend and verified current infrastructure.
D:A script saved on a controller always runs successfully on every target. This is an incorrect generalization for Terraform planning and state. The applicable technical behavior is that Terraform compares declared configuration with tracked state; safe operations depend on accurate state and coordination. The operator should verify Terraform plan diff, resource identifiers, locked state backend and verified current infrastructure.
Question 974
A Terraform apply wants to recreate an existing NX-OS network object because its state file is out of sync. Assume an engineer instead chooses to delete the state file to make Terraform forget the running infrastructure. Which resulting risk or fault should the reviewer identify?
- Verifying server policy references is the reason the missing references occurred.
- Unreconciled or concurrently modified state can trigger unintended replacement or lost configuration.
- Keeping API error responses is the underlying cause of failed automation.
- Reviewing a Terraform plan makes correct configuration objects disappear.
Explanation
Correct Answer
B:Terraform compares declared configuration with tracked state; safe operations depend on accurate state and coordination. That is the direct consequence of choosing the misleading shortcut.
Incorrect Answers
A:This does not explain the actual Terraform planning and state defect after the shortcut. The meaningful failure is that unreconciled or concurrently modified state can trigger unintended replacement or lost configuration.
C:This does not explain the actual Terraform planning and state defect after the shortcut. The relevant evidence is Terraform plan diff, resource identifiers, locked state backend and verified current infrastructure.
D:This does not explain the actual Terraform planning and state defect after the shortcut. In the given case, a Terraform apply wants to recreate an existing NX-OS network object because its state file is out of sync.
Question 975
A Terraform apply wants to recreate an existing NX-OS network object because its state file is out of sync. The observed failure is: unreconciled or concurrently modified state can trigger unintended replacement or lost configuration. Which remediation most directly restores the intended behavior?
- Apply every plan without checking destructive changes.
- Give all operators an unlocked local copy of the same shared state.
- Restore accurate state tracking and locked workflows, then approve only an expected plan.
- Delete the state file to make Terraform forget the running infrastructure.
Explanation
Correct Answer
C:Terraform compares declared configuration with tracked state; safe operations depend on accurate state and coordination. This addresses the observable fault while preserving a check of the expected result.
Incorrect Answers
A: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.
B: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.
D: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.
Question 976
Two operators run Terraform on one fabric and overwrite each other's state when remote locking is absent. Which operator action best meets this technical requirement?
- On this affected device, the engineer should apply every plan without checking destructive changes.
- On this affected device, the engineer should give all operators an unlocked local copy of the same shared state.
- On this affected device, the engineer should delete the state file to make Terraform forget the running infrastructure.
- On this affected device, the engineer should review Terraform plan and state reconciliation, using approved state locking and import procedures before apply.
Explanation
Correct Answer
D:This directly addresses Terraform planning and state because Terraform compares declared configuration with tracked state; safe operations depend on accurate state and coordination.
Incorrect Answers
A:Apply every plan without checking destructive changes. The proposed change targets the wrong mechanism or lacks essential validation. Terraform compares declared configuration with tracked state; safe operations depend on accurate state and coordination. Relevant evidence is Terraform plan diff, resource identifiers, locked state backend and verified current infrastructure.
B:Unreconciled or concurrently modified state can trigger unintended replacement or lost configuration. Give all operators an unlocked local copy of the same shared state.
C:Unreconciled or concurrently modified state can trigger unintended replacement or lost configuration. Delete the state file to make Terraform forget the running infrastructure.
Question 977
Two operators run Terraform on one fabric and overwrite each other's state when remote locking is absent. Which collection of observations most directly tests the suspected cause?
- For this deployment, examine Terraform plan diff, resource identifiers, locked state backend and verified current infrastructure.
- For this deployment, examine a dashboard snapshot detached from actual target configuration and logs.
- For this deployment, examine a successful SSH session without script output, API responses or resulting state.
- For this deployment, examine a saved script file that has never been executed or tested.
Explanation
Correct Answer
A:These observations test the actual Terraform planning and state mechanism rather than a superficial management status. They should be checked after review Terraform plan and state reconciliation, using approved state locking and import procedures before apply.
Incorrect Answers
B:This information cannot independently verify Terraform planning and state. A dashboard snapshot detached from actual target configuration and logs.
C:This information cannot independently verify Terraform planning and state. A successful SSH session without script output, API responses or resulting state.
D:This information cannot independently verify Terraform planning and state. A saved script file that has never been executed or tested.
Question 978
Two operators run Terraform on one fabric and overwrite each other's state when remote locking is absent. Which statement most accurately explains this scenario?
- For this condition, the applicable principle is that a script saved on a controller always runs successfully on every target.
- For this condition, the applicable principle is that Terraform compares declared configuration with tracked state; safe operations depend on accurate state and coordination.
- For this condition, the applicable principle is that an HTTP 200 connection proves the intended device state was changed correctly.
- For this condition, the applicable principle is that cloud or on-box automation removes the need to validate inputs and outcomes.
Explanation
Correct Answer
B:Validation depends on Terraform plan diff, resource identifiers, locked state backend and verified current infrastructure. Terraform compares declared configuration with tracked state; safe operations depend on accurate state and coordination.
Incorrect Answers
A:A script saved on a controller always runs successfully on every target. This is an incorrect generalization for Terraform planning and state. The applicable technical behavior is that Terraform compares declared configuration with tracked state; safe operations depend on accurate state and coordination. The operator should verify Terraform plan diff, resource identifiers, locked state backend and verified current infrastructure.
C:An HTTP 200 connection proves the intended device state was changed correctly. This is an incorrect generalization for Terraform planning and state. The applicable technical behavior is that Terraform compares declared configuration with tracked state; safe operations depend on accurate state and coordination. The operator should verify Terraform plan diff, resource identifiers, locked state backend and verified current infrastructure.
D:Cloud or on-box automation removes the need to validate inputs and outcomes. This is an incorrect generalization for Terraform planning and state. The applicable technical behavior is that Terraform compares declared configuration with tracked state; safe operations depend on accurate state and coordination. The operator should verify Terraform plan diff, resource identifiers, locked state backend and verified current infrastructure.
Question 979
Two operators run Terraform on one fabric and overwrite each other's state when remote locking is absent. Assume an engineer instead chooses to delete the state file to make Terraform forget the running infrastructure. What is the principal technical consequence of the mistaken choice?
- The resulting defect is that reviewing a Terraform plan makes correct configuration objects disappear.
- The resulting defect is that using a dry-run test inherently disables every network management API.
- The resulting defect is that unreconciled or concurrently modified state can trigger unintended replacement or lost configuration.
- The resulting defect is that keeping API error responses is the underlying cause of failed automation.
Explanation
Correct Answer
C:Terraform compares declared configuration with tracked state; safe operations depend on accurate state and coordination. The proper corrective action is to review Terraform plan and state reconciliation, using approved state locking and import procedures before apply.
Incorrect Answers
A:This does not explain the actual Terraform planning and state defect after the shortcut. Reviewing a Terraform plan makes correct configuration objects disappear.
B:This does not explain the actual Terraform planning and state defect after the shortcut. Using a dry-run test inherently disables every network management API.
D:This does not explain the actual Terraform planning and state defect after the shortcut. Keeping API error responses is the underlying cause of failed automation.
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.