Valid ADM-201 Dumps shared by ExamDiscuss.com for Helping Passing ADM-201 Exam! ExamDiscuss.com now offer the newest ADM-201 exam dumps, the ExamDiscuss.com ADM-201 exam questions have been updated and answers have been corrected get the newest ExamDiscuss.com ADM-201 dumps with Test Engine here:
The administrator at Universal Container has created two objects: Containers_c Purchase_c, Management has requested that all container records display on purchase records in Salesforce. Which type of relationship between Containers_c and Purchase_c should satisfy the requirement?
Correct Answer: D
Explanation A lookup field is a type of field that allows administrators to create a relationship between two objects by linking records from one object to another object. For example, a lookup field can link an account record to a purchase record by storing the account ID on the purchase record. A lookup field allows users to select an existing record from a pop-up window or create a new record from the same window. References: https://help.salesforce.com/s/articleView?id=sf.relationships_lookup.htm&type=5
Recent Comments (The most recent comments are at the top.)
xyzzy - Sep 16, 2024
I prefer "C" (Master-Detail) because of the requirement "all container records display on purchased records in Salesforce". If container record is on the detail side of the relationship then it must have a parent (purchase__c).
A Lookup field can be left blank, if not required and thus doesn't meet the requirement.
Skycer - Apr 24, 2024
Why MD field and not a lookup field. I think but not sure the ans is D. Lookup field
Here's why according to Gemini:
Roll-up Summary field: This aggregates data from child records (containers) to a parent record (purchase) but wouldn't display individual container records. Formula field: While you could potentially create a formula to display container data within a purchase record, it wouldn't provide a direct link to individual container records. Master-detail field: This establishes a hierarchical relationship where a container can be linked to only one purchase, which might not be the desired outcome. Lookup field: This is the ideal choice. A lookup field on the Purchase_c object allows you to link multiple container records to a single purchase record. This enables users to see all associated containers for each purchase.
Recent Comments (The most recent comments are at the top.)
I prefer "C" (Master-Detail) because of the requirement "all container records display on purchased records in Salesforce". If container record is on the detail side of the relationship then it must have a parent (purchase__c).
A Lookup field can be left blank, if not required and thus doesn't meet the requirement.
Why MD field and not a lookup field. I think but not sure the ans is D. Lookup field
Here's why according to Gemini:
Roll-up Summary field: This aggregates data from child records (containers) to a parent record (purchase) but wouldn't display individual container records.
Formula field: While you could potentially create a formula to display container data within a purchase record, it wouldn't provide a direct link to individual container records.
Master-detail field: This establishes a hierarchical relationship where a container can be linked to only one purchase, which might not be the desired outcome.
Lookup field: This is the ideal choice. A lookup field on the Purchase_c object allows you to link multiple container records to a single purchase record. This enables users to see all associated containers for each purchase.