The correct answer is A. Create a lookup relationship on Asset Inventory to Asset. Add the Asset Inventory related list to the Asset page layout.
To show Asset Inventory records as a related list on Asset, the child object must contain the relationship field pointing to the parent object. In this scenario, Asset Inventory is the child/detail-style object, and Asset is the parent record where the related list should appear.
Salesforce relationship fields connect records between objects, and related lists can then be added to the parent object's page layout. Salesforce documentation for related lists confirms that related lists are managed from the object's page layout.
Why others are incorrect:
B is incorrect because a roll-up field does not create the relationship or related list.
C is incorrect because the relationship direction is wrong; the relationship field should be created on Asset Inventory, not on Asset.
D is incorrect because a junction object is only needed for many-to-many relationships. Here, Asset Inventory records simply need to relate to Asset records.

omprehensive and Detailed Explanation with all Platform App Builder documents: = The correct answer is A. Roll-up Summary.
DreamHouse Realty wants to show the highest value from related Offer records on each Property record.
Because the objects have a master-detail relationship, a roll-up summary field is the correct declarative solution.
Salesforce documentation explains that roll-up summary fields calculate values from related detail records and display the result on the master record. Salesforce also lists MAX as the roll-up type used to display the highest value from related records.
B is not a Salesforce field type for this requirement.
C, D, and E are data-entry field types and cannot calculate the highest related Offer value.

The correct answer is D. Patch.
In application lifecycle management, patch releases are used for bug fixes and simple, low-impact changes.
Salesforce packaging documentation also describes patch versions as minor upgrades used for fixing bugs or errors.
Major releases are for large changes or significant new functionality. Minor releases are usually for limited- impact enhancements. Roll is not the correct ALM release category here.

The correct answers are A. Create an object-specific action on Account and D. Create predefined values for most of the fields.
For this requirement, sales reps need to create a custom Feedback record related to an Account with minimal clicks on mobile. An object-specific quick action is the best solution because it runs in the context of a specific Account record and can create a related child record automatically. Salesforce Trailhead states that object-specific actions let users create records with automatic relationships to other records and provide a streamlined mobile and desktop experience.
Predefined field values reduce manual typing and save mobile users time. Salesforce mobile customization guidance explains that quick actions can include predefined fields, and Trailhead specifically shows predefined values being used to prepopulate fields on action layouts.
B). Create a feedback object as a parent of Account is incorrect because the Feedback record should be related to each Account, normally as a child record or lookup-related record. C. Create a global action on Account is incorrect because global actions create records without record context; Salesforce explains that global actions create records with no relationship to other records, while object-specific actions work in the context of a particular object.

The correct answer is A because the requirement is to keep one specific field, the Comment field, private from users outside HR. Salesforce field-level security is the correct security layer for controlling whether users can view or edit a field. Salesforce documentation states that field-level security restricts user access to fields and overrides page-layout visibility.
A page layout alone is not enough because page layouts control UI presentation, not full field security.
Salesforce also notes that to ensure users cannot access a field, field permissions should be used because other settings do not provide the same field-level protection.
Why others are incorrect:
B and D are wrong because sharing rules and Apex sharing control record access, not individual field access.
C is wrong because removing a field from a page layout only hides it from that layout; it does not securely prevent access through reports, API, related lists, or other interfaces.