200-901 Cisco Platforms and Development Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  restconf enable

  Why it's wrong here

  restconf enable activates the RESTCONF protocol, which is a separate northbound interface from NX-API and does not enable NX-API's HTTP/HTTPS or sandbox features. It is tempting because both expose programmatic access, but the correct command for NX-API is nxapi enable.

• ✗

  nxapi enable

  Why it's wrong here

  NX-API is enabled from global configuration mode using the feature nxapi command; nxapi enable is not valid NX-OS syntax. It is tempting because it reads like a direct toggle, but NX-OS requires the feature keyword to activate the HTTP/HTTPS API service before any nxapi settings apply.

• ✓

  feature nxapi

  Why this is correct

  `feature nxapi` activates the NX-API management interface on NX-OS, exposing CLI over HTTP/HTTPS for programmatic access. This satisfies the stem's requirement to enable the feature itself, since NX-API remains dormant until this command runs in configuration mode. Without it, REST calls to the device fail regardless of transport settings.

• ✗

  enable nxapi

  Why it's wrong here

  The NX-API feature is enabled from global configuration mode with the feature nxapi command, so enable nxapi is rejected as an invalid exec-mode command. It is tempting because enable is used for privileged exec access, but that grants CLI privilege, not the HTTP-based API.