A prompt template needs to reference the specific pet's name and species when drafting a vaccination reminder, values that live directly on the Patient record being viewed. Which grounding technique is the simplest correct fit?
Select an answer to reveal the explanation.
Short Explanation
When the values you need are already sitting right there on the record in front of you, a simple merge field is the simplest, most direct way to pull them in - no need to reach for anything heavier.
Full Explanation
The correct answer is a merge field, because the requirement is to reference simple, already-present field values (pet name, species) directly from the record context the template is running against - which is exactly what merge-field grounding is designed for, with no additional logic or external lookup required. A Data 360 vector retriever is built for semantic search over unstructured content like documents or notes, which is far more machinery than is needed to pull two known field values off a record currently in view. An Apex invocable action is appropriate when custom logic or computation is needed beyond what declarative grounding can provide, but there's no such logic required here - it would be unnecessary complexity for a straightforward field reference. An external API call is for pulling in data that lives outside Salesforce entirely, which doesn't apply since both needed values already live on the Salesforce record. The exam-relevant principle is to match the grounding technique's complexity to the actual need: simple, present-on-the-record values call for merge fields, not retrievers, Apex, or external calls.