Free Salesforce Rev-Con-201 Actual Exam Questions - Question 4 Discussion

Option C feels right to me because POST methods typically allow more complex queries, like filtering by catalog. GET usually just grabs everything or needs specific query params that might not be available for catalogs. Since the question asks for products in a specific catalog, POST seems better suited to handle that filter neatly. Plus, product-related records (B) sounds more about linked data rather than a straightforward product list. So, C looks like the best fit here.

I think it’s C. The GET method usually just pulls all products without much filtering, so if you need products from one catalog specifically, the POST version makes more sense because it supports complex filters like catalog ID. A seems too general, and B is definitely off since it’s for related records, not listing products by catalog.

It’s A. The GET Products List API is usually designed to retrieve straightforward lists, and since the question mentions just displaying products for a specific catalog, a simple GET with a catalog ID parameter seems most logical. POST methods often imply more complex queries or creating entries, which might be overkill here. B is out because related records typically handle associations, not direct product listings filtered by catalog. So, A fits best for just pulling a filtered list based on catalog membership without extra complexity.

Not B, since related records API is for associations, not direct filtering. Between A and C, POST (C) makes more sense for filtered queries like by catalog ID.

Maybe B, since it mentions related records, could it link products to catalogs indirectly?

I’m thinking maybe A isn’t right since GET usually doesn’t support complex filters like catalog ID. But is B really relevant here if it’s about related records, not filtering by catalog? Could the question be trickier?

Makes sense, POST (C) is likely since you need to filter by catalog ID in the request body.

Maybe C, since POST usually allows filtering by catalog ID in the body.

C definitely, POST lets you pass catalog ID in the body for filtering.

Is there any info on whether the catalog ID or any filters are required to be passed in the API call? The options show different methods and verbs, but without knowing if it’s a GET or POST that supports filtering by catalog, it’s hard to pick. Also, do we know if the API supports query parameters for listing products based on catalog?