You have run a script to configure a new VLAN on a CX switch, but are receiving a '404 - Not Found' HTTP response code. What do you need to do to resolve the issue?

Question

Options

• ASend a POST request to the /rest/v1/login resource.
• BCorrect syntax error contained in the data payload.
• CEnable the switch REST API in read/write mode.
• DSpecify the /rest/v1/system/vlan URI in the request.

• A
  6% (2)
• C
  3% (1)
• D
  90% (28)

Explanation

A 404 "Not Found" error is an HTTP status code that specifically means the server cannot locate the requested URI - the endpoint path in your script is wrong or missing, making D the direct fix: you must target the correct /rest/v1/system/vlan URI for VLAN configuration on HPE Aruba CX switches.

Why the distractors are wrong:

• A is wrong because a missing or expired login would return 401 Unauthorized, not 404; authentication is a separate concern.
• B is wrong because a malformed data payload (JSON syntax error, etc.) would return 400 Bad Request, meaning the server found the resource but rejected the input.
• C is wrong because a read-only or disabled REST API would typically return 403 Forbidden (permission denied), not 404.

Memory tip: Tie the error code to its literal meaning - 404 = "address not found," just like a street address that doesn't exist. Whenever you see 404, your first instinct should be to check the URL/URI path itself, not authentication or payload content.

No community discussion yet for this question.