The correct answers are B. Create a criteria-based sharing rule and C. Update the organization-wide defaults.
To move from a public sharing model to a more restrictive model, the app builder must first update the Organization-Wide Defaults for Accounts. OWDs define the baseline record access for users. Then, because the Sales team must still access all Account records with the Sales record type, the app builder should create a criteria-based sharing rule using record criteria, such as Record Type. Salesforce sharing rules are used to extend access when the OWD is Private or Public Read Only.
A is incorrect because owner-based sharing rules share records based on owner, not record type.
D is incorrect because profiles control object permissions, not record-level access by record type.

The correct answer is D. The Owner field on the Master record.
In a master-detail relationship, the detail record does not have independent ownership. Salesforce documentation states that the Owner field on the detail object isn't available and is automatically set to the owner of the related master record.
Sharing is also controlled by the parent/master record. Salesforce Help explains that when a custom object is on the detail side of a master-detail relationship, its organization-wide default is set to Controlled by Parent.
A and C are incorrect because the detail record does not maintain independent ownership in a master-detail relationship. B is incorrect because ownership is not determined by a default owner setting on the parent object; it comes from the actual Owner field on the master record.

The correct answers are A. Roll-up summaries are limited to master-detail relationships and C. An object can have 25 roll-up summaries.
Roll-up summary fields summarize data from related child records onto the parent record, but standard Salesforce roll-up summaries are available only when the child records are directly related through a master-detail relationship. In this scenario, only one of the three custom objects has a master-detail relationship to Account, so native roll-up summaries cannot be used for the other two lookup/non-master-detail objects.
Salesforce also lists 25 roll-up summary fields per object as the standard allocation, so summarizing 15 fields from three objects would require 45 summaries, which exceeds the normal Account object limit.
B is incorrect because native roll-up summary calculations support COUNT, SUM, MIN, and MAX, not AVG.
D is incorrect because "20 object references" is not the key roll-up summary consideration in this proposal.

The correct answers are B. Flow Builder and D. Escalation rules.
Escalation rules are the most direct Salesforce Service feature for this requirement. They are designed to automate case escalation when cases are not resolved or not acted on within a defined time period. Salesforce documentation explains that escalation rule entries can use business hours, and escalation actions can send notification emails when the case escalates.
Flow Builder can also be used because record-triggered flows support scheduled paths, allowing automation to run after a defined time from a triggering record event. A flow can check whether the Case is still in New status and then send a notification. For strict business-hour calculation, the app builder must design the flow carefully around the correct time source/business-hour logic.
A is incorrect because validation rules only prevent invalid data from being saved; they do not wait four business hours and send notifications.
C is incorrect for the Platform App Builder context because Scheduled Apex is a programmatic approach, while declarative automation tools are available and preferred for this requirement.

The correct answer is B. Feed Tracking.
DreamHouse Realty wants changes to selected fields, such as Asking_Price__c and Real_Estate_Agent__c, to appear prominently in Chatter. This is exactly what Chatter Feed Tracking is used for.
Salesforce documentation states that feed tracking is available for record fields and can be configured for custom objects. Salesforce guidance also says admins can enable feed tracking from Setup, select an object, enable feed tracking, and choose fields to track.
A . Topics is used for categorizing Chatter posts, not automatically tracking field changes.
C . Pin Field is not the Chatter feature for tracking field updates.
D . Publisher Actions are actions users can take from the publisher, not automatic field-change tracking.