Refer to the exhibit. An engineer is trying to automate configuration using NX-API on a Nexus 9000 switch. They have enabled 'feature nxapi' but when they attempt to send a POST request to the NX-API endpoint, they receive '400 Bad Request' with 'Invalid message format'. What is the most likely missing configuration?
Exhibit
show running-config | include feature\nfeature nxapi\nfeature bash\nfeature interface-vlan\nfeature lacp\nfeature vpc
Trap 1: The switch does not have the 'nxapi' feature enabled.
The exhibit shows 'feature nxapi' is already enabled.
Trap 2: The engineer is using the wrong URL path; should be /ins instead of…
While using the wrong path could cause a 404, a 400 indicates malformed request, not wrong path.
Trap 3: The authentication method is set to 'none' but should be 'basic'.
Authentication method affects responses differently; a 400 usually is about syntax, not auth.
- A
The switch does not have the 'nxapi' feature enabled.
Why wrong: The exhibit shows 'feature nxapi' is already enabled.
- B
The NX-API HTTP/HTTPS server is not configured with a port (e.g., 'nxapi http port 80').
Enabling the feature alone does not start the server; a port must be configured.
- C
The engineer is using the wrong URL path; should be /ins instead of /api.
Why wrong: While using the wrong path could cause a 404, a 400 indicates malformed request, not wrong path.
- D
The authentication method is set to 'none' but should be 'basic'.
Why wrong: Authentication method affects responses differently; a 400 usually is about syntax, not auth.