Reference:
Salesforce Help - Dynamic Forms

The requirement is to auto-populate the "Last Maintenance Date" field on the Asset record whenever a Maintenance-type Work Order is closed. This can be achieved declaratively using Flow - specifically, a Record-Triggered Flow that updates the parent record (Asset).
Why D (Flow) is correct:Exact Extract:"Record-triggered flows can update related records when specific changes occur, such as when a Work Order's status is updated to Closed." - Salesforce Help | Record-Triggered FlowsIn this scenario, the flow can:
Why D (Flow) is correct:Exact Extract:"Record-triggered flows can update related records when specific changes occur, such as when a Work Order's status is updated to Closed." - Salesforce Help | Record-Triggered FlowsIn this scenario, the flow can:
Trigger when a Work Order is updated to "Closed."
Check if Type = "Maintenance."
Update the related Asset record's Last Maintenance Date field with the Work Order's Closed Date.
Why not B (Roll-up Summary):Roll-up summary fields can only summarize numeric or date values using MIN, MAX, COUNT, or SUM, but only on Master-Detail relationships. Work Order → Asset is a Lookup relationship, so roll-up summaries are not supported natively.
Why not A (Einstein Next Best Action):NBA provides recommendations, not field updates.
Why not C (Apex Trigger):Apex could achieve this, but Salesforce recommends Flow first as a best practice.
Reference:
Salesforce Help | Record-Triggered Flows
Salesforce Help | Flow Builder Overview
Salesforce Platform App Builder Exam Guide | Business Logic and Process Automation

Reference:
Salesforce Help - Change Sets

The feature that the app builder should use to allow users to create the opportunity is a quick action. A quick action is a type of custom button or link that can create or update records, log calls, send emails, or launch flows from a record page or a global menu. The app builder can create a quick action on the account object that creates an opportunity record with pre-populated fields. Option B is incorrect because a default action is not a valid term, but rather a standard action that appears on every record page by default, such as Edit or Delete. Option C is incorrect because a custom button is not suitable for this requirement, as custom buttons can only display a URL or execute JavaScript when clicked. Option D is incorrect because a custom link is not suitable for this requirement, as custom links can only display a URL or execute JavaScript when clicked.

Since there is a master-detail relationship between Property__c (master) and Offer__c (detail), Salesforce natively supports using Roll-up Summary fields on the master object to summarize values from the related child records.
Why A (Roll-up Summary) is correct:Exact Extract:"A roll-up summary field calculates values from related records, such as those in a related list, on a master record. You can count the number of related records, determine the sum, minimum, or maximum value of a field in the related records." - Salesforce Help | Roll-Up Summary FieldsTherefore, DR can create a Roll-up Summary field on Property__c that uses the MAX function on the "Offer Value" field from Offer__c.
Why A (Roll-up Summary) is correct:Exact Extract:"A roll-up summary field calculates values from related records, such as those in a related list, on a master record. You can count the number of related records, determine the sum, minimum, or maximum value of a field in the related records." - Salesforce Help | Roll-Up Summary FieldsTherefore, DR can create a Roll-up Summary field on Property__c that uses the MAX function on the "Offer Value" field from Offer__c.
Why not B, C, or D:
Rich Text Area and Text Area (Long) store text, not calculated numeric data.
Multi-select Picklist is used for multiple selectable text options, not calculations.
Reference:
Salesforce Help | Roll-Up Summary Fields
Salesforce Platform App Builder Exam Guide | Data Modeling and Management