Platform-App-Builder Salesforce Exam Lab Questions

A master-detail relationship provides the required cascade-delete behavior. Supplier__c should be configured as the master and Supplier_Item__c as the detail. Salesforce explicitly states that when a master record is deleted, its related detail and subdetail records are also deleted. This ensures that terminating the Supplier relationship removes the dependent Supplier Item records automatically without additional Flow or Apex automation. An indirect lookup relationship is used primarily to relate external-object data to Salesforce records and does not provide the required ownership and cascade behavior. A hierarchical relationship is available only for relationships involving the User object. Many-to-many describes a data-model pattern normally implemented with a junction object and does not itself specify the required parent-child cascade. Master-detail therefore directly implements the stated lifecycle dependency.

================

The correct answer is C. A record-triggered flow can run automatically when an Opportunity is updated to Closed Won, create a renewal Opportunity, and notify the contracts team. Salesforce Trailhead explains that record-triggered flows are built around trigger, criteria, and action; for example, when an Opportunity is created or updated and meets criteria, the flow can create another record.

Salesforce Flow can also create records and send emails, which fits both requirements: create the renewal Opportunity and notify an external contracts team.

Why others are incorrect:

A Approval Process is for review/approval routing.

B Outbound Message may notify an external system, but it does not handle the full renewal Opportunity creation requirement by itself.

D Validation Rule only prevents bad data; it does not create records or send notifications.

===========

A before-save record-triggered flow is optimized for updating fields on the same record that initiated the automation. The flow can trigger when an Opportunity is updated, test whether StageName changed, and assign the current date directly to Stage_Last_Changed__c . Salesforce recommends before-save flows for updating fields on new or changed triggering records because the changes are applied before the database save and avoid an additional DML operation. Salesforce also confirms that values assigned to the triggering $Record are automatically persisted. A scheduled path would introduce an unnecessary delay, while an approval process does not fit a simple field-stamping requirement. An autolaunched flow invoked manually would depend on user action and therefore could not reliably guarantee that every Stage change is captured.

================

A schedule-triggered flow is designed for batch automation that must execute at a defined time and frequency. Salesforce allows this flow type to run once, daily, or weekly and to select an object plus entry conditions in the Start element. Universal Containers therefore can configure Account as the target object, Weekly as the frequency, Sunday at 2:00 a.m. as the start schedule, and conditions that identify Accounts whose Last Activity Date is more than 90 days old. A scheduled path on a record-triggered flow is tied to individual record-triggering events rather than a weekly evaluation of all qualifying Accounts. Option D runs only once and fails the recurring requirement. Salesforce explicitly supports weekly schedule-triggered flows for this batch-processing pattern.

================