AW Computing uses a private sharing model for opportunities. Whenever
an opportunity with a type of Service Agreement is created, all users in the Service
Manager role should be able to view the opportunity.
Which tool should AW Computing use to accomplish this?
Correct answer:
B. Criteria-based sharing rules
Explanation:
Why Criteria-Based Sharing Rules Are Correct?
Criteria-based sharing rules are the best tool for this scenario because they allow you to share records based on specific field values. In this case, AW Computing wants to share Opportunities with the Type field set to “Service Agreement” with all users in the Service Manager role. A criteria-based sharing rule can be set up to check if the Opportunity Type equals “Service Agreement” and then grant read access (or more, if needed) to users in the Service Manager role.
For example, imagine an Opportunity record with Type = “Service Agreement.” The criteria-based sharing rule would automatically share this record with all Service Managers, allowing them to view it, even though the Opportunity object uses a private sharing model. This solution is declarative (no coding required), automated, and perfectly matches the requirement to share based on a field value (Type).
Why the Other Options Are Incorrect?
A. Owner-based sharing rules: Owner-based sharing rules grant access based on who owns the record, not based on the record’s field values. For example, you could use an owner-based sharing rule to share all Opportunities owned by users in the “Sales Team” role with the “Service Manager” role. However, this scenario requires sharing based on the Opportunity Type (“Service Agreement”), not the owner, so owner-based sharing rules don’t meet the requirement.
C. Apex sharing rules: Apex sharing rules involve writing custom code (Apex) to programmatically share records. For instance, you could write Apex to share Opportunities with Type = “Service Agreement” with Service Managers. However, this is unnecessarily complex because criteria-based sharing rules can achieve the same result declaratively, without coding. Apex sharing is typically used for complex sharing logic that can’t be handled by standard sharing rules, which isn’t the case here.
D. Manual sharing: Manual sharing allows users to manually share individual records with other users or roles. For example, an Opportunity owner could manually share a “Service Agreement” Opportunity with Service Managers. However, this is not automated and requires users to take action for each record, which is inefficient and doesn’t meet the requirement for automatic sharing when the Opportunity Type is “Service Agreement.”
Summary:
Criteria-based sharing rules (Option B) are the best choice because they automatically share Opportunities with Type = “Service Agreement” with users in the Service Manager role, based on a field value, in a private sharing model. Owner-based sharing rules focus on the owner, not field criteria; Apex sharing rules are overly complex for this task; and manual sharing isn’t automated, making it impractical.
Reference:
Salesforce Help: Criteria-Based Sharing Rules
This documentation explains how criteria-based sharing rules work, including how to share records based on field values like Opportunity Type.
Question 12Choose 1
The app builder at AW Computing has been asked to track the number of times a case has
been reopened.
Which solution should the app builder utilize to help with this request?
Correct answer:
C. Record-triggered flow
Explanation
A record-triggered flow can detect when a Case is updated and its status changes from Closed to a non-closed status. It can then increment a custom number field that tracks how many times the Case has been reopened.
🟢 Correct Option: C. Record-triggered flow
Configure a record-triggered flow on the Case object to run when a record is updated. Use entry conditions or a Decision element to identify a transition from Closed to a non-closed status, then increment a custom number field such as Reopened_Count__c. This declarative solution automatically tracks each reopening without requiring Apex code or manual data entry.
🔴 Incorrect Options
🔴 A. Screen Flow
A Screen Flow requires a user to interact with its screens or launch it through a configured process. It is not the most suitable option for automatically tracking every Case reopening.
🔴 B. Apex Trigger
An Apex Trigger can detect status changes and update a counter, but it requires custom code. A record-triggered flow can handle this requirement declaratively.
🔴 D. Scheduled-Triggered Flow
A schedule-triggered flow evaluates records at scheduled times rather than immediately responding to a Case status change. It is not suitable for reliably counting each reopening event.
Salesforce Help explains how record-triggered flows automate actions when records are created or updated.
⇒ Salesforce Trailhead: Record-Triggered Flows
Question 13Choose 1
Universal Containers needs the 18-digit record ID from Opportunity records when exporting
data to Excel in order to ensure each record is treated uniquely.
What formula should an app builder use to create this new field?
Correct answer:
B. CASESAFEID(Id)
Explanation
CASESAFEID(Id) is the correct formula function. This function returns the 18-character, case-insensitive version of a 15-character ID. The 15-character ID is case-sensitive, which can cause issues when exported to external systems like Excel, as those systems may not preserve the case. The 18-character ID includes a 3-character checksum that ensures its uniqueness regardless of case, making it safe for export and use in spreadsheets or databases where case-sensitivity might be an issue.
Why the other options are incorrect: A. ISNUMBER(Id): This function returns a Boolean value (TRUE or FALSE) checking if the referenced value is a number. A Salesforce ID is a text string, not a number, so this formula would always return FALSE. It is useless for this requirement.
C. TEXT(Id): While this function correctly converts the ID to a text string, it does not perform the necessary conversion from a 15-character ID to an 18-character ID. If the record has already been saved and has the 18-character ID, TEXT(Id) would simply return that 18-character ID. However, for consistency and to guarantee the 18-character format (especially in any context), CASESAFEID() is the more explicit and functionally correct choice.
D. VALUE(Id): This function converts a text string representing a number into a numeric value. Since a Salesforce ID is an alphanumeric text string (e.g., 0015j00000X1Y2Z3), it cannot be converted to a number. Using this function would result in an error.
Reference: This falls under the Data Modeling and Management section. It tests knowledge of Salesforce record IDs and the specific formula functions available for handling them within a custom formula field.
Key Takeaway: Always use CASESAFEID(Id) in formula fields when you need a guaranteed case-insensitive, 18-character record ID for data export or integration purposes.
Question 14Choose 1
An app builder wants to create a custom object and 10 fields.
What should they use to create the object, fields, and relationships quickly from one place?
Correct answer:
A. Schema Builder
Explanation:
Schema Builder is the most efficient tool for creating a custom object, adding multiple fields, and defining relationships — all from a single visual interface.
It provides a drag-and-drop canvas that lets you:
Create custom objects
Add fields (standard and custom)
Define relationships (lookup, master-detail)
View the entire data model in real time
This is ideal when you're building a new object with several fields and want to visualize how it fits into your org’s data architecture.
❌ Why Not the Other Options? B. Developer Console Primarily used for coding (Apex, SOQL, etc.). Not designed for declarative object/field creation. C. Manage Field Permissions Used to control visibility/access to fields, not for creating objects or fields. D. Lightning Object Creator Allows creation of a custom object from a spreadsheet, but doesn’t support creating multiple fields and relationships in one place visually.
🔗 Reference:
Salesforce Help: Create Objects with Schema Builder
CRS Info Solutions: Step-by-step guide to creating objects and fields
Question 15Choose 1
A customer service representative at a call center wants to be able to collect
information from customers using a series of question prompts.
What should an app builder use to accomplish this?
Correct answer:
B. Flow
Explanation:
Flow for Interactive Guided Processes: A Flow is the correct tool for creating a series of question prompts. A Screen Flow, specifically, can present a user (in this case, the customer service representative) with a series of screens to collect information and guide them through a business process. Approval Process: An Approval Process is used to automate how records are approved in Salesforce, not to collect information interactively. Validation Rule: A Validation Rule is used to ensure data quality by preventing users from saving records with incorrect data. It doesn't guide users through a series of questions. Path: A Path is a visual tool on a record page that guides users through stages in a process (like a sales process). While helpful for visualizing progress, it is not designed to present a series of questions and prompts to collect information.
How a Flow would work
An app builder would create a Screen Flow and embed it on the appropriate record page (e.g., the Case record page). The flow would then:
Display a screen with the first question.
Use the user's input to determine the next screen or action.
Continue this process, collecting all necessary information from the customer via the representative.
Finally, the flow would perform an action, such as creating a new record, updating the current record, or sending an email. The correct option is B. Flow.
Question 16Choose 1
Universal Containers has deployed custom tabs to Production via changes sets, without
including the profile settings or permission sets.
What is the settings for the visibility of custom tabs?
Correct answer:
A. Custom tabs are default off for all users.
Explanation:
When custom tabs are deployed to a Salesforce org (e.g., Production) via change sets without including profile settings or permission sets, the visibility of those tabs is not automatically configured for users. Let’s break down the options:
A. Custom tabs are default off for all users: Correct. In Salesforce, when a custom tab is deployed without associated profile settings or permission sets, the tab is not automatically visible to any users. The tab exists in the org, but its visibility must be explicitly enabled by updating profiles or permission sets to grant access (e.g., setting the tab to "Default On" or "Tab Hidden"). By default, the tab is "Default Off," meaning users cannot see it until permissions are configured. B. Custom tabs are default on for all users: Incorrect. Custom tabs are not automatically visible to all users upon deployment. Visibility requires explicit configuration in profiles or permission sets, such as setting the tab to "Default On." C. Custom tabs are hidden for all users: Incorrect. While this sounds similar to "Default Off," the term "hidden" implies the tab is explicitly set to "Tab Hidden" in profiles, which is not the default behavior. "Default Off" means the tab is not visible unless a user’s profile or permission set explicitly enables it, whereas "Tab Hidden" is a specific setting to hide the tab even if permissions exist. D. Custom tabs are NOT deployed: Incorrect. The question states that the custom tabs have been deployed via change sets, so they are present in the Production org. The issue is about their visibility, not whether they were deployed.
Why "Default Off"?
In Salesforce, tab visibility is controlled by profiles or permission sets. When deploying custom tabs without these settings, Salesforce does not assume any visibility settings. The tabs are deployed but are effectively "Default Off" for all users, meaning they won’t appear in the user interface (e.g., in the App Launcher or navigation bar) until an administrator configures access. This is a security and governance feature to ensure that new tabs are only visible to the intended users.
Implementation Note:
To make the custom tabs visible after deployment:
Navigate to the relevant profiles or permission sets in Setup.
Edit the Tab Settings for the custom tab.
Set the tab to Default On (visible in the app navigation) or Default Off (available but not shown unless added by the user). Avoid Tab Hidden if you want users to access it.
Save and test visibility for affected users.
References:
Salesforce Help: Custom Tabs
Salesforce Help: Control Tab Visibility
Trailhead: Change Sets Best Practices
Question 17Choose 1
An app builder has a custom component they want to make available on the utility bar, but
the component is unavailable.
How should the component be tagged?
Correct answer:
B. For use in Lightning App Builder.
Explanation:
The utility bar is a part of the Lightning App Builder interface. To make a custom Lightning web component or Aura component available for placement on the utility bar, it must be explicitly configured to be compatible with the Lightning App Builder. This is done by including the tag in the component's XML metadata file and specifying the Lightning__AppPage target.
Why this is correct: Tagging a component "For use in Lightning App Builder" (Lightning__AppPage) is the prerequisite that makes it available for drag-and-drop into any region of an app page built with the tool, which includes the utility bar, the header, the main body, and the footer. The utility bar is not a separate tag but a specific location within the App Builder's purview.
Why the other options are incorrect: A. For use on record pages: This is a more specific target (Lightning__RecordPage). While a component tagged for record pages is also available in the Lightning App Builder (because Lightning__RecordPage inherits from Lightning__AppPage), it is not the most direct or fundamental answer. The question is about general availability in the App Builder tool itself.
C. For use on the utility bar: There is no specific, standalone metadata tag for "utility bar." The utility bar is a location within an app built in the Lightning App Builder. Availability is controlled by the broader Lightning__AppPage target.
D. For use in App Manager: The App Manager is an administrative setup screen used to create and manage apps. Custom components are not added to the App Manager interface itself. This is not a valid target for a component.
Reference: This falls under the User Interface section. It tests the understanding of how to configure custom components for deployment in different parts of the Lightning Experience, specifically the metadata targets required for the Lightning App Builder.
Key Takeaway: To make a component available in the Lightning App Builder (and consequently its utility bar), its .js-meta.xml file must include the target Lightning__AppPage.
Question 18Choose 1
A business user wants a quick way to edit a record's status and enter a custom due date
field from the record's feed in Salesforce Mobile App.
What should be used to accomplish this?
Correct answer:
A. Custom action
Explanation:
Why A is Correct: A Custom Action is the modern and supported way to create a quick, inline editing experience directly from the Chatter feed on both desktop and the Salesforce Mobile App. You can create a "Update Record" action that is pinned to the publisher layout. This allows users to see and interact with specific fields (like Status and a custom Due Date) without having to navigate away from the feed to the full record edit page. This provides the "quick way" the business user requires, especially on mobile where screen space is limited.
Why B is Incorrect: Custom Buttons are built using JavaScript or a URL. They are not fully supported or displayed in the Salesforce Mobile App. Even if they were, they typically navigate the user to a new page, which is not the "quick" inline experience requested from the feed.
Why C is Incorrect: A Quick Access Link (part of the Utility Bar) is designed for global navigation within the Salesforce console or app. It is not used for editing specific fields of a record from its feed. It's a navigation tool, not an editing tool.
Why D is Incorrect: A Custom URL Formula field is a read-only field that displays a hyperlink. It cannot be used to edit the data on the record itself. Its purpose is to link to an internal or external page.
Reference: Salesforce Help - "Add Actions to the Publisher Layout" and "Actions Overview". The documentation specifically promotes using actions for quick updates: "Create actions to make your users more productive. For example, add an action that lets users update a record... without navigating away from the page they’re on." This functionality is core to the Lightning Experience and Mobile App.
Question 19Choose 1
Universal Containers is setting up salesforce for the first time. Management wants the
sales and marketing teams to have different navigation names in the salesforce1 mobile
app. Which option is available to an app builder to satisfy the requirement?
Correct answer:
C. Create mobile navigation menus for both the sales and marketing profiles.
Explanation:
In the Salesforce1 mobile app (now part of the Salesforce mobile experience), navigation menus can be customized by profile. This means:
You can create distinct mobile navigation menus for different user profiles.
The App Builder can configure what tabs, objects, and apps appear for each team.
This allows sales and marketing teams to see different navigation names and layouts, tailored to their needs.
This is the only option that directly addresses the requirement to customize navigation menus based on team.
❌ Why the other options don’t work: A. Create sales and marketing profiles to ensure read access to different objects This controls data access, not navigation layout. B. Create roles and assign homepage layouts Homepage layouts affect desktop experience, not mobile navigation. D. Create public groups and mobile menus Mobile navigation menus cannot be assigned to public groups — only to profiles.
Universal Containers (UC) has several picklist fields on the Account object whose values
are routinely modified to meet changing business requirements. Due to
these revolving changes, UC has a high number of inactive picklist values that are
impacting system performance and user experience.
What can the app builder do to alleviate this issue?
Correct answer:
B. Set up Global Values in Picklist Value Sets.
Explanation:
The issue described involves a high number of inactive picklist values on the Account object’s picklist fields, which negatively impacts system performance and user experience. Salesforce provides Global Value Sets (also known as Picklist Value Sets) as a solution to manage picklist values more efficiently, especially when values are reused across multiple fields or need frequent updates.
B. Set up Global Values in Picklist Value Sets (Correct):
Global Value Sets allow you to define a single set of picklist values that can be reused across multiple picklist fields in different objects. By converting the picklist fields on the Account object to use a Global Value Set, Universal Containers can centrally manage the values, including deactivating or removing outdated ones. This reduces redundancy, simplifies maintenance, and can improve performance by minimizing the number of inactive values stored for each field.
Additionally, Global Value Sets make it easier to update values across all associated fields at once, addressing the issue of frequent changes due to evolving business requirements. Reference: Salesforce Help - Define Picklist Value Sets
Why not the other options? A. Establish upper bound on existing picklists in Picklist Settings (Incorrect):
Salesforce does not provide an option in Picklist Settings to set an upper bound on the number of picklist values (active or inactive). While there are system limits (e.g., 1,000 total values for a standard picklist, including active and inactive), these are not configurable by the admin in the way described. This option does not address the issue of managing inactive values or improving performance. Reference: Salesforce Help - Picklist Limitations
C. Remove upper bound on inactive picklist values in Picklist Settings (Incorrect):
There is no setting in Salesforce to specifically “remove an upper bound” on inactive picklist values. The platform imposes limits on the total number of picklist values (active and inactive), and inactive values still count toward this limit. Removing or adjusting such a bound is not a feature in Salesforce, and this option does not solve the performance or user experience issue. Reference: Salesforce Help - Picklist Field Limits
D. Convert the picklist fields to a different field type that will still meet the business requirements (Incorrect):
Converting picklist fields to another field type (e.g., text, multi-select picklist, or lookup) may not be feasible or desirable, as it could disrupt existing business processes, reports, or integrations that rely on the picklist structure. Additionally, this does not directly address the issue of managing inactive values or improving performance. It’s a drastic change that may not meet the business requirements without significant rework. Reference: Salesforce Help - Change Field Type
Recommended Approach:
Navigate to Setup > Object Manager > Picklist Value Sets.
Create a new Global Value Set with the required picklist values.
Update the Account object’s picklist fields to use the Global Value Set instead of individual picklist values.
Review and remove unnecessary inactive values from the Global Value Set to streamline performance.
Test the updated fields to ensure they meet business requirements and improve user experience.
Additional Notes:
Inactive picklist values can impact performance, especially in large orgs, as they are still stored and processed in the background (e.g., in reports, list views, or SOQL queries). Using Global Value Sets reduces redundancy and simplifies value management.
If the number of inactive values is significantly high, you can also archive or delete unused values (if not referenced in historical data) to further optimize performance, but this must be done cautiously to avoid data integrity issues.
Reference:
Salesforce Help: Create and Manage Global Picklist Value Sets
Salesforce Trailhead: Data Modeling - Picklist Administration
Experience the real exam before you take it
Our timed 2026 Platform App Builder practice test mirrors the format, number of questions and time limit of the official exam.
The #1 challenge isn't just knowing the material, it's managing the clock. The simulation builds your speed and stamina, so you walk in knowing exactly what to expect.