Platform-App-Builder Questions and Answers

The correct answer is B.

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

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

===========

The correct answer is B. Quick action.

Sales reps need to create Opportunity records directly from an Account, with several fields prepopulated. This is an object-specific Quick Action use case. Salesforce states that object-specific actions let users create or update records in the context of a particular object. Salesforce also supports predefined field values for quick actions, which can prepopulate fields and make record creation faster.

Default action is not the correct feature name for this requirement. Custom button and custom link are older navigation-style tools and are not the best Lightning/mobile-friendly option for creating related records with predefined values.

===========

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 B. Roles and Subordinates, C. Public Groups, and D. Users / Individual Users.

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

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

So, based on your option wording:

B appears to mean Roles and Subordinates.

C is Public Groups.

D appears to mean Users / Individual Users.

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

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

===========

The correct answers are C. Custom object, D. Apex class, and E. Custom field.

Change sets are used to move metadata between related Salesforce environments, such as sandbox and production. Salesforce documentation confirms that change sets can migrate components such as custom objects, custom fields, and Apex classes. Salesforce also notes that custom fields can be migrated individually in a change set.

A. Web-to-lead is not one of the common metadata components normally selected as an item in this exam context. B. Standard fields are standard Salesforce metadata and are not moved like custom fields in change sets.

===========

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

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

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

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

===========

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 answers are B. Assign the page to a combination of apps and profiles, C. Make the page the default homepage for specific apps, and E. Make the page the org default.

When activating Lightning pages, Salesforce supports assigning a page as an org default, assigning it to specific Lightning apps, and assigning it to combinations such as app and profile. Salesforce Trailhead also confirms that Lightning record page activation supports org default, app default, and app/record type/profile assignments.

A is incorrect because Lightning page activation uses profiles, not permission sets, for this assignment model.

D is incorrect because Lightning pages are not activated by role as a standard activation option.

===========

The correct tool is Data Loader.

Cloud Kicks needs to insert over 1 million net new Account records. Salesforce Data Loader is the correct tool for large-volume imports because it supports bulk insert, update, delete, and export operations. Salesforce’s Data Loader documentation describes it as a client application for bulk data import and export, including inserting Salesforce records. Salesforce also distinguishes it from the Data Import Wizard, which is limited to smaller imports.

Why the other options are wrong:

Data Import Wizard is not suitable for over 1 million records because it is intended for much smaller imports. Schema Builder is for viewing and creating data model components, not loading a million records. Lightning Object Creator creates objects from spreadsheets, not mass-inserting large Account datasets into an existing model.

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.

===========

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

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

Why others are incorrect:

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

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

Feed quick action is manual, not automatic.

===========

The correct 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 B. The deployed permission set will only contain changes related to the change set.

When permission sets are included in change sets, the deployment carries permission settings related to the components included in the change set. The existing permission set in production is not completely overwritten as a whole object, and field-level security changes can be included when the relevant fields are part of the deployment. Salesforce documents permission sets and profile settings as access settings that can be included with change sets.

A is incorrect because the whole permission set is not simply wiped and replaced.

C is incorrect because field-level security can be deployed when included properly.

D is close in plain language, but the more accurate exam answer is that the deployed permission set contains only changes related to the change set.

===========

The required metric is the total monetary value of won Opportunities for each Account. Salesforce supports roll-up summary fields on Account that aggregate Opportunity Amount and apply filtering criteria so that only qualifying child records are included. The appropriate configuration therefore uses SUM on Opportunity Amount with a filter restricting the calculation to Opportunities whose Stage represents Closed Won. Option C would incorrectly include open and lost Opportunities. COUNT-based options calculate the number of records rather than total sales value, and the roll-up belongs on the Account because that is where the summarized result must appear. Salesforce ' s current documentation specifically gives the example of an Account roll-up displaying total Opportunity amount and filtering the aggregation to only won Opportunities.

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

Quick Deploy is designed precisely to reduce production deployment duration after a deployment has already been successfully validated. The app builder should upload the change set before the cutover window and perform a Validate Only deployment against production with the necessary Apex tests. If validation succeeds, tests pass, and code coverage requirements are met, Salesforce allows the validated deployment to be Quick Deployed within the permitted validation window without rerunning the complete Apex test suite. Salesforce currently states that successful validations qualifying for Quick Deploy remain eligible for up to 10 days. Simply uploading a change set in advance does not avoid running tests during the actual deployment. Therefore, pre-validating and using Quick Deploy at cutover provides the smallest production deployment window. Salesforce

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

The correct answer is C. Internal profiles.

When an app builder creates a custom field using Schema Builder, Salesforce sets field-level security for custom fields to visible and editable for internal profiles by default.

That is why B. All profiles is not the best answer. Salesforce’s documented default is specifically internal profiles, not every possible profile type.

===========

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

The requirement is automatic: when an Account Type changes to Past-Customer, all directly related Contacts must have their Status updated to Re-Market. A record-triggered flow is the correct declarative automation because it can run when an Account record is updated and then update related Contact records. Salesforce describes record-triggered flows as automation that runs automatically when records are created, updated, or deleted. Salesforce also documents that Flow can update records related to the record that triggered the flow.

Validation rules only prevent invalid saves. Lightning components are UI elements. Screen flows require user interaction, while this requirement needs background automation.

===========

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.

===========

To display Component records as children in a related list on Product, the relationship field must be created on the Component object and point to Product. A lookup relationship provides exactly this parent-child association while allowing the records to remain independently managed. Salesforce explains that a lookup field on a child object relates it to a parent record and that users viewing the parent can then see the child records through a related list. After creating the lookup from Component to Product, the app builder adds the Component related list to the Product page layout. A junction object is unnecessary because the requirement does not describe a many-to-many relationship. Option C places the relationship in the wrong direction, while a roll-up field does not create a relationship or related list. Salesforce

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

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 answers are A. Enable Feed Tracking on Opportunities and D. Use a record-triggered flow on Opportunity and a Chatter post action.

Feed Tracking is the correct configuration to track field changes on the Opportunity record feed. Salesforce states that feed tracking detects changes to tracked record fields and posts updates to the feed for users who follow the record. Salesforce also allows admins to enable feed tracking for an object and select tracked fields.

A record-triggered flow with a Chatter post action handles the automatic notification requirement. The flow can detect when the Opportunity Close Date changes and post to Chatter, such as mentioning the sales manager or a manager group. Salesforce supports posting to a record’s Chatter feed through automation when feed tracking is enabled.

B is incorrect because an outbound message sends data to an external endpoint, not a manager notification on the Opportunity. C is incorrect because Historical Trending is mainly for reporting on changes over time, not automatic manager notification on the record.

The correct answer is D.

Salesforce allows converting a master-detail relationship to a lookup relationship only when there are no roll-up summary fields on the master object that summarize the detail records. Salesforce documentation states that after a roll-up summary field exists on an object, the object’s master-detail relationship can’t be converted into a lookup relationship.

In this case, if Account has roll-up summary fields based on related Park records, Salesforce blocks the conversion.

A is incorrect because a flow using Account does not normally prevent converting the relationship. B is incorrect because formulas on Park referencing Account are not the primary restriction. C is incorrect because custom objects do not need at least one master-detail relationship for reporting.

===========

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

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

Current Salesforce functionality makes D. Dynamic Forms the appropriate declarative answer. Lightning App Builder supports visibility rules on Dynamic Forms Field and Field Section components, and Salesforce specifically documents device-based visibility through the Device context. An app builder can therefore configure a section to appear for the required form factor, such as phone or desktop, without developing a custom Lightning Web Component. Record Types determine business processes, picklist availability, and layout assignments; they are not device-detection mechanisms. Traditional Page Layouts likewise do not provide device-specific section visibility. A custom LWC could implement custom form-factor behavior programmatically, but it is unnecessary when Dynamic Forms provides native declarative visibility controls.

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

The correct answer is A. Quick Action on the Account object.

Universal Containers wants users to create Opportunity records related to an Account, with many Opportunity fields automatically populated from the Account and some fields entered by the user. The best solution is an object-specific Quick Action on Account that creates an Opportunity. Object-specific actions run in the context of the parent record, and predefined field values can automatically populate fields to make record creation faster and more consistent.

C is incorrect because a Quick Action on Opportunity would not naturally start from the Account context. B and D are incorrect because assignment rules are not used for creating related Opportunities or prepopulating fields.

===========

The correct answer is A.

UC has three Lead sources: web, trade shows, and partners. Some Lead information is common to all, while other fields are unique to each source. The best configuration is to use Lead record types with separate page layouts so each type of Lead shows the fields relevant to that process. Salesforce documentation states that record types allow different business processes, picklist values, and page layouts for different users or record categories.

B is not ideal because it leaves irrelevant fields visible and relies on users to collapse sections. C unnecessarily creates a different Lead object for the partner community. D is incorrect because separate custom objects would fragment Lead management and prevent standard Lead functionality from being used consistently.

===========

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 C. Custom object with Master-detail field to Opportunity.

AW Computing needs many help requests related to one Opportunity, so the help request should be a custom child object under Opportunity. Because the Opportunity page must show the most recent request date, the app builder needs a Roll-Up Summary field on Opportunity using MAX on the request date field.

Salesforce roll-up summary fields work on the master side of a master-detail relationship, and MAX can be used for date/date-time fields.

A is backward because the master-detail field belongs on the child object, not Opportunity.

B and D use lookup relationships, which do not support standard roll-up summary fields.

===========

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 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 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 answers are C. Unique and D. External ID.

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

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

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

===========

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

===========

A Text field configured as External ID and Unique satisfies both requirements. Existing Invoice Numbers can be migrated directly from the external system without changing their values, while the Unique attribute prevents duplicate Invoice Numbers from being stored later. Salesforce defines an External ID as a field containing an identifier from a system outside Salesforce and supports Text fields as External IDs. Salesforce also states that marking the field Unique prevents duplicate values and makes it suitable for record matching and future data operations. An Auto Number field would generate Salesforce-controlled values and therefore would not preserve externally assigned Invoice Numbers. Maintaining separate legacy and Salesforce numbering fields is unnecessary when one field can preserve the external identifier and enforce uniqueness. Salesforce

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

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.

===========

A Global Picklist Value Set is used when the same picklist values must be reused across multiple objects and fields. Salesforce states that global picklist value sets let admins share values across objects and custom picklist fields.

Why not others:

A. Shared Custom Field is not a Salesforce feature for this requirement.

C. Dependent Picklist controls values based on another field.

D. Related Picklist is not the correct Salesforce feature.

===========

The correct answer is B. Data Import Wizard.

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

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

===========

Limitations when changing custom field data types include:

A. It is not possible to change the data type of a formula field – formula fields cannot be converted to other field types because they are calculated dynamically.

D. It is not possible to change a Text Area (Long) field to Text – Salesforce prevents reducing the field length because data loss could occur.

Salesforce documentation highlights these restrictions: (Salesforce Help)

B is partially true; changing fields referenced in Apex requires careful handling, but Apex references can sometimes be updated automatically.

C is allowed with some limitations if the External ID type is compatible.

===========

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.

===========

A before-save record-triggered flow is optimized for updating fields on the same record that initiated the automation. The flow can trigger when an Opportunity is updated, test whether StageName changed, and assign the current date directly to Stage_Last_Changed__c . Salesforce recommends before-save flows for updating fields on new or changed triggering records because the changes are applied before the database save and avoid an additional DML operation. Salesforce also confirms that values assigned to the triggering $Record are automatically persisted. A scheduled path would introduce an unnecessary delay, while an approval process does not fit a simple field-stamping requirement. An autolaunched flow invoked manually would depend on user action and therefore could not reliably guarantee that every Stage change is captured.

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

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 validation must happen when a Contact is saved because the missing field is Region on the Contact record. Salesforce validation rules evaluate data before a record is saved and return an error when the formula evaluates to True.

The app builder can create a validation rule on Contact that checks the related Account’s Customer Status field and requires Region only when the Account is marked High Priority.

Example logic:

AND(

ISPICKVAL(Account.Customer_Status__c, " High Priority " ),

ISBLANK(Region__c)

)

Why others are incorrect:

A is wrong because the missing field is on Contact, not Account.

B is wrong because Customer Status being required does not require Contact Region.

D is wrong because it would require Region for all Contacts, not only High Priority Account Contacts.

===========

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.

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 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 formula is TEXT(Galaxy__r.Type__c) .

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

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

===========

The correct 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 next steps are A. Add the fields to the page layout on the object and C. Create a permission set for access to the object and fields .

This is a two-part access problem in Salesforce: users need both security access and user-interface exposure . Creating a custom object and fields in Schema Builder only creates the metadata. It does not automatically guarantee that end users can see, create, edit, or use those records and fields.

C is required because object permissions define the base-level access users have to records for an object, such as create, read, edit, and delete. Salesforce also uses field permissions / field-level security to control whether users can view or edit individual fields. Permission sets are the correct modern mechanism to grant object and field permissions to selected users without changing their base profile.

A is also required because page layouts control the organization of fields on record detail and edit pages. Even if a user has field-level access, the field must be placed on the relevant page layout for normal record-page visibility and editing in the UI. Salesforce specifically separates field-level security as the access-control layer and page layouts as the UI organization layer.

B is incorrect because “Allow Reports” only makes the object available for report creation; it does not grant users object CRUD access or field-level visibility. D is incorrect because data types are assigned during field creation, not after, and choosing a data type does not grant user access.

In-App Guidance is Salesforce ' s native capability for contextual onboarding, feature adoption, prompts, and guided walkthroughs directly inside Lightning Experience. Salesforce documents that administrators can create prompts and walkthroughs, determine the target audience, and specify where and when that guidance appears. Targeted prompts can highlight a specific page element, while walkthroughs connect multiple prompts into a step-by-step guided experience. This aligns directly with Universal Containers ' goals of increasing adoption and guiding users through a newly launched application. A Screen Flow is appropriate when collecting information or executing an interactive business process, but it is not the dedicated adoption feature. Dynamic Actions control which actions appear, while Dynamic Forms controls field and section presentation. Neither provides structured onboarding walkthroughs.

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

Collection Sort is designed to reorder a collection and optionally reduce the number of records retained after sorting. Salesforce documents that the Collection Sort element can sort a record collection by a selected field in ascending or descending order and can specify the maximum number of items to keep afterward. The flow should therefore sort the Opportunity collection by Amount in descending order and retain only five records. A Collection Filter selects records based on Boolean-style criteria, but it does not identify the top N records based on ranking. A Decision controls execution paths rather than restructuring a collection. Transform maps data between structures but is not intended to rank and limit records. Collection Sort directly implements both requirements—highest Amount first and only five records retained.

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

The correct answer is D.

Managers need to create child Accounts directly from a parent Account and auto-populate fields from that parent record. This is an object-specific custom action use case. Salesforce Trailhead states that object-specific actions can create records that have automatic relationships to other records and provide a streamlined experience across desktop and mobile. Salesforce also documents that predefined field values can be used with quick actions to set field values automatically, improving consistency and speed.

A. Global Quick Action is not ideal because it does not run in the specific parent Account context. B. Path does not create child records. C. Custom link is not the recommended Lightning approach for creating related records with predefined values.

===========

A master-detail relationship provides the required cascade-delete behavior. Supplier__c should be configured as the master and Supplier_Item__c as the detail. Salesforce explicitly states that when a master record is deleted, its related detail and subdetail records are also deleted. This ensures that terminating the Supplier relationship removes the dependent Supplier Item records automatically without additional Flow or Apex automation. An indirect lookup relationship is used primarily to relate external-object data to Salesforce records and does not provide the required ownership and cascade behavior. A hierarchical relationship is available only for relationships involving the User object. Many-to-many describes a data-model pattern normally implemented with a junction object and does not itself specify the required parent-child cascade. Master-detail therefore directly implements the stated lifecycle dependency.

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

The correct answers are C. Currency, D. Date, and E. Percent.

Salesforce roll-up summary fields support different field types depending on the summary operation. For SUM, Salesforce supports number, currency, and percent fields. For MIN and MAX, Salesforce supports number, currency, percent, date, and date/time fields. Therefore, from the options given, Currency, Date, and Percent are valid field types for roll-up summary calculations.

Checkbox is not a supported field type for roll-up summary aggregation. Time is not the intended supported option in this exam context.

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.

A validation rule is required because Cloud Kicks needs to prevent , rather than merely discourage, users from skipping required Opportunity stages. A validation formula can evaluate the new StageName together with the prior stage, required fields, or other process criteria and block the save when the transition violates the sales process. Salesforce validation rules are designed to prevent records from being saved when specified business conditions are violated. Path and Guidance for Success improve usability and tell representatives what they should do, but neither inherently stops a user from jumping directly to Contract Signed. An approval process would add unnecessary managerial routing and does not directly represent the requirement to enforce valid stage progression. Therefore, a validation rule is the most efficient declarative mechanism for enforcing the required pipeline sequence.

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

A Screen Flow is Salesforce ' s interactive flow type and is specifically intended to guide users through a business process while collecting input. The app builder can create multiple Screen elements representing troubleshooting steps, display instructions and questions, store the representative ' s responses, and then use Create Records to generate the follow-up Case at the end of the process. Salesforce explicitly distinguishes Screen Flows from background automation because Screen Flows require user interaction and support screens, choices, and other interactive components. Schedule-triggered, record-triggered, and platform event-triggered flows execute automatically in the background and therefore do not provide the required multi-step wizard interface. The combination of guided navigation, data capture, and record creation makes Screen Flow the appropriate declarative solution.

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

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

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

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

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

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

===========

The correct answers are B. Each object can have up to 25 custom external ID fields and D. An external ID field can be an auto-number field.

Salesforce documentation states that each object can have up to 25 custom external ID fields. It also confirms that supported external ID field types include custom auto-number, email, number, and text fields.

A is incorrect because the limit is per object, not per org.

C is incorrect because a URL field is not one of the supported external ID field types.

===========

The requirement specifies detailed descriptions that can include pictures and links. Salesforce Rich Text Area fields support:

Multiple lines of text

Inline images

Hyperlinks

Formatting (bold, italic, lists)

Salesforce documentation confirms that Rich Text Area fields are the standard choice when storing formatted content on a record. (Salesforce Help)

D. Long Text Area supports only plain text, not images or links.

C. URL is for a single web address only.

B. Lightning Web Component is for custom UI elements, not a field type.

===========

A Flow Approval Process provides Salesforce ' s declarative framework for structured approval routing. It uses stages and approval steps, can assign approval work to specific users, groups, or queues, tracks approval state, and supports conditional execution. Salesforce states that stages execute sequentially and that individual approval steps can also be configured to start after another step is completed. Universal Containers can therefore configure the manager approval first and use conditions so the CFO step is required only when the expense exceeds $5,000. Associated background steps or flows can update the Expense Report Status when approval completes. A regular record-triggered flow does not by itself provide the complete approval work-item lifecycle, while validation rules and screen flows are not substitutes for managed asynchronous approvals. Salesforce

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

If a new report type is created but users cannot select it, it is usually because the report type status is “In Development”. Salesforce only makes report types available in the Report Type list once they are deployed. (Salesforce Help)

B. Access to objects could prevent report creation, but the question assumes the user can create reports on records they own.

C. Deploye is the correct deployed state, which would make the report type selectable.

D. Create and Customize Reports permission is required, but the question specifies users are trying to create the report.

===========

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.

===========

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

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

Why others are incorrect:

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

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

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

===========

The correct answer is A.

When custom tabs are deployed through change sets without profile settings or permission sets, the deployed custom tabs are hidden by default for all users. Salesforce Help states that deployed custom tabs are hidden by default unless the change set also includes profiles that set the tab visibility.

Tab visibility is controlled through profile or permission set tab settings such as Default On, Default Off, and Tab Hidden.

Why others are incorrect:

B and C are incorrect because the tabs are not automatically default off or default on for all users.

D is incorrect because the custom tabs are deployed; they are just not visible until access is configured.

===========

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

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

===========

Agentforce is Salesforce ' s platform for autonomous AI agents that can understand requests, reason over context, retrieve business information, determine appropriate next steps, and execute actions. Salesforce describes Agentforce agents as autonomous and proactive applications capable of taking action with or without continuous human intervention. Agents can use Salesforce CRM data and invoke flows, Apex, APIs, prompts, and other configured actions to complete business tasks. This directly matches the requirement for end-to-end customer service handling. Case Assignment Rules only route Cases. Experience Cloud with Live Chat provides customer interaction channels but does not independently reason and execute complete workflows. Einstein Bots provide conversational automation but do not represent the current autonomous agent architecture described in the scenario. Agentforce is therefore the verified answer.

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

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

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

Why others are incorrect:

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

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

The correct answer is B. Master-detail relationship.

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

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

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

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

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

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

Change sets can be exchanged only between deployment-connected organizations, such as a production org and its own sandboxes. UMS Logistics is a separate production organization and has no deployment relationship with the UMS source environment, so an outbound change set cannot be sent there. Salesforce documents unmanaged packages as a mechanism for packaging metadata components in a source org, uploading the package, obtaining an installation URL, and installing those components into another Salesforce organization. A managed package is intended primarily for distributed applications requiring namespace and provider-controlled versioning, such as commercial AppExchange solutions, and is unnecessary for this evaluation transfer. A sandbox likewise cannot be refreshed from an unrelated organization ' s Developer sandbox. Therefore, the appropriate deployment vehicle is an unmanaged package installed through its generated URL.

A scheduled path on an after-save record-triggered flow is specifically intended to execute automation at a dynamically calculated time after an individual record-triggering event. The flow should trigger when Project__c.Status transitions to On Hold and schedule the email seven days after that update. Salesforce states that scheduled paths are available for record-triggered flows optimized for Actions and Related Records and can use “When Record Is Created or Updated” as their time source. Using CreatedDate would calculate the delay from record creation rather than when the project became On Hold. A daily schedule-triggered flow could poll records, but it is less precise and unnecessary when Salesforce can queue a per-record scheduled action directly. Thus, C matches the required independent seven-day timer.

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

The correct answer is B. Lookup.

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

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

===========

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

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

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

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

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

A Screen Flow is required because the process must interact directly with a user and collect input. Salesforce defines screen flows as interactive automation that uses Screen elements and screen components to gather information from running users. After the required information is captured, an Update Records element can locate the related Account and write the supplied values to that existing record. Salesforce ' s Screen Flow documentation specifically describes adding an Update Records element and identifying an Account by its record ID when existing data must be changed. An autolaunched flow cannot contain normal interactive Screen elements. Record-triggered and schedule-triggered flows execute from record or time-based events rather than interactive user input. Create Records is also incorrect because the requirement is to update an existing related Account, not create a new one.

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

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

===========

An indirect lookup relationship is used when an external object must relate to a standard or custom Salesforce object and the external data does not contain Salesforce record IDs. Salesforce requires the parent Salesforce object to contain a custom field marked External ID and Unique . Values from the external object ' s indirect lookup field are matched against this external ID field to establish the relationship. Salesforce specifically states that indirect lookups link a child external object to a parent standard or custom object using a custom unique External ID field. TEXT(Id) does not create such a relationship key, and CASESAFEID() merely converts Salesforce IDs to their 18-character representation. A normal Salesforce Record ID is used for standard lookup relationships, not indirect lookups.

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

A Salesforce validation rule prevents a record from being saved when its formula evaluates to TRUE. The rule therefore must return TRUE when the Account is locked and the current user ' s profile is not System Administrator. $Profile.Name is the appropriate global variable for testing the current user ' s profile. Salesforce documents $Profile global merge fields for accessing profile properties, including $Profile.Name , and provides validation-rule examples using profile-name comparisons to exempt authorized profiles. Option A tests the user ' s role, but System Administrator is a profile, not a role. Option C introduces an unrelated Opportunity Stage condition. Option D reverses the logic and would block the System Administrator instead of exempting that profile. Therefore, B correctly implements the stated lock exception.

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

The correct bulk-safe Flow pattern is to modify each current Case with an Assignment element and add the modified record to a record collection variable. After the Loop finishes, one Update Records element should update the complete collection. Salesforce explicitly warns against putting Get Records, Create Records, Update Records, or Delete Records elements inside loops because repeated SOQL or DML operations can quickly exceed governor limits. Trailhead ' s recommended pattern is to retrieve records before the loop, use assignments while iterating, store changed records in a collection, and perform one database update after the loop. A Collection Filter does not replace the collection used to stage modified records. An Update Records element inside the loop defeats the stated requirement for one database operation. Therefore, Assignment plus a collection variable is the correct architecture.

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

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 answer is C. Create a master-detail relationship between the parent and child object with a roll-up summary field that filters on the status field.

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

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

Why others are incorrect:

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

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

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

===========

The correct answer is 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.

===========

Agentforce Service Agent is built for autonomous, conversational customer support. Salesforce states that Agentforce Service agents can process incoming customer requests, resolve common inquiries autonomously, use business data, and execute actions without requiring a service representative for every step. Agent actions can invoke Flow or Apex and perform operational tasks such as retrieving order status or updating fulfillment information. That matches Cloud Kicks ' requirement for dynamic support that can investigate missing packages, determine delays, and take appropriate customer-service actions. An approval flow introduces unnecessary human review, while scheduled email templates provide static rather than real-time assistance. A Screen Flow could collect issue information but would generally create a Case rather than independently reason about the customer ' s request and perform resolution actions.

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

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

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

Example logic:

Estimated_Hours__c > PRIORVALUE(Estimated_Hours__c)

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

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

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

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

===========

The correct answers are 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.

===========

Current Salesforce documentation makes C the correct answer. Salesforce Help states that to enforce validation rules during Lead conversion, the Require Validation for Converted Leads setting must be enabled under Lead Settings. If it is disabled, validation automation that would otherwise protect the resulting Account, Contact, or Opportunity can be bypassed during conversion. Therefore, missing information on Accounts created through Lead conversion indicates that this Lead setting has not been enabled.

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

With Account organization-wide defaults set to Private, users cannot automatically see records owned by peers at the same role-hierarchy level. Salesforce sharing rules provide an exception to restrictive organization-wide defaults and can grant additional record access to selected users, roles, or public groups. If User A belongs to a public group targeted by an Account sharing rule, User A can receive access to User C ' s Account while User B does not. Being at the same role level as User C does not provide upward hierarchy access. “View All Fields” concerns field visibility and does not grant access to otherwise inaccessible records. Login access policies concern when or where users can authenticate, not access to one particular Account. Therefore, membership in a public group used by a sharing rule explains the different record visibility.

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

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

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

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

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

Why others are incorrect:

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

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

===========

The correct answer is D. Rich text area.

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

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

===========

View All Fields is an object-level permission designed specifically for users who require access to every field on a particular object. Salesforce states that this permission grants access to all existing fields and field data for the specified object and, importantly, automatically grants access to newly created fields in the future. This directly satisfies the integration requirement without administrators continually updating field-level security. View All Records controls record visibility but does not independently override field-level security. View All Data provides much broader organization-wide access than necessary and violates least-privilege design. A permission set group merely aggregates permission sets and would not automatically provide access to future Account fields unless the appropriate field permission were included. Therefore, View All Fields on Account is the precise solution. Salesforce

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

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.

===========

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.

To show Component records as a related list on Product, the app builder should create a relationship field on the child object, Component, pointing to the parent object, Product. Salesforce documentation explains that when a lookup relationship is defined, the lookup field is added on one object and a related list can be shown on the associated object’s page layout.

A is unnecessary unless the requirement is many-to-many. B is incorrect because a roll-up summary does not create a related list. D is incorrect because the relationship field direction is wrong; the field should be on Component, not Product.

===========

\

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 B. Approval Process.

An Approval Process is used when a record must be reviewed and approved before moving forward. Salesforce Trailhead gives a very similar example: opportunities with high discounts requiring approval before proceeding.

Here, Cloud Kicks needs CFO sign-off when a major shoe retail deal has a discount greater than 30% before it can be closed. This is exactly what an approval process is designed to handle.

Why others are incorrect:

Slack message only sends communication.

Email alert only notifies someone.

Field update changes a field value but does not collect formal approval.

===========