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

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.

===========

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 A. Build an approval process that requires unanimous approval from the manager and VP of Sales and D. Create a flow that submits the record for an approval process.

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

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

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

Why others are incorrect:

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

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

===========

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

===========

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. Use a roll-up summary field on the Park record and C. Use a master-detail relationship between the Park and Trail objects.

Northern Trail Outfitters wants the total number of Trails displayed on the Park record without code. In Salesforce, a standard roll-up summary field can count related child records, but it requires a master-detail relationship between the parent and child objects. Salesforce documentation confirms that roll-up summary fields calculate values from related records, and this is the correct declarative feature for this requirement.

A is incorrect because a formula field cannot count child records. D is incorrect because standard roll-up summary fields do not work on ordinary lookup relationships.

===========

The correct answers are A. Streams and D. Out of Office.

Streams allow users to combine multiple Chatter feeds into one custom feed, making it easier to monitor updates from important people, records, and groups. This directly solves the issue of gathering feed updates from core team members. Salesforce documentation describes Chatter streams as custom feeds created by combining multiple related feeds into one feed.

Out of Office helps team members understand who is available to respond. Salesforce documentation explains that users can schedule and customize an out-of-office message and display it next to their name in Chatter.

Why the other options are incorrect:

Topics help categorize Chatter content but do not directly gather core-team feeds or show availability.

Polls are useful for collecting opinions, but they do not solve feed monitoring or availability visibility.

===========

AW Computing wants to grant access to all users in the Service Manager role for Opportunities of type Service Agreement in a private sharing model.

Criteria-based sharing rules allow sharing records automatically based on field values (e.g., Type = Service Agreement) to roles, public groups, or users.

Salesforce documentation confirms that when the org-wide default is private, sharing rules are the declarative way to grant access to specific users based on criteria. (Salesforce Help)

Owner-based sharing rules share based on the record owner, not a field criterion.

Apex sharing rules are needed only if declarative sharing is insufficient.

Manual sharing requires user action and is not scalable.

===========

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 answers are A. Assign app to profiles and B. Build a Custom Tab for the app.

Your option A appears corrupted as “Asking new options,” but the known Salesforce wording for this question is Assign app to profiles.

To make a custom Lightning app available to internal users, users must have access to the app through profile/app assignment. Salesforce documentation explains that assigned app settings specify which apps users can select from the Lightning Platform app menu.

A Custom Tab is also needed when exposing the custom app/component as something users can access from the Salesforce UI. Salesforce documentation states that custom tabs can appear in the app navigation bar and App Launcher.

Adding the app to a Visualforce page is not required, and uploading it to Static Resources is not how Lightning apps are made available to users.

===========

The correct answer is B. Apex unit test failures.

When installing a package that contains Apex in a production org, Salesforce runs Apex tests as part of the installation/deployment validation. Salesforce documentation states that package installs or upgrades can fail when Apex test requirements are not met.

Even though the unmanaged package was tested in a Full Copy sandbox, production installation can still fail if Apex tests fail during production validation.

Why others are incorrect:

A, C, and D are not the best answer because the package already installed successfully in a Full Copy sandbox that matched production. The most certification-relevant reason for production failure is Apex unit test failure.

===========

The correct answer is A. AppExchange.

For a Salesforce Classic-to-Lightning Experience migration, the app builder should look for prebuilt apps, components, adoption tools, and consultant solutions on AppExchange. Salesforce now refers to this marketplace as AgentExchange in newer Trailhead content, but the exam op tion “AppExchange” is still the intended answer. Salesforce describes it as the marketplace for Salesforce solutions, including apps, agents, components, and more, and specifically notes that admins can look there instead of building everything from scratch.

Flow Builder is for automation, Lightning Object Creator is for creating objects from spreadsheets, and Import Wizard is for importing data. They are not marketplaces for prebuilt adoption or migration resources.

===========

The correct answer is D. Create an Apex Trigger on the Account object.

The requirement is conditional: allow Account deletion generally, but block deletion when the Account has open Opportunities. A validation rule is not the correct tool because validation rules evaluate record data during save operations, while this requirement is specifically about preventing a delete operation.

An Apex before delete trigger can query related open Opportunities and call addError() on the Account record to stop the delete. Salesforce Apex documentation confirms that triggers can run before or after delete events, and trigger errors can prevent DML operations from completing.

A is incorrect because removing Delete permission blocks all Account deletion.

B is incorrect because removing the Delete button is not security and does not stop deletion through other channels.

C is incorrect because validation rules are not the right mechanism to block conditional deletes.

===========

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

The approval request must go to department members who can approve overnight shipments. In Salesforce approval processes, routing an approval to a queue is appropriate when a group of users can own or act on the approval request and any one of the queue members can handle it. Salesforce approval documentation describes approval processes as automation that specifies each approval step, including who receives the approval request.

A queue is better than a role or hierarchy field when the request needs to be handled by a department group rather than a single manager or a specific user from a hierarchy field.

A. Role is less appropriate because roles are for hierarchy-based access and routing.

C. Hierarchy field is used when routing to a user identified through a manager-style field.

D. Public group is used for sharing and grouping users, but approval queues are the standard routing choice for a group of approvers in this scenario.

===========

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 answers are A. Use a master-detail relationship between the Park and Trail objects and C. Use a roll-up summary field on the Park record to show the total number of trails .

To show the total number of child Trail records on the parent Park record without code, the app builder should use a roll-up summary field . Salesforce documentation states that roll-up summary fields display values on a master record based on related detail records.

That means Park should be the master object and Trail should be the detail object. Then a roll-up summary field on Park can count the related Trail records.

B is incorrect because standard lookup relationships do not support roll-up summary fields.

D is incorrect because a formula field cannot count multiple child records.

===========

The correct answer is D.

Validation rules are the right declarative tool to enforce data compliance before a record is saved. They can prevent a Case from moving backward to an earlier Status and can require specific fields when Case criteria are met. Salesforce formula functions such as ISCHANGED() compare whether a field value changed, and validation rules can use formula logic to stop invalid saves.

Why others are incorrect:

Approval Process is for routing records for approval.

Dependent picklists control picklist value availability, not status regression.

Case Flow can automate case processes, but validation rules are the best tool for enforcing save-time compliance.

===========

\

The correct answer is B. Use field-level security on page layouts with record types to restrict editing fields.

The requirement changes after the Opportunity is closed. The best configuration is to use record types with assigned page layouts so the closed Opportunity layout can make most fields read-only while allowing the Sales Operations team to edit the two post-close fields. Salesforce page layouts can control which fields are visible, read-only, or required, and page layouts can be assigned by profile and record type.

A is incomplete because it does not account for different behavior after close. C is incorrect because field sets are not used for page-layout field editability. D is too broad because it would make fields read-only for the Sales profile regardless of Opportunity stage.

The correct answer is D. Create a new text field and import the formula field values in it.

The existing Specialty__c field is a formula field, so users cannot manually edit it. Formula fields calculate their value automatically from other fields. Since Cloud Kicks now wants Opportunity Specialty__c values to be different from the related Account value, the app builder should create a new editable field, such as a Text field, and then load the existing calculated formula values into that new field for existing Opportunity records.

This preserves historical Opportunity values while allowing sales reps to enter or update Specialty values going forward. Salesforce documentation explains that roll-up/formula-style calculated values are system-derived, while changing custom field types has limitations and requires care when data must be preserved.

A and B are incorrect because a formula field cannot simply become an editable text field while safely preserving all existing calculated values.

C is incomplete because creating a new text field without importing the existing formula values does not preserve the current values on existing Opportunities.

===========

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 correct answer is B. Field-level security.

Only users with the Outer Planets profile need to see the Jupiter field. Salesforce field-level security, also called field permissions, controls whether users can view or edit individual fields on an object. This is the proper way to restrict a field by profile or permission set.

Sharing rules control record-level access, not field visibility. Filtered views affect list views, not field security. Classic encryption protects sensitive data but is not the correct feature for profile-based field visibility.

===========

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

A junction object is commonly created with two master-detail relationships. 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 on the relationship fields.

Here, Account Interest is the junction object between Account and Interest. If users do not have read access to the Interest object, they cannot view the Interest records. Because access to the junction object depends on access to both master records, they also cannot view the associated Account Interest records.

Why not others:

A is wrong because lack of read access to Interest does not give read-only access automatically.

B is wrong because the user can still view the Account if they have Account access.

D is wrong because junction object access is not simply “show junction but hide Interest details.”

===========

The correct answers are A and B .

The requirement is to display a visual flag image based on Case Priority. Salesforce’s own sample image formula for Case Priority uses the IMAGE() function with CASE() to display green, yellow, or red flag images.

Both formulas are valid because:

A uses IMAGE() with nested IF() and ISPICKVAL() checks.

B uses IMAGE() with CASE() to return the correct image URL.

C and D are incorrect because they return only the image URL text, not the actual image. The formula must use IMAGE() to display a visual flag.

===========

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 because the requirement is to keep one specific field, the Comment field, private from users outside HR. Salesforce field-level security is the correct security layer for controlling whether users can view or edit a field. Salesforce documentation states that field-level security restricts user access to fields and overrides page-layout visibility.

A page layout alone is not enough because page layouts control UI presentation, not full field security. Salesforce also notes that to ensure users cannot access a field, field permissions should be used because other settings do not provide the same field-level protection.

Why others are incorrect:

B and D are wrong because sharing rules and Apex sharing control record access, not individual field access.

C is wrong because removing a field from a page layout only hides it from that layout; it does not securely prevent access through reports, API, related lists, or other interfaces.

===========

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 answer is D. Choose an unmanaged package from AppExchange that closely meets the requirements of the project and allows programmatic development.

The requirement has two key parts: the app builder has very little time, and the solution must be fully customizable. Salesforce documentation describes unmanaged packages as suitable for one-time drops of applications that require customization after installation. That fits this scenario better than building everything from scratch.

C is incorrect because managed packages are better for distributed, upgradeable AppExchange apps, but they can restrict subscriber changes to packaged components. The question specifically says the solution still needs full customization, which points to an unmanaged package.

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 answer is B. The Allow reparenting checkbox, Child records can be reparented to other parent records after they are created, is unchecked.

A service plan must be associated with one Contact, and users cannot change the Contact after the service plan is created. Since field access and validation rules are not the issue, the likely cause is a master-detail relationship where Allow reparenting is not enabled.

Salesforce documentation states that in master-detail relationships on custom objects, administrators can allow child records to be reparented by selecting Allow reparenting. If that option is not selected, users cannot change the parent record after the child record is created.

A and C relate to master-detail sharing settings, not changing the parent record. D is the opposite of the problem; if Allow reparenting were checked, users could change the parent Contact.

===========

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

The correct answer is A. Sandbox cloning.

Cloud Kicks needs many parallel sandboxes that start from the same base configuration and data. Sandbox cloning is designed for this because Salesforce copies the source sandbox’s data and metadata into a new sandbox. Salesforce documentation states that cloning a sandbox copies its data and metadata into the new sandbox.

Partial copy and full copy are sandbox types, not the best mechanism for repeatedly creating many sandboxes from the same prepared baseline. Sandbox refreshes update existing sandboxes; they do not create at least 20 parallel environments from the same baseline.

===========

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 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 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 answers are A. Flow Launcher and D. Quick Action.

A flow can be exposed to users through a page-based launcher/component. Salesforce Trailhead explains that users can access a flow by adding it to a Lightning page through Lightning App Builder. The Flow component can be dragged onto the Lightning page so users can run the flow from that page.

A Quick Action can also launch a flow. Salesforce documentation states that quick actions help users launch and navigate through workflows, and Trailhead confirms that custom actions can invoke flows.

Why others are incorrect:

B. Apex can invoke automation programmatically, but it is not the best user-facing access feature in this question.

C. Approval Process routes records for approval; it is not a general method for users to access flows.

===========

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

===========

The correct answers are A. Create a custom-based sharing rule and B. Update the organization-wide defaults.

Here, “custom-based” is most likely referring to a criteria-based sharing rule. UC wants to move from public sharing to a more restrictive model, so the app builder must first update the Organization-Wide Defaults for Accounts. Salesforce OWDs define the default access users have to records they do not own.

Then, to continue giving the Sales team access to all Account records with the Sales record type, the app builder should create a criteria-based sharing rule based on record criteria, such as Record Type. Salesforce criteria-based sharing rules share records based on field values.

C is incorrect because profiles control object permissions, not record-level sharing by record type.

D is incorrect because owner-based sharing rules share records based on record owner, not record type.

===========

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

The app builder needs automation to run when a child record is deleted and then update a field on the related parent record. Salesforce states that a record-triggered flow can automatically perform actions when a record is created, updated, or deleted, without user interaction.

Autolaunched flow can perform logic, but it does not run automatically on record deletion unless invoked by another automation. Validation rule only prevents invalid data entry. Quick action requires user interaction and is not suitable for automatic updates after deletion.

===========

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 answers are A. Task, B. Email Alert, and D. Outbound Message.

In a Salesforce approval process, automated actions can be configured when a record is submitted, approved, rejected, or recalled. Salesforce approval process setup supports workflow action types such as tasks, email alerts, field updates, and outbound messages.

C. Invocable Flow is not one of the classic approval-process action types in this exam context. E. Decision Element is a Flow element, not an approval-process action.

===========

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.

===========

The correct answers are A. Lightning App Builder and D. Quick Action.

A Lightning component can be exposed for use in Salesforce pages through supported targets such as App Page, Home Page, and Record Page, which are configured through Lightning App Builder. Salesforce developer documentation also confirms that components can be configured as quick actions using targets such as lightning__RecordAction or lightning__GlobalAction .

C. Validation Rule is incorrect because validation rules are business logic formulas, not places where Lightning components are placed or rendered. B. Time Failure is not a valid Salesforce area for using Lightning components based on the given option wording.

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 C. Configure Campaign Hierarchies and Campaign statistics.

To understand return on investment for an advertising buy, Universal Containers should use Salesforce Campaigns, especially Campaign Hierarchies and campaign reporting/statistics. Salesforce campaign hierarchy documentation explains that child campaign metrics roll up to the parent campaign, and Salesforce campaign reports can include campaign-hierarchy statistics for aggregate values.

The private security model does not require changing the whole org to public. The business need is marketing ROI tracking, so Campaigns are the correct feature.

A is incorrect because an opportunity pipeline report does not directly track advertising campaign ROI.

B is incorrect because Account Hierarchies and roll-up summaries are not the standard solution for campaign ROI.

D is incorrect because changing to a public security model is unnecessary and weakens data security.

===========

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

The correct answer is A. The report type is already based on Opportunities with or without Shipments, so the app builder should not change the report type’s primary object. To expose Account Rating, the app builder should edit the custom report type layout and use Add fields related via lookup from the Opportunity view, because Opportunity has a relationship to Account. Salesforce documentation confirms that custom report types allow fields from objects not directly included in the report type structure by using Add fields related via lookup.

Why others are incorrect:

B is incorrect because the standard Account–Opportunity relationship cannot simply be changed to master-detail.

C is incorrect because changing the primary object to Account would change the report purpose.

D is incorrect because adding a field to a record page does not make it available in a report type.

===========

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 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 correct answer is A. Page structure will automatically adapt to the device being used to view the record page.

When choosing a Lightning record page template, the app builder should consider how the template displays across supported devices. Salesforce Lightning pages are designed for Lightning Experience and the Salesforce mobile app, and Salesforce documentation states that the chosen template controls how the page displays across devices.

B is incorrect because users do not need “View All Data” just to view a Lightning record page; normal object and record access applies.

C is incorrect because Salesforce supports switching Lightning page templates, subject to template-switching considerations.

D is incorrect because the app builder does not create a separate template for every device type.

===========

The correct answer is B.

Universal Containers needs the 18-digit Salesforce record ID for Opportunity records when exporting to Excel. Salesforce’s CASESAFEID() formula function converts a 15-character Salesforce ID into the 18-character, case-insensitive ID format that works better with external tools such as Excel. Salesforce documentation specifically describes CASESAFEID as the function used to convert IDs to 18-character IDs for Excel compatibility.

Correct formula:

CASESAFEID(Id)

A. VALUE(14) is unrelated. C. TEXT(Id) does not convert the ID to the 18-character case-safe format. D. ISNUMBER(Id) only checks whether a value is numeric, which is not useful for Salesforce record IDs.

===========

The correct answer is D. Partial Copy sandbox.

A Partial Copy sandbox is designed for testing and UAT when users need a subset of production data. Salesforce states that Partial Copy sandboxes include metadata plus a subset of production data via sandbox template, support 5 GB data storage, and have a 5-day refresh interval, which satisfies a weekly refresh requirement.

A. Full sandbox is incorrect because it copies all production data and has a longer refresh interval.

B/C. Developer or Developer Pro are incorrect because they do not copy production data through a template in the same way required for this UAT scenario.

========

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

To show Chatter on a custom object Lightning record page, the app builder should use the standard Chatter Feed / Chatter component in Lightning App Builder. Salesforce documentation describes adding Chatter components such as Chatter Feed, Chatter Publisher, and Chatter to Lightning record pages, usually after feed tracking is enabled for the object.

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

C and D are incorrect because a custom component or AppExchange component is not required for standard Chatter feed functionality.

===========

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.

===========

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.

===========

The correct action is to validate the inbound change set in Production before the deployment window. Salesforce states that an inbound change set can be validated without deploying changes, and validation shows the same success or failure messages that would occur during an actual deployment.

This helps the app builder confirm whether Apex tests, dependencies, and deployment requirements will pass while the developer is away.

Why not others:

A is wrong because removing Apex classes would remove required code.

B is wrong because deployment validation is done from the inbound change set in the target org.

C is not the standard change-set validation process.

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 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 answers are A. Review the Contact record and ensure it is linked to an Account, C. Verify the users with the issue have access to the Contact object, and E. Confirm whether Default Organization-Wide Sharing Settings provide access to the Account.

A Contact that is not linked to an Account is treated as a private contact. Salesforce states that contacts without an account are private regardless of the sharing model, so checking whether the Contact is associated with an Account is a valid troubleshooting step.

Users also need object-level access to the Contact object. Object permissions control whether users have base-level access such as read, create, edit, and delete for an object.

Finally, Contact visibility is often affected by Account access, especially when Contact sharing is controlled by the parent Account. Organization-Wide Defaults define the default record access users have for records they do not own, so checking the Account OWD is also correct.

B is incorrect because creating a new Contact does not troubleshoot the actual sharing/security issue.

D is incorrect because creating a broad Account Sharing Rule for all records is not the first troubleshooting step and may overexpose data.

===========

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 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 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 C. AppExchange package.

The key word is daily. Salesforce’s native Data Export Service supports manual and scheduled exports, but Salesforce documentation states that backup files can be generated manually once every 7 days for weekly export or 29 days for monthly export, depending on edition. That does not meet an automatic daily backup requirement.

For daily automated backups, the app builder should recommend a backup solution from AppExchange. Report export is not an org backup, and refreshing a full copy sandbox is not a backup automation tool.

===========

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.

===========