The correct solutions are D. Create a custom app page and assign it to the mobile menu and B. Include Today as a navigation item in the app.

Salesforce supports creating a mobile app page with Lightning App Builder for the Salesforce mobile app. This allows an app builder to design a mobile-focused experience and make it available through mobile navigation.

Salesforce also provides Today in the mobile app to help users manage their day, prepare for meetings, and access relevant mobile productivity information. Salesforce documentation states that users access Today from the Salesforce mobile app navigation menu, and admins can add Today to Lightning app navigation and the Mobile Only app.

C is not the best verified exam answer for the standard version of this question. While mobile navigation can be customized, the stronger Platform App Builder mobile UX recommendations here are adding a custom mobile app page and adding Today as a navigation item.

===========

The correct answer is B.

This is a one-user exception. Salesforce recommends using permission sets to extend access without changing the user’s base profile. A permission set can grant read-only field access through field-level security to just the selected customer service agent. Salesforce documentation explains that permission sets extend user access, and field permissions control whether users can view or edit individual fields.

Why others are incorrect:

A creates a new profile for one user, which is not the recommended scalable solution.

C is not accurate because field-level security is assigned through profiles or permission sets, not directly to one user from the field alone.

D would give all users with the Customer Service profile read-only access, not only the single agent.

===========

The correct answers are C. Users, D. Public Groups, and E. Roles and Subordinates.

Manual sharing is used when the org-wide default is private and users need to share individual records on a case-by-case basis. Salesforce documentation confirms that manual sharing allows users to share individual records with other users, public groups, and roles.

A public group can include users, roles, and roles with subordinates, which makes it useful when sharing records with departments or groups of people.

A. Permission Set Groups is incorrect because permission set groups grant permissions, not manual record-level sharing.

B. Private Groups is not the standard manual-sharing option tested here.

===========

The correct answer is C. Internal profiles.

When an app builder creates a custom field using Schema Builder, Salesforce sets field-level security for custom fields to visible and editable for internal profiles by default.

That is why B. All profiles is not the best answer. Salesforce’s documented default is specifically internal profiles, not every possible profile type.

===========

The correct answer is C. Custom object with Master-detail field to Opportunity.

AW Computing needs many help requests related to one Opportunity, so the help request should be a custom child object under Opportunity. Because the Opportunity page must show the most recent request date, the app builder needs a Roll-Up Summary field on Opportunity using MAX on the request date field.

Salesforce roll-up summary fields work on the master side of a master-detail relationship, and MAX can be used for date/date-time fields.

A is backward because the master-detail field belongs on the child object, not Opportunity.

B and D use lookup relationships, which do not support standard roll-up summary fields.

===========

The correct answer is B. Add the standard Chatter feed component.

In Lightning App Builder, Salesforce provides a standard Chatter component. Salesforce documentation states that the Feed component was renamed Chatter in Lightning App Builder and is used to place the publisher and feed on a record page.

A is incorrect because a custom Chatter feed component is not needed.

C is incorrect because this does not come from the AppExchange/App College.

D is incorrect because Chatter feed is not added by using the standard related list component.

===========

The correct answer is C. AppExchange package.

The key word is daily. Salesforce’s native Data Export Service supports manual and scheduled exports, but Salesforce documentation states that backup files can be generated manually once every 7 days for weekly export or 29 days for monthly export, depending on edition. That does not meet an automatic daily backup requirement.

For daily automated backups, the app builder should recommend a backup solution from AppExchange. Report export is not an org backup, and refreshing a full copy sandbox is not a backup automation tool.

===========

The correct answer is C. Developer sandbox.

For small, individual projects where teams need separate environments before moving work into a larger shared testing sandbox, a Developer sandbox should be considered first. It is intended for development and testing of configuration changes in an isolated environment and is the lowest-cost sandbox option compared with Developer Pro, Partial, and Full sandboxes. Salesforce describes sandbox types for different testing and development needs, with Developer and Developer Pro sandboxes copying configuration/metadata rather than full production data.

Developer Pro provides more storage, but the question emphasizes small projects and keeping costs down. Partial and Full sandboxes are better for broader testing with data, but they are not the first choice for many small isolated development efforts.

===========

The correct answer is B. Data is unable to be deployed with change sets.

Change sets deploy metadata/configuration, not business data. Salesforce documentation states that change sets can contain setup modifications, but they cannot be used to upload a list of records such as contacts.

So the report itself can be deployed, but the underlying records needed for the report results are not deployed through the change set. If the Partial Copy sandbox does not contain matching sample data, the report returns no data.

Why others are incorrect:

Data is not deployed just because it is added to a change set.

Reports do not have to be manually recreated if they are deployed properly.

“Salesforce OK” is not a deployment requirement.

===========

The correct answer is C. Enhanced List.

Salesforce documentation states that the Enhanced List related list type shows up to 10 fields and allows users to resize columns, sort columns, perform mass actions, and wrap text. This exactly matches the requirement: users need to see ten fields and need the ability to sort and wrap text on related lists.

D. Basic List is incorrect because the Basic List type shows fewer fields and does not provide the enhanced related-list behavior required here. A. List View and B. List Class are not the correct Related List Lightning component type for this requirement.

===========