The correct sandbox type is Partial Copy.
A Partial Copy sandbox is built for testing with a subset of production data. Salesforce lists Partial Copy sandboxes with 5 GB data storage and a 5-day refresh interval, which supports the requirement to refresh it every weekend.
Why the other options are wrong:
Developer and Developer Pro sandboxes are mainly for development and do not copy a production data subset in the same way. A Full sandbox can copy all production data, but its refresh interval is longer and it is unnecessary for a subset under 5 GB.

The correct answers are A. Flow Launcher and D. Quick Action.
A flow can be exposed to users through a page-based launcher/component. Salesforce Trailhead explains that users can access a flow by adding it to a Lightning page through Lightning App Builder. The Flow component can be dragged onto the Lightning page so users can run the flow from that page.
A Quick Action can also launch a flow. Salesforce documentation states that quick actions help users launch and navigate through workflows, and Trailhead confirms that custom actions can invoke flows.
Why others are incorrect:
B . Apex can invoke automation programmatically, but it is not the best user-facing access feature in this question.
C . Approval Process routes records for approval; it is not a general method for users to access flows.

The verified exam answer is D. Add the Path component to the Lightning record page.
Salesforce Path is designed to guide users through stages of a business process. For each step, such as each Opportunity Stage, an app builder can highlight key fields and add guidance for success. Salesforce documentation states that when creating a Path, the app builder can select key fields for each step and enter success guidance.
This fits the requirement because users need to know which fields should be completed at each Opportunity stage.
Important nuance: Path guides users, but it does not hard-enforce stage-based required fields by itself. Salesforce notes that page layouts cannot require different fields in different Path steps; strict enforcement requires validation rules based on the stage/path step.

Existing data will be truncated to the first 255 characters.
Salesforce documentation on changing custom field types states that when a Long Text Area field is converted to Email, Phone, Text, Text Area, or URL, the record data is truncated to the first 255 characters. Since the target is a standard Text Area with a 255-character limit, longer Manager Notes values would not remain intact.
Why not the others? Salesforce does not preserve values beyond the new limit in this conversion. The data is not completely lost, but anything after the first 255 characters is removed.

The correct answers are A. Data loss may occur when changing custom field types and D. Field History Tracking records value changes of 255 characters or less.
A is correct because Salesforce warns that changing the data type of an existing custom field can cause data loss in certain situations. This is a key consideration before converting Text Area (Long) fields to Rich Text Area fields.
D is correct because Salesforce field history tracking has a character limitation. Salesforce tracks changes to fields with more than 255 characters as edited, but it does not record the old and new values. That means long/rich text changes beyond that limit do not provide full before-and-after history values.
Why others are incorrect:
B is not the relevant consideration for this field conversion requirement.
C is incorrect because Salesforce reports do not display rich text field values of all lengths fully; Salesforce documentation notes report display limits for long text and rich text area fields.