The correct answer is A. Flow.
The requirement is to automatically update a field on the Asset record when a related maintenance Work Order is closed. This is a record-change automation requirement. A record-triggered Flow can run when a Work Order is updated, check whether it is a maintenance work order and closed, and then update the related Asset's last maintenance date.
Salesforce Flow supports updating related records through the Update Records element in record-triggered flows.
C). Roll-up Summary is not the best answer because Salesforce roll-up summary fields require a master-detail relationship, and the Work Order's Asset field is a lookup relationship to Asset.
B is incorrect because Einstein Next Best Action recommends actions; it does not maintain roll-up style data.
D is incorrect because Apex Trigger is unnecessary when Flow can meet the requirement declaratively.

The correct answer is D. Accordion.
For an object with 100+ fields, the app builder should avoid one large monolithic Record Detail area.
Salesforce Trailhead explains that Dynamic Forms breaks the Record Detail component into individual field and section components, which can be placed in separate tabs and accordion sections.
Salesforce also states that moving lower-priority fields into tabs or accordion sections can improve page performance because the content is not visible when the page first loads.
A). Highlights panel is for key record fields and actions at the top of the page. B. Record detail would keep fields together in one large block. C. Field section groups fields, but the better component for breaking a large page into collapsible organized areas is Accordion.

The correct answer is C. Dynamic action.
Dynamic Actions allow an app builder to control which actions appear on a Lightning record page and apply filters to control action visibility. Salesforce documentation states that Dynamic Actions can be assigned in Lightning App Builder and visibility filters can control when actions are shown.
For this requirement, the custom Sync action can be shown only when the Account custom Status field equals Ready to Sync. A custom link alone does not provide the same Lightning App Builder visibility control, a formula field cannot call the Lightning Web Component action, and an AppExchange product is unnecessary.

The Automation Lightning App ' s Monitor tab is Salesforce ' s centralized interface for examining failed and paused flow interviews. Salesforce states that the Monitor tab displays failed interviews, their error information, and details needed to determine why execution failed. From the failed interview details, an administrator can open the run in debug mode and inspect the execution information without requiring the user to reproduce the issue. This directly satisfies the requirement to troubleshoot intermittent production failures from historical flow runs. Option A focuses primarily on paused interviews and is not the current comprehensive monitoring experience. Apex Replay Debugger is intended for Apex debugging rather than declarative Flow execution. Running the flow manually as another user creates a new test execution rather than analyzing the specific production failures that already occurred.

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.