Free Platform-App-Builder Practice Test Questions 2026

Explanation:

To provide Salesforce mobile app users with access to a contact’s Twitter profile, the app builder should leverage the Twitter component available in Lightning Experience, which can be added to a Contact Lightning page. This component displays a contact’s Twitter profile based on a field (e.g., a Twitter handle stored in a custom field). Here’s why:

Option A: Add a formula field to the Contact page layout.
Incorrect. A formula field could generate a Twitter profile URL (e.g., HYPERLINK("https://twitter.com/" & Twitter_Handle__c, "View Twitter")), but it only creates a clickable link. It doesn’t provide the rich Twitter profile integration (e.g., tweets, followers) available through the Twitter Lightning component, which is more user-friendly for mobile access.

Option B: Add an AppExchange Lightning Component to the mobile app.
Incorrect. While AppExchange may offer Twitter-related components, Salesforce provides a standard Twitter Lightning component for displaying Twitter profiles. Using a native component avoids the need for third-party solutions, which may require additional configuration, cost, or maintenance.

Option C: Add the Twitter component to mobile view Lightning pages.
Correct. The standard Twitter Lightning component can be added to a Contact Lightning record page via the Lightning App Builder. This component integrates with a Twitter handle field (e.g., Twitter_Handle__c) to display the contact’s Twitter profile, including recent tweets and profile details, optimized for both desktop and mobile views in the Salesforce mobile app.

Option D: Add a Twitter Quick Action to the mobile navigation.
Incorrect. Quick Actions are used for creating or updating records, logging calls, or performing specific tasks, not for displaying external content like a Twitter profile. There’s no standard Quick Action for viewing Twitter profiles, and custom actions would be less seamless than the Twitter component.

Implementation Steps:
Ensure a custom field (e.g., Twitter_Handle__c) exists on the Contact object to store the Twitter handle.
In Setup, go to Lightning App Builder and edit the Contact Lightning record page.
Drag the Twitter component (under Standard Components) onto the page layout.
Configure the component to map to the Twitter handle field (e.g., Twitter_Handle__c).
Save and activate the page, ensuring it’s assigned to the mobile app (default Lightning pages apply to both desktop and mobile unless customized separately).
Verify the Twitter profile displays correctly in the Salesforce mobile app.

References:
Salesforce Documentation: Add the Twitter Component to Lightning Pages
Salesforce Help: Customize Lightning Record Pages for Mobile

Explanation:

Why: The requirement is that a Lead must have a sales owner (a User) before it can be added as a Campaign Member. In formulas, the polymorphic Owner field can be checked via Owner:User (populated when owned by a User) or Owner:Queue (populated when owned by a Queue).
If the Lead is still in the qualification queue, Lead.Owner:User.Id is blank.
ISNEW() ensures the rule fires only when creating the Campaign Member (so you don’t block later edits).

Why the others are wrong
A. ISBLANK(Lead.Owner.Id) — the Owner is never blank (it’s either a User or a Queue).
B. NOT(ISNEW() && ISBLANK(Lead.Owner:Queue.Id)) — this would fire on any edit (since ISNEW() is false → expression becomes NOT(FALSE)), blocking updates unnecessarily.
D. NOT(ISBLANK(Lead.Owner:Queue.Id)) — fires whenever the Lead is owned by a queue, including on edits; too broad and would prevent updates.

Explanation:

An Approval Process is the standard Salesforce tool for automating record approval. It is the only option that can route a record to a specific user (the CFO) for review and approval based on a predefined set of criteria (e.g., a discount of more than 30%).

Here's a breakdown of how it would work:
The approval process is configured on the Opportunity object.
The entry criteria are set to trigger the process when the Discount field is greater than 30%.
The approval steps are defined to route the request to the CFO.
The final approval action can set the opportunity to "Closed Won," while the final rejection action can set it back to a different stage and notify the user.

Why the other options are incorrect
B. Email Alert: An email alert is a component of a larger automation tool (like a Workflow Rule or Flow), not a stand-alone solution. It can send a notification, but it can't enforce a business process or require a specific user's approval before a record is closed.
C. Field Update: A field update is an action within an automation tool (like a Workflow Rule or Flow) that modifies a field's value. It cannot, by itself, enforce a review process or stop a deal from being closed.
D. Workflow Rule: A Workflow Rule is a legacy automation tool. While it can trigger actions like email alerts or field updates, it cannot enforce an approval process where a user must manually approve or reject a record. Workflow Rules are not capable of locking records or managing a formal approval request.

Explanation:

The issue is that brokers at DreamHouse Realty need to view key fields on Contact records at a glance in the Salesforce mobile app without scrolling, despite the small screen size. The app builder must configure the mobile app to display these fields at the top of the Contact record page.

Option A: Compact layout
Correct. Compact layouts in Salesforce determine which fields are displayed in the highlights panel at the top of a record page in the Salesforce mobile app (and in Lightning Experience for the record highlights section). By customizing the Contact object’s compact layout to include the key fields the brokers need, the app builder ensures these fields are prominently displayed at the top of the screen in the mobile app, eliminating the need to scroll.

Option B: Record Detail component
Incorrect. The Record Detail component is used in Lightning App Builder to display a record’s full details on a Lightning record page. While it shows all fields in the page layout, it does not control the compact, at-a-glance view at the top of the mobile app screen. Fields in the Record Detail component may still require scrolling to view on a small screen.

Option C: Object specific action
Incorrect. Object-specific actions (e.g., Quick Actions) are used to create, update, or perform specific tasks on a record, such as logging a call or creating a related record. They do not control the display of fields on the mobile app’s record page or prioritize key fields at the top.

Option D: Mobile navigation
Incorrect. Mobile navigation settings in Salesforce configure the app’s navigation menu, determining which objects, apps, or tabs are accessible. They do not affect the layout of fields on a record page or prioritize specific fields for display.

Implementation Steps:
Go to Setup > Object Manager > Contact > Compact Layouts.
Edit the existing compact layout or create a new one for Contacts.
Add the key fields (up to 10) that brokers need to see at a glance (e.g., Name, Phone, Email, Title).
Save and assign the compact layout as the primary compact layout for the Contact object (via Compact Layout Assignment).
Test in the Salesforce mobile app to ensure the selected fields appear in the highlights panel at the top of the Contact record page.

References:
Salesforce Documentation: Customize Compact Layouts
Explains how compact layouts control the fields displayed in the mobile app’s highlights panel and Lightning Experience record highlights.
Salesforce Help: Salesforce Mobile App Customization
Details how compact layouts are used to optimize the mobile app experience.

Explanation:

To control which fields a user can see on an object, you use field-level security (FLS). This is the most granular level of control for data visibility in Salesforce. It determines whether a user can view, edit, or delete the value of a specific field. FLS is configured on the profile or permission set and applies across the entire platform, including page layouts, reports, and API access.
In this scenario, the requirement is to show the "Jupiter" field only to users with the "Outer Planets" profile. By setting the field-level security for the "Jupiter" field to "Visible" only on the "Outer Planets" profile, you ensure that no other profile can see the field, regardless of the page layout.

Why the Other Options are Incorrect?

A. Classic encryption:
This is a security feature used to encrypt data at rest, making it unreadable in the database. It's not a tool for controlling field visibility based on a user's profile. Classic encryption is meant to protect sensitive data from being accessed by unauthorized parties, but it doesn't solve the problem of making a field visible to one profile and invisible to all others.

B. Filtered view:
A filtered view, or a list view, is a tool for filtering a list of records based on criteria. It affects which records are displayed in a list, not which fields are visible on a record's detail page. It's a tool for record-level filtering, not field-level visibility.

D. Sharing rules:
Sharing rules are used to grant additional record-level access to users or groups, beyond what's defined by the organization-wide defaults (OWD). They control which records a user can see, not which fields they can see on those records. For instance, a sharing rule might give a user access to all "Solar System" records owned by a specific sales team, but it won't hide a field like "Jupiter" from that user if they already have field-level access to it. Sharing rules and field-level security operate at different levels of the Salesforce security model.

References:
Salesforce Help: Field-Level Security
Salesforce Trailhead: Data Security

Explanation:

When converting a lookup relationship to a master-detail relationship in Salesforce, there are strict conditions that must be met. Universal Containers is likely facing two common blockers:

✅ B. There are already two master-detail relationships on the Invoice Line Item
Salesforce allows a maximum of two master-detail relationships per object.
If the Invoice Line Item object already has two master-detail relationships, you cannot add a third.
You would need to remove one before converting the lookup.

✅ C. Invoice Line-Item records exist without having the Invoice lookup field populated This is the most common blocker.
When converting to master-detail, the lookup field becomes required.
If any existing Invoice Line Item records have a blank Invoice reference, the conversion will fail2.
You must populate all lookup fields before attempting the conversion.

❌ Why the Other Options Don’t Work
A. Custom objects are unable to be on the detail side of a master-detail relationship ❌
Incorrect — custom objects can absolutely be detail objects in master-detail relationships.
D. There is a roll-up summary field on the Invoice object ❌
Not a blocker — in fact, roll-up summary fields are only available when a master-detail relationship exists. They don’t prevent conversion.

📘 References
Salesforce Help: Unable to create a master-detail relationship

Explanation:

For custom solutions where ease of updates is the primary consideration, a managed package is the superior choice for an app builder. Managed packages are designed for distribution and ongoing maintenance and updates, which the package developer can push to all installed instances.
Here's a breakdown of why this is the best option and why the others are incorrect:

A. A managed package from AppExchange: This is the best option for ease of updates. The developer of a managed package can push updates and patches to their customers automatically or offer them as an upgrade. The package's intellectual property is also protected, as the code is hidden from the end-user.
B. An unmanaged package from AppExchange: Unmanaged packages are essentially templates or open-source solutions. They do not support upgrades. If the package developer releases a new version, the end-user must manually uninstall the old version (potentially losing data) and then reinstall the new version. This process is not easy and is prone to errors.
C. An open-source unmanaged package: This is essentially the same as option B. Being open-source means the components are editable after installation, but there is no built-in upgrade path. Updates must be managed manually, which is not easy.
D. An open-source custom development: While this gives an app builder complete control, it also puts the full burden of maintenance and updates on the app builder. There are no automated update mechanisms. This option offers the least ease of updates and relies entirely on in-house development and management.

Explanation

Why: In Lightning App Builder you can drop a Rich Text component on the record page and use Component Visibility filters to show it only when a condition is met—e.g., Case → Account → Support_Level__c = "Platinum". That displays a clear banner/notice without code.

Why not the others
B/C: Visualforce is unnecessary; this is easily done with native Lightning visibility filters.
D: You can’t assign Lightning record pages based on a record’s data (or a related record’s data); assignment is by app, record type, and profile—not “platinum accounts.”

Explanation:

Ursa Major Solar operates in a private data model (e.g., Organization-Wide Default (OWD) set to Private for Work Orders and related objects), meaning users only have access to records they own or those explicitly shared. The Service Coordinator (SC) needs to:
Modify data and delete attachments on Work Orders owned by technicians in a specific region. Access other related records owned by those technicians.

Here’s why the chosen solution works and others do not:
Option A: Give the SC a permission set with the Modify All Data system permission.
Incorrect. The Modify All Data permission grants full access to all records and objects in the org, far exceeding the SC’s need for access to specific technicians’ Work Orders and related records in one region. This violates the principle of least privilege and poses a security risk.
Option B: Put the SC in the role hierarchy above the technicians whose work orders they review.
Correct. In a private data model, placing the SC in a role above the technicians in the role hierarchy grants the SC access to all records owned by those technicians (and their subordinates) for objects with Private OWD. This includes Work Orders and related records (e.g., via lookup or master-detail relationships). The SC can then edit fields, delete attachments, and access related records without needing overly broad permissions. Role hierarchy is a scalable, secure way to meet the requirement.
Option C: Create a workflow rule that updates records owned by technicians in that region with the SC.
Incorrect. Workflow rules (now retired in favor of Flows) can update fields or trigger actions but cannot grant record access or modify sharing rules dynamically. They also cannot delete attachments or provide access to related records, making this option irrelevant.
Option D: Change work order access on the SC's profile to 'Modify All.' Incorrect. Setting Modify All on the Work Order object via the SC’s profile grants the SC edit and delete access to all Work Orders in the org, not just those owned by technicians in a specific region. This is too broad and does not address access to related records owned by technicians.

Implementation Steps:
Verify the OWD for Work Orders and related objects is set to Private in Setup > Sharing Settings. In Setup > Roles, create or adjust the role hierarchy:
Place the SC’s role (e.g., “Regional Service Coordinator”) above the roles of technicians in the specific region (e.g., “Region X Technicians”).
Ensure the SC’s profile has at least Read, Edit, and Delete permissions for the Work Order object and related objects (via Object Permissions).
Confirm the SC can delete attachments by ensuring the profile has access to the ContentDocument object (for attachments) or appropriate permissions for Salesforce Files.
Test in a sandbox to verify the SC can edit Work Orders, delete attachments, and access related records owned by technicians in the region.

References:
Salesforce Documentation: Role Hierarchy
Explains how role hierarchy grants access to records owned by users lower in the hierarchy in a private data model.
Salesforce Help: Sharing Rules and OWD
Details how Private OWD restricts access and how role hierarchy expands it.

Explanation:

In the context of application lifecycle management (ALM) and release management, Cloud Kicks needs to categorize changes like bug fixes and simple changes.

Option A: Patch
Correct. A patch release is used for small, targeted updates, such as bug fixes, minor enhancements, or simple changes that don’t significantly alter functionality. These releases typically have a low risk and are deployed quickly to address issues or make small improvements without requiring extensive testing or downtime.
Option B: Minor
Incorrect. A minor release involves more significant updates than a patch, such as new features or enhancements that add functionality but don’t overhaul the system. Minor releases require more testing and planning than bug fixes or simple changes.
Option C: Major
Incorrect. A major release involves significant changes, such as new modules, major feature additions, or architectural updates. These require extensive testing, planning, and often user training, far beyond the scope of bug fixes or simple changes.
Option D: Rollback
Incorrect. A rollback is not a release category but an action taken to revert a system to a previous state after a failed or problematic deployment. It’s unrelated to categorizing bug fixes or simple changes.

References:
Salesforce Documentation: Application Lifecycle Management
Describes patch releases as small updates for bug fixes and minor changes.
Salesforce Trailhead: Release Management Basics
Explains patch, minor, and major release types in the context of Salesforce ALM.

Explanation:

Why: Roll-up summaries don’t work on lookup relationships like Case → Account. The standard pattern is to use Process Builder (on Case create/edit) to launch an autolaunched Flow that:
Queries the number of open Cases for the Case’s Account (and its Parent Account, if any),
Updates number fields on those Account records with the counts.

Why not the others
B. Workflow: can’t perform record-count queries.
C. Approval Process: unrelated to counting or updating fields.

Note:
Today you can do this with a single record-triggered Flow (no PB), but given these options, the combo is Process Builder + Flow.

Explanation:

Universal Containers needs to capture crossroads or location markers for remote construction sites, which are inherently location-based data points. The appropriate field type in Salesforce for storing location information, such as coordinates or addresses, is the Geolocation field.

Option A: Number
Incorrect. A Number field stores numeric values (e.g., integers or decimals) and is unsuitable for capturing location-based data like crossroads or markers, which require coordinates (latitude and longitude) or address-like information.
Option B: Geolocation
Correct. The Geolocation field type is designed to store latitude and longitude coordinates, making it ideal for capturing precise location data like crossroads or location markers. It supports both custom and standard objects and can be used to display maps or calculate distances in Salesforce.
Option C: Reference
Incorrect. A Reference (Lookup or Master-Detail) field creates a relationship to another Salesforce object, not a way to store location data. It’s irrelevant for capturing crossroads or markers unless referencing a separate object with location data, which isn’t implied here.
Option D: External Lookup
Incorrect. An External Lookup field links to records in an external system via an External ID, not for storing location data like coordinates or markers. It’s used for integrations, not direct location capture.

Implementation Notes:
Create a custom Geolocation field (e.g., Site_Location__c) on the relevant object (e.g., a custom Container or Site object).
Configure the field to store latitude and longitude (in decimal degrees).
Customers can provide crossroads or markers as coordinates, or UC can convert address-based inputs to coordinates using external tools (e.g., Google Maps) before entering them.
Add the field to page layouts for visibility and consider using it in reports or maps for delivery planning.

References:
Salesforce Documentation: Geolocation Field Type
Describes the Geolocation field for storing latitude and longitude coordinates.