Cisco 350-601 Practice Test 90
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.
Question 891
An API token can read NX-OS operational data but fails when the automation tries to modify an interface. Which configuration decision MOST directly resolves the issue?
- Give every API consumer unrestricted administrator privileges by default.
- Disable NX-OS RBAC entirely instead of scoping the required command.
- Apply the minimum authorized NX-OS role and API permissions required for the operation.
- Change the device hostname to bypass API role enforcement.
Explanation
Correct Answer
C:This directly addresses nX-API authorization control because successful authentication does not necessarily authorize configuration operations under RBAC. Confirm the change against aPI authentication and authorization response, user role, permitted commands and audit log.
Incorrect Answers
A:Using a read-only role for write requests produces predictable authorization failures. The relevant correction is to apply the minimum authorized NX-OS role and API permissions required for the operation.
B:Disable NX-OS RBAC entirely instead of scoping the required command. The proposed change targets the wrong mechanism or lacks essential validation. Successful authentication does not necessarily authorize configuration operations under RBAC. Relevant evidence is aPI authentication and authorization response, user role, permitted commands and audit log.
D:Using a read-only role for write requests produces predictable authorization failures. The appropriate action remains to apply the minimum authorized NX-OS role and API permissions required for the operation.
Question 892
An API token can read NX-OS operational data but fails when the automation tries to modify an interface. What should the engineer inspect to confirm the actual state?
- An API endpoint returning HTML instead of validated inventory or outcome.
- A successful SSH session without script output, API responses or resulting state.
- An old CI job name without run records or configuration diffs.
- API authentication and authorization response, user role, permitted commands and audit log.
Explanation
Correct Answer
D:These observations test the actual nX-API authorization control mechanism rather than a superficial management status. Successful authentication does not necessarily authorize configuration operations under RBAC.
Incorrect Answers
A:An API endpoint returning HTML instead of validated inventory or outcome. This information cannot independently verify nX-API authorization control. The decisive records instead include aPI authentication and authorization response, user role, permitted commands and audit log. Successful authentication does not necessarily authorize configuration operations under RBAC.
B:A successful SSH session without script output, API responses or resulting state. This information cannot independently verify nX-API authorization control. The decisive records instead include aPI authentication and authorization response, user role, permitted commands and audit log. Successful authentication does not necessarily authorize configuration operations under RBAC.
C:An old CI job name without run records or configuration diffs. This information cannot independently verify nX-API authorization control. The decisive records instead include aPI authentication and authorization response, user role, permitted commands and audit log. Successful authentication does not necessarily authorize configuration operations under RBAC.
Question 893
An API token can read NX-OS operational data but fails when the automation tries to modify an interface. What technical behavior underlies the correct decision?
- Successful authentication does not necessarily authorize configuration operations under RBAC.
- A script saved on a controller always runs successfully on every target.
- The existence of a state file proves all remote resources match desired state.
- One initial successful run guarantees all later automation remains correct.
Explanation
Correct Answer
A:Validation depends on aPI authentication and authorization response, user role, permitted commands and audit log. This explains why the most appropriate response is to apply the minimum authorized NX-OS role and API permissions required for the operation.
Incorrect Answers
B:A script saved on a controller always runs successfully on every target. This is an incorrect generalization for nX-API authorization control. The applicable technical behavior is that successful authentication does not necessarily authorize configuration operations under RBAC. The operator should verify aPI authentication and authorization response, user role, permitted commands and audit log.
C:The existence of a state file proves all remote resources match desired state. This is an incorrect generalization for nX-API authorization control. The applicable technical behavior is that successful authentication does not necessarily authorize configuration operations under RBAC. The operator should verify aPI authentication and authorization response, user role, permitted commands and audit log.
D:One initial successful run guarantees all later automation remains correct. This is an incorrect generalization for nX-API authorization control. The applicable technical behavior is that successful authentication does not necessarily authorize configuration operations under RBAC. The operator should verify aPI authentication and authorization response, user role, permitted commands and audit log.
Question 894
An API token can read NX-OS operational data but fails when the automation tries to modify an interface. Assume an engineer instead chooses to give every API consumer unrestricted administrator privileges by default. Which resulting risk or fault should the reviewer identify?
- Storing execution logs causes the original script to use invalid parameters.
- Using a read-only role for write requests produces predictable authorization failures.
- Verifying server policy references is the reason the missing references occurred.
- Keeping API error responses is the underlying cause of failed automation.
Explanation
Correct Answer
B:The proper corrective action is to apply the minimum authorized NX-OS role and API permissions required for the operation. Successful authentication does not necessarily authorize configuration operations under RBAC.
Incorrect Answers
A:This does not explain the actual nX-API authorization control defect after the shortcut. The meaningful failure is that using a read-only role for write requests produces predictable authorization failures.
C:This does not explain the actual nX-API authorization control defect after the shortcut. The relevant evidence is aPI authentication and authorization response, user role, permitted commands and audit log.
D:This does not explain the actual nX-API authorization control defect after the shortcut. Keeping API error responses is the underlying cause of failed automation.
Question 895
An API token can read NX-OS operational data but fails when the automation tries to modify an interface. The observed failure is: using a read-only role for write requests produces predictable authorization failures. Which remediation most directly restores the intended behavior?
- Disable NX-OS RBAC entirely instead of scoping the required command.
- Change the device hostname to bypass API role enforcement.
- Assign an appropriately scoped approved role and verify the specific write action and audit trail.
- Give every API consumer unrestricted administrator privileges by default.
Explanation
Correct Answer
C:This addresses the observable fault while preserving a check of the expected result. Successful authentication does not necessarily authorize configuration operations under RBAC.
Incorrect Answers
A:Disable NX-OS RBAC entirely instead of scoping the required command. This would not reliably restore service after the stated fault. Using a read-only role for write requests produces predictable authorization failures. The controlled recovery is to assign an appropriately scoped approved role and verify the specific write action and audit trail.
B:Change the device hostname to bypass API role enforcement. This would not reliably restore service after the stated fault. Using a read-only role for write requests produces predictable authorization failures. The controlled recovery is to assign an appropriately scoped approved role and verify the specific write action and audit trail.
D:Give every API consumer unrestricted administrator privileges by default. This would not reliably restore service after the stated fault. Using a read-only role for write requests produces predictable authorization failures. The controlled recovery is to assign an appropriately scoped approved role and verify the specific write action and audit trail.
Question 896
A network automation account has a valid HTTPS session but the switch denies an API configuration command due to role restrictions. Which operator action best meets this technical requirement?
- On this affected device, the engineer should disable NX-OS RBAC entirely instead of scoping the required command.
- On this affected device, the engineer should change the device hostname to bypass API role enforcement.
- On this affected device, the engineer should give every API consumer unrestricted administrator privileges by default.
- On this affected device, the engineer should apply the minimum authorized NX-OS role and API permissions required for the operation.
Explanation
Correct Answer
D:This directly addresses nX-API authorization control because successful authentication does not necessarily authorize configuration operations under RBAC.
Incorrect Answers
A:Disable NX-OS RBAC entirely instead of scoping the required command. The proposed change targets the wrong mechanism or lacks essential validation. Successful authentication does not necessarily authorize configuration operations under RBAC. Relevant evidence is aPI authentication and authorization response, user role, permitted commands and audit log.
B:Using a read-only role for write requests produces predictable authorization failures. In the given case, a network automation account has a valid HTTPS session but the switch denies an API configuration command due to role restrictions.
C:Using a read-only role for write requests produces predictable authorization failures. Give every API consumer unrestricted administrator privileges by default.
Question 897
A network automation account has a valid HTTPS session but the switch denies an API configuration command due to role restrictions. Which collection of observations most directly tests the suspected cause?
- For this deployment, examine aPI authentication and authorization response, user role, permitted commands and audit log.
- For this deployment, examine a saved script file that has never been executed or tested.
- For this deployment, examine an API endpoint returning HTML instead of validated inventory or outcome.
- For this deployment, examine a successful SSH session without script output, API responses or resulting state.
Explanation
Correct Answer
A:These observations test the actual nX-API authorization control mechanism rather than a superficial management status. They should be checked after apply the minimum authorized NX-OS role and API permissions required for the operation.
Incorrect Answers
B:A saved script file that has never been executed or tested. This information cannot independently verify nX-API authorization control. The decisive records instead include aPI authentication and authorization response, user role, permitted commands and audit log. Successful authentication does not necessarily authorize configuration operations under RBAC.
C:An API endpoint returning HTML instead of validated inventory or outcome. This information cannot independently verify nX-API authorization control. The decisive records instead include aPI authentication and authorization response, user role, permitted commands and audit log. Successful authentication does not necessarily authorize configuration operations under RBAC.
D:A successful SSH session without script output, API responses or resulting state. This information cannot independently verify nX-API authorization control. The decisive records instead include aPI authentication and authorization response, user role, permitted commands and audit log. Successful authentication does not necessarily authorize configuration operations under RBAC.
Question 898
A network automation account has a valid HTTPS session but the switch denies an API configuration command due to role restrictions. Which statement most accurately explains this scenario?
- 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 successful authentication does not necessarily authorize configuration operations under RBAC.
- 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 an HTTP 200 connection proves the intended device state was changed correctly.
Explanation
Correct Answer
B:Validation depends on aPI authentication and authorization response, user role, permitted commands and audit log.
Incorrect Answers
A:One initial successful run guarantees all later automation remains correct. This is an incorrect generalization for nX-API authorization control. The applicable technical behavior is that successful authentication does not necessarily authorize configuration operations under RBAC. The operator should verify aPI authentication and authorization response, user role, permitted commands and audit log.
C:A script saved on a controller always runs successfully on every target. This is an incorrect generalization for nX-API authorization control. The applicable technical behavior is that successful authentication does not necessarily authorize configuration operations under RBAC. The operator should verify aPI authentication and authorization response, user role, permitted commands and audit log.
D:An HTTP 200 connection proves the intended device state was changed correctly. This is an incorrect generalization for nX-API authorization control. The applicable technical behavior is that successful authentication does not necessarily authorize configuration operations under RBAC. The operator should verify aPI authentication and authorization response, user role, permitted commands and audit log.
Question 899
A network automation account has a valid HTTPS session but the switch denies an API configuration command due to role restrictions. Assume an engineer instead chooses to give every API consumer unrestricted administrator privileges by default. What is the principal technical consequence of the mistaken choice?
- The resulting defect is that keeping API error responses is the underlying cause of failed automation.
- The resulting defect is that reviewing a Terraform plan makes correct configuration objects disappear.
- The resulting defect is that using a read-only role for write requests produces predictable authorization failures.
- The resulting defect is that verifying server policy references is the reason the missing references occurred.
Explanation
Correct Answer
C:The proper corrective action is to apply the minimum authorized NX-OS role and API permissions required for the operation. That is the direct consequence of choosing the misleading shortcut.
Incorrect Answers
A:This does not explain the actual nX-API authorization control defect after the shortcut. In the given case, a network automation account has a valid HTTPS session but the switch denies an API configuration command due to role restrictions.
B:This does not explain the actual nX-API authorization control defect after the shortcut. Reviewing a Terraform plan makes correct configuration objects disappear.
D:This does not explain the actual nX-API authorization control defect after the shortcut. Verifying server policy references is the reason the missing references occurred.
Question 900
A network automation account has a valid HTTPS session but the switch denies an API configuration command due to role restrictions. The observed failure is: using a read-only role for write requests produces predictable authorization failures. What should the engineer do to recover and validate the service?
- The controlled remediation is to change the device hostname to bypass API role enforcement.
- The controlled remediation is to give every API consumer unrestricted administrator privileges by default.
- The controlled remediation is to disable NX-OS RBAC entirely instead of scoping the required command.
- The controlled remediation is to assign an appropriately scoped approved role and verify the specific write action and audit trail.
Explanation
Correct Answer
D:This addresses the observable fault while preserving a check of the expected result. Validate against aPI authentication and authorization response, user role, permitted commands and audit log.
Incorrect Answers
A:Change the device hostname to bypass API role enforcement. This would not reliably restore service after the stated fault. Using a read-only role for write requests produces predictable authorization failures. The controlled recovery is to assign an appropriately scoped approved role and verify the specific write action and audit trail.
B:Give every API consumer unrestricted administrator privileges by default. This would not reliably restore service after the stated fault. Using a read-only role for write requests produces predictable authorization failures. The controlled recovery is to assign an appropriately scoped approved role and verify the specific write action and audit trail.
C:Disable NX-OS RBAC entirely instead of scoping the required command. This would not reliably restore service after the stated fault. Using a read-only role for write requests produces predictable authorization failures. The controlled recovery is to assign an appropriately scoped approved role and verify the specific write action and audit trail.