The correct answer is B. Create a new roll-up summary field called First Order Date, using type MIN on the Opportunity Close Date with a filter where IsWon = TRUE.
Cloud Kicks wants to track the first purchase date for each customer. The first purchase is the earliest won Opportunity Close Date. A roll-up summary field can calculate values from related records and supports summary types such as COUNT, SUM, MIN, and MAX. Salesforce Trailhead states that MIN displays the lowest value from the selected field and supports date/date-time fields.
So the app builder should create a roll-up summary field on the Account, summarize related Opportunities, choose MIN on CloseDate , and filter to only include won Opportunities, such as IsWon = TRUE .
A and C are incorrect because the field should be a roll-up summary field itself, not a regular date field updated by a roll-up.
D is incorrect because SUM is for number, currency, and percent fields, not date fields. Salesforce documentation confirms that MIN/MAX support date fields, while SUM is for numeric-style fields.

The correct answer is B. Lookup.
This is a one-to-many mentorship relationship: one experienced Realtor can mentor many new Realtors, but each new Realtor works with only one experienced Realtor. A lookup relationship is appropriate for connecting one record to another in this type of flexible parent-child model. Salesforce relationship documentation confirms that lookup relationships are used to relate objects without the strict ownership, sharing, and deletion behavior of master-detail relationships.
Master-detail is too restrictive because the new Realtor record should not necessarily inherit ownership and deletion behavior from the mentor. Many-to-many is incorrect because each new Realtor has only one mentor.
Indirect lookup is used for external objects, not this internal Salesforce relationship.

The correct answers are A. Tabular format and B. Summary format.
Salesforce reporting snapshots can use custom tabular or summary reports as the source report. Salesforce documentation specifically states that a reporting snapshot source report can be tabular or summary.
Why others are incorrect:
C). Joined format is not supported as a reporting snapshot source report.
D). Matrix format is not supported because matrix reports group by rows and columns, and Salesforce troubleshooting guidance states that matrix reports can't be used with reporting snapshots.

The correct answer is D. Record-triggered flow.
The requirement is automatic: when an Account Type changes to Past-Customer, all directly related Contacts must have their Status updated to Re-Market. A record-triggered flow is the correct declarative automation because it can run when an Account record is updated and then update related Contact records. Salesforce describes record-triggered flows as automation that runs automatically when records are created, updated, or deleted. Salesforce also documents that Flow can update records related to the record that triggered the flow.
Validation rules only prevent invalid saves. Lightning components are UI elements. Screen flows require user interaction, while this requirement needs background automation.

The correct answer is C. Record-triggered flow.
To track the number of times a Case is reopened, the app builder can create a record-triggered flow on the Case object that runs when the Case is updated. The flow can check when the Status changes from Closed to an open/reopened status and increment a custom number field such as Number_of_Reopens__c . Salesforce Trailhead explains that record-triggered flows run when records are created, updated, created or updated, or deleted.
Why not Apex Trigger? Apex could work, but the Platform App Builder best answer is the declarative option:
Flow before code.