Download Latest Platform-App-Builder Questions

The three reasons user A has access but user B is unable to access the record are:

User A is on the same account team as user C. Account teams are groups of users who work together on an account. Users who are on an account team can have access to the account and related records owned by other team members.

User C has manually shared the record with user A. Manual sharing is a way of granting access to individual users or groups by the record owner or someone above them in the role hierarchy.

User A is in a public group that has access via a sharing rule. Public groups are groups of users who can be used to share data or assign permissions. Sharing rules are automatic rules that grant access to groups of users based on certain criteria. Option B and D are not reasons for user A’s access.

For tracking whether contracts have been sent for Opportunities:

D. Checkbox. This field type allows users to clearly indicate (Yes/No) whether a contract has been sent. This binary nature of checkboxes makes it simple to filter and report on Opportunities based on whether a contract was sent.

Steps to configure this field:

Navigate to Setup → Object Manager → Opportunity.

Click Fields & Relationships → New → Checkbox.

Define the field with a label (e.g., Contract Sent).

Set the default value to false (unchecked).

Add the field to the relevant page layouts.

This setup facilitates accurate reporting and ensures that opportunities cannot be marked as "Closed Won" without indicating whether a contract was sent.

For guidance on creating fields, see Salesforce's documentation on Custom Field Creation.

Component visibility filter is the feature on the Lightning app builder that should be utilized to restrict a Lightning component to mobile app users. According to the Salesforce documentation, “Use component visibility filters to show or hide components on a record page based on field values or user profile.” Chatter feed, highlights panel, and related list quick links are not features for controlling component visibility, but standard components that can be added to a record page.

The Account record includes Invoice roll-up summary fields. This is correct because roll-up summary fields are only available on the master object in a master-detail relationship, and changing the field type to lookup would delete the roll-up summary fields