Platform-App-Builder Salesforce Certified Platform App Builder (Plat-Admn-202) Free Practice Exam Questions (2026 Updated)

Global actions are designed to be available broadly, not only from one object’s record page. Salesforce Trailhead states that global actions can be placed anywhere actions are supported and can let users send email without leaving the page they are on.

This fits the requirement because users need a Send New Email action available from Leads, Contacts, and Accounts in the Salesforce mobile app.

Why others are incorrect:

A is incorrect because a global action layout does not automatically clone the default page layout.

B is incorrect because the Lightning Component Library is not the reason to use global actions.

C is incorrect because global actions are not record-specific; object-specific actions are record-specific.

===========

The correct answer is B. Unable to reference the child records.

Formula fields can reference fields on related parent records through cross-object formulas. For example, a formula field on Contact can reference Account fields because Account is the parent of Contact. Salesforce Trailhead shows this pattern by inserting Contact | Account | Account Number in a formula on Contact.

However, the reverse direction is not supported in a normal formula field. An Account formula cannot directly reference values from multiple related Contact child records. Since Contacts are child records of Account, the Contact relationship does not appear in the Account formula editor.

A is incorrect because the issue described is about relationship direction, not the number of formula fields.

C is incorrect because Contact and Account do not need a master-detail relationship for this limitation to apply.

D is incorrect because Salesforce formula character limits are separate from this parent-to-child reference limitation. Salesforce documents formula character limits separately.

===========

A Partial Copy sandbox is specifically intended for testing scenarios that need representative production data without requiring an entire production dataset. Salesforce states that Partial Copy sandboxes contain production metadata plus a selected sample of production data defined through a sandbox template and explicitly identifies User Acceptance Testing, integration testing, and training as appropriate uses. The template also lets administrators select the objects required for testing and exclude sensitive or irrelevant data sets when necessary. Developer and Developer Pro sandboxes primarily copy metadata and do not automatically provide representative production data. A Scratch Org is a temporary source-driven development environment rather than the preferred UAT environment for actual business users and realistic production-derived data. Therefore, A is the appropriate sandbox type.

================

Page layouts are metadata components. When an updated layout is included in a deployment, the target organization receives the source version of that layout rather than merging independent layout customizations field by field. Consequently, if three fields existed only on the production version but were absent from the sandbox version being deployed, those field placements can disappear when the source layout configuration replaces the target configuration. Salesforce ' s deployment documentation emphasizes that metadata deployments apply the layout configuration supplied in the deployment payload and warns that page-layout metadata and assignments require complete deployment planning. Option A cannot be correct because a failed deployment is rolled back. Missing field permissions affect visibility, but the scenario specifically identifies fields disappearing from the deployed layout configuration. Therefore, B best explains the behavior.

================

The correct answer is A because the rule must fire only when Sales Organization = Canada and Pricing Tier is blank.

ISPICKVAL() checks whether a picklist equals a specific text value, and TEXT() converts a picklist value into text so ISBLANK() can evaluate whether it is empty. Salesforce documents ISPICKVAL() for comparing picklist values and TEXT() for converting picklist values in formulas.

Why others are incorrect:

B has invalid formula structure.

C uses incorrect picklist blank logic.

D uses OR , which would require Pricing Tier even when Sales Organization is not Canada.

===========

The correct answers are A. Remove the delete button from the Delivery page layout and C. Remove the Delete permission from the Shipper profile.

The real security control is C because object permissions define whether users can create, read, edit, or delete records for an object. To prevent shipping users from deleting Delivery__c records, the app builder must remove the Delete object permission from the Shipper profile.

A is also a valid supporting UI step because Salesforce page layouts can control whether standard/custom buttons are displayed. Removing the Delete button reduces the visible delete option on the record page. However, this alone is not complete security because hiding a button does not fully remove the underlying permission.

Why others are incorrect:

B is incorrect because a regular permission set grants additional access; it does not remove profile access.

D is incorrect because OWD controls record-level sharing, not object-level Delete permission.

===========

The correct answers are C. Use Data Loader to update leads using the CSV file and D. Select Insert Null Values in Settings.

Universal Containers wants to delete values from fields on 5,000 Lead records. The correct method is to use Data Loader Update with the record IDs in the CSV file, leave the target field cells blank, and enable Insert Null Values so Data Loader treats the blank CSV values as null updates. Salesforce Help explains that to change field values to blank/null with Data Loader, export IDs and fields, clear the values in the CSV, select Insert Null Values, and run an update.

Why others are incorrect:

A is unrelated because record type selection does not delete field values.

B is not the best choice because the Import Wizard is not the proper tool for mass clearing field values using null updates.

The correct answers are A. Change the Lead Duplicate Rule details to Bypass Sharing Rules and D. Change the Lead Duplicate actions to Block on Create.

Because Lead OWD is Private, users may not have access to existing duplicate Lead records. Salesforce duplicate rules can be configured to bypass sharing rules, allowing the duplicate rule to check possible duplicates regardless of ownership or user visibility. Salesforce Help specifically explains duplicate prevention can block users from creating duplicate records whether or not they have access to the existing record.

D is also required because detecting a duplicate is not enough. The duplicate rule action must be set to Block on Create to stop users from saving new duplicate Leads.

Why others are incorrect:

B is incorrect because Lead Assignment Rules assign leads; they do not prevent duplicate creation.

C may expose more Lead records, but changing OWD from Private to Public Read is not the best security-safe solution when duplicate rules can bypass sharing.

===========

Permission Sets are the appropriate mechanism for granting additional object and field access to users who perform a particular function without changing their base profiles. The app builder can create a permission set for hiring managers that grants the required access to JobApplication__c and Read access to the sensitive salary fields through field-level security. Salesforce specifically recommends permission sets and permission set groups rather than profiles for extending field permissions. Sharing Rules and organization-wide defaults govern record-level access; they do not make fields visible when field-level security hides them. Page Layouts control which fields are placed in the interface but cannot override field-level security. Because salary information represents restricted field-level data that only a designated functional group should see, Permission Sets provide the precise least-privilege solution.

================

A junction object ' s accessibility is governed by both master records because the junction object contains two master-detail relationships. Salesforce explicitly states that sharing access to a junction-object record depends on the user ' s access to both associated master records and the sharing configuration of the relationship fields. The manager already has Read access to Store but lacks access to Loyalty Member. Granting Read access to the Loyalty_Member__c object provides the missing object-level prerequisite. A sharing rule cannot compensate for missing object permission because record sharing only extends record-level visibility after the user has appropriate object access. Additionally, a junction object on the detail side of master-detail relationships does not independently control sharing like an ordinarily owned custom object. Therefore, B addresses the actual missing access layer.

================

The correct answers are A. Unique and D. External ID.

The legacy ID should be marked as an External ID because Salesforce can use an external ID field to match records during import, integration, and upsert operations. Salesforce REST API documentation states that records can be inserted or updated using a specified external ID field.

The field should also be marked Unique so that the legacy system ID identifies one Salesforce Account record only. Salesforce documentation explains that an external ID can represent an ID from another external system, and uniqueness helps prevent duplicate matching values.

B is incorrect because encrypted text is not appropriate for a matching/upsert key.

C is incorrect because Required only forces a value; it does not make the field usable for upsert matching or prevent duplicate legacy IDs.

===========

Salesforce states that to make a custom object ' s records searchable, an administrator can create a custom tab set to Default On or Default Off ; creating the tab enables the object ' s search capability. Salesforce also warns that a custom object ' s tab must be visible for the user ' s profile and specifically says not to set the tab to Tab Hidden. A Search Layout controls which fields users see in search results but does not by itself enable object searchability. A search filter similarly refines results rather than enabling the custom object in Global Search. Therefore, among the available options, creating the custom tab with Default Off is the correct configuration.

Salesforce imposes a daily limit on mass and list email sent to external recipients. Current Salesforce documentation specifies a limit of 5,000 external email addresses per day per licensed org , meaning a recurring campaign to 7,000 contacts cannot be completed using standard Salesforce mass-email functionality in one day. Salesforce recommends considering a third-party mass-email solution from its marketplace when higher-volume sending is required. This corresponds to option B in the question. Requesting an arbitrary increase does not remove the standard product limitation. Exporting contacts to an external email client creates additional data-management and compliance concerns, while developing Apex and an LWC does not bypass Salesforce ' s applicable email limits. A purpose-built marketplace solution is therefore the appropriate scalable approach. Salesforce

================

The correct answer is A. TODAY().

The formula needs to calculate how many whole days have elapsed since a marketing communication was sent. The TODAY() function returns the current date as a Date value, which is appropriate for whole-day calculations. Salesforce documentation also shows that TODAY() can be used with addition and subtraction operators for date calculations.

NOW() returns a Date/Time value and can introduce fractional day/time calculations. DATEVALUE() converts a Date/Time or text value into a Date, but the question asks which function should return today’s date for calculating elapsed days. DATETIMEVALUE() returns a Date/Time value, not the desired whole-date calculation.

===========

The correct answers are A. Build an approval process that requires unanimous approval from the manager and VP of Sales and D. Create a flow that submits the record for an approval process.

The requirement is not just to notify users or block the change. The manager and VP of Sales must review the close-date delay. Salesforce approval processes are designed to automate how records are approved, including approval steps, approvers, and approval/rejection actions.

A is correct because an approval process can route the Opportunity to the manager and VP of Sales for approval. Requiring unanimous approval ensures both reviewers must approve the delayed close date.

D is correct because a record-triggered flow can detect when the Opportunity Close Date changes and is delayed by more than 60 days, then use the Submit for Approval action. Salesforce Flow supports prior-value/change logic in record-triggered flows, and Salesforce documents the Flow Submit for Approval action.

Why others are incorrect:

B is incorrect because a validation rule blocks saving the record. It does not allow manager/VP review.

C is incorrect because a formula field and email alert do not create an approval review process, and the stated logic does not satisfy the approval requirement.

===========

Record type availability determines which record types a user can select when creating records. Salesforce allows record types to be assigned through profiles, permission sets, and permission set groups. Therefore, if the support team ' s profile currently provides access to Bronze, removing Bronze from that profile prevents users from selecting that record type, assuming it is not granted through another permission set. Organization-wide defaults and sharing rules regulate access to records after they exist; they do not control which record types a user can select during creation. A permission set group containing Platinum and Diamond could grant additional access but does not inherently revoke Bronze access already provided by the profile. The direct solution described by the options is therefore to remove the Bronze record type assignment from the support team ' s profile.

================

The correct answer is D. Rich text area.

The requirement says users need to write detailed descriptions that can include pictures and links. Salesforce Rich Text Area fields are designed for formatted text and support images and hyperlinks.

Long text area supports longer plain text but not rich formatting with images. URL stores a single web address. Multi-select picklist stores selected values, not detailed formatted descriptions.

===========

Performing Data Manipulation Language operations such as Update Records inside a Loop is a classic Flow governor-limit anti-pattern. Each loop iteration can perform another database operation, rapidly consuming transaction limits when a large collection of Opportunities is processed. Salesforce ' s official Flow guidance explicitly says never to place DML operations inside loops. Instead, the app builder should iterate through the records, use Assignment elements to modify them and add them to a record collection, and perform one bulk Update Records operation after the loop. Fault paths improve error handling but do not prevent governor-limit consumption. Schedule-triggered flows can update standard objects, so D is incorrect. The scalability problem described is therefore directly caused by performing Update Records repeatedly inside the Loop element.

A Screen Flow is the best declarative tool when the user must answer questions through a guided UI and use those answers to update record fields. Salesforce documents that screen flows provide a UI that guides users through a business process, and they can be launched from quick actions or Lightning pages.

A custom button or action can launch the flow, collect the extra approval-related information, update the Account fields, and then continue the approval submission logic.

Why not others:

A. Custom object only stores data; it does not provide the popup/question flow.

B. Visualforce could be custom-coded, but Flow is the declarative App Builder solution.

D. Custom Lightning component requires development and is not the best declarative answer.

===========