Universal Containers has created two custom objects called Seminars and Attendees.
Organization-wide defaults for these objects have been set to Private. Universal Containers
wants to set up a new Junction object between these custom objects. A select group of
users should be able to edit records in the Junction object.
Which two steps should an app builder take to configure the proper security?
Correct answer:
A. Set Sharing Settings to Road Only on both Master-Detail relationship fields.
D. Create an owner-based sharing rule that gives Road action to the junction object.
Explanation:
A. Set Sharing Settings to Read Only on both Master-Detail relationship fields: When a user is given edit access to a junction object record, they will inherit access from the master records. To allow a user to edit the junction record while only providing read access to the master records, you need to set the "Sharing Settings" option on the master-detail relationship field to "Read Only". This prevents a user who has edit permission on the junction object from also gaining edit access to the master records. D. Create an owner-based sharing rule that gives Read action to the junction object: With the junction object's OWD set to Private, only the record owner and users higher in the role hierarchy have access by default. To give a select group of users (not just the owner) the ability to edit the junction records, you must first give them at least Read access via a sharing rule. Once they have Read access, and their profile permissions grant Edit access, they can edit the junction records. This sharing rule can be based on the owner of the junction records.
Why other options are incorrect B. Create owner-based sharing rules that give Read access to the master objects: While users need at least Read access to the master objects (Seminars and Attendees) to interact with the junction object, creating sharing rules for the master objects is not sufficient to grant edit access specifically on the junction object. The question asks how to secure access to the junction object for editing, which requires a sharing rule on the junction object itself. C. Sat lookup filters on both Junction object relationship field: Lookup filters are used to restrict the records that can be selected in a lookup relationship. They do not control or grant record-level access for security purposes.
Question 32Choose 2
Cloud Kicks is implementing an approval process for opportunities that requires managers
to approve all opportunities above $50,000 before they can be
marked as Closed Won.
Which two delivery methods can a manager utilize to respond to approval requests in the
Salesforce mobile app?
(Choose 2 answers)
Correct answer:
B. In-App Notification
C. Record Detail
Explanation:
Cloud Kicks requires managers to approve opportunities exceeding $50,000 before they can be marked as Closed Won, and the approval process must be accessible via the Salesforce mobile app. In Salesforce, approval requests can be responded to in specific ways within the mobile app. Below is a concise analysis of each option:
A. Home Screen (Incorrect):
The Home Screen in the Salesforce mobile app displays key metrics, tasks, or quick actions but does not provide a direct interface for responding to approval requests. While it may show notifications or tasks related to approvals, managers cannot take action (approve/reject) directly from the Home Screen. Reference: Salesforce Help - Salesforce Mobile App
B. In-App Notification (Correct):
In-App Notifications in the Salesforce mobile app alert users to pending approval requests. Managers can tap on an approval notification, which directs them to the approval request details, where they can approve or reject the request. This is a primary method for responding to approvals in the mobile app, providing a quick and direct way to act on notifications. Reference: Salesforce Help - Respond to Approval Requests in the Salesforce Mobile App
C. Record Detail (Correct):
The Record Detail page for an Opportunity in the Salesforce mobile app displays the approval request if one is pending. Managers can navigate to the Opportunity record, view the approval section, and take action (approve/reject) directly from the record’s detail page. This is a standard method for handling approvals in the mobile app. Reference: Salesforce Help - Approvals in Salesforce Mobile
D. Navigation Menu (Incorrect):
The Navigation Menu in the Salesforce mobile app allows users to access objects, apps, or other features but does not provide a direct interface for responding to approval requests. While managers can navigate to the Opportunity object or an Approvals tab (if configured), the actual approval action occurs on the Record Detail page or via In-App Notifications, not directly in the Navigation Menu. Reference: Salesforce Help - Salesforce Mobile Navigation
Recommended Approach: In-App Notification: Managers receive a push notification or in-app alert for pending approval requests. Tapping the notification takes them to the approval interface to approve or reject the Opportunity. Record Detail: Managers can navigate to the Opportunity record in the mobile app, locate the approval request section, and take action directly on the record.
Additional Notes:
Ensure the approval process is configured in Setup > Approval Processes to trigger for Opportunities with an amount exceeding $50,000.
Verify that managers have the necessary permissions (via Profile or Permission Set) to approve/reject requests.
The Salesforce mobile app must be properly configured to display notifications and allow approval actions.
References:
Salesforce Help: Approvals in the Salesforce Mobile App
Salesforce Trailhead: Approval Processes
Question 33Choose 1
Universal containers wants to ensure that they are accepting clean data from their users
and verify that important fields are entered. What should an app builder recommend to
meet this requirement?
Correct answer:
D. Configure a validation to require a field for a specific record type
Explanation:
Why: Validation rules are designed to verify data before save and block the save when the data doesn’t meet your standards—perfect for enforcing both required fields and format checks (e.g., ISBLANK(), REGEX()). You can also scope the rule to specific record types (e.g., RecordType.DeveloperName = "Enterprise"), so the requirement only applies where needed.
Why not the others A. Required on page layout: Only enforces entry when that specific page layout is used; it doesn’t consistently enforce requirements across all entry points (API/imports/automations). It also doesn’t validate format.
B. Formula field: Formula fields are calculated and read-only; they can’t enforce input or block saves.
C. Workflow rule: Workflow automates after a record is saved; it can’t stop a bad save. Use validation rules to prevent the save instead.
References:
Salesforce Help: Validation Rules (verify data before save, apply to new/updated records).
Salesforce Help: Make a custom field required (page-layout requirement is layout-specific).
Question 34Choose 1
Sales reps at Cloud Kicks (CK) forget to submit for approval when CK needs orders
reviewed before close won. CK wants to automatically submit opportunities into the Secure
Commitment Stage to eliminate manual submission.
Which features would meet the business requirements?
Correct answer:
D. Record-Triggered flow optimized for Actions and Related Records
Explanation:
This question tests the selection of the correct Flow optimization type for automating an approval submission. The requirement is to automatically submit an Opportunity for approval when it reaches the Secure Commitment stage, eliminating manual submission. Submitting a record for approval is an action that interacts with an Approval Process and requires the record's ID to be available. Therefore, the flow must run after the record is saved and be optimized for Actions and Related Records, not for Fast Field Updates.
✔️ Correct Option:
D. Record-Triggered flow optimized for Actions and Related Records
This optimization type runs after the record is saved, making the record's ID available for the "Submit for Approval" action . Salesforce documentation confirms that to call the Submit for Approval core action, an After-Save Record-Triggered Flow must be used . The flow can be configured to trigger when the Opportunity Stage changes to Secure Commitment and then invoke the approval action, fully automating the process without user intervention.
❌ Incorrect options:
A. Custom button and screen flow
A custom button with a Screen Flow requires the user to manually click the button and interact with the flow. This does not eliminate manual submission—it simply replaces the standard button with a custom one. The requirement is to automatically submit the record, which a manual button cannot achieve.
B. Record-Triggered flow optimized for Fast Field Updates
This optimization type runs before the record is saved and is designed only for updating fields on the triggering record itself . It cannot perform actions like submitting for approval because the record ID is not yet finalized and actions are not supported in Before-Save flows . It cannot fulfill the requirement to submit the Opportunity for approval.
C. Platform Event-Triggered flow
A Platform Event-Triggered flow runs in response to a platform event message being published, typically used for integrations or system-wide event handling. It is not designed to react to standard record stage changes on the Opportunity object. Using it here would require additional complexity and does not match the straightforward record-update trigger required.
🔧 Reference:
→ Salesforce Help: Auto Submit Salesforce Campaign Record into Approval Process with Flow — Confirms an After-Save Record-Triggered Flow is required to use the Submit for Approval action.
→ Trailhead: Build Record-Triggered Flows Guide — Explains the difference between Before-Save (Fast Field Updates) and After-Save (Actions and Related Records) optimization types.
Question 35Choose 1
Sales reps at Universal Containers use Salesforce on their mobile devices. They want a
way to odd new contacts quickly and then follow up later to complete the additional
Information necessary.
What mobile solution should an App Builder recommend?
Correct answer:
B. Build a global action to create Contacts.
Explanation:
Sales reps need a fast and efficient way to add new Contacts on mobile, with the ability to fill in additional details later. This calls for a solution that’s:
Quick to access
Streamlined for minimal input
Mobile-optimized
✅ Global Actions are perfect for this:
They allow users to create records from anywhere in the Salesforce mobile app.
You can design the action layout to include only essential fields, making it fast to complete.
Reps can later edit the Contact record to add more details.
Global actions appear in the publisher layout, making them easy to access on mobile.
❌ Why the other options don’t work: A. Customize the mobile menu This only changes navigation order — it doesn’t streamline record creation. C. Add a compact layout Compact layouts affect record display, not how records are created. D. Use Path and set pre-defined values Path is used for guiding users through stages (like Lead or Opportunity), not for quick record creation.
🔗 References:
Salesforce Help: Global Actions
Trailhead: Customize the Salesforce Mobile App
Question 36Choose 1
Cloud Kicks has five years of sales data and would like to track when customers made their
first purchase. How should an app builder use a roll-up summary to meet the
requirements?
Correct answer:
A. Create a new roll-up summary field called First Order Date, using Type MIN on the
Opportunity Close Date with a filter where IsWon = TRUE.
Explanation:
Roll-up Summary Field: A roll-up summary field is designed to aggregate data from a set of related detail records and display the result on the master record. In this case, you can create a roll-up summary field on the Account object (the master) to summarize data from the related Opportunity records (the details). MIN Function: The MIN function is used to find the earliest date in a set of date fields. By applying MIN to the Opportunity Close Date, the roll-up summary will return the date of the earliest successful purchase. Filter IsWon = TRUE: This filter is crucial. It ensures that only Won opportunities are included in the calculation, so the roll-up summary only considers actual purchases and ignores opportunities that were lost or are still in progress.
Why other options are incorrect B. Create a new date field called First Order Date, create a new Workflow to set the date, and roll up the value with a filter where IsWon = TRUE: A workflow rule cannot perform a roll-up summary. This approach is incorrect because it mixes two different functionalities in an unworkable way. C. Create a new roll-up summary field called First Order Date, using Type SUM on Opportunity Close Date: You cannot use SUM on a date field. The SUM type is used for number fields, not dates. D. Create a new date field called First Order Date, then create a roll-up summary to update the field using Type MIN: This describes a two-step process that is unnecessary. The roll-up summary field itself is the field that will store the date. You don't need to create a separate date field and then have the roll-up summary update it. The roll-up summary field is a dedicated field type.
Question 37Choose 1
A sales rep at AW Computing is unable to find what they are looking for while scrolling
through their Chatter feed.
How can a filter be utilized to show only posts from their key account and opportunity
records?
Correct answer:
C. Create a Chatter stream.
Explanation:
Why: In Lightning, Chatter Streams let users build a custom feed from specific records (e.g., key Accounts and Opportunities), people, or groups. The rep can add those key records to a stream and view only posts from them—perfect for filtering a noisy feed.
Why not the others: A. Chatter group: Groups organize people/topics, not posts from specific records.
B. Chatter bookmarks: Save individual posts; they don’t create a filtered feed.
D. Chatter notification: Alerts you, but doesn’t provide a dedicated filtered feed view.
Question 38Choose 1
An app builder wants to create a custom Sync button on Account that will call a Lightning
Web Component that connects with an external system. This action should only be
available If the custom Status field is set to Ready to Sync.
What should an app builder use to add this functionality to an Account record page?
Correct answer:
B. Dynamic action
Explanation:
The requirement is to:
Add a custom Sync button to the Account record page
Trigger a Lightning Web Component (LWC) that connects to an external system
Ensure the button is conditionally visible only when the Status field = "Ready to Sync"
✅ Why Dynamic Action is the right choice:
Dynamic Actions allow you to conditionally show or hide buttons on Lightning record pages based on field values, user profiles, or record data.
You can configure the Sync button to appear only when Status = "Ready to Sync".
The button can be tied to a custom Lightning Web Component via a Lightning Action or Quick Action.
This is a declarative, flexible, and mobile-friendly solution.
❌ Why the other options don’t work: A. Formula field Formula fields are read-only and cannot trigger actions or components. C. AppExchange product Overkill for this use case — no need to install a third-party app for a simple conditional button. D. Custom link Custom links are static and cannot be conditionally displayed based on field values. Also, they don’t integrate cleanly with LWCs.
🔗 References:
Salesforce Help: Dynamic Actions on Record Pages
Trailhead: Lightning App Builder
Question 39Choose 1
Universal Containers uses the Asset object to track products that are installed at customer
locations. A new object, Asset Inventory, has been created to capture details about the
asset.
Which approach should the app builder take to show Asset Inventory as a related list on
Asset?
Correct answer:
C. Create a lookup relationship on Asset Inventory to Asset. Add the Asset Inventory
related list to the Asset page layout.
Explanation:
To show a related list on a parent object (in this case, Asset), you must have a relationship field on the child object (Asset Inventory) that points to the parent.
Create a lookup relationship on Asset Inventory to Asset: Creating a lookup relationship field on the Asset Inventory object that references the Asset object is the correct way to establish this parent-child connection. Add the Asset Inventory related list to the Asset page layout: Once the relationship is established, Salesforce will automatically make the child object (Asset Inventory) available to be added as a related list on the parent's (Asset) page layout.
Why other options are incorrect A. Create a roll-up on Asset. Add the Asset Inventory related list to the Asset page layout: A roll-up summary is used to aggregate data from child records onto a parent record; it does not create a related list. The related list is a result of the relationship itself, not a roll-up summary. B. Create a junction object to relate Asset Inventory and Asset. Add the Asset Inventory related list to the Asset page layout: A junction object is used to create a many-to-many relationship between two objects. While it would create related lists, it's an unnecessary and overly complex solution for a simple one-to-many relationship, where Asset Inventory is the child of Asset. D. Create a master-detail relationship on Asset-to-Asset Inventory Add the Asset Inventory related list to the Asset page layout: This is incorrect. The master-detail relationship field must be created on the child object (Asset Inventory) and reference the parent object (Asset). The option incorrectly states the relationship direction.
Question 40Choose 2
DreamHouseRealty (DR) is expanding into subsidized housing by partnering with local
government entitles. DR uses Sales Cloud and has enabled field history tracking on the
Opportunity object. Due to increased Information requirements, the App Dev team is
changing Text Area (Long) fields to Rich Text fields to allow for up to 1,000 characters and
better descriptions.
Which two considerations should be made by the team?
(Choose 2 answers)
Correct answer:
B. Data loss may occur when changing custom field types.
C. Field History Tracking records value changes of 255 characters or less.
Explanation:
Changing a field's data type is a significant modification that can have unintended consequences, especially when dealing with data limits and history tracking.
Why B is Correct: Converting a field from one data type to another can often result in data truncation or loss. A Text Area (Long) field can hold up to 131,072 characters. A Rich Text field can only hold up to 32,768 characters in most contexts (and is often effectively limited to much less when stored in HTML format). If any existing records have text longer than the new Rich Text field's capacity, that data will be truncated and lost during the conversion process. The team must analyze their existing data to ensure no values exceed the new limit before proceeding.
Why C is Correct: Field History Tracking has a known limitation: it only captures the first 255 characters of any changed field value for the history trail. This is true regardless of the original field's data type (Text, Text Area, Rich Text) or length. If the business requirement for tracking changes relies on the full content of these potentially long descriptions, this limitation makes Field History Tracking an inadequate solution. The team may need to consider a different auditing strategy, such as using a custom object or an external logging system.
Why A is Incorrect: This statement is false. In Salesforce reports, Rich Text fields are truncated and do not display their full content. You typically see a preview or a shortened version. To see the full value, a user must click into the individual record. This is an important UI consideration when choosing to use Rich Text fields.
Why D is Incorrect: While the Field History Tracking data is accessible via the API, the specific term "Audit Trail" in Salesforce typically refers to the Setup Audit Trail, which logs changes to your org's configuration, not changes to individual record data. This option is a distractor and does not address the core considerations of data loss and history tracking character limits related to the field type change.
Reference: Salesforce Help:
"Convert Field Type Considerations": Explicitly warns that converting fields can lead to data loss.
"Field History Tracking Considerations": States "Field history tracking retains the previous 255 characters for any changed field whose length is greater than 255 characters."
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.