Which statement best describes Path Parameters versus Query Parameters?

Which statement best describes Path Parameters versus Query Parameters?

• A. Query parameters identify specific resource and are required.
• B. Path parameters are optional modifiers that filter results.
• C. Path parameters identify which specific resource you want (required); Query parameters are optional filters.
• D. Query parameters are used to identify the resource.

Answer: (C)

Path parameters specify exactly which resource you want by being part of the URL path and are usually required. They identify the resource itself, not how you want to view it. Query parameters come after the question mark and act as optional refinements to the response—filters, sorting, pagination, or other modifiers that don’t change which resource is fetched. For example, GET /users/42/orders retrieves the orders for user 42, where 42 is a path parameter identifying the specific user’s orders. Adding query parameters like ?status=shipped&page=2 refines the results without changing the resource you’re addressing. So, path parameters identify the resource (and are typically required), while query parameters are optional filters or modifiers.

Path parameters specify exactly which resource you want by being part of the URL path and are usually required. They identify the resource itself, not how you want to view it. Query parameters come after the question mark and act as optional refinements to the response—filters, sorting, pagination, or other modifiers that don’t change which resource is fetched.

For example, GET /users/42/orders retrieves the orders for user 42, where 42 is a path parameter identifying the specific user’s orders. Adding query parameters like ?status=shipped&page=2 refines the results without changing the resource you’re addressing.

So, path parameters identify the resource (and are typically required), while query parameters are optional filters or modifiers.