Platform-App-Builder Sample Questions Answers

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. Dynamic Actions and C. Approval Process.

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

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

Why others are incorrect:

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

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

===========

The correct answers are A. Navigation Menu and C. In-App Notification.

Salesforce documentation states that users can receive and act on approval requests in the Salesforce mobile app by tapping the notification or by going to Approval Requests in the navigation menu. Salesforce also describes the Approval Requests navigation item as showing pending approvals where users can approve or reject items from within Salesforce.

Why others are incorrect:

B. Home Screen is not the documented approval-response delivery method in this context.

D. Record Detail is not the best answer here because the documented mobile approval response paths are the notification and the Approval Requests navigation item.

===========

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 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 A. A hyperlink to the parent Account of the parent Opportunity.

A formula field can use cross-object references to parent records, and Salesforce states that cross-object formulas can reference fields from objects up to 10 relationships away. Since Opportunity Product relates to Opportunity, and Opportunity relates to Account, a formula on Opportunity Product can reference the parent Opportunity’s Account.

Salesforce also supports the HYPERLINK() formula function, which creates a clickable link from specified link text to a specified URL. So a formula field can be configured to create a hyperlink to the Account record related to the parent Opportunity.

B is incorrect because formula field data types do not include Rich Text Area as a formula return type.

C is incorrect because Salesforce restricts formulas from using long text area, encrypted, or Description fields.

D is not the best verified answer because large cross-object concatenations can run into formula relationship, size, or complexity limits, while the clearly supported Platform App Builder use case here is the cross-object HYPERLINK formula.

===========

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

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

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

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

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

D is not supported by the scenario.

===========

To optimize Salesforce Mobile experience:

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

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

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

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

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

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

===========

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

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

Why others are incorrect:

A Approval Process is for review/approval routing.

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

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

===========

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

The requirement is to show the number of open Cases for both the Account and the Parent Account. This is not a simple native roll-up summary scenario because standard roll-up summary fields are mainly for master-detail relationships, while lookup relationships do not support standard roll-up summary fields.

Salesforce specifically documents Flow examples where a flow looks up the parent account, checks how many open cases it has, and evaluates that count. Salesforce also has guidance for creating roll-up-style summaries using Flow, including a use case to count Cases related to an Account.

Why others are incorrect:

A. Approval Process is for approvals, not counting open Cases.

C. Custom object is unnecessary.

D. Roll-up summary is not the best fit for counting Cases across Account and Parent Account relationships.

===========

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

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

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

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

C is incorrect because CASE() itself is allowed.

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

===========

The correct formula is TEXT(Galaxy__r.Type__c) .

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

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

===========

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

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

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

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

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

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

===========

The correct answer is A. Highlights panel.

In Lightning Experience, record actions such as New Task appear in the Highlights Panel area of the Lightning record page. Salesforce documentation explains that the actions in the highlights panel come from the object’s page layout, specifically the Salesforce Mobile and Lightning Experience Actions section, unless dynamic actions are enabled.

Since the custom action was already added to the Mobile & Lightning Actions section on the page layouts, the app builder must add the Highlights Panel component to display those actions on the Lightning record page.

Activities shows activity timeline/composer-related functionality, but it is not where page-layout actions are generally displayed. Related Lists and Related Record do not display the main action bar.

===========

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

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

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

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

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

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

===========

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

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

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

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

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

===========

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

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

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

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

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

===========

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.

===========

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

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

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

===========

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

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

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

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

===========

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

The Lightning record page already supports both mobile and desktop, but the downloaded custom component is not visible on mobile. That points to the component itself, not the page activation. Lightning components must be configured to support the required form factors. Salesforce developer documentation explains that components can be configured for desktop form factor Large, phone form factor Small, or both.

So, if the AppExchange component was built only for desktop pages or only supports the large form factor, users cannot view it in the Salesforce mobile app.

A and D are incorrect because the issue is not page activation if the page already supports mobile and desktop. B is incorrect because the scenario states the record page supports both mobile app and desktop.

===========

Users need Read access to both master objects.

Request Inventory is a junction object with two master-detail relationships: Inventory and Order. For junction objects, access is based on the associated master records and the sharing behavior of the master-detail relationships. Salesforce documentation for object relationship considerations explains that sharing access to a junction object record is determined by access to both associated master records.

Why not the others? Sharing rules are not created directly on a master-detail detail object in the same way, because it is controlled by parent. Apex-based sharing is not needed. Read access to only the first master object is not enough because the junction record connects two master records.

===========

The correct answer is D.

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

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

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

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

===========

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

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

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

Why others are incorrect:

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

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

===========

The correct answer is A. Import Wizard.

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

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

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

===========

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

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

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

Why others are incorrect:

Modify All Data is too broad.

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

Workflow does not grant record access.

===========

The correct answer is D. Approval process.

The marketing director wants all free parts to receive sign-off before they are allowed. Salesforce Approval Processes are used to automate how records are approved, define who approves at each step, and specify actions after approval or rejection. Trailhead describes approval processes as automation for record approval and explains that approval steps assign approval requests to specific users.

Chatter approval is not the standard feature for formal record sign-off. Slack post and automated email message can notify people, but they do not enforce approval. An Approval Process is the correct declarative feature for required business sign-off.

===========

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 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 validation rule is:

AND(

ISNEW(),

ISBLANK(Lead.Owner:User.Id)

)

This rule prevents a new Campaign Member from being created when the related Lead does not have a User as owner. Leads can be owned by either a user or a queue, and Salesforce queues can own Lead records.

Salesforce validation rules block a save when the formula evaluates to True. The ISNEW() function checks whether the record is being created, and ISBLANK() checks whether the Lead owner’s User Id is empty.

For owner fields in cross-object formulas, Salesforce requires being explicit about the owner type, such as Owner:User or Owner:Queue .

Why not others:

A is wrong because Lead.Owner.Id is normally populated whether the owner is a user or queue.

B and D focus on queue ownership, but the best exam answer checks that the Lead has an actual User owner when the Campaign Member is created.

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 C. To make a Contact’s Twitter profile available in the Salesforce mobile app, the app builder should add the Twitter component to the mobile Lightning record page. Salesforce guidance states that to make Twitter accessible on Account or Contact record pages and in the Salesforce mobile app, add the Twitter component in Lightning App Builder.

Why others are incorrect:

A is wrong because mobile navigation is for navigation items, not displaying a Contact Twitter profile.

B is unnecessary because Salesforce provides the component declaratively.

D may show a link, but it does not provide the standard Twitter profile component experience.

===========

To display a weather map component only when a house is scheduled for a listing, the app builder should use Component Visibility in the Lightning App Builder.

Component visibility allows setting filters so components appear conditionally based on field values or other conditions.

Salesforce documentation states that conditional visibility rules control when a component is displayed dynamically on a Lightning page. (Salesforce Help)

B. Field-level security controls access to fields, not component visibility.

C. Formula field only calculates values but does not control component display directly.

D. Sharing rules control record access, not UI components.

===========

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

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

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

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

===========

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

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

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

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

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

Why others are incorrect:

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

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

===========

The correct answer is A. Lookup field.

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

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

===========

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

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

A does not automate data entry.

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

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

===========

The correct answer is D. Patch.

In application lifecycle management, patch releases are used for bug fixes and simple, low-impact changes. Salesforce packaging documentation also describes patch versions as minor upgrades used for fixing bugs or errors.

Major releases are for large changes or significant new functionality. Minor releases are usually for limited-impact enhancements. Roll is not the correct ALM release category here.

===========

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.

===========

The correct answer is D. Flow.

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

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

C. Quick action is manual, not automatic.

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

===========

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

===========

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

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

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

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

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

===========

The correct answer is 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 answers are B. Create a criteria-based sharing rule and C. Update the organization-wide defaults.

To move from a public sharing model to a more restrictive model, the app builder must first update the Organization-Wide Defaults for Accounts. OWDs define the baseline record access for users. Then, because the Sales team must still access all Account records with the Sales record type, the app builder should create a criteria-based sharing rule using record criteria, such as Record Type. Salesforce sharing rules are used to extend access when the OWD is Private or Public Read Only.

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

D is incorrect because profiles control object permissions, not record-level access by record type.

Existing data will be truncated to the first 255 characters.

Salesforce documentation on changing custom field types states that when a Long Text Area field is converted to Email, Phone, Text, Text Area, or URL, the record data is truncated to the first 255 characters. Since the target is a standard Text Area with a 255-character limit, longer Manager Notes values would not remain intact.

Why not the others? Salesforce does not preserve values beyond the new limit in this conversion. The data is not completely lost, but anything after the first 255 characters is removed.

The correct answers are A. There are already two master-detail relationships on the Invoice Line Item and C. Invoice Line Item records exist without having the Invoice lookup field populated.

Salesforce allows a lookup relationship to be converted to a master-detail relationship only when the lookup field has a value on all existing records. Therefore, if any Invoice_Line_Item__c records do not have the Invoice lookup populated, Salesforce prevents the conversion.

Salesforce also limits each custom object to up to two master-detail relationships. If Invoice Line Item already has two master-detail relationships, it cannot have another master-detail relationship added or converted.

B is incorrect because custom objects can be on the detail side of master-detail relationships. D is incorrect because a roll-up summary field on Invoice is not the reason this lookup-to-master-detail conversion would be blocked.

===========

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

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

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

Why not others:

A is not the stated Salesforce limitation.

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

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

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

Here, the flow can:

Detect when the client is won.

Send an email notification to the finance manager.

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

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

Why not others:

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

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

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

===========

The correct answers are C. The report is in the manager’s Private reports folder and D. The report does not have a chart.

The Report Chart component is used to display a chart from a report on a Lightning page. If the report has no chart, it cannot be used as a Report Chart component source. Salesforce documentation describes the Report Chart component as a way to include a chart from a report in a Lightning page.

The app builder also must have access to the report through report folder sharing. Reports saved in a user’s private report folder are not visible to other users unless moved/shared appropriately. Salesforce explains that reports are saved by default into private reports or dashboards folders unless a public/custom folder is selected.

A is incorrect because a report having no returned data does not stop the report from being selectable. B is incorrect because the app builder does not need to be the report creator; they need access to the report folder and the report must contain a chart.

===========

The correct design is to create a master-detail relationship from Testimonial__c to Account and a lookup relationship from Testimonial__c to Contact.

The Account relationship must be master-detail because Salesforce deletes related detail records when the master record is deleted. That matches the requirement that if the Account is deleted, the related Testimonial__c records are also deleted. The Contact relationship must be lookup because the Testimonial__c record must remain when the Contact is deleted. Salesforce lookup relationships can keep the child record and clear the lookup value when the referenced record is deleted.

Why the other options are wrong:

A reverses the required behavior. B would delete the testimonial if either master side caused deletion behavior, which does not fit the Contact requirement. D uses lookup for Account, so it does not guarantee Account deletion will also delete Testimonial__c record

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. 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 C. Two Master-detail relationships on a new custom object.

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

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

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

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

===========

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

===========

The correct answer is A. Account Object .

Roll-up summary fields are created on the parent object , because the summary value is displayed on the parent record. Here, the KPI values need to appear for each Account , and they summarize related Opportunity records. Therefore, the app builder should go to the Account object in Object Manager and create roll-up summary fields there.

For this requirement, the app builder would create separate roll-up summary fields on Account, such as:

Count of open Opportunities

Count of won Opportunities

Salesforce documentation describes roll-up summary fields as fields that calculate values from related records, such as records in a related list.

C. Opportunity Object is incorrect because Opportunity is the child/related record being counted.

D. Lightning App Builder is incorrect because Lightning App Builder controls page layout/components, not the creation of roll-up fields.

B. Lightning Object Creator is used to create objects from spreadsheets, not build rollups.

===========

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

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

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

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

Why others are incorrect:

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

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

===========

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

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

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

Why others are incorrect:

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

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

===========

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

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

Why others are incorrect:

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

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

===========

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

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

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

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

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

===========

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 B. Master-detail relationship.

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

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

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

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

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

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

The correct answer is C. Compact layout.

Compact layouts control the key fields shown in the record highlights area at the top of a record, including in the Salesforce mobile app. Salesforce documentation states that compact layout fields populate the record highlights section at the top of record views in the Salesforce mobile app.

Why others are incorrect:

A. Mobile navigation controls navigation menu items, not fields on a record.

B. Record Detail component shows record fields but does not specifically place key fields at the top.

D. Object specific action is used for actions, not at-a-glance field display.

===========

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.

===========