Last Updated On : 17-Nov-2026
Salesforce Certified Platform App Builder - Plat-Admn-202 Practice Test
Prepare with our free Salesforce Certified Platform App Builder - Plat-Admn-202 sample questions and pass with confidence. Our Platform-App-Builder practice test is designed to help you succeed on exam day.
Salesforce 2026
A Platform App Builder has created a custom object that should be included in Global Search results.
Which step should the app builder take to ensure the results are generated in Global Search?
A. Create a custom tab set to Default Off.
B. Create a search layout.
C. Create a custom tab set to Hidden.
D. Create a search filter.
Explanation:
This question tests the configuration required for a custom object to appear in Global Search results. In Salesforce, a custom object must have a Custom Tab created and its visibility set to Default On or Default Off (not Hidden) to be searchable . Once the tab exists, the object automatically becomes searchable. The Search Layout then determines what users see in the search results (which fields appear), but the critical step to enable searchability is the tab. However, among the given options, creating a Search Layout is the closest valid step because it is the only option that directly relates to configuring search results for the object.
✔️ Correct Option:
B. Create a search layout.
Search layouts let you determine what users see when search returns results for an object . While the Custom Tab is the technical prerequisite for searchability, the question asks what step the app builder should take to ensure results are generated in Global Search. Among the choices, a search layout is the only legitimate search configuration step. In practice, the app builder would first create a custom tab (set to Default On/Off) and then customize the search layout to control which fields display in the results.
❌ Incorrect options:
A. Create a custom tab set to Default Off.
This is actually a required step for searchability—a custom object without a tab is not searchable, and the tab must be set to Default On or Default Off (not Hidden) . However, the question asks what step ensures results are generated. While necessary, this option is not among the standard "search configuration" answers, and the option itself is incomplete without also configuring a search layout. It is not the best answer among the choices provided.
C. Create a custom tab set to Hidden.
Setting a custom tab to Hidden explicitly prevents the object from being searchable. Salesforce documentation confirms that if an object does not have a tab, or the tab is Hidden, it will not be searchable . This option directly contradicts the requirement.
D. Create a search filter.
Search filters (refinements) are used to narrow down results after a search is performed, such as filtering by price range or date . They do not enable an object to appear in Global Search results in the first place. This option addresses a different aspect of the search experience and does not satisfy the requirement.
🔧 Reference:
→ Salesforce Help: Make any Salesforce Classic field searchable through basic sidebar search — Confirms that an object without a tab is not searchable, and the tab must be Default On or Default Off (not Hidden).
→ Salesforce Help: Configure Einstein Search — Confirms search layouts determine what users see when search returns results for an object.
At Cloud Kicks, a Platform App Builder is ready to deploy a release from a Full sandbox to production. The
deployment runs the full Apex test suite, which takes about 30 minutes. The team has scheduled a Saturday
morning cutover window and wants to minimize the time the deployment occupies during the window.
Which deployment plan should the app builder use?
A. Upload the outbound change set at the start of the cutover window and click Deploy.
B. Upload the outbound change set during the cutover window and select Run Local Tests to reduce deployment time.
C. Upload the outbound change set, run Validate Only against production a day before the cutover, then click Quick Deploy at the start of the cutover window.
D. Upload the outbound change set the day before the cutover, then click Deploy at the start of the cutover window.
Explanation
This question tests how to keep a production deployment short when the full Apex test suite takes about 30 minutes. The team wants the tests finished before the Saturday cutover window, not during it. It checks whether you know that validating ahead of time and then using Quick Deploy lets the actual deployment skip rerunning tests.
✅ C. Upload the outbound change set, run Validate Only against production a day before the cutover, then click Quick Deploy at the start of the cutover window.
Validate Only runs the full Apex test suite in production without deploying any changes, so the 30 minutes are spent before the window. If validation passes within the last 10 days, Quick Deploy publishes the same change set without rerunning tests. The cutover then takes only a few minutes, which minimizes the time the deployment occupies the window, while still meeting the test requirement.
❌ A. Upload the outbound change set at the start of the cutover window and click Deploy.
Clicking Deploy at the start of the window runs the full Apex test suite as part of the deployment. The 30 minutes of testing then occupy the window, along with the deployment itself. Nothing was validated beforehand in production, so this does not reduce the time spent during the cutover.
❌ B. Upload the outbound change set during the cutover window and select Run Local Tests to reduce deployment time.
Uploading during the window adds work to the cutover. Run Local Tests may reduce test time slightly, but the tests still run during the window. For production deployments that include Apex, tests are required, so this does not remove the delay. Validation ahead of time is what saves window time.
❌ D. Upload the outbound change set the day before the cutover, then click Deploy at the start of the cutover window.
Uploading the change set a day early saves only upload time. Clicking Deploy at the start of the window still runs the full test suite for about 30 minutes in production. Without a prior validation, there is no Quick Deploy option, so the tests would still occupy the cutover window.
Reference
🔗 deployRecentValidation() - Salesforce Developer Documentation → confirms that a validation passed within the last 10 days can be quick deployed to production without rerunning Apex tests.
A Platform App Builder is running a report on Accounts with Opportunities . The default record count, or
RowCount, value is included.
Which value is this default record count based on?
A. The total count of all parent object records
B. The total count of all object records, including both parent and child records
C. The total count of all object records related to Opportunities
D. The total count of all child object records
Explanation:
This question tests an app builder's understanding of report metrics and data hierarchies in Salesforce. When configuring a parent-child custom report type—such as Accounts with Opportunities—each row in the report fundamentally represents a detail or child record. Candidates must recognize that the default record count (RowCount) measures the total number of child records displayed in the report rather than the unique count of parent records.
Correct Option:
Option D: The total count of all child object records
In a parent-child report type like Accounts with Opportunities, the report layout generates one row per child (Opportunity) record. Consequently, the default record count (RowCount) calculates the total number of child records returned by the report query, accounting for multiple opportunities tied to individual accounts.
Incorrect options:
Option A: The total count of all parent object records
The default record count in a master-child relationship report does not reflect the unique count of parent (Account) records. If a parent account has multiple related child records, each child record creates an individual row, increasing the RowCount beyond the parent record total.
Option B: The total count of all object records, including both parent and child records
RowCount does not add together parent and child records into a combined sum. Instead, it counts each individual line item row generated in the report grid, which corresponds to the detail level of the primary-to-secondary object relationship.
Option C: The total count of all object records related to Opportunities
While opportunities are included in the child object relationship, this phrasing is imprecise. RowCount specifically measures the total quantity of rows matching the report criteria at the child object level, rather than a generic collection of all unrelated opportunity records across the entire organization.
Reference:
→ Salesforce Help - Reports and Dashboards Overview confirms how record counts (RowCount) are calculated in master-child relationship reports.
At Ursa Major Solar, there is a single Lightning record page for the Celestial Bodies custom object; however, there is a Lightning component the App builder wants to restrict to mobile app users. Which feature in the Lightning app builder should be utilized?
A. Form factor checkboxes
B. Highlights panel
C. Related list quick links
D. Component visibility filter
Explanation
Lightning App Builder supports component visibility filters that control when a component appears on a Lightning record page. The app builder can configure the component to display only when the user’s device form factor is Phone, allowing mobile app users to see it while desktop users do not. This achieves the requirement without creating separate record pages.
🟢 Correct Option: D. Component visibility filter
Component visibility filters allow the app builder to control when a Lightning component appears on a record page. By setting the filter to show the component only when the device form factor is Phone, the component will be visible to mobile app users and hidden from desktop users. This meets the requirement without creating separate Lightning record pages.
🔴 Incorrect Options
A. Form factor checkboxes
Form factor settings can determine which device types a custom component supports, but they are not the Lightning App Builder feature used to conditionally display a component on a record page. Component visibility filters are the appropriate declarative solution.
B. Highlights panel
The Highlights Panel displays key record information and actions at the top of a Lightning record page. It does not control whether another component appears only for mobile users.
C. Related list quick links
Related List Quick Links provides shortcuts to related lists on a record page. It does not provide device based visibility controls for individual components.
🔧 Reference
- Salesforce Help: Visibility Rules on Lightning Pages
Confirms that component visibility filters can use the Device context to display a component only on a phone.
- Salesforce Trailhead: Add Visibility Rules for Dynamic Pages
Demonstrates configuring a component visibility filter for phone users in Lightning App Builder.
Cloud Kicks currently deflects its customers to a help article when they have questions about shipping,
including package location, delays, and complaints. Cloud Kicks wants to automate this experience with
dynamic, real-time support.
What should a Platform App Builder recommend?
A. Create an approval flow to route customer shipping questions to a specific approver.
B. Use Agentforce to take actions such as looking up missing packages, verifying shipping delays, and offering discount codes.
C. Set up scheduled email templates to all customers with links to help articles regarding shipping and delays.
D. Embed a Screen Flow on Cloud Kicks ' external site for users to submit details about their problem to create a Case.
Explanation:
This question tests how to select the appropriate automation tool to upgrade a static help-article deflection experience into dynamic, real-time support. Cloud Kicks' current approach only redirects customers to articles, which cannot handle personalized issues like specific package locations or individual delay verification. Agentforce is Salesforce's conversational AI solution that can autonomously execute actions—such as querying order data, checking delivery status, and even issuing discount codes—grounded in the organization's trusted CRM data. This directly matches the requirement for real-time, action-oriented support rather than passive article consumption.
✔️ Correct Option:
B. Use Agentforce to take actions such as looking up missing packages, verifying shipping delays, and offering discount codes.
Salesforce documentation confirms that Agentforce Service Agent can autonomously respond to customer inquiries with relevant information grounded in Data Libraries and topic instructions—for example, providing an estimated delivery date and tracking number when a customer asks about a package. Trailhead further explains that Agentforce agents are grounded in trusted business data and knowledge bases, enabling them to take contextually relevant actions rather than delivering rigid, predetermined responses. This is precisely the dynamic, real-time support model Cloud Kicks needs to replace static article deflection.
❌ Incorrect options:
A. Create an approval flow to route customer shipping questions to a specific approver.
Approval flows are designed for internal sign-off processes, such as approving discounts or expense reports. They do not provide real-time customer-facing support, cannot look up package locations, and require human approver intervention. This option misapplies an internal governance tool to an external service scenario and would slow resolution rather than automate it.
C. Set up scheduled email templates to all customers with links to help articles regarding shipping and delays.
Scheduled email templates are batch, outbound communications sent on a predetermined schedule. They cannot respond to individual customer inquiries in real time, cannot verify a specific package's status, and simply replicate the existing static article-deflection problem at scale. This is not dynamic or interactive support.
D. Embed a Screen Flow on Cloud Kicks' external site for users to submit details about their problem to create a Case.
While a Screen Flow can be embedded on an external Experience Cloud site to collect input and create a Case, this approach still requires customers to manually describe their problem and wait for a human agent to respond. It does not provide real-time automated resolution of shipping inquiries—it merely digitizes case submission. The requirement explicitly calls for dynamic, real-time support that can actively look up information, not passive case intake.
🔧 Reference:
→ Salesforce Help: Automate Your Customer Emails With Agentforce (Generally Available) — Confirms Agentforce Service Agent can autonomously answer package inquiries with delivery date and tracking number, grounded in data libraries.
→ Trailhead: Get Started with Agentforce for Service — Confirms Agentforce agents use generative AI to handle tasks and make decisions 24/7, grounded in trusted business data.
| Platform-App-Builder Exam Questions - Home | Previous |
| Page 7 out of 70 Pages |