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

To optimize Salesforce Mobile experience:

B. Minimize formula fields and lookup fields improves page load performance on mobile devices.

C. Put key fields in the compact layout ensures important information is visible immediately.

E. Use Global Actions simplifies creating or updating records from mobile quickly.

Salesforce documentation on mobile best practices recommends limiting complex fields, prioritizing compact layouts, and using quick actions for essential functionality. (Salesforce Help)

A is incorrect because default values improve speed and reduce user errors, not eliminate them.

D is unnecessary; Lightning layouts are responsive and do not require separate OS-specific layouts.

===========

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 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 C. Unable to reference the child records.

A formula field on Account cannot directly pull data from multiple related Contact records because Contacts are child records of Account. Cross-object formulas work by referencing fields through supported parent relationships, not by traversing from a parent record down to multiple child records. Salesforce documentation describes cross-object formulas as formulas that reference fields on related objects, especially parent records through relationships.

Because an Account can have many Contacts, Salesforce does not expose that child relationship in the formula editor as a single field reference. For summarized child data, the app builder would normally use a roll-up-style solution where supported, or automation such as Flow.

A is unrelated unless the formula has already exceeded character limits.

B is misleading because the core issue is not simply that Account and Contact lack master-detail; it is that formulas cannot directly reference child records.

D is not supported by the scenario.

===========

The verified exam answer is D. Add the Path component to the Lightning record page.

Salesforce Path is designed to guide users through stages of a business process. For each step, such as each Opportunity Stage, an app builder can highlight key fields and add guidance for success. Salesforce documentation states that when creating a Path, the app builder can select key fields for each step and enter success guidance.

This fits the requirement because users need to know which fields should be completed at each Opportunity stage.

Important nuance: Path guides users, but it does not hard-enforce stage-based required fields by itself. Salesforce notes that page layouts cannot require different fields in different Path steps; strict enforcement requires validation rules based on the stage/path step.

===========

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.

===========

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.

===========

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

Formula fields can reference fields from related parent records using cross-object formulas, but they cannot directly pull values from multiple child records onto a parent record. Salesforce describes cross-object formulas as formulas that can reference fields from a parent object when the formula is created on the child/detail side of the relationship.

In this case, Account is the parent and Contacts are child records. Since the formula is being created on Account and trying to reference related Contacts, the relationship does not appear in the formula editor.

Correct design alternatives: use a roll-up summary where supported, Flow, Apex, or reporting.

===========

The correct answers are C. Users, D. Public Groups, and E. Roles and Subordinates.

Manual sharing is used when the org-wide default is private and users need to share individual records on a case-by-case basis. Salesforce documentation confirms that manual sharing allows users to share individual records with other users, public groups, and roles.

A public group can include users, roles, and roles with subordinates, which makes it useful when sharing records with departments or groups of people.

A. Permission Set Groups is incorrect because permission set groups grant permissions, not manual record-level sharing.

B. Private Groups is not the standard manual-sharing option tested here.

===========

A utility bar gives users quick access to commonly used productivity tools and components from within a Lightning app or console app. Salesforce describes the utility bar as a fixed footer that provides fast access to tools such as Notes, History, softphone, flows, and custom utilities. Utilities open in docked panels, allowing users to keep working without leaving the current page. This exactly matches the requirement: components accessible from anywhere in the app without leaving the page.

The correct sandbox type is Partial Copy.

A Partial Copy sandbox is built for testing with a subset of production data. Salesforce lists Partial Copy sandboxes with 5 GB data storage and a 5-day refresh interval, which supports the requirement to refresh it every weekend.

Why the other options are wrong:

Developer and Developer Pro sandboxes are mainly for development and do not copy a produc tion data subset in the same way. A Full sandbox can copy all production data, but its refresh interval is longer and it is unnecessary for a subset under 5 GB.

===========

The correct solutions are D. Create a custom app page and assign it to the mobile menu and B. Include Today as a navigation item in the app.

Salesforce supports creating a mobile app page with Lightning App Builder for the Salesforce mobile app. This allows an app builder to design a mobile-focused experience and make it available through mobile navigation.

Salesforce also provides Today in the mobile app to help users manage their day, prepare for meetings, and access relevant mobile productivity information. Salesforce documentation states that users access Today from the Salesforce mobile app navigation menu, and admins can add Today to Lightning app navigation and the Mobile Only app.

C is not the best verified exam answer for the standard version of this question. While mobile navigation can be customized, the stronger Platform App Builder mobile UX recommendations here are adding a custom mobile app page and adding Today as a navigation item.

===========

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.

===========

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 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 answer is C. Record-triggered flow.

To track the number of times a Case is reopened, the app builder can create a record-triggered flow on the Case object that runs when the Case is updated. The flow can check when the Status changes from Closed to an open/reopened status and increment a custom number field such as Number_of_Reopens__c . Salesforce Trailhead explains that record-triggered flows run when records are created, updated, created or updated, or deleted.

Why not Apex Trigger? Apex could work, but the Platform App Builder best answer is the declarative option: Flow before code.

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.

===========

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 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 answer is B. Use an AppExchange solution.

UC has a time-sensitive need and the developers are delayed for several months. AppExchange is the best recommendation because it provides ready-to-install apps, components, and solutions that can extend Salesforce without building everything from scratch. Salesforce describes AppExchange as the marketplace for ready-to-install solutions, including apps, components, and experts.

A and C still require building the solution internally. D. Bolt solution is more specific to prebuilt Experience Cloud/community templates and is not the best answer for a general custom component requirement. Salesforce describes Bolt Solutions as combinations of Lightning apps, business process flows, and Experience Builder templates/pages.

===========

The correct answer is B. Add the standard Chatter feed component.

In Lightning App Builder, Salesforce provides a standard Chatter component. Salesforce documentation states that the Feed component was renamed Chatter in Lightning App Builder and is used to place the publisher and feed on a record page.

A is incorrect because a custom Chatter feed component is not needed.

C is incorrect because this does not come from the AppExchange/App College.

D is incorrect because Chatter feed is not added by using the standard related list component.

===========

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 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. Enhanced List.

Salesforce documentation states that the Enhanced List related list type shows up to 10 fields and allows users to resize columns, sort columns, perform mass actions, and wrap text. This exactly matches the requirement: users need to see ten fields and need the ability to sort and wrap text on related lists.

D. Basic List is incorrect because the Basic List type shows fewer fields and does not provide the enhanced related-list behavior required here. A. List View and B. List Class are not the correct Related List Lightning component type for this requirement.

===========

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 answer is C. Add the standard Chatter feed component.

In Lightning App Builder, Salesforce provides a standard Chatter component for record pages. Salesforce documentation states that the Feed component was renamed Chatter in Lightning App Builder and is used to place the publisher and feed on a record page.

A is incorrect because a related list component does not add the Chatter feed.

B is incorrect because the standard Chatter component is available in Lightning App Builder; it does not need to come from AppExchange.

D is incorrect because a custom component is unnecessary when Salesforce provides the standard Chatter component.

===========

The correct answer is D. Apex unit test failures.

The option text says “Apps unit test failures,” but the intended Salesforce answer is Apex unit test failures. When a package containing Apex is installed or deployed to production, Salesforce runs Apex tests. If the required tests fail, the package installation can fail. Salesforce documentation states that package installation involving Apex runs unit tests, and production deployments with Apex require tests to pass.

A, B, and C are not the best answers because the package already installed successfully in a Full Copy sandbox matching production. The most certification-relevant production failure reason is Apex test failure.

===========

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.

Universal Containers wants to accept clean data and verify that important fields are entered. The best solution is a validation rule, because validation rules verify that data entered by users meets defined standards before the record can be saved. This is stronger than making a field required only on a page layout, because validation rules can enforce requirements based on conditions such as record type.

A is weaker because page-layout required fields apply mainly to that UI layout and do not provide the same conditional data-quality enforcement. B is reactive cleanup after bad data exists. D can calculate or display a value, but it does not enforce user data entry by itself.

===========

The correct answer is D. Deselect auto add to custom report type.

When creating a new custom field, Salesforce provides an Auto Add option that can automatically add the new field to applicable existing custom report types. If the app builder does not want the new field to appear on pre-existing custom report types, they should deselect the Auto add to custom report type option during field creation. Salesforce release documentation confirms that Auto Add automatically adds custom fields to custom report types based on that object.

Why the other options are incorrect:

Removing the field from page layouts only affects record-page visibility, not report type availability.

Changing profile visibility or read-only access affects field security, not whether the field is added to the custom report type layout.

===========

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

A sandbox template is used to define which object data is copied into a sandbox. Salesforce documentation states that sandbox templates control what data is copied into Full or Partial Copy sandboxes. Since the question says the app builder created a sandbox template for Accounts, Projects, and Project Milestones, the correct testing environment is Partial Copy because it includes metadata plus a selected sample of production data defined by the sandbox template. Developer, Developer Pro, and Scratch Orgs do not use sandbox templates for selected production data in this way.

===========

The correct answer is B. Cross-object formula.

Opportunity has a standard relationship to Account, so an app builder can create a formula field on Opportunity that references the parent Account field. Salesforce defines a cross-object formula as a formula that spans related objects and references fields on those related objects.

Because Account_Region__c is a picklist on Account, the Opportunity formula would commonly be a text formula like:

TEXT(Account.Account_Region__c)

Field history tracking only tracks changes, a lookup field would create a relationship rather than display the Account field value, and field-level security controls visibility but does not copy or display the parent field on Opportunity.

===========

The correct answer is D. The Owner field on the Master record.

In a master-detail relationship, the detail record does not have independent ownership. Salesforce documentation states that the Owner field on the detail object isn’t available and is automatically set to the owner of the related master record.

Sharing is also controlled by the parent/master record. Salesforce Help explains that when a custom object is on the detail side of a master-detail relationship, its organization-wide default is set to Controlled by Parent.

A and C are incorrect because the detail record does not maintain independent ownership in a master-detail relationship. B is incorrect because ownership is not determined by a default owner setting on the parent object; it comes from the actual Owner field on the master record.

===========

The correct answer is B. Edit a record page using Lightning App Builder > Drag the component onto the page.

A custom Lightning component installed from AppExchange is configured on a Lightning record page through Lightning App Builder. Salesforce documentation states that Lightning App Builder supports custom Lightning components, including Aura and Lightning web components, and record pages are edited as Lightning pages.

The Page Layout editor is used for fields, buttons, related lists, and layout behavior, not for placing Lightning components on a Lightning record page. App Manager manages apps and utility bars, but the page canvas configuration is done in Lightning App Builder.

The correct answer is A. Web-to-Case is the Salesforce feature designed to let visitors submit case information from a public-facing website. Salesforce documentation states that Web-to-Case is set up by enabling the feature, creating and customizing a web form, and adding that form to a website.

Why others are incorrect:

B. Outbound message sends data out of Salesforce; it does not create cases from a website.

C. Screen flow could require extra site/guest-user setup and is not the standard feature for this requirement.

D. Email-to-case creates cases from inbound email, not directly from a public web form.

The correct answer is C. A record-triggered flow can run automatically when an Opportunity is updated to Closed Won, create a renewal Opportunity, and notify the contracts team. Salesforce Trailhead explains that record-triggered flows are built around trigger, criteria, and action; for example, when an Opportunity is created or updated and meets criteria, the flow can create another record.

Salesforce Flow can also create records and send emails, which fits both requirements: create the renewal Opportunity and notify an external contracts team.

Why others are incorrect:

A Approval Process is for review/approval routing.

B Outbound Message may notify an external system, but it does not handle the full renewal Opportunity creation requirement by itself.

D Validation Rule only prevents bad data; it does not create records or send notifications.

===========

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.

===========

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 D.

Universal Containers wants the Account Region value to appear on related Contact records and stay in sync whenever the Account value changes. A cross-object formula field on Contact is the best declarative solution because it dynamically references the parent Account field. Salesforce Trailhead explains that a cross-object formula can pull information from a parent object through a lookup relationship, such as showing Account information on Contact.

Because Account Region is a picklist, the formula must convert the picklist value to text using the TEXT() function. Trailhead gives the same pattern with Account Industry on Contact: TEXT(Account.Industry) .

B is incorrect because ISPICKVAL() checks whether a picklist equals a specific text value and returns true/false; it does not display the picklist value.

A and C are incorrect because creating a copied field and trying to update it through a relationship is unnecessary when a formula field can stay synchronized automatically.

===========

The correct answer is B. Create a new roll-up summary field called First Order Date, using type MIN on the Opportunity Close Date with a filter where IsWon = TRUE.

Cloud Kicks wants to track the first purchase date for each customer. The first purchase is the earliest won Opportunity Close Date. A roll-up summary field can calculate values from related records and supports summary types such as COUNT, SUM, MIN, and MAX. Salesforce Trailhead states that MIN displays the lowest value from the selected field and supports date/date-time fields.

So the app builder should create a roll-up summary field on the Account, summarize related Opportunities, choose MIN on CloseDate , and filter to only include won Opportunities, such as IsWon = TRUE .

A and C are incorrect because the field should be a roll-up summary field itself, not a regular date field updated by a roll-up.

D is incorrect because SUM is for number, currency, and percent fields, not date fields. Salesforce documentation confirms that MIN/MAX support date fields, while SUM is for numeric-style fields.

===========

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 answer is C.

The app builder needs to display only the first five digits from the parent Account’s ZIP+4 custom text field. Salesforce’s LEFT() function returns a specified number of characters from the beginning of a text string, so the correct formula is:

LEFT(Account.Zip_Code__c, 5)

Salesforce formula documentation confirms that LEFT returns characters from the beginning of a text string.

BEGINS() checks whether text starts with specific characters. LPAD() pads text to a specified length. TEXT() converts certain data types to text, but it does not extract the first five characters.

===========

The correct answer is A. Sharing rules.

Because the Account OWD is Private, users can’t automatically see records owned by users in another branch of the role hierarchy. Salesforce sharing rules are used to extend record access beyond the organization-wide default and role hierarchy. Salesforce documentation states that sharing rules grant additional access to users in public groups, roles, or territories.

Why others are incorrect:

B. Public groups can be used inside a sharing rule, but the public group alone does not share records.

C. Aliases are user display shortcuts, not security controls.

D. Assignment rules assign records; they do not grant cross-team record visibility.

===========

The correct answers are A. Set up new public Chatter groups and D. Use post action on the Account object.

Public Chatter groups support open collaboration where company users can share information in a group feed. Salesforce Chatter groups are designed for teams to share information, files, and discussions.

Post action on the Account object allows users to discuss customer accounts directly from the Account record feed. Salesforce Chatter feeds appear on record pages and allow users to follow records and see updates about them.

Why others are incorrect:

Private Chatter groups are not suitable because CK wants all company employees to see the conversations.

Chatter actions to create tasks help assign work, but they do not primarily solve open company-wide collaboration around accounts.

===========

The correct answer is C. Approval process.

The key requirement is that the manager’s sign-off on free parts must be processed. Salesforce approval processes are designed to automate record approval, define approval steps, assign approvers, and perform actions when records are approved or rejected. Salesforce Trailhead gives a similar discount-management example where discount percentage is tracked and manager approval is requested through an approval process.

Why others are incorrect:

A. High Velocity Sales is for sales engagement/cadences, not approval sign-off.

B. Quotes may help with pricing, but it does not by itself process manager approval.

D. Checkbox can store a value but cannot route approval.

===========

Use a Record-Triggered Flow optimized for Actions and Related Records.

Submitting a record for approval is an action in Flow. Salesforce provides a Submit for Approval action, and after-save record-triggered flows are used when the automation needs to perform actions or work with related records after Salesforce saves the triggering record.

Option A is wrong because Fast Field Updates is the before-save path, mainly for updating fields on the triggering record. It is not the right optimization for submitting an approval request. Option B still requires a custom button and manual user action. Option C is unrelated because this requirement is based on an Opportunity record change, not a platform event.

===========

The correct answer is A because Salesforce provides the Establish upper bound on existing picklists option to protect picklist performance by limiting inactive picklist values. Salesforce documentation states that this setting runs a query to identify picklists with fewer than 4,000 inactive values and enforce the limit.

Why others are incorrect:

B is for reusing picklist values across fields, not reducing inactive picklist performance impact.

C would worsen the issue because it removes limits on inactive values.

D is too drastic and not the recommended Salesforce feature for this issue.

===========

The correct answer is B.

Salesforce supports roll-up summary fields for summarizing related records, including scenarios involving Account and related Opportunity values. However, Salesforce documentation states that if Advanced Currency Management is enabled, currency roll-up summary fields are invalid when they are on Accounts and summarize Opportunity values.

Because the VP wants to aggregate Opportunity Amount values on Account, the app builder cannot create that roll-up summary field if Advanced Currency Management is enabled.

Why not others:

A is not the stated Salesforce limitation.

C is wrong because roll-up summary fields are available on Account in supported scenarios.

D is wrong because currency fields can be used in roll-up summaries generally; the issue is specifically Advanced Currency Management with Account-to-Opportunity currency rollups.

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 D. Flow.

The requirement is to automatically clear the Phone field on Contact when the Do Not Call checkbox is checked. A record-triggered Flow can run when a Contact is created or updated, check whether Do_Not_Call is true, and then update the triggering Contact record by setting the Phone field to blank. Salesforce Flow supports updating records, including directly updating the record that triggered the flow.

B. Validation rule is incorrect because it can block a save but cannot delete or clear the Phone field automatically.

C. Quick action is manual, not automatic.

A. If-then rule is not the best current Salesforce automation tool for this requirement.

===========

The correct answer is C.

A Partial Copy sandbox uses a sandbox template to determine which objects and data are copied from production. Salesforce states that sandbox templates let admins select specific objects and data to copy to a Full or Partial Copy sandbox. If the custom object Shipping was not included in the sandbox template, its production records would not be copied into the refreshed partial sandbox.

Why others are incorrect:

A is not the likely issue; refresh timing does not explain one object having no data.

B is less likely as the scenario points to template selection.

D is not the best answer because capacity may limit copied data, but missing all data for a specific object usually indicates the object was not selected in the sandbox template.

===========

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 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.

===========

For an unmanaged package, Salesforce documentation states that the developer who created and uploaded the package has no control over installed components and can’t change or upgrade them after installation.

Therefore, an unmanaged package does not follow the normal managed-package upgrade path. To get a newer version, the practical process is to remove the installed unmanaged package and install the newer version.

Why others are incorrect:

B and D describe managed/update-style behavior, not unmanaged package behavior.

C is not the package upgrade process itself; it describes a deployment workaround, not upgrading the installed unmanaged package.

===========

The correct answer is A. Import Wizard.

Cloud Kicks needs to insert 25,000 records and use deduplication for a custom object. Salesforce Trailhead states that the Data Import Wizard can import data into custom objects and supports up to 50,000 records at a time, so 25,000 records fits within the Import Wizard limit.

Salesforce Help also states that the Data Import Wizard prevents duplicate custom object records by matching records against fields such as the custom object name or Salesforce ID.

B. Data Loader is not the best answer because Data Loader is better for larger or automated loads, but this question specifically requires deduplication and only 25,000 records. C. Lightning Object Creator creates objects from spreadsheets; it is not the correct deduplication import tool. D. Schema Builder is for creating and viewing data models, not importing records.

===========

The correct answer is B, based on the intended Salesforce wording.

In a private data model, users normally access records they own or records shared with them. Salesforce role hierarchy opens record access upward: users higher in the hierarchy can view, edit, and report on records owned by users below them, depending on object permissions and hierarchy settings.

Because the Service Coordinator needs access to work orders and related records owned by technicians, placing the SC above the technicians in the role hierarchy gives the required record access without granting excessive org-wide permissions.

Why others are incorrect:

Modify All Data is too broad.

Modify All on Work Order only applies to that object and does not solve access to other related technician-owned records.

Workflow does not grant record access.

===========

The correct answer is A. Existing reports created under the Sun__c with Planet__c report type made by Salesforce will be unusable, but not deleted.

When a relationship is changed from master-detail to lookup, the available standard report types can change. Salesforce documentation notes that converting a lookup relationship to master-detail or vice versa can make existing custom reports unusable because of differences in available standard report types.

B is incorrect because roll-up summary fields are not automatically deleted from reports as part of the conversion. In fact, Salesforce states that a master-detail relationship cannot be converted to lookup while roll-up summary fields exist on the master object.

C is incorrect because roll-up summary fields do not remain and simply stop updating.

D is incorrect because the reports are not deleted; they become unusable.

===========

The correct place to verify whether a change set can be deployed is Inbound Change Sets in the target org, normally Production.

Salesforce guidance says that after uploading a change set from the source sandbox, the app builder goes to Setup → Inbound Change Sets, opens the change set awaiting deployment, and clicks Validate. Validation checks whether the deployment succeeds or fails before committing the changes.

A. Deployment Settings is mainly used to authorize deployment connections and allow inbound changes from another org. C. Deployment Status is used to monitor deployment progress/results, not to initiate validation of an inbound change set.

The correct answer is A. Path.

Salesforce Path is designed to guide users through different stages of a business process. It can show key fields and provide Guidance for Success at each step, which matches the manager’s requirement to give new sales reps help during different sales processes.

B. Chatter Publisher is for collaboration posts, not guided sales-process help.

C. Journey Builder is a Marketing Cloud tool, not the standard Sales Cloud guidance feature.

D. Flow can automate steps, but Path is the best UI guidance tool for this requirement.

===========

The correct answers are A. Tabular format and B. Summary format.

Salesforce reporting snapshots can use custom tabular or summary reports as the source report. Salesforce documentation specifically states that a reporting snapshot source report can be tabular or summary.

Why others are incorrect:

C. Joined format is not supported as a reporting snapshot source report.

D. Matrix format is not supported because matrix reports group by rows and columns, and Salesforce troubleshooting guidance states that matrix reports can’t be used with reporting snapshots.

===========

The correct answers are A. Dynamic Actions and C. Approval Process.

An Approval Process is required because sales managers must provide formal sign off when an Opportunity discount meets the defined criteria. Salesforce approval processes define the criteria a record must meet, the steps required for approval, and who must approve it.

Dynamic Actions are also needed because Universal Containers wants the sign-off action available quickly from the Opportunity record page. Dynamic Actions let app builders control which actions appear on Lightning record pages based on conditions.

Why others are incorrect:

Schema Builder is for data model design, not approval/sign-off UI behavior.

Validation Rule can block invalid data, but it does not provide manager approval or sign-off.

===========

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 C. Data Export Service.

Salesforce Data Export Service is the native tool used to export backup data from a Salesforce org. It allows admins to create export files of Salesforce data and schedule exports. Salesforce documentation describes Data Export as the feature for exporting backup data from Salesforce.

Important exam note: the question says “daily backup,” but standard Salesforce Data Export scheduling is commonly weekly or monthly depending on edition and settings. Among the listed options, Data Export Service is still the correct Platform App Builder answer.

A is incorrect because refreshing a Full Copy sandbox is not a backup strategy.

B is incorrect because packages move metadata, not org data backup.

D is incorrect because “Support expert” is not the Salesforce backup/export tool.

===========

The correct answer is D. Approval process.

The requirement is to automate travel request form submission and enforce an internal approval policy. Salesforce approval processes are specifically designed to automate how records are submitted, reviewed, approved, rejected, recalled, and acted upon. Salesforce Trailhead explains that an approval process defines the criteria a record must meet before submission, the approval steps, approvers, and the actions taken when the record is approved or rejected.

This exact scenario also aligns with Salesforce’s travel approval training example, where a Travel Approval object uses an approval process to route travel requests to the employee’s manager and, when needed, to another approver.

A is incorrect because assignment rules route leads or cases, not approval requests.

B is incorrect because validation rules prevent invalid saves but do not manage approval routing.

C is incorrect because Apex is unnecessary when a standard declarative approval process fits the requirement.

===========

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 C. Research and evaluate data enrichment products on the AppExchange to automate data entry.

The sales manager wants reps to spend less time manually entering business-card information while maintaining data quality. Salesforce AppExchange is the correct place to evaluate packaged solutions that extend Salesforce functionality. Trailhead describes AppExchange as a place to find solutions for business needs, and AppExchange contains business-card scanning apps that can create or match Salesforce Leads, Contacts, and Accounts with reduced manual entry.

A does not automate data entry.

B is not the best fit because Flow cannot read business cards by itself.

D is incorrect because formula fields calculate values from existing data; they do not capture business-card information.

===========

The correct answers are A. Data loss may occur when changing custom field types and D. Field History Tracking records value changes of 255 characters or less.

A is correct because Salesforce warns that changing the data type of an existing custom field can cause data loss in certain situations. This is a key consideration before converting Text Area (Long) fields to Rich Text Area fields.

D is correct because Salesforce field history tracking has a character limitation. Salesforce tracks changes to fields with more than 255 characters as edited, but it does not record the old and new values. That means long/rich text changes beyond that limit do not provide full before-and-after history values.

Why others are incorrect:

B is not the relevant consideration for this field conversion requirement.

C is incorrect because Salesforce reports do not display rich text field values of all lengths fully; Salesforce documentation notes report display limits for long text and rich text area fields.

===========

The correct answer is B. Data is unable to be deployed with change sets.

Change sets deploy metadata/configuration, not business data. Salesforce documentation states that change sets can contain setup modifications, but they cannot be used to upload a list of records such as contacts.

So the report itself can be deployed, but the underlying records needed for the report results are not deployed through the change set. If the Partial Copy sandbox does not contain matching sample data, the report returns no data.

Why others are incorrect:

Data is not deployed just because it is added to a change set.

Reports do not have to be manually recreated if they are deployed properly.

“Salesforce OK” is not a deployment requirement.

===========

Use a Roll-Up Summary field on Account to count the related Opportunity records. Salesforce roll-up summary fields can calculate values from related records, and the COUNT summary type totals the number of related records. Trailhead also gives the Account and Opportunity example for roll-up summaries.

A formula field cannot count child records by itself. A lookup field only creates a relationship. AppExchange is unnecessary for this standard use case.

===========

The correct answers are B. AppExchange and D. Lightning Components.

Salesforce Trailhead states that custom Lightning components can be created with Lightning Web Components or Aura, and existing Lightning components can also be installed from the AppExchange. Custom components configured for Lightning App Builder appear in the Lightning Components pane and can be added to Lightning pages.

Why others are incorrect:

A. Import Wizard is a data import tool, not a source of UI components.

C. Apex Code provides server-side logic, but Apex itself is not a Lightning page component resource.

===========

The lookup field is created on the custom object Box and points to Account. That makes Account the parent-side object and Box the related child object. Salesforce automatically creates a standard relationship report type in the format Parent Object with Child Object, so the report type is Accounts with Boxes. Salesforce Help confirms that standard report types can be generated automatically when reportable custom objects have lookup relationships.

Why others are incorrect:

A. Boxes with Accounts starts from the child object perspective.

C and D include “with or without,” which is normally configured through custom report type relationship options, not the automatically created standard relationship report type.

===========

The correct answer is C. A delegated approver is the recommended Salesforce feature when the assigned approver is unavailable, such as during vacation. Salesforce documentation confirms that users can identify a delegate in approval settings, and delegated approvers can approve or reject approval requests.

This ensures the closed-won Opportunity can still be reviewed before the leaderboard is updated, even though the owner’s manager is away.

Why others are incorrect:

A is not the best recommended setup because relying on an assistant to reassign requests is manual and reactive.

B is incorrect because forwarding approval requests is not the standard solution for planned approver absence.

D is incorrect because assignment rules do not assign delegated approvers for approval processes.

===========

The correct answer is B. Create a unique External ID field and use Data Loader.

Cloud Kicks is receiving shipment data from an external shipping system on a regular basis. To prevent duplicate Delivery records and update the correct existing records, the app builder should create a field such as Tracking Number on Delivery__c , mark it as External ID and Unique, then use Data Loader Upsert.

Salesforce documentation states that external IDs can be used when importing custom objects to prevent duplicate records. Salesforce Data Loader documentation also states that upsert combines insert and update: if a matching record exists, it updates it; otherwise, it creates a new record.

A is less appropriate because this is a recurring system migration/update scenario, and Data Loader with External ID is the stronger tool.

C is incomplete because matching only on Salesforce ID requires the external system to already store Salesforce record IDs.

D may help detect duplicates, but duplicate/matching rules do not provide the clean upsert mechanism needed to update the correct existing record.

===========