When an admin configures a new retriever for Ridgeline's insurance-claims FAQ content, which two choices most directly define how that retriever behaves?
Select an answer to reveal the explanation.
Short Explanation
Strip away everything else and a retriever really only needs two decisions: what it's searching, and how it searches it.
Full Explanation
A retriever is fundamentally defined by its data source — which content it is scoped to search — and its search type, whether keyword, vector, or hybrid, which determines how matching works against that content. Together these two choices drive what gets retrieved and how well it matches a given query pattern, which is why they're the central configuration decisions for any retriever, including one built for Ridgeline's insurance-claims FAQ material. The org's API version and Lightning theme are platform administration details entirely unrelated to how a specific retriever searches content. License counts and storage limits are capacity and cost considerations, not functional configuration of a retriever's search behavior. Interface color scheme is purely cosmetic and has no bearing on any backend retrieval logic. For the exam, keep the retriever's identity anchored to just these two dimensions — source and search type — since distractors often try to substitute unrelated admin or UI details in their place.