Cisco 350-601 Practice Test 97
Question 960
Nexus Dashboard reports inter-fabric anomalies and operations wants evidence from topology and historical telemetry to localize them. The observed failure is: a single healthy interface counter does not establish cross-fabric application path health. What is the BEST controlled recovery once this failure is recognized?
- The controlled remediation is to interpret any one dashboard warning as an automatic command to reboot every switch.
- The controlled remediation is to assume Nexus Dashboard itself automatically replaces all physical links.
- The controlled remediation is to disable telemetry export because a UI score is sufficient proof.
- The controlled remediation is to correlate Dashboard findings with device telemetry, remediate the underlying fault, and verify improved health.
Explanation
Correct Answer
D:Nexus Dashboard can aggregate fabric-wide monitoring and operational insights beyond one switch at a time. Validate against dashboard fabric inventory, health events, historical trends and affected node or link mapping.
Incorrect Answers
A:Interpret any one dashboard warning as an automatic command to reboot every switch. This would not reliably restore service after the stated fault. A single healthy interface counter does not establish cross-fabric application path health. The controlled recovery is to correlate Dashboard findings with device telemetry, remediate the underlying fault, and verify improved health.
B:Assume Nexus Dashboard itself automatically replaces all physical links. This would not reliably restore service after the stated fault. A single healthy interface counter does not establish cross-fabric application path health. The controlled recovery is to correlate Dashboard findings with device telemetry, remediate the underlying fault, and verify improved health.
C:Disable telemetry export because a UI score is sufficient proof. This would not reliably restore service after the stated fault. A single healthy interface counter does not establish cross-fabric application path health. The controlled recovery is to correlate Dashboard findings with device telemetry, remediate the underlying fault, and verify improved health.
Question 961
A PowerShell script uses an incorrect authorization header when requesting inventory from Intersight and receives an access denial. What is the BEST supported implementation or corrective action?
- Use supported PowerShell HTTP client methods with correct API authentication and typed JSON response checks.
- Assume any HTML login page is a valid JSON inventory result.
- Place API secrets in a publicly readable script repository.
- Hard-code successful output regardless of server response.
Explanation
Correct Answer
A:This directly addresses powerShell REST automation because powerShell can orchestrate management REST APIs but must handle authentication, serialization and error conditions. Confirm the change against powerShell request headers, HTTP error codes, parsed JSON properties and verified inventory count.
Incorrect Answers
B:Ignoring HTTP and schema errors can make automation act on absent or misleading inventory. The relevant correction is to use supported PowerShell HTTP client methods with correct API authentication and typed JSON response checks.
C:Place API secrets in a publicly readable script repository. The proposed change targets the wrong mechanism or lacks essential validation. PowerShell can orchestrate management REST APIs but must handle authentication, serialization and error conditions. Relevant evidence is powerShell request headers, HTTP error codes, parsed JSON properties and verified inventory count.
D:Ignoring HTTP and schema errors can make automation act on absent or misleading inventory. The appropriate action remains to use supported PowerShell HTTP client methods with correct API authentication and typed JSON response checks.
Question 962
A PowerShell script uses an incorrect authorization header when requesting inventory from Intersight and receives an access denial. Which evidence BEST verifies the intended technical behavior?
- An old CI job name without run records or configuration diffs.
- PowerShell request headers, HTTP error codes, parsed JSON properties and verified inventory count.
- An API endpoint returning HTML instead of validated inventory or outcome.
- A dashboard snapshot detached from actual target configuration and logs.
Explanation
Correct Answer
B:These observations test the actual powerShell REST automation mechanism rather than a superficial management status. PowerShell can orchestrate management REST APIs but must handle authentication, serialization and error conditions.
Incorrect Answers
A:An old CI job name without run records or configuration diffs. This information cannot independently verify powerShell REST automation. The decisive records instead include 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.
C:An API endpoint returning HTML instead of validated inventory or outcome. This information cannot independently verify powerShell REST automation. The decisive records instead include 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.
D:A dashboard snapshot detached from actual target configuration and logs. This information cannot independently verify powerShell REST automation. The decisive records instead include 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.
Question 963
A PowerShell script uses an incorrect authorization header when requesting inventory from Intersight and receives an access denial. Which principle BEST explains why the recommended solution is appropriate?
- One initial successful run guarantees all later automation remains correct.
- Cloud or on-box automation removes the need to validate inputs and outcomes.
- PowerShell can orchestrate management REST APIs but must handle authentication, serialization and error conditions.
- The existence of a state file proves all remote resources match desired state.
Explanation
Correct Answer
C:This explains why the most appropriate response is to use supported PowerShell HTTP client methods with correct API authentication and typed JSON response checks. Validation depends on powerShell request headers, HTTP error codes, parsed JSON properties and verified inventory count.
Incorrect Answers
A:One initial successful run guarantees all later automation remains correct. This is an incorrect generalization for powerShell REST automation. The applicable technical behavior is that powerShell can orchestrate management REST APIs but must handle authentication, serialization and error conditions. The operator should verify powerShell request headers, HTTP error codes, parsed JSON properties and verified inventory count.
B:Cloud or on-box automation removes the need to validate inputs and outcomes. This is an incorrect generalization for powerShell REST automation. The applicable technical behavior is that powerShell can orchestrate management REST APIs but must handle authentication, serialization and error conditions. The operator should verify powerShell request headers, HTTP error codes, parsed JSON properties and verified inventory count.
D:The existence of a state file proves all remote resources match desired state. This is an incorrect generalization for powerShell REST automation. The applicable technical behavior is that powerShell can orchestrate management REST APIs but must handle authentication, serialization and error conditions. The operator should verify powerShell request headers, HTTP error codes, parsed JSON properties and verified inventory count.
Question 964
A PowerShell script uses an incorrect authorization header when requesting inventory from Intersight and receives an access denial. Assume an engineer instead chooses to assume any HTML login page is a valid JSON inventory result. What is the MOST significant failure introduced by that shortcut?
- Using a dry-run test inherently disables every network management API.
- Storing execution logs causes the original script to use invalid parameters.
- Verifying server policy references is the reason the missing references occurred.
- Ignoring HTTP and schema errors can make automation act on absent or misleading inventory.
Explanation
Correct Answer
D:The proper corrective action is to use supported PowerShell HTTP client methods with correct API authentication and typed JSON response checks. PowerShell can orchestrate management REST APIs but must handle authentication, serialization and error conditions.
Incorrect Answers
A:This does not explain the actual powerShell REST automation defect after the shortcut. The meaningful failure is that ignoring HTTP and schema errors can make automation act on absent or misleading inventory.
B:This does not explain the actual powerShell REST automation defect after the shortcut. The relevant evidence is powerShell request headers, HTTP error codes, parsed JSON properties and verified inventory count.
C:This does not explain the actual powerShell REST automation defect after the shortcut. Verifying server policy references is the reason the missing references occurred.
Question 965
A PowerShell script uses an incorrect authorization header when requesting inventory from Intersight and receives an access denial. The observed failure is: ignoring HTTP and schema errors can make automation act on absent or misleading inventory. What is the BEST controlled recovery once this failure is recognized?
- Correct request signing or token flow and response handling, then validate the actual target objects.
- Place API secrets in a publicly readable script repository.
- Hard-code successful output regardless of server response.
- Assume any HTML login page is a valid JSON inventory result.
Explanation
Correct Answer
A:Validate against powerShell request headers, HTTP error codes, parsed JSON properties and verified inventory count. This addresses the observable fault while preserving a check of the expected result.
Incorrect Answers
B: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.
C: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.
D: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.
Question 966
A network workflow written in PowerShell fails to parse a JSON API response and treats an error field as valid inventory. Which configuration decision MOST directly resolves the issue?
- On this affected device, the engineer should place API secrets in a publicly readable script repository.
- On this affected device, the engineer should use supported PowerShell HTTP client methods with correct API authentication and typed JSON response checks.
- On this affected device, the engineer should hard-code successful output regardless of server response.
- On this affected device, the engineer should assume any HTML login page is a valid JSON inventory result.
Explanation
Correct Answer
B:This directly addresses powerShell REST automation because powerShell can orchestrate management REST APIs but must handle authentication, serialization and error conditions.
Incorrect Answers
A:Place API secrets in a publicly readable script repository. The proposed change targets the wrong mechanism or lacks essential validation. PowerShell can orchestrate management REST APIs but must handle authentication, serialization and error conditions. Relevant evidence is powerShell request headers, HTTP error codes, parsed JSON properties and verified inventory count.
C:Ignoring HTTP and schema errors can make automation act on absent or misleading inventory. In the given case, a network workflow written in PowerShell fails to parse a JSON API response and treats an error field as valid inventory.
D:Ignoring HTTP and schema errors can make automation act on absent or misleading inventory. Assume any HTML login page is a valid JSON inventory result.
Question 967
A network workflow written in PowerShell fails to parse a JSON API response and treats an error field as valid inventory. What should the engineer inspect to confirm the actual state?
- For this deployment, examine a successful SSH session without script output, API responses or resulting state.
- For this deployment, examine an old CI job name without run records or configuration diffs.
- For this deployment, examine powerShell request headers, HTTP error codes, parsed JSON properties and verified inventory count.
- For this deployment, examine an API endpoint returning HTML instead of validated inventory or outcome.
Explanation
Correct Answer
C:These observations test the actual powerShell REST automation mechanism rather than a superficial management status. They should be checked after use supported PowerShell HTTP client methods with correct API authentication and typed JSON response checks.
Incorrect Answers
A:A successful SSH session without script output, API responses or resulting state. This information cannot independently verify powerShell REST automation. The decisive records instead include 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.
B:An old CI job name without run records or configuration diffs. This information cannot independently verify powerShell REST automation. The decisive records instead include 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.
D:An API endpoint returning HTML instead of validated inventory or outcome. This information cannot independently verify powerShell REST automation. The decisive records instead include 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.
Question 968
A network workflow written in PowerShell fails to parse a JSON API response and treats an error field as valid inventory. What technical behavior underlies the correct decision?
- 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 a script saved on a controller always runs successfully on every target.
- For this condition, the applicable principle is that powerShell can orchestrate management REST APIs but must handle authentication, serialization and error conditions.
Explanation
Correct Answer
D:This explains why the most appropriate response is to use supported PowerShell HTTP client methods with correct API authentication and typed JSON response checks.
Incorrect Answers
A:The existence of a state file proves all remote resources match desired state. This is an incorrect generalization for powerShell REST automation. The applicable technical behavior is that powerShell can orchestrate management REST APIs but must handle authentication, serialization and error conditions. The operator should verify powerShell request headers, HTTP error codes, parsed JSON properties and verified inventory count.
B:One initial successful run guarantees all later automation remains correct. This is an incorrect generalization for powerShell REST automation. The applicable technical behavior is that powerShell can orchestrate management REST APIs but must handle authentication, serialization and error conditions. The operator should verify powerShell request headers, HTTP error codes, parsed JSON properties and verified inventory count.
C:A script saved on a controller always runs successfully on every target. This is an incorrect generalization for powerShell REST automation. The applicable technical behavior is that powerShell can orchestrate management REST APIs but must handle authentication, serialization and error conditions. The operator should verify powerShell request headers, HTTP error codes, parsed JSON properties and verified inventory count.
Question 969
A network workflow written in PowerShell fails to parse a JSON API response and treats an error field as valid inventory. Assume an engineer instead chooses to assume any HTML login page is a valid JSON inventory result. Which resulting risk or fault should the reviewer identify?
- The resulting defect is that ignoring HTTP and schema errors can make automation act on absent or misleading inventory.
- The resulting defect is that verifying server policy references is the reason the missing references occurred.
- The resulting defect is that keeping API error responses is the underlying cause of failed automation.
- The resulting defect is that storing execution logs causes the original script to use invalid parameters.
Explanation
Correct Answer
A:The proper corrective action is to use supported PowerShell HTTP client methods with correct API authentication and typed JSON response checks. That is the direct consequence of choosing the misleading shortcut.
Incorrect Answers
B:This does not explain the actual powerShell REST automation defect after the shortcut. In the given case, a network workflow written in PowerShell fails to parse a JSON API response and treats an error field as valid inventory.
C:This does not explain the actual powerShell REST automation defect after the shortcut. Keeping API error responses is the underlying cause of failed automation.
D:This does not explain the actual powerShell REST automation defect after the shortcut. Storing execution logs causes the original script to use invalid parameters.
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.