A company has an API to manage purchase orders, with each record identified by a unique purchase order ID. The API was built with RAML according to
MuleSoft best practices.
What URI should a web client use to request order PO5555?
A company has an API to manage purchase orders, with each record identified by a unique purchase order ID. The API was built with RAML according to
MuleSoft best practices.
What URI should a web client use to request order PO5555?
The URI for a web client to request a specific order by its purchase order ID should directly include the ID in the path. The appropriate format is '/orders/PO5555' as it directly targets the specific resource identified by PO5555. Curly braces are typically used in API documentation to denote path parameters and are not included in the actual URI sent by the client.
Correct is D
Definitely, correct answer is D The question is: "Which uri should a WEB CLIENT use to request ...". This means that we are on the client side. You never put curly braces when you type the address in your browser or postman or any other HTTP client... But on the server side, you have to put those braces in your RAML file or in the listener if you use Anypoint Studio. If the question was about the setup, the correct answer would have been A. But the question is about the web client, so the correct answer is D.
Answer should be D
correct ans should be D
D is correct
D is correct option
CURLY BRACES IS NOT NEEED TO SEND A REQUEST FOR URI PARAM
option 'D' is correct.
D is correct. A is not even a valid URI
D is correct
La correcta es la D
Correct is D
Option D is correct
D is correct
Correct is D
Correct is D