Free Salesforce Platform-App-Builder Practice Exam with Questions & Answers | Set: 2

The correct answers are C. My Domain must be deployed and D. The component is tagged for record pages instead of home pages.

Salesforce custom Lightning components must be properly configured before they appear in Lightning App Builder. Salesforce Trailhead explains that custom components configured for Lightning App Builder appear in the Lightning Components pane, and the component bundle must be compatible with Lightning App Builder and Lightning pages.

C is correct because Salesforce requires My Domain for adding custom Lightning components in Lightning Experience/App Builder scenarios. Salesforce Help notes that users cannot add a custom Lightning component without enabling and deploying My Domain.

D is correct because Lightning components must be exposed for the correct page type. A component exposed only for record pages will not appear for a Lightning Home page. Salesforce Developer documentation states that lightning__HomePage enables a component to be used on a Home page, while record-page-only configuration is separate.

Why others are incorrect:

A is incorrect because a custom tab is not required to add components to a Lightning Home page.

B is incorrect because “developer permission” is not the normal reason a downloaded component cannot be added to a Lightning Home page.

===========

The correct answer is B. Queue.

The approval request must go to department members who can approve overnight shipments. In Salesforce approval processes, routing an approval to a queue is appropriate when a group of users can own or act on the approval request and any one of the queue members can handle it. Salesforce approval documentation describes approval processes as automation that specifies each approval step, including who receives the approval request.

A queue is better than a role or hierarchy field when the request needs to be handled by a department group rather than a single manager or a specific user from a hierarchy field.

A. Role is less appropriate because roles are for hierarchy-based access and routing.

C. Hierarchy field is used when routing to a user identified through a manager-style field.

D. Public group is used for sharing and grouping users, but approval queues are the standard routing choice for a group of approvers in this scenario.

===========

The correct answers are A. Review the Contact record and ensure it is linked to an Account, C. Verify the users with the issue have access to the Contact object, and E. Confirm whether Default Organization-Wide Sharing Settings provide access to the Account.

A Contact that is not linked to an Account is treated as a private contact. Salesforce states that contacts without an account are private regardless of the sharing model, so checking whether the Contact is associated with an Account is a valid troubleshooting step.

Users also need object-level access to the Contact object. Object permissions control whether users have base-level access such as read, create, edit, and delete for an object.

Finally, Contact visibility is often affected by Account access, especially when Contact sharing is controlled by the parent Account. Organization-Wide Defaults define the default record access users have for records they do not own, so checking the Account OWD is also correct.

B is incorrect because creating a new Contact does not troubleshoot the actual sharing/security issue.

D is incorrect because creating a broad Account Sharing Rule for all records is not the first troubleshooting step and may overexpose data.

===========

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.

===========

The correct answer is A. Roll-up summary field.

Cloud Kicks wants to count how many Subscription records are related to each Shoe record. Because a master-detail relationship already exists between Subscription and Shoe__c , the app builder should create a Roll-Up Summary field on the master object.

Salesforce documentation confirms that roll-up summary fields can count the number of detail records related to a master record. Trailhead also explains that roll-up summaries display values on the master record based on directly related detail records in a master-detail relationship.

B. Lookup field and C. Master-detail field define relationships, but the relationship already exists. D. Sum field is not a Salesforce field type.

===========

The correct answer is B. This lookup relationship will need to be converted to a master-detail relationship before a roll-up summary field can be created.

A Salesforce roll-up summary field is created on the object that is on the master side of a master-detail relationship. Lookup relationships do not support standard roll-up summary fields. Salesforce documentation confirms that roll-up summary fields are defined on the master object in a master-detail relationship.

A and D are incorrect because formula fields cannot count related child records across a lookup relationship.

C is incorrect because the relationship is currently lookup, so a standard roll-up summary field cannot be created yet.

===========

The correct answers are C. Unique and D. External ID.

The legacy ID should be stored in a custom field marked as an External ID because Salesforce uses External ID fields to identify records from an outside system and to support update/upsert operations during future data loads. The field should also be marked Unique so each legacy system ID maps to only one Salesforce Account record and avoids duplicate-match problems during upsert. Salesforce documentation defines External ID fields as fields that contain record identifiers from outside Salesforce and can be used to update or upsert records.

A. Required is not necessary for the upsert-matching requirement.

B. Encrypted/Text encrypted is not appropriate because encrypted fields are not used for this legacy-ID matching purpose.

===========

The correct answer is A. Quick Action on the Account object.

Universal Containers wants users to create Opportunity records related to an Account, with many Opportunity fields automatically populated from the Account and some fields entered by the user. The best solution is an object-specific Quick Action on Account that creates an Opportunity. Object-specific actions run in the context of the parent record, and predefined field values can automatically populate fields to make record creation faster and more consistent.

C is incorrect because a Quick Action on Opportunity would not naturally start from the Account context. B and D are incorrect because assignment rules are not used for creating related Opportunities or prepopulating fields.

===========

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

To add Chatter feed functionality to a custom object Lightning record page, the app builder should use the standard Chatter component in Lightning App Builder. Salesforce documentation states that the Feed component was renamed Chatter in Lightning App Builder and is used to place the publisher and feed combination on a record page.

A is incorrect because no custom Chatter feed component is required. B is incorrect because related lists do not add the Chatter feed. D is incorrect because the standard Chatter component is already available; an AppExchange component is unnecessary.

===========

A roll-up summary field requires a master-detail relationship. Since Galaxy__c and Star__c currently have a lookup relationship, the app builder cannot create a standard roll-up summary field to count related Star__c records. The lookup must be converted to master-detail first, with Galaxy__c as the master and Star__c as the detail. Salesforce Trailhead confirms that roll-up summary fields display values on the master record based on directly related detail records in a master-detail relationship.

===========