Cisco 350-601 Practice Test 89
Question 880
A script uses standard Bash utilities on a Nexus platform without verifying the supported Bash access mode. The observed failure is: running Bash syntax in the NX-OS configuration parser will not perform the intended shell operation. What is the BEST controlled recovery once this failure is recognized?
- The controlled remediation is to use Fibre Channel zoning to provide UNIX shell syntax translation.
- The controlled remediation is to disable NX-OS CLI parsing globally to enable all Bash commands.
- The controlled remediation is to treat every Linux command as equivalent to an NX-OS configuration command.
- The controlled remediation is to enter the supported shell mode and execute authorized diagnostics without altering switch configuration accidentally.
Explanation
Correct Answer
D:This addresses the observable fault while preserving a check of the expected result. Validate against supported shell launch, command interpreter output and permission boundary.
Incorrect Answers
A:Use Fibre Channel zoning to provide UNIX shell syntax translation. This would not reliably restore service after the stated fault. Running Bash syntax in the NX-OS configuration parser will not perform the intended shell operation. The controlled recovery is to enter the supported shell mode and execute authorized diagnostics without altering switch configuration accidentally.
B:Disable NX-OS CLI parsing globally to enable all Bash commands. This would not reliably restore service after the stated fault. Running Bash syntax in the NX-OS configuration parser will not perform the intended shell operation. The controlled recovery is to enter the supported shell mode and execute authorized diagnostics without altering switch configuration accidentally.
C:Treat every Linux command as equivalent to an NX-OS configuration command. This would not reliably restore service after the stated fault. Running Bash syntax in the NX-OS configuration parser will not perform the intended shell operation. The controlled recovery is to enter the supported shell mode and execute authorized diagnostics without altering switch configuration accidentally.
Question 881
A network program gets HTTP success to an NX-API endpoint but its body is rejected because it sends malformed JSON. What is the BEST supported implementation or corrective action?
- Match the NX-API endpoint, required content type, supported JSON or XML schema and authorized API action.
- Put raw CLI syntax in an unrelated web form and expect NX-API to parse it.
- Assume any syntactically valid JSON represents a supported NX-OS method.
- Disable TLS verification and ignore all API error responses.
Explanation
Correct Answer
A:This directly addresses nX-API REST request format because nX-API accepts structured requests whose encoding and endpoint semantics must match supported device APIs. Confirm the change against HTTP status and response body, NX-API payload schema, authentication details and device configuration readback.
Incorrect Answers
B:A reachable TCP or HTTPS endpoint does not imply that the submitted API payload is valid. The relevant correction is to match the NX-API endpoint, required content type, supported JSON or XML schema and authorized API action.
C:Assume any syntactically valid JSON represents a supported NX-OS method. The proposed change targets the wrong mechanism or lacks essential validation. NX-API accepts structured requests whose encoding and endpoint semantics must match supported device APIs. Relevant evidence is HTTP status and response body, NX-API payload schema, authentication details and device configuration readback.
D:A reachable TCP or HTTPS endpoint does not imply that the submitted API payload is valid. The appropriate action remains to match the NX-API endpoint, required content type, supported JSON or XML schema and authorized API action.
Question 882
A network program gets HTTP success to an NX-API endpoint but its body is rejected because it sends malformed JSON. Which evidence BEST verifies the intended technical behavior?
- A dashboard snapshot detached from actual target configuration and logs.
- HTTP status and response body, NX-API payload schema, authentication details and device configuration readback.
- 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 nX-API REST request format mechanism rather than a superficial management status. NX-API accepts structured requests whose encoding and endpoint semantics must match supported device APIs.
Incorrect Answers
A:This information cannot independently verify nX-API REST request format. The decisive records instead include HTTP status and response body, NX-API payload schema, authentication details and device configuration readback.
C:This information cannot independently verify nX-API REST request format. NX-API accepts structured requests whose encoding and endpoint semantics must match supported device APIs.
D:This information cannot independently verify nX-API REST request format. In the given case, a network program gets HTTP success to an NX-API endpoint but its body is rejected because it sends malformed JSON.
Question 883
A network program gets HTTP success to an NX-API endpoint but its body is rejected because it sends malformed JSON. Which principle BEST explains why the recommended solution is appropriate?
- 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.
- NX-API accepts structured requests whose encoding and endpoint semantics must match supported device APIs.
- Cloud or on-box automation removes the need to validate inputs and outcomes.
Explanation
Correct Answer
C:Validation depends on HTTP status and response body, NX-API payload schema, authentication details and device configuration readback. This explains why the most appropriate response is to match the NX-API endpoint, required content type, supported JSON or XML schema and authorized API action.
Incorrect Answers
A:The existence of a state file proves all remote resources match desired state. This is an incorrect generalization for nX-API REST request format. The applicable technical behavior is that nX-API accepts structured requests whose encoding and endpoint semantics must match supported device APIs. The operator should verify HTTP status and response body, NX-API payload schema, authentication details and device configuration readback.
B:An HTTP 200 connection proves the intended device state was changed correctly. This is an incorrect generalization for nX-API REST request format. The applicable technical behavior is that nX-API accepts structured requests whose encoding and endpoint semantics must match supported device APIs. The operator should verify HTTP status and response body, NX-API payload schema, authentication details and device configuration readback.
D:Cloud or on-box automation removes the need to validate inputs and outcomes. This is an incorrect generalization for nX-API REST request format. The applicable technical behavior is that nX-API accepts structured requests whose encoding and endpoint semantics must match supported device APIs. The operator should verify HTTP status and response body, NX-API payload schema, authentication details and device configuration readback.
Question 884
A network program gets HTTP success to an NX-API endpoint but its body is rejected because it sends malformed JSON. Assume an engineer instead chooses to put raw CLI syntax in an unrelated web form and expect NX-API to parse it. What is the MOST significant failure introduced by that shortcut?
- 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.
- A reachable TCP or HTTPS endpoint does not imply that the submitted API payload is valid.
Explanation
Correct Answer
D:The proper corrective action is to match the NX-API endpoint, required content type, supported JSON or XML schema and authorized API action. NX-API accepts structured requests whose encoding and endpoint semantics must match supported device APIs.
Incorrect Answers
A:This does not explain the actual nX-API REST request format defect after the shortcut. The meaningful failure is that a reachable TCP or HTTPS endpoint does not imply that the submitted API payload is valid.
B:This does not explain the actual nX-API REST request format defect after the shortcut. The relevant evidence is HTTP status and response body, NX-API payload schema, authentication details and device configuration readback.
C:This does not explain the actual nX-API REST request format defect after the shortcut. Storing execution logs causes the original script to use invalid parameters.
Question 885
A network program gets HTTP success to an NX-API endpoint but its body is rejected because it sends malformed JSON. The observed failure is: a reachable TCP or HTTPS endpoint does not imply that the submitted API payload is valid. What is the BEST controlled recovery once this failure is recognized?
- Correct headers, payload structure and API privileges, then verify resulting running state.
- Assume any syntactically valid JSON represents a supported NX-OS method.
- Disable TLS verification and ignore all API error responses.
- Put raw CLI syntax in an unrelated web form and expect NX-API to parse it.
Explanation
Correct Answer
A:Validate against HTTP status and response body, NX-API payload schema, authentication details and device configuration readback. This addresses the observable fault while preserving a check of the expected result.
Incorrect Answers
B:Assume any syntactically valid JSON represents a supported NX-OS method. This would not reliably restore service after the stated fault. A reachable TCP or HTTPS endpoint does not imply that the submitted API payload is valid. The controlled recovery is to correct headers, payload structure and API privileges, then verify resulting running state.
C:Disable TLS verification and ignore all API error responses. This would not reliably restore service after the stated fault. A reachable TCP or HTTPS endpoint does not imply that the submitted API payload is valid. The controlled recovery is to correct headers, payload structure and API privileges, then verify resulting running state.
D:Put raw CLI syntax in an unrelated web form and expect NX-API to parse it. This would not reliably restore service after the stated fault. A reachable TCP or HTTPS endpoint does not imply that the submitted API payload is valid. The controlled recovery is to correct headers, payload structure and API privileges, then verify resulting running state.
Question 886
An automation client attempts to configure NX-OS with XML content while its request headers declare the wrong media type. Which configuration decision MOST directly resolves the issue?
- On this affected device, the engineer should assume any syntactically valid JSON represents a supported NX-OS method.
- On this affected device, the engineer should match the NX-API endpoint, required content type, supported JSON or XML schema and authorized API action.
- On this affected device, the engineer should disable TLS verification and ignore all API error responses.
- On this affected device, the engineer should put raw CLI syntax in an unrelated web form and expect NX-API to parse it.
Explanation
Correct Answer
B:This directly addresses nX-API REST request format because nX-API accepts structured requests whose encoding and endpoint semantics must match supported device APIs.
Incorrect Answers
A:Assume any syntactically valid JSON represents a supported NX-OS method. The proposed change targets the wrong mechanism or lacks essential validation. NX-API accepts structured requests whose encoding and endpoint semantics must match supported device APIs. Relevant evidence is HTTP status and response body, NX-API payload schema, authentication details and device configuration readback.
C:A reachable TCP or HTTPS endpoint does not imply that the submitted API payload is valid. In the given case, an automation client attempts to configure NX-OS with XML content while its request headers declare the wrong media type.
D:A reachable TCP or HTTPS endpoint does not imply that the submitted API payload is valid. Put raw CLI syntax in an unrelated web form and expect NX-API to parse it.
Question 887
An automation client attempts to configure NX-OS with XML content while its request headers declare the wrong media type. What should the engineer inspect to confirm the actual state?
- 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 HTTP status and response body, NX-API payload schema, authentication details and device configuration readback.
- For this deployment, examine an old CI job name without run records or configuration diffs.
Explanation
Correct Answer
C:These observations test the actual nX-API REST request format mechanism rather than a superficial management status. They should be checked after match the NX-API endpoint, required content type, supported JSON or XML schema and authorized API action.
Incorrect Answers
A:This information cannot independently verify nX-API REST request format. An API endpoint returning HTML instead of validated inventory or outcome.
B:This information cannot independently verify nX-API REST request format. In the given case, an automation client attempts to configure NX-OS with XML content while its request headers declare the wrong media type.
D:This information cannot independently verify nX-API REST request format. An old CI job name without run records or configuration diffs.
Question 888
An automation client attempts to configure NX-OS with XML content while its request headers declare the wrong media type. What technical behavior underlies the correct decision?
- 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 nX-API accepts structured requests whose encoding and endpoint semantics must match supported device APIs.
Explanation
Correct Answer
D:Validation depends on HTTP status and response body, NX-API payload schema, authentication details and device configuration readback.
Incorrect Answers
A:Cloud or on-box automation removes the need to validate inputs and outcomes. This is an incorrect generalization for nX-API REST request format. The applicable technical behavior is that nX-API accepts structured requests whose encoding and endpoint semantics must match supported device APIs. The operator should verify HTTP status and response body, NX-API payload schema, authentication details and device configuration readback.
B:The existence of a state file proves all remote resources match desired state. This is an incorrect generalization for nX-API REST request format. The applicable technical behavior is that nX-API accepts structured requests whose encoding and endpoint semantics must match supported device APIs. The operator should verify HTTP status and response body, NX-API payload schema, authentication details and device configuration readback.
C:One initial successful run guarantees all later automation remains correct. This is an incorrect generalization for nX-API REST request format. The applicable technical behavior is that nX-API accepts structured requests whose encoding and endpoint semantics must match supported device APIs. The operator should verify HTTP status and response body, NX-API payload schema, authentication details and device configuration readback.
Question 889
An automation client attempts to configure NX-OS with XML content while its request headers declare the wrong media type. Assume an engineer instead chooses to put raw CLI syntax in an unrelated web form and expect NX-API to parse it. Which resulting risk or fault should the reviewer identify?
- The resulting defect is that a reachable TCP or HTTPS endpoint does not imply that the submitted API payload is valid.
- 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 match the NX-API endpoint, required content type, supported JSON or XML schema and authorized API action. That is the direct consequence of choosing the misleading shortcut.
Incorrect Answers
B:This does not explain the actual nX-API REST request format defect after the shortcut. In the given case, an automation client attempts to configure NX-OS with XML content while its request headers declare the wrong media type.
C:This does not explain the actual nX-API REST request format defect after the shortcut. Verifying server policy references is the reason the missing references occurred.
D:This does not explain the actual nX-API REST request format defect after the shortcut. Using a dry-run test inherently disables every network management API.
Question 890
An automation client attempts to configure NX-OS with XML content while its request headers declare the wrong media type. The observed failure is: a reachable TCP or HTTPS endpoint does not imply that the submitted API payload is valid. Which remediation most directly restores the intended behavior?
- The controlled remediation is to disable TLS verification and ignore all API error responses.
- The controlled remediation is to correct headers, payload structure and API privileges, then verify resulting running state.
- The controlled remediation is to put raw CLI syntax in an unrelated web form and expect NX-API to parse it.
- The controlled remediation is to assume any syntactically valid JSON represents a supported NX-OS method.
Explanation
Correct Answer
B:Validate against HTTP status and response body, NX-API payload schema, authentication details and device configuration readback. NX-API accepts structured requests whose encoding and endpoint semantics must match supported device APIs.
Incorrect Answers
A:Disable TLS verification and ignore all API error responses. This would not reliably restore service after the stated fault. A reachable TCP or HTTPS endpoint does not imply that the submitted API payload is valid. The controlled recovery is to correct headers, payload structure and API privileges, then verify resulting running state.
C:Put raw CLI syntax in an unrelated web form and expect NX-API to parse it. This would not reliably restore service after the stated fault. A reachable TCP or HTTPS endpoint does not imply that the submitted API payload is valid. The controlled recovery is to correct headers, payload structure and API privileges, then verify resulting running state.
D:Assume any syntactically valid JSON represents a supported NX-OS method. This would not reliably restore service after the stated fault. A reachable TCP or HTTPS endpoint does not imply that the submitted API payload is valid. The controlled recovery is to correct headers, payload structure and API privileges, then verify resulting running state.