Platform-App-Builder Salesforce Certified Platform App Builder (Plat-Admn-202) Question and Answers

The correct answer is D. Create both customer and dealer as accounts, add each rep as a contact on the corresponding account and create an account hierarchy.

Universal Containers needs to represent separate business entities because separate bills are sent to each customer and each dealer. In Salesforce, business accounts are used to represent companies or organizations, and contacts represent the people who work for those accounts. Salesforce account hierarchies are used to show relationships between related accounts through the Parent Account field.

So the best model is:

Customer = Account

Dealer = Account

Representative at each business = Contact on that Account

Customer/dealer relationship = Account Hierarchy

A is incorrect because Account Teams represent internal Salesforce users working on an account, not external dealer/customer representatives.

B and C are incorrect because they do not correctly represent separate billing entities as separate Accounts.

===========

The correct answers are B. Cross-object field updates between Training and Student records are not supported and C. On Training record, the Student Lookup field can be made optional.

This question is about creating a Student lookup field on the Training object. A lookup relationship is a looser relationship than master-detail. Salesforce documentation explains that lookup relationships do not support roll-up summary fields, unlike master-detail relationships.

Because this is a lookup relationship, the Student lookup field on Training can be optional unless the app builder marks it required. Cross-object field updates are also not supported in this lookup relationship scenario; Salesforce documents that cross-object field updates work for master-detail relationship scenarios, not normal lookup relationships.

A is incorrect because roll-up summary fields require a master-detail relationship.

D is incorrect because deleting Student records is controlled by object permissions and relationship delete behavior, not simply by access from the Training record.

===========

A roll-up summary field requires a master-detail relationship. Since Galaxy__c and Star__c currently have a lookup relationship, the app builder cannot create a standard roll-up summary field to count related Star__c records. The lookup must be converted to master-detail first, with Galaxy__c as the master and Star__c as the detail. Salesforce Trailhead confirms that roll-up summary fields display values on the master record based on directly related detail records in a master-detail relationship.

===========

The correct answer is D. Validation Rule.

A validation rule is used to stop users from saving a record when required business conditions are not met. Salesforce documentation explains that validation rules verify that record data meets defined standards before the record can be saved.

For this requirement, the validation rule would check that when the Opportunity stage is Qualified, the Expected_Close_Date__c field is not blank.

Example logic:

AND(ISPICKVAL(StageName, " Qualified " ), ISBLANK(Expected_Close_Date__c))

Why others are incorrect:

Record Type controls business process, picklist values, and layouts, but it does not enforce this conditional save requirement by itself. Activity History and page layout do not reliably stop record save based on stage logic.

===========

The correct answer is D. Set the Organization-Wide Default to Private for accounts. Create criteria-based sharing rules for each marketing team, and create an Inside Sales Team profile with the “View All” setting for Accounts.

The field sales team should only see Accounts they own, so Account OWD must be Private. Salesforce OWDs define users’ default access to records they do not own.

North American and European marketing teams need access by region, so use criteria-based sharing rules based on the Account region. Salesforce criteria-based sharing rules share records when records match field criteria.

Inside sales needs access to all Account records, so give that group View All Records on Account. Salesforce object permissions define that View All Records lets users view all records for that object regardless of sharing settings.

===========

The correct answer is B. Actions & Recommendations component.

The Actions & Recommendations component is used to give agents a guided to-do list/checklist on a record page. Salesforce documentation describes it as a component that can show flows, quick actions, and recommendations so agents can complete required steps consistently. This matches the requirement to provide service agents with checklist items when servicing a Case.

Why others are incorrect:

A “Business component” is not the standard Salesforce feature for this.

Activity Timeline shows activities, not a required checklist.

Highlights Panel shows key fields and actions, not guided service steps.

===========

The correct solution is to configure validation rules with help text/error messaging.

Validation rules are the right tool because they evaluate record data before save and stop the save when the record does not meet the defined conditions. They can enforce that a Case status is not changed back to an earlier value by using formula logic such as PRIORVALUE() and picklist checks. They can also require certain fields only when specific Case criteria are met by checking whether those fields are blank under those conditions.

Why the other options are wrong:

Dependent picklists control valid picklist values, but they do not enforce status progression or conditional required fields across all save paths. Approval processes are not the best fit for real-time save validation. Page layout required fields are UI-level requirements and are not flexible enough for criteria-based enforcement.

The correct answer is A. Allow Salesforce to import Contacts from mobile device Contact lists.

Salesforce supports importing contacts from a mobile device contact list into Salesforce from the Salesforce mobile app using Import from Device. Salesforce also notes that users need the permission Allow Salesforce to import Contacts from mobile device Contact lists to use this feature.

Why others are incorrect:

B only notifies users; it does not move phone contacts into Salesforce.

C helps users create/edit records offline in Salesforce, but it does not import contacts already entered in the phone’s contact list.

D is for account-contact relationship modeling, not mobile contact capture.

===========

The correct solution is to add a Rich Text component to the Case Lightning record page and then use component visibility so it only appears when the related Account’s support level is Platinum.

Salesforce Lightning App Builder supports visibility rules that show or hide components based on field criteria. Salesforce documentation confirms that visibility filters on record pages rely on field data associated with the page’s object, and related lookup fields can be used in visibility-rule considerations.

This is the best declarative solution because the requirement is only to display a text notification. A custom Lightning Web Component or cloned Lightning page is unnecessary.

Why others are incorrect:

A is incorrect because assigning a Case page to “platinum accounts” is not the correct assignment model.

C and D are incorrect because custom Lightning Web Components add unnecessary development effort for a simple text notification.

===========

The correct answer is C. Salesforce Schema Builder can create fields, including relationship fields, formula fields, and normal fields, and it also helps visualize existing object relationships. However, a field created in Schema Builder is not automatically added to the object’s page layout. Salesforce documentation states that after using Schema Builder, the field must be added through the Page Layout Editor.

Why others are incorrect:

A is incorrect because Schema Builder can create formula fields.

B is incorrect because Schema Builder can create relationship fields.

D is incorrect because Schema Builder is specifically used to view and understand object relationships.

===========

The correct answer is B. Data Import Wizard.

The list contains only approximately 800 leads, which is well within the Salesforce Data Import Wizard limit. Salesforce documentation states that Data Import Wizard can import leads and supports up to 50,000 records at a time. It is also the best standard tool here because the requirement includes preventing duplicate lead records during import.

Data Loader is better for large-volume or scheduled technical loads, but it does not provide the same simple duplicate-prevention import experience for this small daily lead list. Manual entry is inefficient, and DataLoader.io is not the standard Platform App Builder exam answer.

===========

When deploying from sandbox to production using Change Sets, the following are critical considerations:

A. Transactions will revert if the deployment errors – Salesforce applies deployments as a single transaction; any failure rolls back the deployment to maintain org integrity.

D. Change sets do not include all components and may require manual configuration – Certain components, such as record data or some metadata, may need manual setup or additional deployment steps.

Salesforce documentation emphasizes that change sets cannot deploy everything and must be carefully reviewed before validation. (Salesforce Help)

B. Users being logged out is not required; deployments can occur while users are logged in.

C. Salesforce Connect does not automatically link environments; it is unrelated to change sets.

===========

The correct answer is C. Formula Field.

The Service Manager wants a visual color indicator based on the age of an open Case: green for new, yellow for one day old, and red for three days old. This can be implemented with a formula field using conditional logic and the Salesforce IMAGE() function to display different colored indicators based on Case age. Salesforce documentation confirms that the IMAGE function is available in formula fields and can display an image based on field values.

A formula field can evaluate the case age using fields such as CreatedDate , TODAY() , and IsClosed , then return the correct colored image.

A. Custom Button is incorrect because this is not a user action.

B. Quick Action is incorrect because the requirement is display-based, not action-based.

D. Lightning Web Component could do this with code, but a formula field is the simplest declarative Platform App Builder solution.

===========

The correct answer is A. Lookup field.

Cloud Kicks wants to assign a Customer Service Manager user to an Account in addition to the standard Account Owner. The best field type is a Lookup field to the User object. A lookup field stores a relationship to another record and supports reporting, filtering, and record-level navigation. Salesforce describes lookup relationships as a way to relate two records while keeping the records otherwise independent.

A Text field would not create a real user relationship and could cause inconsistent names. A Picklist or Multi-select picklist would require manual maintenance of user names and would not behave like an assigned user reference.

===========

The correct answer is A. Add the field to the custom report type field layout.

The report already exists: Position with or without Applicants Report. The issue is not that reporting is disabled for the object; the issue is that the new Applicant field is not available as a column in that custom report type. For custom report types, fields available to report builders are controlled by the custom report type field layout. Salesforce’s documentation for adding fields to a custom report type directs admins to open the report type and use Edit Layout to add the missing fields.

B is incorrect because field-level security can hide a field from a user, but the troubleshooting step for a field missing from a custom report type column list is to add it to the custom report type layout.

C is incorrect because the report type already exists and is being used.

D is incorrect because the field data type was already assigned when the field was created.

===========

The correct answer is B.

When customer invitations are enabled for Chatter groups, invited customers get limited collaboration access. Salesforce documentation states that customers can see only the groups they’re invited to and can interact only with members of those groups.

A is incorrect because invited customers do not automatically get broad group-invitation rights. C is incorrect because Chatter customer access does not grant access to Account records. D is incorrect because customers are invited to specific groups; they do not receive general public-group request access.

===========

The correct answer is B. User will be presented with a “Record Lock” notification.

When a record is submitted for approval, Salesforce locks the record to prevent users from editing it during the approval process. Salesforce documentation states that records submitted for approval are locked, and by default only admins can edit locked records unless editability settings allow otherwise.

The employee submitted the Opportunity for approval, so the employee cannot simply edit the Description field after submission. The expected user experience is a locked-record message.

===========

When deploying from a sandbox on a newer Salesforce version to production on a current version, any components that rely on features not yet available in production will fail.

Change sets do not automatically upgrade production.

All features must be supported in the target org at deployment time.

Salesforce documentation notes that compatibility issues may occur if components use version-specific features, and deployments must be tested against the target org’s current version. (Salesforce Help)

A is incorrect because deployments do not automatically wait for production upgrades.

B is partially true, but deployments are possible if features are supported.

C is incorrect; components are not automatically upgraded.

===========

The correct answers are B. Roles and Subordinates, C. Public Groups, and D. Users / Individual Users.

Salesforce manual sharing allows record owners or users with proper access to share individual records with users, public groups, and roles. Salesforce documentation specifically states that manual sharing is used to share individual records with other users, public groups, and roles.

For Lightning manual sharing, Salesforce also describes entering groups, users, roles, or territories in the sharing search box.

So, based on your option wording:

B appears to mean Roles and Subordinates.

C is Public Groups.

D appears to mean Users / Individual Users.

A. Permission Set Groups is incorrect because permission set groups grant object, field, app, and system permissions, not case-by-case record sharing.

E. Private Groups is not the standard answer for this Platform App Builder manual-sharing question.

===========

Salesforce requires installation records to be directly associated with Opportunities, and sales reps need visibility of all installations tied to their Opportunities. A Master-Detail relationship is the correct solution because:

The Installation object (detail) inherits sharing and security from the Opportunity (master), ensuring sales reps see only their related installations.

Enables roll-up summaries on Opportunity if needed.

Salesforce documentation confirms that Master-Detail relationships provide parent-controlled ownership and access, making them ideal for enforcing related record visibility. (Salesforce Help)

B. Hierarchical is only available for User object.

C. Many-to-Many requires a junction object; not needed here.

D. Lookup allows optional, independent access; would not automatically enforce visibility.

===========

The correct answer is B. Master-detail relationship.

Cloud Kicks needs two things: count Gift Card records on the Account and prevent Gift Cards from being moved to another Account after creation. A master-detail relationship supports both requirements.

First, master-detail enables a roll-up summary field on Account to count related Gift Card records. Salesforce documentation confirms that roll-up summaries work from detail records up to the master record.

Second, master-detail relationships prevent reparenting by default. Salesforce documentation states that records cannot be reparented in master-detail relationships by default, although admins can allow reparenting if they choose.

A is incorrect because a lookup relationship does not support standard roll-up summary fields and does not permanently lock the parent Account by default.

C is incorrect because roll-up summary is a field on the parent Account, not the relationship field type on Gift Card.

D is incorrect because a formula cannot count related child records or enforce parent locking.

The formula must evaluate true when:

Stage = Negotiation/Review

Close Date < 1 week from today

Salesforce formula functions used:

ISPICKVAL() for picklist equality checks

AND() to combine multiple conditions

CloseDate < TODAY() + 7 to check the Close Date is within one week

Correct formula:

AND(

ISPICKVAL(StageName, " Negotiation/Review " ),

CloseDate < TODAY() + 7

)

Options A, C, D use invalid syntax (missing quotation marks, incorrect function structure).

Salesforce Help confirms correct syntax for picklist comparison and date arithmetic in formula fields. (Salesforce Help)

This formula evaluates true only when both conditions are simultaneously met.

===========

The correct answer is B. Lookup.

This is a one-to-many mentorship relationship: one experienced Realtor can mentor many new Realtors, but each new Realtor works with only one experienced Realtor. A lookup relationship is appropriate for connecting one record to another in this type of flexible parent-child model. Salesforce relationship documentation confirms that lookup relationships are used to relate objects without the strict ownership, sharing, and deletion behavior of master-detail relationships.

Master-detail is too restrictive because the new Realtor record should not necessarily inherit ownership and deletion behavior from the mentor. Many-to-many is incorrect because each new Realtor has only one mentor. Indirect lookup is used for external objects, not this internal Salesforce relationship.

===========

The correct answer is A. Configure Campaign Interactions and Campaign statistics.

The option text appears to contain an OCR/wording issue. The intended Salesforce feature is Campaign Hierarchies and Campaign statistics. For advertising ROI, Salesforce Campaigns are the correct feature because Campaign ROI reports calculate return on investment using campaign cost and won opportunity value. Salesforce also states that campaign hierarchy metrics roll up from child campaigns to parent campaigns, which helps analyze campaign performance across related marketing efforts.

B is incorrect because Account interactions and roll-up summary fields are not the standard marketing ROI solution.

C is incorrect because changing the whole org to a public security model is unnecessary.

D is incorrect because an opportunity pipeline report alone does not provide campaign ROI analysis.

The correct answers are A. Create owner-based sharing rules that give Read access to the master objects and C. Set Sharing Settings to Read Only on both Master-Detail relationship fields.

A junction object is normally created with two master-detail relationships to represent a many-to-many relationship. Salesforce documentation states that sharing access to a junction object record is determined by the user’s access to both associated master records and the Sharing Setting option on the master-detail relationship fields.

Because the master objects, Seminars and Attendees, have private organization-wide defaults, selected users need record access to those master records. Owner-based sharing rules can grant the selected group Read access to the master object records. Salesforce also documents that organization-wide defaults define baseline record access, and sharing rules are used to extend access when defaults are private or restricted.

The Read Only sharing setting on the master-detail relationship allows users with at least read access to the master records to work with related detail records, assuming they also have the required object permissions on the junction object.

B is incorrect because lookup filters restrict selectable related records; they do not grant record access.

D is incorrect because junction object records in master-detail relationships inherit sharing from the master records. Sharing is not handled directly through an owner-based sharing rule on the junction object.

==========

A Record-Triggered Flow is the best tool because the automation must run automatically when a client is won. Salesforce Trailhead explains that record-triggered flows run when a record is created, updated, or deleted, and can update records, send notifications, create related records, call actions, and handle criteria-based logic.

Here, the flow can:

Detect when the client is won.

Send an email notification to the finance manager.

Use a decision element to check whether the client is top-tier.

Create an onboarding task for the sales manager only when the client is not top-tier.

Why not others:

A. Approval Process is for approval routing, not general client-won automation.

C. Apex is unnecessary because Flow can meet the requirement declaratively.

D. Screen Flow requires user interaction, but this must happen automatically.

===========

Based on the exact options provided, the correct answer is A. Create a master-detail relationship field on Open Position to Application.

The requirement says one applicant must be able to apply for multiple open positions using a single application. In Salesforce, the relationship field is created on the detail/child object. Therefore, to allow one Application__c record to relate to multiple Open_Position__c records, the master-detail field would be created on Open_Position__c and point to Application__c . Salesforce Trailhead confirms that in a master-detail relationship, the relationship field is created on the detail object.

Salesforce also uses master-detail relationships and junction objects to model many-to-many relationships.

Important note: In a fully normalized recruiting data model, a separate junction object between Application and Open Position is usually cleaner. But from the provided answer choices, A is the only option that supports one Application being connected to multiple Open Positions.

===========

The correct answer is C. Create a validation rule that uses the PRIORVALUE function.

The requirement is: once Estimated Hours is set, users can decrease the value but cannot increase it. A validation rule can compare the new value with the old value by using PRIORVALUE() .

Example logic:

Estimated_Hours__c > PRIORVALUE(Estimated_Hours__c)

Salesforce documents PRIORVALUE() as the function used to return the previous value of a field, and Salesforce examples use it in validation rules to compare a changed value against the prior value.

A is incomplete because ISCHANGED() only detects that the field changed; it does not determine whether the value increased or decreased.

B is incorrect because a default value does not control later edits.

D is incorrect because PREVGROUPVAL() is used in reports, not validation rules.

===========

The correct answers are C. Email Alert, D. Task, and E. Outbound Message.

In a standard Salesforce approval process, available approval action types include Email Alerts, Tasks, Field Updates, and Outbound Messages. Since Field Update is not listed in the answer choices, the three valid action types from the options are Email Alert, Task, and Outbound Message. Salesforce documentation identifies approval-process actions around task, email alert, field update, and outbound message automation.

A. Invocable Flow is incorrect because it is not a standard approval-process action type in this exam context.

B. Decision Element is incorrect because Decision is a Flow element, not an approval-process action.

===========

The correct answer is C. Create a master-detail relationship between the parent and child object with a roll-up summary field that filters on the status field.

A roll-up summary field is the recommended declarative solution when Salesforce needs to summarize child-record data on a parent record. Salesforce documentation states that roll-up summary fields calculate values from related records and are defined on the master side of a master-detail relationship.

In this scenario, Opportunity is the parent and Detailed_Sales__c is the child. The roll-up summary field can summarize sales metrics and use filter criteria so only child records where Status = Active are included.

Why others are incorrect:

A is incorrect because a third-party AppExchange app is unnecessary when native roll-up summary functionality meets the requirement.

B is incorrect because Apex is not recommended when a declarative feature can solve the requirement.

D is incorrect because lookup relationships do not support standard roll-up summary fields. Salesforce documentation states that lookup relationships are similar to master-detail relationships, except they do not support roll-up summary fields.

===========

The correct answer is A. Roll-up summary field.

Cloud Kicks wants to count how many Subscription records are related to each Shoe record. Because a master-detail relationship already exists between Subscription and Shoe__c , the app builder should create a Roll-Up Summary field on the master object.

Salesforce documentation confirms that roll-up summary fields can count the number of detail records related to a master record. Trailhead also explains that roll-up summaries display values on the master record based on directly related detail records in a master-detail relationship.

B. Lookup field and C. Master-detail field define relationships, but the relationship already exists. D. Sum field is not a Salesforce field type.

===========

The correct answer is C. Use Dynamic Forms to display the Years of Previous Experience field if Previous Experience is checked.

This is a conditional field-visibility requirement. Salesforce Dynamic Forms lets app builders manage fields and sections directly in Lightning App Builder and use visibility rules to show users only the fields they need, when they need them.

So the app builder can place the Years of Previous Experience field on the Dynamic Forms-enabled record page and set visibility so it displays only when Previous Experience = True.

A is unnecessary and overcomplicated.

B is incorrect because field dependencies apply to picklists, not checkbox-to-number visibility.

D is incorrect because Visualforce is unnecessary when Dynamic Forms provides a declarative solution.

===========

The correct answers are A. The NOW() function in the formula field and D. A cross-object field referenced in the formula field.

Salesforce allows roll-up summary fields to summarize formula fields only when the formula does not contain unsupported dynamic or cross-object references. Salesforce documentation states that roll-up summaries can calculate formula fields only if the formula does not contain cross-object field references or functions that derive values dynamically, such as NOW() or TODAY().

A is correct because NOW() changes dynamically based on current date/time.

D is correct because cross-object field references prevent the formula from being used in the roll-up summary.

C is incorrect because CASE() itself is allowed.

B is incorrect because the issue is not simply a field update; the restriction is specifically cross-object references or dynamic formula functions inside the formula being summarized.

===========

Use a Component visibility filter. The issue is not object access or field access. The Contact Lightning record page is shared, but one component should be hidden for users with the Marketing profile. Salesforce Lightning App Builder supports visibility filters on Lightning page components, so the app builder can conditionally show or hide that component based on user/profile criteria.

Why not the others? AppExchange is unrelated. Detail page layouts control field layout, not visibility of a Lightning page component. Field-level security controls field access, not whether a large component appears on a Lightning record page.

===========

The correct answer is B. Universal Containers has internal Account OWD set to Public Read/Write, which lets internal users broadly access Account records. However, Experience Cloud / customer community users can have a separate external sharing model. Salesforce documentation explains that External Organization-Wide Defaults provide separate default access for external authenticated users so companies can better secure data for community users.

Setting the Account external OWD to Private prevents customer community users from seeing all company Account records by default.

Why others are incorrect:

A record types do not control record visibility.

C an owner-based sharing rule would grant more access, not restrict default access.

D permission sets grant object/field permissions; they do not replace OWD record-sharing control.

===========

Feed Tracking is the correct feature because Salesforce can automatically generate feed updates when a tracked field changes on a record. Salesforce Help explains that feed tracking detects changes to tracked record fields and posts updates to the feed. It can also be configured for custom objects.

For this scenario, the app builder would track the travel request approval/status field. When the request becomes Approved, Salesforce posts that tracked change automatically on the record feed.

Why others are incorrect:

Auto-response rule sends automatic email responses, mainly for Lead/Case scenarios.

Approval process manages record approval routing, but the feature that creates automatic feed posts for field changes is Feed Tracking.

Feed quick action is manual, not automatic.

===========

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.

===========

The correct answers are A. Roll-up summaries are limited to master-detail relationships and C. An object can have 25 roll-up summaries.

Roll-up summary fields summarize data from related child records onto the parent record, but standard Salesforce roll-up summaries are available only when the child records are directly related through a master-detail relationship. In this scenario, only one of the three custom objects has a master-detail relationship to Account, so native roll-up summaries cannot be used for the other two lookup/non-master-detail objects.

Salesforce also lists 25 roll-up summary fields per object as the standard allocation, so summarizing 15 fields from three objects would require 45 summaries, which exceeds the normal Account object limit.

B is incorrect because native roll-up summary calculations support COUNT, SUM, MIN, and MAX, not AVG.

D is incorrect because “20 object references” is not the key roll-up summary consideration in this proposal.

The correct answer is B. This lookup relationship will need to be converted to a master-detail relationship before a roll-up summary field can be created.

A Salesforce roll-up summary field is created on the object that is on the master side of a master-detail relationship. Lookup relationships do not support standard roll-up summary fields. Salesforce documentation confirms that roll-up summary fields are defined on the master object in a master-detail relationship.

A and D are incorrect because formula fields cannot count related child records across a lookup relationship.

C is incorrect because the relationship is currently lookup, so a standard roll-up summary field cannot be created yet.

===========

The correct answer is C. Submit the record for approval from an automated process.

The issue is not the approval process itself. The issue is that sales reps forget to manually submit the Opportunity. Salesforce supports submitting records for approval from automation, including Flow’s Submit for Approval action. Salesforce also documents using an after-save record-triggered flow to automatically submit records into an approval process.

A does not solve the problem because changing approval entry criteria does not automatically submit the record. B only reminds the manager and does not run the approval process. D is unrelated to automatic submission.

===========

The correct answer is C. Flow.

The requirement is to automatically delete rejected Quote records. Salesforce Flow is the correct declarative automation tool because Flow can identify records and delete them using the Delete Records element.

Why not the others:

Approval Process routes records for approval. Einstein Next Best Action recommends actions. Validation Rule prevents bad saves. None of those tools is designed to delete rejected child records automatically.

===========

The correct answer is B. Geolocation.

Salesforce geolocation fields are used to identify locations using latitude and longitude and can support distance calculations.

Because Universal Containers delivers containers to remote construction sites and customers provide crossroads or location markers, the app builder should use a Geolocation field to capture location-based information rather than a number, reference, or external lookup field.

Why others are incorrect:

A. Number stores numeric values only.

C. Reference is not the correct field type for capturing physical location.

D. External Lookup is used to relate Salesforce records to external object records, not to store site location details.

===========

The correct answer is C. App Manager.

To add components to the Utility Bar of an existing Lightning app, the app builder edits the app from Setup → App Manager, then uses the app’s Utility Items configuration. Salesforce Help specifically states that to edit or add a utility bar to an existing app, use App Manager and click Edit for the app.

Why others are incorrect:

A is close, but the entry point for editing an existing app’s utility bar is App Manager, not directly Lightning App Builder.

B is wrong because a Lightning Record Page is for record page layout/components, not app-level utility bar configuration.

D is wrong because App Menu is for launching apps, not configuring them.

===========

The correct formula is TEXT(Galaxy__r.Type__c) .

The parent field Type__c is a picklist. In Salesforce formulas, a picklist value cannot be displayed directly as plain text unless it is converted with the TEXT() function. Salesforce documentation states that TEXT() converts picklist values to text in supported formula contexts. Cross-object formulas can reference fields from related parent records, so the child object Star__c can reference the parent Galaxy__c field using the relationship syntax Galaxy__r.Type__c .

VALUE() is for converting numeric text into a number, ISPICKVAL() checks whether a picklist equals a specific value, and FIND() searches text. None of those displays the parent picklist value as text.

===========

The correct answers are B. Set organization-wide default to Private, D. Disable Grant Access Using Hierarchies, and E. Create a criteria-based Sharing Rule for the HR Department.

Set the Review object’s OWD to Private so review records are not visible to all employees by default. Organization-wide defaults define the baseline record access users have to records they do not own.

Disable Grant Access Using Hierarchies because this is a custom object and the requirement says only HR and the submitting employee should see the review. Salesforce allows this setting to be disabled for custom objects so managers higher in the role hierarchy do not automatically inherit access.

Create a criteria-based sharing rule for the HR department so HR can see the Review records even though the default access is private. Salesforce sharing rules are used to grant wider access beyond OWD.

Why others are incorrect:

A is not needed and a Master-Detail relationship to User is not the right access-control design.

C is incorrect because removing Review Read permission from non-HR users would also prevent the submitting employee from viewing their own submitted review.

===========

The correct answer is A. A custom detail page link on the Contract object.

Users need access to the pricing guidelines document while viewing a Contract record. A custom detail page link can be added to an object’s page layout and used from the record detail page to open an internal document, external URL, intranet page, or other resource. Salesforce documen tation confirms that custom buttons and links can be added to object and record detail pages to give users quick access to needed resources.

Since the document is needed while viewing the Contract, the link belongs on the Contract object, not the Account object.

===========

The correct answer is D. Component visibility filter.

In Lightning App Builder, component visibility rules can control whether a component appears based on context, including the device/form factor. Salesforce Trailhead specifically describes creating a visibility rule so a component appears only when the page is viewed on a phone, which matches restricting a Lightning component to mobile users.

A is incorrect because form factor settings are generally used for page/device availability or preview behavior, not the best feature for hiding or showing one specific component on a single Lightning record page.

B and C are incorrect because the Highlights Panel and Related List Quick Links are page components, not conditional visibility tools.

===========

The requirement specifies that a new vendor must accept terms on Agreements before an Opportunity can be closed. Salesforce Approval Processes are the declarative solution for enforcing such business rules. An approval process can:

Require users (vendors) to accept or approve records (Agreements).

Prevent Opportunities from moving to a closed stage until approval is completed.

Send email notifications automatically to approvers.

Salesforce documentation confirms that approval processes are used to enforce conditions on record lifecycle and ensure required steps are completed before record status changes. (Salesforce Help)

A. Email Alert cannot enforce record progression.

B. Dynamic Action only controls field-level UI visibility, not enforcement.

D. Validation Rule could prevent saving a record, but it cannot require explicit approval from a specific user group.

===========

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

The legacy ID should be stored in a custom field marked as an External ID because Salesforce uses External ID fields to identify records from an outside system and to support update/upsert operations during future data loads. The field should also be marked Unique so each legacy system ID maps to only one Salesforce Account record and avoids duplicate-match problems during upsert. Salesforce documentation defines External ID fields as fields that contain record identifiers from outside Salesforce and can be used to update or upsert records.

A. Required is not necessary for the upsert-matching requirement.

B. Encrypted/Text encrypted is not appropriate because encrypted fields are not used for this legacy-ID matching purpose.

===========

The correct answer is C. Two Master-detail relationships on a new custom object.

This is a many-to-many relationship: one Contact can be related to many Solar Projects, and one Solar Project can be related to many Contacts. Salesforce’s standard declarative design for many-to-many relationships is a junction object. A junction object is a custom object with two master-detail relationships connecting the two related objects.

A is incorrect because the two master-detail relationships belong on the new junction object, not directly on Contact and Solar Project.

B can technically relate records, but it is not the standard Salesforce many-to-many model tested here.

D does not correctly create a scalable many-to-many model.

===========

The correct answers are B. Flow Builder and D. Escalation rules.

Escalation rules are the most direct Salesforce Service feature for this requirement. They are designed to automate case escalation when cases are not resolved or not acted on within a defined time period. Salesforce documentation explains that escalation rule entries can use business hours, and escalation actions can send notification emails when the case escalates.

Flow Builder can also be used because record-triggered flows support scheduled paths, allowing automation to run after a defined time from a triggering record event. A flow can check whether the Case is still in New status and then send a notification. For strict business-hour calculation, the app builder must design the flow carefully around the correct time source/business-hour logic.

A is incorrect because validation rules only prevent invalid data from being saved; they do not wait four business hours and send notifications.

C is incorrect for the Platform App Builder context because Scheduled Apex is a programmatic approach, while declarative automation tools are available and preferred for this requirement.

===========

The correct answers are A. Create a child record, C. Update a related record, and D. Send an email alert.

Process Builder was designed to automate repetitive business actions. Salesforce documentation describes Process Builder as a tool for automating tasks, emails, and record updates.

Process Builder can improve productivity by performing actions such as:

Create a child record — Process Builder can create a record when criteria are met.

Update a related record — Process Builder can update the record that started the process or related records.

Send an email alert — Salesforce documentation specifically states that a process can send an email by using an email alert.

B is incorrect because “Start an additional message” is not a standard Process Builder productivity capability.

E is incorrect because Process Builder does not delete related records as a standard declarative action.

===========

This question is testing the classic Salesforce Process Builder automation best practice , not a generic Flow-only rule. Salesforce’s official process design guidance states that an org should have only one record-change process per object . The reason is simple: every time a record is created or updated, Salesforce evaluates the record-change processes for that object. If an object has multiple record-change processes, the automation becomes harder to predict, harder to troubleshoot, and more likely to hit governor limits. Salesforce specifically explains that consolidating automation into one record-change process gives admins a single view of all criteria and actions for that object, reduces duplicated automation overhead, and allows the app builder to control the order of criteria evaluation.

A is not the best exam answer here. In modern Flow architecture, “one Flow per object” is often discussed as a design pattern, but it is not the exact best-practice wording being tested by this Platform App Builder-style question. Salesforce Flow design is more nuanced today because record-triggered flows can vary by trigger timing and event. B is wrong because validation rules should be separated by validation requirement, not forced into one rule per object. C is wrong because invocable processes are reusable modular processes, not the main record-change automation container.

The correct answer is B. Create a Chatter stream.

A Chatter stream gives users a combined feed from selected people, groups, and records. Salesforce documentation states that users can create a Chatter stream to get a combined view of feeds from selected profiles, groups, and records.

For this requirement, the sales rep can create a stream that includes only the key Account and Opportunity records, so their Chatter feed is filtered to those important records.

Why others are incorrect:

A. Chatter bookmarks save individual posts, but they do not create a filtered feed.

C. Chatter notification alerts users, but it does not filter the feed.

D. Chatter group is for group collaboration, not filtering posts from selected records.

===========

omprehensive and Detailed Explanation with all Platform App Builder documents: =

The correct answer is A. Roll-up Summary.

DreamHouse Realty wants to show the highest value from related Offer records on each Property record. Because the objects have a master-detail relationship, a roll-up summary field is the correct declarative solution.

Salesforce documentation explains that roll-up summary fields calculate values from related detail records and display the result on the master record. Salesforce also lists MAX as the roll-up type used to display the highest value from related records.

B is not a Salesforce field type for this requirement.

C, D, and E are data-entry field types and cannot calculate the highest related Offer value.

===========

The correct answers are B. Apex and C. AppExchange.

Cloud Kicks needs to count related Case records on Account based on open and closed status. Standard roll-up summary fields work only in supported roll-up relationships, mainly master-detail relationships. Salesforce documentation states that lookup relationships do not support roll-up summary fields.

Because Cases are related to Accounts through a lookup-style relationship, native roll-up summary fields are not the best available option in this answer set. The app builder can meet the requirement by using:

Apex — Apex triggers can run before or after record changes such as insert, update, or delete, allowing custom logic to recalculate the open and closed Case counts on the Account.

AppExchange — AppExchange roll-up tools, such as lookup roll-up packages, can summarize records across lookup relationships without building custom code.

Why others are incorrect:

Validation Rule prevents invalid data entry; it does not calculate related record counts.

Approval Process routes records for approval; it does not summarize Case counts.

===========

The correct answer is A. Create a lookup relationship on Asset Inventory to Asset. Add the Asset Inventory related list to the Asset page layout.

To show Asset Inventory records as a related list on Asset, the child object must contain the relationship field pointing to the parent object. In this scenario, Asset Inventory is the child/detail-style object, and Asset is the parent record where the related list should appear.

Salesforce relationship fields connect records between objects, and related lists can then be added to the parent object’s page layout. Salesforce documentation for related lists confirms that related lists are managed from the object’s page layout.

Why others are incorrect:

B is incorrect because a roll-up field does not create the relationship or related list.

C is incorrect because the relationship direction is wrong; the relationship field should be created on Asset Inventory, not on Asset.

D is incorrect because a junction object is only needed for many-to-many relationships. Here, Asset Inventory records simply need to relate to Asset records.

===========

The correct answers are A. Recent items, B. Filter list/List View, and C. Rich text.

Lightning App Builder includes standard components built by Salesforce. Salesforce documentation identifies standard Lightning page components and references components such as Recent Items, Rich Text, and List View for Lightning App Builder pages.

D. Report details is incorrect because the standard component is Report Chart, not Report Details. E. Plain text is incorrect because the standard component is Rich Text, not plain text.

===========

The correct answers are A. Create an object-specific action on Account and D. Create predefined values for most of the fields.

For this requirement, sales reps need to create a custom Feedback record related to an Account with minimal clicks on mobile. An object-specific quick action is the best solution because it runs in the context of a specific Account record and can create a related child record automatically. Salesforce Trailhead states that object-specific actions let users create records with automatic relationships to other records and provide a streamlined mobile and desktop experience.

Predefined field values reduce manual typing and save mobile users time. Salesforce mobile customization guidance explains that quick actions can include predefined fields, and Trailhead specifically shows predefined values being used to prepopulate fields on action layouts.

B. Create a feedback object as a parent of Account is incorrect because the Feedback record should be related to each Account, normally as a child record or lookup-related record. C. Create a global action on Account is incorrect because global actions create records without record context; Salesforce explains that global actions create records with no relationship to other records, while object-specific actions work in the context of a particular object.

===========

The correct answers are A. Tabs and B. Related record.

Tabs help create a more condensed Lightning record page by grouping information into separate tabbed sections instead of showing everything in one long page. Salesforce Lightning App Builder allows app builders to add, remove, reorder, and customize components on Lightning record pages.

Related Record is required because service agents want to modify the associated Contact and Account directly from the Case Lightning record page. Salesforce Help states that the Related Record component uses quick action metadata and requires an associated quick action to update records.

Why others are incorrect:

Path is used to guide users through stages or status values, not to edit related Account or Contact records.

Rich Text displays formatted guidance or static text; it does not provide editable related-record functionality.

The correct answer is B. Clone the change set and re-deploy.

After a change set has been uploaded, Salesforce does not allow its contents to be changed. Salesforce documentation states that after upload, the change set contents cannot be changed; to redeploy the same set of components, the app builder should clone the change set, and the cloned change set includes the latest changes to its components from the source org.

A is incorrect because renaming does not update uploaded components. C is unnecessary. D is incorrect because an uploaded change set cannot simply be updated and redeployed.

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 C. External objects and D. Big objects.

External objects are suitable because they represent data stored outside Salesforce while still being accessible in Salesforce. Salesforce documentation explains that external objects behave similarly to custom objects, but the record data is stored outside the Salesforce org. External objects can also participate in lookup-style relationships, including external and indirect lookup relationships, and Salesforce Connect supports reports that include external objects.

Big objects are also suitable for archiving very large volumes of historical data on the Salesforce platform. Salesforce describes big objects as a way to store and manage massive amounts of data, including archived data from other objects. Big objects support querying through SOQL/API patterns, and Salesforce documentation also covers viewing big object data in reports and dashboards, commonly by using a working dataset for reportable subsets.

A is incorrect because “related objects” does not reduce Salesforce data storage.

B is incorrect because moving data into custom objects still consumes Salesforce data storage, so it does not solve the storage-limit issue.

===========

The correct answers are B. Upload the lead list using the Import Wizard and select a Matching Type to prevent duplicate lead creation and D. Utilize a Lead Matching Rule and corresponding Duplicate Rule to block newly created duplicate leads.

For 400 leads, the Data Import Wizard is appropriate because Salesforce supports importing leads and other common objects with the wizard, and it can handle up to 50,000 records.

Salesforce documentation for lead imports states that choosing a matching type sets criteria for avoiding duplicate leads when using the Data Import Wizard.

Duplicate Management also uses matching rules and duplicate rules to identify and control duplicates. Salesforce states that duplicate rules can block users from creating duplicate records, including lead duplicates.

Why others are incorrect:

A is incorrect because Data Loader’s update operation updates existing records and normally requires record IDs or proper matching/upsert configuration; it is not the best duplicate-prevention answer here.

C is not the correct Salesforce setup wording. The correct tools are Lead Matching Rules and Duplicate Rules.

===========

The correct answer is D. Roll-up summary field.

Cloud Kicks wants to display a count of related Opportunities on the Account record where the Opportunities are Closed Won and have a Close Date within the last year. A roll-up summary field is the correct declarative feature because it calculates values from related records, including counts, sums, minimums, and maximums. Salesforce documentation confirms that roll-up summary fields calculate values from related records and can display values on the parent record.

The app builder can create a roll-up summary field on Account with filter criteria such as:

Stage = Closed Won

Close Date = Last 365 Days / Last Year

Why others are incorrect:

Activity timeline displays activities, not Opportunity counts.

Formula field cannot count multiple child Opportunity records.

Validation rule blocks invalid saves; it does not calculate related record totals.

===========

The validation rule must fire when two things are true:

Job_Accepted__c is already populated

Hire_Date__c is being changed

Salesforce’s ISCHANGED() function returns true when a field’s value changes from its previous value, and formula functions can be used in validation rules.

So this formula prevents users from changing the hire date after the candidate has accepted the offer:

NOT(ISBLANK(Job_Accepted__c)) & & ISCHANGED(Hire_Date__c)

Why others are incorrect:

The other options either use the wrong logical operator or validate the opposite condition. A validation rule must return TRUE only when Salesforce should block the save.

===========

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 answer is A. Flow.

The requirement says the Opportunity should store the Account Billing State value, but the value must remain static after the Opportunity is created. A record-triggered Flow is the recommended declarative automation because it can run when an Opportunity is created and populate a custom field with the related Account’s Billing State. Salesforce Trailhead describes record-triggered flows as automation that can run when a record is created or updated, and can update the triggering record or related records depending on configuration.

D. Formula field is incorrect because formula fields are automatically calculated and read-only. A formula would continue to reflect the current Account Billing State, so it would not preserve the original value after creation.

B. Apex is not the recommended first choice because Flow handles this requirement declaratively.

C. Roll-up summary field is incorrect because roll-ups aggregate child records; they do not copy a parent Account field value onto an Opportunity.

The correct answer is D. For use on the utility bar.

For a custom Lightning web component to appear as an available component in the utility bar, it must be exposed in its metadata configuration with the lightning__UtilityBar target. Salesforce developer documentation states that lightning__UtilityBar enables a component to be used as a utility item in an app’s utility bar, and the component must be exposed with the appropriate target.

B. For use in Lightning App Builder is broader and not enough by itself for utility-bar availability. C. For use on record pages exposes the component for record pages, not the utility bar. A. For use in App Manager is not the correct component target wording.

===========

The correct answer is A. The requirement is to combine four custom text fields into one formula field and display the result on two lines.

The formula works as follows:

Street__c displays the street on the first line.

BR() inserts a line break. Salesforce documents the BR formula function as inserting a line break in a text string.

City__c & " , " & Planet__c & " " & Galaxy__c displays the remaining location information on the second line. The & operator connects two or more strings in Salesforce formulas.

Why others are incorrect:

Options using field names without __c are not correct for custom fields. Options using __r are relationship references, not direct custom field references. Options without BR() do not satisfy the two-line requirement.

===========

The correct answer is B.

This is a one-user exception. Salesforce recommends using permission sets to extend access without changing the user’s base profile. A permission set can grant read-only field access through field-level security to just the selected customer service agent. Salesforce documentation explains that permission sets extend user access, and field permissions control whether users can view or edit individual fields.

Why others are incorrect:

A creates a new profile for one user, which is not the recommended scalable solution.

C is not accurate because field-level security is assigned through profiles or permission sets, not directly to one user from the field alone.

D would give all users with the Customer Service profile read-only access, not only the single agent.

===========

Schema Builder can create custom objects, relationship fields, formula fields, and normal fields, but a key limitation is that fields created through Schema Builder are not automatically added to the object’s page layout. The app builder must go to the page layout separately and place the fields where users need to see them. Salesforce Trailhead confirms Schema Builder supports relationship fields, formula fields, and normal fields, so option B is incorrect. Salesforce Help also notes that fields added through Schema Builder are not automatically added to the page layout.

The correct answer is A. Two Master-detail relationships on a new custom object.

This is a classic many-to-many relationship requirement: one Contact can relate to many Solar Projects, and one Solar Project can relate to many Contacts. Salesforce recommends using a junction object for many-to-many relationships. A junction object is a custom object with two master-detail relationships.

The new custom junction object would sit between Contact and Solar Project, with one master-detail relationship to Contact and one master-detail relationship to Solar Project.

C could technically connect records using lookups, but the standard Salesforce data-modeling answer for a true many-to-many relationship is a junction object with two master-detail relationships.

===========

The correct answer is D. Approval process with a record-triggered flow.

Salesforce does not provide a simple “approval before delete” button behavior by default. The practical declarative pattern is to use an Approval Process for manager permission and a record-triggered Flow to automate the submit/delete logic. Flow includes a Submit for Approval action for Classic Approval Processes and also supports deleting records through the Delete Records element.

Why not the others:

A two-step approval process only handles approval routing; it does not complete the deletion automation by itself. A scheduled path or schedule-triggered flow is not appropriate because this is based on a user’s delete request, not a time-based batch process.

===========