The verified answer is A. Applications is the detail object in a master-detail relationship, so its record access is inherited from the Internship master. Salesforce explicitly states that custom objects on the detail side cannot have independent sharing rules, manual sharing, or queues because they do not have an independent Owner field. To let recruiters edit Application records, the app builder must therefore grant the required Read
/Write access to the related Internship master records, such as through a sharing rule. Option C is invalid because the detail object ' s sharing model cannot simply be independently configured as Public Read/Write.
Option D is also invalid because a detail custom object cannot have its own sharing rule in this configuration.
This corrects the PDF answer key, which identifies D.

omprehensive and Detailed Explanation with all Platform App Builder documents: = The correct answer is A. The report type is already based on Opportunities with or without Shipments, so the app builder should not change the report type's primary object. To expose Account Rating, the app builder should edit the custom report type layout and use Add fields related via lookup from the Opportunity view, because Opportunity has a relationship to Account. Salesforce documentation confirms that custom report types allow fields from objects not directly included in the report type structure by using Add fields related via lookup.
Why others are incorrect:
B is incorrect because the standard Account-Opportunity relationship cannot simply be changed to master- detail.
C is incorrect because changing the primary object to Account would change the report purpose.
D is incorrect because adding a field to a record page does not make it available in a report type.

The correct answer is B.
Universal Containers needs the 18-digit Salesforce record ID for Opportunity records when exporting to Excel. Salesforce's CASESAFEID() formula function converts a 15-character Salesforce ID into the 18- character, case-insensitive ID format that works better with external tools such as Excel. Salesforce documentation specifically describes CASESAFEID as the function used to convert IDs to 18-character IDs for Excel compatibility.
Correct formula:
CASESAFEID(Id)
A). VALUE(14) is unrelated. C. TEXT(Id) does not convert the ID to the 18-character case-safe format. D.
ISNUMBER(Id) only checks whether a value is numeric, which is not useful for Salesforce record IDs.

The correct answer is D. Flow.
A call center representative needs to collect customer information through a series of question prompts. This is a classic use case for a Screen Flow. Salesforce describes screen flows as interactive automation that asks users questions, presents information, and uses user responses to update records or show more prompts.
Approval Process is for approvals, Path guides users through stages, and Validation Rule enforces data quality. None of those tools provide a guided question-and-answer experience.

The correct answers are C. External objects and D. Big objects.
External objects are suitable because they represent data stored outside Salesforce while still being accessible in Salesforce. Salesforce documentation explains that external objects behave similarly to custom objects, but the record data is stored outside the Salesforce org. External objects can also participate in lookup-style relationships, including external and indirect lookup relationships, and Salesforce Connect supports reports that include external objects.
Big objects are also suitable for archiving very large volumes of historical data on the Salesforce platform.
Salesforce describes big objects as a way to store and manage massive amounts of data, including archived data from other objects. Big objects support querying through SOQL/API patterns, and Salesforce documentation also covers viewing big object data in reports and dashboards, commonly by using a working dataset for reportable subsets.
A is incorrect because "related objects" does not reduce Salesforce data storage.
B is incorrect because moving data into custom objects still consumes Salesforce data storage, so it does not solve the storage-limit issue.