Free Salesforce Rev-Con-201 Actual Exam Questions - Question 2 Discussion
search.
What should the administrator do to accomplish this?
B/C? Indexing the field is key for search functionality, but if users can’t see or filter by it in the UI, just indexing won’t be enough. Modifying the screen flow (C) might be necessary to actually let users search that field.
Maybe C makes more sense here if the main goal is to actually surface that custom field on the product list page for users to search by. If it’s not visible in the UI, marking it searchable won’t help much. A is too basic since adding a filter option doesn’t guarantee the field is searchable across the system. B sounds like the right step for indexing, but without updating the screen flow to include the custom field, you can’t really search it properly in quotes or orders. So, probably C to make it actionable for users.
B imo, because the question specifically mentions needing the field for search. Just adding it as a filter in the list view (A) won’t make it searchable if it’s not indexed. Modifying the screen flow (C) seems more about UI than actual search functionality. So, setting the field as searchable and running the Rebuild Index job sounds like the step that actually makes the field searchable across quotes and orders.
B, indexing is key for the search to actually recognize that custom field.
B imo. Just adding the field as a filter (A) won’t be enough if it’s not indexed first. The search engine won’t pick up the custom field unless it’s set as searchable and then you run the rebuild index job. That’s how you make sure the data is actually searchable behind the scenes, not just visible in a UI filter. C sounds like changing UI elements, which doesn’t guarantee the field is searchable either. So indexing plus rebuilding is key here.
Maybe B makes sense since indexing is usually required for search functionality to work well, especially if it’s a custom field. Without indexing, the system might not recognize the field in searches.
If the field isn’t indexed, just adding a filter won’t let you search it properly, right?
Maybe A makes more sense here because if the field isn’t available as a filter in the catalog list view, then users can’t search by it directly. Indexing helps but you still need that filter option visible.
A imo, adding the custom field to the Browse Catalog list view as a filter should make it searchable within the quote/order context. If the field isn’t visible there, you can’t really search by it. B makes sense but feels more like a backend setup step, while A directly impacts what the admin sees when searching for products. C sounds more involved and unnecessary unless you’re customizing UI components beyond just enabling search.
B. You gotta index it and run that Rebuild Index job first.