Platform-App-Builder Practice Exam Questions with Answers Salesforce Certified Platform App Builder (Plat-Admn-202) Certification

Create a validation rule that uses the PRIORVALUE function is how an app builder can meet the requirement of preventing users from increasing the value of Estimated Hours after it is set. According to the Salesforce documentation, “PRIORVALUE returns the previous value of a field.” The validation rule can compare the current value and the prior value of Estimated Hours and display an error message if the current value is greater than the prior value. Creating a formula default value for the custom field, creating a formula field that uses the PREVGROUPVAL function, and creating a validation rule that uses the ISCHANGED function are not valid or correct solutions for this requirement.

The import wizard only allows values to be imported into a dependent picklist if they match the appropriate controlling field. This ensures data integrity and prevents invalid values from being imported. Custom picklist fields can be either controlling or dependent fields. This allows the app builder to create custom dependencies between custom picklists. Checkbox fields can be controlling fields but not dependent fields. This allows the app builder to create dependencies based on checkbox values, such as true or false. Multi-select picklist fields can be dependent picklist fields but not controlling fields. This allows the app builder to create dependencies based on multiple values selected in a multi-select picklist field. Standard and custom picklist fields can be dependent fields, but not all standard picklist fields can be controlling fields. Some standard picklist fields, such as Lead Status or Opportunity Stage, cannot be controlling fields because they are used in other processes, such as lead conversion or sales path

The app builder should use Apex code to update a field on the parent record when a child record connected via lookup is deleted. Apex code is a programming language that allows developers to execute complex logic on the Salesforce platform. Apex code can be triggered by certain events, such as insert, update, delete, or undelete of records. In this case, the app builder can write an Apex trigger that runs after a child record is deleted and updates a field on the parent record accordingly. Option A, B, and D are not automation tools that can perform this task.

Highlights Panel. This is correct because the highlights panel component displays key fields from a record at the top of the page, and it can be configured to show up to 10 fields.

Opportunities are in a master-detail-like relationship with Accounts (standard lookup behaves with special roll-up capabilities). Salesforce provides a standard roll-up summary feature on the Account object to count related Opportunities.

Why B (Roll-up Summary) is correct:Exact Extract:“Use a roll-up summary field to automatically display a value from related detail records on a master record. You can count related records, or calculate the sum, min, or max of a field on those records.” — Salesforce Help | Roll-Up Summary FieldsOn Account, you can create a roll-up summary field to COUNT related Opportunities.

Why B (Roll-up Summary) is correct:Exact Extract:“Use a roll-up summary field to automatically display a value from related detail records on a master record. You can count related records, or calculate the sum, min, or max of a field on those records.” — Salesforce Help | Roll-Up Summary FieldsOn Account, you can create a roll-up summary field to COUNT related Opportunities.

Why not A:Formula fields cannot count related records.

Why not C:AppExchange is not required; Salesforce provides native functionality.

Why not D:A lookup only links records—it does not perform aggregation.

The most likely reason why users are unable to view the custom Lightning component on mobile devices is that the component has been developed for Desktop Pages only. Some components are not supported on mobile devices or have different behavior on mobile devices. An app builder should check the component documentation or metadata to see if it is compatible with mobile devices.

The Twitter component is a standard Lightning component that can be added to mobile view Lightning pages using the Lightning App Builder. It displays a contact’s Twitter profile and recent tweets

One of the limitations when using the Schema Builder for creating fields is:

C. Cannot add fields to page layouts. While Schema Builder allows for easy visualization and creation of fields and objects, it does not support placing these fields onto specific page layouts directly from the Schema Builder interface.

To place fields on page layouts, you need to:

Navigate to Setup ? Object Manager ? select your object.

Click on Page Layouts, choose the appropriate layout, and manually add the newly created fields.

This step is necessary to ensure fields are visible and properly arranged on user interfaces.

For more details, Salesforce's Schema Builder documentation outlines its capabilities and limitations.

Upon adding a lookup field to Account from a custom object, Box:

D. Accounts with Boxes. Salesforce automatically creates a new report type that reflects the relationship from the perspective of the parent object, in this case, Accounts, showing related Box records.

This new report type enables users to create reports that list Accounts along with their associated Boxes, if any.

For further understanding of report types and relationships, Salesforce's guide on Report Types provides comprehensive information on how these are structured following modifications to object relationships.

The app builder should recommend UC use Salesforce Connect to access the assets in real-time data in Salesforce. Salesforce Connect is a feature that allows users to view, search, and modify data that is stored outside Salesforce, such as in an external system. Salesforce Connect uses external objects and external data sources to integrate data from various sources without copying or synchronizing it2. This can help UC access their assets in real-time without consuming data storage limits in Salesforce. Option A, C, and D are not features that can meet this requirement.

TEXT() is a formula function that converts a picklist value to text. This can be used to display the Type field from the parent object Galaxy on the child record Star. ISPICKVAL() is used to check if a picklist value is equal to a specified value. VALUE() is used to convert text that represents a number to a number. FIND() is used to locate one text string within another text string.

To provide a help guide to enable reps to easily get help where needed during the different sales processes, an app builder should recommend Path. Path is a component that displays the key fields and guidance for each stage of a sales process on an object’s record page. Users can see where they are in the process, update the stage and fields, and access resources such as tips and links. [Source]

The category that handles bug fixes and simple changes is minor. A minor release is a type of release that introduces small enhancements or fixes to existing functionality, such as correcting spelling errors or improving performance. A minor release usually has a low impact on users and does not require extensive testing or training. A patch release is a type of release that addresses critical issues or defects that affect the functionality or security of an application, such as fixing broken links or resolving vulnerabilities. A patch release usually has a high impact on users and requires immediate deployment. A major release is a type of release that introduces new functionality or features to an application, such as adding new objects or components or changing business processes. A major release usually has a high impact on users and requires extensive testing and training. A rollback is not a type of release, but an action that reverses a release that has been deployed to an environment, such as undoing changes or restoring previous versions. A rollback may be necessary if a release causes errors or issues that affect the functionality or performance of an application.

The app builder should recommend utilizing the manage assignments button to assign a permission set group and additional individual permission sets to each user. This way, the app builder can assign the five consistent permission sets to all users in one permission set group, and then assign additional permission sets to higher-level staff as needed. Option B is incorrect because it will not account for the varying levels of support staff and their different permission sets. Option C is incorrect because the Data Import Wizard cannot be used to assign permission sets or permission set groups to users. Option D is incorrect because the Data Loader cannot be used to assign permission set groups to users.

The email button item will not be visible on the Lightning record page if the page layout includes the case feed component or if the email button contains JavaScript. The case feed component replaces the standard buttons on the page layout with actions in the feed. The email button item will not work if it contains JavaScript because JavaScript buttons are not supported in Lightning Experience.

 Groups is available in the Chatter section of the navigation menu, not in the selected list for the navigation menu. According to the Salesforce documentation, “Groups appear in Chatter, not in Navigation Menu.” Groups is not available in the recent section of the navigation menu, nor is it included in the Smart Search items but unavailable on the navigation menu. Groups is unavailable in the selected list for the navigation menu.

Lightning Object Creator is a tool that allows app builders to create an object with fields and import data from a spreadsheet simultaneously. Import Wizard and Data Loader are tools for importing data into existing objects, not creating new objects. Schema Builder is a tool for creating and modifying objects and fields, but not importing data.

Data is unable to be deployed with change sets. Change sets are used to deploy metadata components such as custom objects, fields, workflows, reports, etc. from one Salesforce org to another. However, change sets do not include any data or records from the source org. Users will need to use other tools such as Data Loader or Data Import Wizard to migrate data between orgs. [Source]

The requirement is to copy the parent Account’s Billing State onto a custom field on Opportunity at the moment the Opportunity is created, and keep that value static thereafter.

Why not Formula (B): A formula would always recalculate, so the value would change if the Account’s Billing State later changes.Exact Extract: “Formula fields are read-only fields that automatically recalculate their values when any referenced fields change.” — Salesforce Help | Formula Fields

Why not Roll-Up Summary (A): Roll-up summary fields only summarize child records onto a master (parent) record; they do not copy values from a parent (Account) down to a child (Opportunity), and they can’t summarize a text/state value.Exact Extract: “A roll-up summary field calculates values from related records, such as those in a related list, on a master record.” — Salesforce Help | Roll-Up Summary Fields

Why Flow (C) is correct: A Record-Triggered Flow on Opportunity (when a record is created) can set a field value by referencing the related Account (e.g., Opportunity.Account.BillingState) and writing it into a dedicated “snapshot” field (e.g., Billing State at Create__c). Because this is a one-time assignment on create, the value remains static unless intentionally updated by further automation.Exact Extract 1: “Use Flow Builder to automate business processes by collecting data and performing actions in your Salesforce org.” — Salesforce Help | Flow BuilderExact Extract 2: “Record-triggered flows launch when a record is created, updated, or deleted, and can update fields on the triggering record.” — Salesforce Help | Record-Triggered Flows

Why Apex (D) is not preferred: While Apex could do the same copy-on-create, Salesforce’s recommended approach is to use declarative automation (Flow) when possible.Exact Extract: “Before considering Apex, evaluate whether your solution can be implemented with declarative tools such as Flow.” — Salesforce Architect Guidance | Clicks, Not Code

Implementation note (for clarity): Create a custom text field on Opportunity, e.g., Billing State at Create (Billing_State_at_Create__c). Build a Record-Triggered Flow:

Trigger: Opportunity — “A record is created”

Get or use the related Account from the $Record.AccountId relationship

Update the new Opportunity field with Account.BillingState

Do not run the flow on updates

References (Salesforce Platform App Builder documents / Study Guide topics):

Salesforce Help — Formula Fields

Salesforce Help — Roll-Up Summary Fields

Salesforce Help — Flow Builder

Salesforce Help — Record-Triggered Flows

Salesforce Architect Guidance — Clicks, Not Code

Salesforce Platform App Builder Exam Guide — Business Logic and Process Automation

A formula field is a read-only field that derives its value from a formula expression you define. The formula field is updated when any of the source fields change. You can use formula fields to display images based on certain conditions. In this case, a formula field can be used to display a green, yellow, or red circle image based on the case age.

For automatically updating contact statuses when an account type changes:

D. Record triggered flow. This type of automation can monitor changes in account types and accordingly update related records, such as contacts.

Steps to implement:

Navigate to Setup ? Flows.

Create a new Flow and choose the record-triggered flow type.

Configure the flow to trigger when the Account record is updated to 'Past-Customer'.

Add an Update Records element to modify all related contacts, setting their status to 'Re-Market'.

Activate the flow.

This automation ensures that contact statuses are updated in real-time when their related account's type changes, maintaining data consistency and relevancy.

For more on record-triggered flows, check out Salesforce's Record-Triggered Flows documentation.

The Account record includes Invoice roll-up summary fields. This is correct because roll-up summary fields are only available on the master object in a master-detail relationship, and changing the field type to lookup would delete the roll-up summary fields

The two steps that should be suggested to meet these requirements are to select insert null values in settings and to use Data Loader to update leads using the CSV file. Selecting insert null values in settings will allow Data Loader to overwrite existing values with null values. Data Loader is a tool that can import, export, update, or delete large amounts of data.

Approval process is the best way to automate travel requests based on internal policy. Approval process can define the steps, criteria, and actions for approving records. The app builder can create an approval process for travel requests that requires approval from managers or executives before they are submitted. Workflow rule, Process Builder, and Apex are not suitable for this requirement.

 Create a master-detail relationship between the parent and child object with a roll-up summary field that filters on the status field is the recommended method for the app builder to achieve the request of rolling up sales metrics to an opportunity for only Detailed.Sales__c records that have their picklist status set to Active. According to the Salesforce documentation, “Roll-up summary fields calculate values from related records, such as those in a master-detail relationship.” A roll-up summary field can filter on a field value of the child records and sum up only those records that match the criteria. Utilize the AppExchange to download a third-party application that can roll up the sales dollars with the appropriate filter, create a lookup relationship between the parent and child object with a roll-up summary field that filters on the status field, and utilize Apex code to roll up the desired amounts are not valid or necessary methods for this request.

To ensure that opportunities are submitted into the approval process when their close date is pushed more than 30 days, an app builder should use an automated process to submit the record for approval. An automated process can be created using tools such as Process Builder or Flow Builder, and it can define the criteria and actions for submitting a record for approval. [Source]

The Highlights Panel in the Lightning Record Page displays key fields and record actions prominently at the top of the page, exactly as described in the requirement.

Why A (Highlights Panel) is correct:Exact Extract:“The highlights panel displays important fields and key record actions at the top of the record page in Lightning Experience.” — Salesforce Help | Highlights Panel

Why not B:Path is used to visualize progress through stages (e.g., Opportunity Stage), not display multiple fields.

Why not C:A custom component is unnecessary since the standard Highlights Panel fulfills the requirement.

Why not D:Accordion is used to organize information in collapsible sections, not display key fields at the top.

Polls and Out of Office are two ways that CK can use Chatter to gather feedback and understand availability. Polls allow users to create surveys and collect opinions from other users. Out of Office lets users set a status message and an end date to inform others when they are away or busy. Streams and Topics are not related to the problem.

UMS wants each Application to connect both to a Job Candidate and an Open Position, where:

One Job Candidate can apply for multiple Open Positions.

One Open Position can receive multiple Applications.This is a many-to-many relationship, which in Salesforce is implemented by using a junction object.

In this case, Application__c serves as the junction object between Job_Candidate__c and Open_Position__c.

Exact Extract:

“To create a many-to-many relationship, create two master-detail relationships on the junction object. Each master-detail relationship links the junction object to one of the objects you want to relate.” — Salesforce Help | Create a Many-to-Many Relationship

Step 1: On Application__c, create a Master-Detail relationship to Job_Candidate__c (Answer C).

Step 2: On Application__c, create a Master-Detail relationship to Open_Position__c (Answer D).

This setup allows:

Viewing all Applications related to a given Job Candidate.

Viewing all Applications related to a given Open Position.

Exact Extract:

“A junction object is a custom object with two master-detail relationships, and it is the key to building many-to-many relationships between two objects.” — Salesforce Help | Junction Object Concepts

References (Salesforce Platform App Builder documentation / Study Guide topics):

Salesforce Help | Create a Many-to-Many Relationship

Salesforce Help | Junction Object Concepts

Salesforce Platform App Builder Exam Guide | Data Modeling and Management

A cross-object formula field is a formula field that references fields from another object. This can be used to display the value of the Account_Region__c field on Opportunities, as long as there is a relationship between the two objects. Option A, B, and C are not relevant for this requirement.

When creating a new field, if an app builder does not want the field to be automatically added to pre-existing custom report types, the step to take is:

Deselect 'Add Field to Custom Report Types' (D). This option is available when creating or editing a custom field and ensures that the field is not automatically included in report types where 'Automatically add new custom fields to report type layouts' is enabled.

Removing the field from page layouts (A) affects the visibility on record pages but not reports. Adjusting visibility (B) or setting read-only access (C) for report profiles affects user permissions to see the field in reports, but does not remove the field from report types if it was previously added.

Reference for managing fields in custom report types:

Custom Report Types and Fields: https://help.salesforce.com/articleView?id=reports_report_type_layouts.htm &type=5

The two reasons that could be preventing this relationship conversion are that there are already two master-detail relationships on the Invoice Line Item and that Invoice Line Item records exist without having the Invoice lookup field populated. A custom object can have up to two master-detail relationships, so adding another one would exceed the limit. Also, a master-detail relationship requires that the detail records have a value in the master lookup field, so any records with a blank Invoice lookup field would prevent the conversion.

To allow quick editing of a record's status and entering a due date from the record's feed in the Salesforce Mobile App:

A. Custom action. This option enables users to perform specific tasks directly from the record page in the Salesforce Mobile App, such as editing fields.

Steps to create a custom action:

Navigate to Setup ? Object Manager ? select the relevant object.

Click Buttons, Links, and Actions ? New Action.

Set Action Type to 'Update a Record'.

Configure the action layout to include the Status and Custom Due Date fields.

Add the action to the Salesforce Mobile layout.

This setup provides an efficient way for users to update key fields without navigating away from the record feed.

For detailed setup instructions, see Salesforce's documentation on Creating Quick Actions.

When Cloud Kicks needs to calculate summaries from child objects of a standard object declaratively, a few key considerations about master-detail relationships come into play. Master-detail relationships are critical in Salesforce when working with roll-up summary fields, which allow you to calculate values from child records.

Option B: An object can have up to two master-detail relationships.

Salesforce allows an object to have two master-detail relationships. This is important because if you want to aggregate child record data using roll-up summary fields, you need to have a master-detail relationship in place. Each master-detail relationship links a child object to a parent, and you can create roll-up summary fields on the parent object to summarize the child record data.

 The app builder would enable this ability in Chatter Settings. Chatter Settings is a setup menu that allows an app builder to configure various aspects of Chatter functionality, such as feeds, groups, email notifications, and more. One of the options in Chatter Settings is Enable Approvals via Chatter, which allows users to approve or reject requests from their team via Chatter posts or comments. Option A, B, and D are not places where an app builder would enable this ability.

Two reasons that can prevent an app builder from adding a custom component to the Lightning home page are if My Domain is not deployed, or if the component is tagged for record pages instead of home pages. My Domain must be deployed to add custom components to the page with the App Builder, as it enables Lightning components and other features. The component must be tagged for home pages in its configuration file, otherwise it will not show up in the App Builder for home pages

Using Process Builder on Opportunities and a Chatter post action, and enabling Feed Tracking on Opportunities are two configurations that an app builder can recommend to meet the requirement of notifying and tracking changes to an Opportunity Close Date. Process Builder can create a process that triggers a Chatter post action when the Close Date field is changed on an Opportunity. Feed Tracking can enable tracking of field history for the Close Date field on the Opportunity feed. Creating an Opportunity outbound message and activating Historical Trending for Opportunities are not valid configurations for this requirement.

To allow users access to Flows, Salesforce offers multiple integration points:

A. Quick Action: Flows can be initiated from record pages, the app utility bar, or global actions using Quick Actions. This allows users to execute flows relevant to specific records or global processes.

C. Flow Launcher: A component available in Lightning App Builder that enables users to start flows directly from a Lightning page.

Steps to set up these features:

For Quick Actions, navigate to Setup ? Object Manager ? select object ? Buttons, Links, and Actions ? New Action ? Action Type (Flow).

For Flow Launcher, navigate to Lightning App Builder ? select the page ? drag the Flow component to the desired section of the page ? configure it to launch the specific flow.

For more information on integrating Flows, check the Salesforce documentation on Flow Distribution.

 Apex. This is correct because Apex is a programming language that can perform complex logic and manipulate data in Salesforce. Apex can be used to create a trigger on the opportunity object that copies the value of the billing state from the related account record when the opportunity is created, and prevents it from being changed afterwards. The other options are not suitable for this requirement because they either cannot copy data from a related object (formula field, roll-up summary field) or cannot prevent data from being changed (workflow).

Create a Chatter stream. This is correct because a Chatter stream allows users to follow multiple records and people in one feed, and filter the feed by selecting a stream.

 The best feature to use to ensure consistent case priority entry is Path. Path allows users to see key fields and guidance for each stage of a process, such as a case lifecycle. Path can also enforce data quality by making certain fields required at each stage. See [this article] for more information on Path.

The best practice that the app builder should follow when building out automation is one record change process per object. A record change process is a type of process in Process Builder that starts when a record is created or updated. Having one record change process per object can avoid conflicts or errors when multiple processes try to update the same record at the same time. Option A is incorrect because one workflow rule per object is not a best practice, as workflow rules are considered legacy tools and have limitations compared to Process Builder. Option B is incorrect because one flow per object is not a best practice, as flows are more complex and require more resources than processes. Option C is incorrect because one invocable process per object is not a best practice, as invocable processes are used to invoke other processes from within a process or a flow.

The requirement specifies:

Subset of production data (not all data)

Under 5 GB of data

Periodic refresh (every weekend)

A Partial Copy sandbox fits these requirements perfectly — it includes sample data defined by a sandbox template, up to 5 GB, and has a refresh interval of 5 days (the shortest interval available besides Developer types).

Why A (Partial Copy) is correct:Exact Extract:“A Partial Copy sandbox includes your organization’s metadata and a sample of your production data as defined by a sandbox template. The maximum size is 5 GB and the refresh interval is 5 days.” — Salesforce Help | Sandbox Types and Templates

Why not B (Full Copy):Full Copy includes all production data and has a 29-day refresh interval.

Why not C or D:Developer and Developer Pro sandboxes contain metadata only and no production data.

The record will not save and the validation rule’s error message will be displayed because the field update will violate the validation rule. The validation rule will prevent the record from being saved if the Industry field is longer than 6 characters, and Technology is 10 characters long.

A Partial Copy Sandbox is designed for testing and development with a subset of production data based on a sandbox template. Since the question mentions that a sandbox template was created for certain objects (Accounts, Projects, Project Milestones), the environment must support template-based sampling, which only Partial Copy and Full sandboxes do.

Why B (Partial Copy) is correct:Exact Extract:“A Partial Copy sandbox includes your organization’s metadata and a sample of your production data as defined by a sandbox template. Use it for quality assurance tasks, integration testing, and user training.” — Salesforce Help | Sandbox Types and TemplatesDeveloper and Developer Pro sandboxes do not support sandbox templates.

Why B (Partial Copy) is correct:Exact Extract:“A Partial Copy sandbox includes your organization’s metadata and a sample of your production data as defined by a sandbox template. Use it for quality assurance tasks, integration testing, and user training.” — Salesforce Help | Sandbox Types and TemplatesDeveloper and Developer Pro sandboxes do not support sandbox templates.

Why not A or C:Developer and Developer Pro contain metadata only — no data templates or sample data.

Why not D:Scratch Orgs are for source-driven development and are not created from sandbox templates.

Given the need to automate a welcome email including a customized survey with customization requirements and a tight timeline, the best approach is:

Use Salesforce Flow to build the survey declaratively to meet the criteria and send it to the customer as an email (B). Flow is a powerful tool for automation in Salesforce, allowing the creation of complex workflows and user interactions without needing to write custom code. It can be used to build a survey and integrate it with email services for automated dispatch.

Working with a developer to create custom Apex and LWC (A) might meet the criteria but would not align with the limited time frame. Managed (C) and unmanaged packages (D) from AppExchange can provide pre-built solutions, but they may not offer the needed customization or could require more setup time than building directly in Flow.

Reference for automating processes with Salesforce Flow:

Salesforce Flow: https://help.salesforce.com/articleView?id=sf.flow_considerations_design.htm &type=5

The two components that could be included on the layout to display the actions are the Highlights panel and the Path. The Highlights panel is a component that shows key information and actions for a record. It can display up to 10 actions from the Mobile & Lightning Actions section of the page layout. The Path is a component that shows the stages of a process, such as a sales process or a service process. It can display up to 5 actions from the Mobile & Lightning Actions section of the page layout. The Chatter and Activities components do not display actions from the Mobile & Lightning Actions section of the page layout. They display other types of actions, such as posting, commenting, liking, logging a call, creating a task, or sending an email.

All data should be backed up before converting a text field to a picklist, as some data may be lost or truncated during the conversion. Changing a field type will remove existing field history, as the history tracking values are not converted

The two considerations that should be made are: The Star records are all required to have an existing value in their Galaxy field. This is a prerequisite for converting a lookup relationship to a master-detail relationship. A lookup relationship is an optional relationship that links two objects together, but does not enforce referential integrity or cascade delete. A master-detail relationship is a required relationship that links two objects together and enforces referential integrity and cascade delete. To convert a lookup relationship to a master-detail relationship, all child records must have a value in their lookup field that references an existing parent record. The Galaxy object has fewer than two existing master-detail relationships. This is another prerequisite for converting a lookup relationship to a master-detail relationship. An object can have up to two master-detail relationships with other objects and can act as both the parent and child in different relationships. To convert a lookup relationship to a master-detail relationship, the parent object must have fewer than two existing master-detail relationships with other objects. The Galaxy object is required to contain existing roll-up summary fields is not a valid consideration, as it is not related to converting a lookup relationship to a master-detail relationship. 

Apex unit test failures can cause a package installation to fail. According to the Salesforce documentation, “If your package contains Apex code, all tests must complete successfully for your package to install.” Incorrect license types, package features not compatible, and object limits exceeded are not valid reasons for a package installation failure.

 Two Master-detail relationships on a new custom object is how an app builder should configure the data model to create a relationship between Contact and Solar Project objects where each Contact can be related to multiple Solar Project objects, and each Solar Project can have multiple Contacts associated with it. This is an example of a many-to-many relationship that requires a junction object with two master-detail relationships. One Master-detail relationship on Contact and one Master-detail relationship on Solar Project, two Lookup relationships on a new custom object, and one Lookup relationship on Contact and one Lookup relationship on Solar Project are not valid or correct ways to create a many-to-many relationship.

The formula that should be used to select the contact’s preferred name for email communications is IF(NOT(BLANKVALUE(Nickname__c)),Nickname__c, FirstName). This formula checks if the Nickname__c field is blank or null, and if not, it returns the value of the Nickname__c field. Otherwise, it returns the value of the FirstName field.

Sharing rules and manual sharing are two features that can extend record access beyond the organization-wide defaults. Sharing rules are automatic rules that grant access to groups of users based on certain criteria, such as role, public group, or territory. Manual sharing is a manual way of granting access to individual users or groups by the record owner or someone above them in the role hierarchy. Option B and C are not features that extend record access.

When a master-detail relationship is created between two objects, Salesforce automatically creates a standard report type that allows users to report on the parent and child together.

Why A (Galaxy__c with Star__c) is correct:Exact Extract:“When you create a master-detail relationship, Salesforce automatically creates a primary report type that includes records from both the master and its detail.” — Salesforce Help | Standard Report TypesTherefore, a “Galaxy__c with Star__c” report type is automatically generated, allowing users to create reports showing all child records (Star__c) related to each parent (Galaxy__c).

Why A (Galaxy__c with Star__c) is correct:Exact Extract:“When you create a master-detail relationship, Salesforce automatically creates a primary report type that includes records from both the master and its detail.” — Salesforce Help | Standard Report TypesTherefore, a “Galaxy__c with Star__c” report type is automatically generated, allowing users to create reports showing all child records (Star__c) related to each parent (Galaxy__c).

Why not B:The parent-to-child relationship drives the report type. A “Star__c with Galaxy__c” type is not automatically created.

Why not C or D:Custom report types are only needed if you want to include additional related objects or modify relationships; Salesforce automatically provides one for master-detail pairs.

Update the organization-wide defaults and create a criteria based sharing rule are two actions that an app builder should complete to implement the change of moving to a more restrictive sharing model while allowing the Sales team to access all account records with the sales record type. Updating the organization-wide defaults can set the baseline level of access for accounts, and creating a criteria based sharing rule can grant additional access based on record type. Updating the Sales profile and creating an owner-based sharing rule are not necessary or sufficient actions for this change.

A flow is an application that automates a business process by collecting data and performing operations in your org or an external system. Flows can also manipulate data in your org by creating, updating, deleting, or submitting records for approval. You can use flows to update fields on related records when a certain event occurs, such as closing a work order. In this case, a flow can be used to update the last maintenance date field on the Asset record when a maintenance work order gets closed.

The app builder needs to do two steps to make the custom Lightning App available to the internal users at Universal Containers:

Create a subdomain using My Domain: My Domain is a feature that allows an organization to set up a custom domain name for their Salesforce instance. This is required to use custom Lightning components and apps in Salesforce1.

Build a Custom Tab for the app: A custom tab is a tab that displays any custom object or web page in Salesforce. This is required to make the custom Lightning App accessible from the navigation menu or app launcher2. Option A and B are not necessary steps to make the custom Lightning App available to the internal users.

The feature that the app builder should use to create easy access to the document is a custom detail page link on the Contract object. A custom detail page link is a type of custom button or link that can display a URL or execute JavaScript when clicked. The app builder can create a custom detail page link on the Contract object that displays the pricing guidelines document in a new window or tab. Option A is incorrect because a quick action on the Contracts object is not suitable for this requirement, as quick actions are used to create or update records, log calls, send emails, or launch flows. Option B is incorrect because a quick action on the Account object is not suitable for this requirement, as quick actions are not related to the Contract object. Option C is incorrect because a custom detail page link on the Account object is not suitable for this requirement, as custom detail page links are not related to the Contract object.

A template for a new Lightning record page determines how the page is divided into regions. The template is responsive and will automatically adapt to the device being used to view the record page. The template can be changed after the initial save, and users do not need “View All Data” permissions for the object

The app builder should use the CASESAFEID(Id) formula to create this new field. The CASESAFEID function returns the 18-digit case-insensitive version of the record ID, which is unique for each record in Salesforce. The 18-digit record ID is useful for exporting data to external systems that require case-sensitive IDs1. Option A, C, and D are not formulas that can return the 18-digit record ID.

 A geolocation field can be used to capture the coordinates of a location in latitude and longitude. This field type can also be used in reports, formulas, validation rules, and Apex

 The app builder should recommend building a global action to create Contacts. A global action allows users to create records quickly from any page in Salesforce on their mobile devices. The app builder can also specify predefined values for some fields in the global action, such as Account Name or Phone Number, to make data entry easier for users. Option A is incorrect because customizing the mobile menu to move Contacts to the top does not help users create new contacts quickly or follow up later. Option C is incorrect because adding a compact layout to Contacts does not help users create new contacts quickly or follow up later, but rather shows them more fields on record detail pages or list views. Option D is incorrect because using Path and setting pre-defined values does not help users create new contacts quickly or follow up later, but rather guides them through different stages of a record.

The app builder should use two tools to automate this process:

Process Builder: This is a type of automation tool that can execute actions based on certain criteria. In this case, the process builder can have a criteria that evaluates if an opportunity goes to the closed won stage, and then execute an action that posts a message to a Chatter group.

Workflow: This is another type of automation tool that can execute actions based on certain criteria. In this case, the workflow can have a criteria that evaluates if an opportunity goes to the closed won stage, and then execute an action that posts a message to a Chatter group. Option A and C are not tools that can automate this process.

The common items that can be moved using a change set are custom object, Apex class, and custom field. These are metadata components that can be deployed from one environment to another using change sets. Web-to-lead and standard fields are not metadata components that can be moved using change sets.

The best solution to enable reps to see and access the most-used components from anywhere within the app without leaving the page they are working on is Utility bar. This is a footer that can be added to any Lightning app and can contain tools such as history, notes, or softphone. Favorites, home page, and global actions are not solutions that provide access to components from anywhere within the app. See [this article] for more information on Utility bar.

 Marking stage dependent fields as required on the Opportunity page layout is a good solution to improve efficiency and data quality, as it ensures that users enter the necessary information for each stage of the sales process. Adding a Path component with fields and instructions aligning to stages on the Opportunity is another good solution to improve efficiency and collaboration, as it provides guidance and best practices for users to move the Opportunity along the sales cycle. Using two Tabs components to separate record information from activities may not be an optimal solution, as it may reduce the visibility and accessibility of important data. Setting up an approval process requiring manager consent at each stage of the Opportunity may not be a feasible solution, as it may introduce unnecessary delays and complexity in the sales process

The Invoice Number field should be a Text field and marked as a unique external ID field. This will allow the migration of invoices from an external system while maintaining their original Invoice Number. It will also ensure that each new Invoice created in Salesforce has a unique Invoice Number.

Schema Builder is a tool that allows app builders to view and modify the data model of their Salesforce org. Some of the capabilities of Schema Builder are:

Creating and editing custom objects and fields

Creating and editing relationships between objects

Showing selected objects on a page

Editing custom settings

Schema Builder cannot be used to create a new record type or view page layouts in a new window.

 The best way to configure Account sharing so that community users only see their own Account is to set the account external OWD to private. This will restrict the access to Account records for external users based on the sharing rules and criteria. Creating an account record type, defining an owner-based sharing rule, or defining a permission set will not prevent community users from seeing other accounts.

 A validation rule is a formula that evaluates the data in one or more fields and returns a value of “True” or “False”. Validation rules verify that the data a user enters in a record meets the standards you specify before the user can save the record. In this case, a validation rule can be used to check if the Expected_Close_Date_c field is populated before the Opportunity stage is set to qualified

The app builder should go to the Account object to build these new rollups. A roll-up summary field is a type of field that can aggregate numeric values from child records related to a parent record by a master-detail relationship. The app builder can create two roll-up summary fields on the Account object that count the number of open Opportunities and the number of won Opportunities related to each Account. Lightning App Builder is not a place where the app builder can build these new rollups. Lightning App Builder is a tool that allows the app builder to customize the layout and components of Lightning pages, such as record pages, home pages, or app pages. It cannot create new fields or relationships on objects. Lightning Object Creator is not a place where the app builder can build these new rollups. Lightning Object Creator is a tool that allows the app builder to create custom objects from spreadsheet data by uploading a file and mapping columns to fields. It cannot create roll-up summary fields or relationships on existing objects. Opportunity object is not a place where the app builder can build these new rollups. The Opportunity object is the child object in the relationship with the Account object, and roll-up summary fields can only be created on the parent object.

 Create a validation rule on the Account object is how the app builder can keep accounts with open opportunities from being deleted. According to the Salesforce documentation, “Validation rules verify that data entered by users in records meet the standards you specify before they can save it.” A validation rule can check if an account has any open opportunities and display an error message if someone tries to delete it. Create an Apex trigger on the Account object, remove the delete button on the account layout, and remove the Delete permission from the Sales Rep profile are not valid or sufficient solutions for this requirement.

The requirement specifies that when the Close Date is delayed by more than 60 days, the record must go through review by both the manager and VP of Sales — this implies an approval process or Flow-initiated approval is needed, not just a restriction.

Why B (Flow) is correct:A Record-Triggered Flow can be configured to detect when the Opportunity Close Date changes by more than 60 days and then automatically submit the record for approval.Exact Extract:“You can use a flow to automatically submit records for approval when they meet certain criteria.” — Salesforce Help | Flow and Approval Processes

Why C (Approval Process) is correct:The approval process enforces the review by both the manager and VP, ensuring a controlled approval sequence.Exact Extract:“An approval process automates how records are approved in Salesforce. Each approval process specifies the steps necessary for a record to be approved and who must approve it.” — Salesforce Help | Approval ProcessesYou can configure multiple approvers and specify that both must approve (“Unanimous Approval”).

Why not A (Validation Rule):A validation rule would only block saving but would not trigger a review or approval.

Why not D (Formula Field):Formula fields are read-only and cannot trigger workflow or approval actions directly.

References (Salesforce Platform App Builder documentation / Study Guide topics):

Salesforce Help | Flow Builder and Approval Processes

Salesforce Help | Approval Processes

Salesforce Platform App Builder Exam Guide | Business Logic and Process Automation

To manage field editability based on the opportunity status:

C. Use field-level security on page layouts with record types to restrict editing fields. This combination allows for different layouts and editable fields based on the status of the record (e.g., closed or open).

Steps to implement:

Create or adjust record types for open and closed opportunities.

For each record type, create a specific page layout.

On the page layout for closed opportunities, set the majority of fields to read-only using field-level security, except for the 'Post-Close Follow-up Date' and 'Post-Close Follow-up Comments' fields.

Assign the appropriate page layouts to the respective record types.

Update profiles or permission sets to use these record types and page layouts accordingly.

This setup ensures that sales reps can modify fields only when the opportunity is open, and the sales operations team can edit specific fields after closure.

For more information on using record types and page layouts, check Salesforce's documentation on Record Types.

For a customer service representative to collect information through a series of question prompts:

B. Flow. Salesforce Flows allow for the creation of guided interactions that can prompt users for information in a step-by-step manner.

Steps to create a flow for this purpose:

Navigate to Setup ? Flows.

Click on 'New Flow' and select a Screen Flow to interactively prompt users.

Design the flow with Screen elements for each question.

Add logic to process responses as necessary.

Save and activate the flow.

Embed or link the flow in a relevant location accessible to the service representative, such as on a record page or in the utility bar.

Flows provide a flexible and powerful way to interactively gather and process customer data in real time.

For detailed guidance on creating Flows, see Salesforce's Flow Builder documentation.

The solution that an app builder should use to meet this requirement is master-detail relationship. A master-detail relationship is a type of relationship that creates a parent-child relationship between two objects, where the child records inherit the sharing and security settings of their parent record. The app builder can create a master-detail relationship between Supplier__c and SupplierItem__c objects, where Supplier__c is the parent object and SupplierItem__c is the child object. This way, when a Supplier__c record is deleted, all related SupplierItem__c records are also deleted automatically. Option A is incorrect because many-to-many relationship is not suitable for this requirement, as many-to-many relationship allows two objects to be linked in both directions through a junction object, but does not support cascading delete. Option B is incorrect because indirect lookup relationship is not suitable for this requirement, as indirect lookup relationship allows an external object to link with another object using an external ID field, but does not support cascading delete. Option C is incorrect because hierarchical relationship is not suitable for this requirement, as hierarchical relationship allows users to use a lookup field that links an object with itself, but does not support cascading delete.

For an app builder who needs to ensure all fields from the page layout are visible on a Lightning Record Page after using the Lightning Object Creator, the correct component to use is:

Record Detail (C). The Record Detail component automatically displays all fields that are included on the assigned page layout for the object. It is designed to reflect the layout configuration and is the simplest way to ensure all fields are presented as configured in the layout editor.

Highlights Panel (A) is used primarily to display key fields at the top of the record page, providing a summary view rather than full field visibility. Recommendations (B) is used for displaying prompts or suggestions and does not display record fields. Path (D) is useful for displaying stages in a process (like sales stages or service processes) and does not show field data directly.

Reference for setting up Lightning Record Pages and using components effectively:

Lightning Record Pages: https://help.salesforce.com/articleView?id=sf.lightning_page_components.htm &type=5

Two conditions that can prevent inline editing on a list view are if the list view selected is the recently viewed list view, or if the list view contains more than one record type. The recently viewed list view does not support inline editing, as it is not based on a single object. The list view must have a single record type to enable inline editing, as different record types may have different fields and values

The validation rule should be AND(ISNEW(), ISBLANK(Lead.Owner:User.Id)). This rule will prevent saving a new lead record if the owner is not a user. This will ensure that campaign members have a sales owner. Option A is incorrect because it will prevent saving any lead record if the owner is blank, which is not the requirement. Option B is incorrect because it will prevent saving an existing lead record if the owner is a queue, which is not the requirement. Option D is incorrect because it will prevent saving any lead record if the owner is a queue, which is not the requirement.

The "Accordion" Lightning component is designed to break up content into collapsible sections. This component would be suitable for managing the visibility of large numbers of fields by grouping them into separate tabs or sections that can expand and collapse. This makes navigation easier and declutters the interface.

A: Highlights panel is used for displaying key record information at the top of the page and is not designed for managing multiple fields.

B: Record detail displays all fields on a single layout, which does not suit the requirement to break up the fields.

C: Field section does not exist as a standard Lightning component. Reference: Accordion Component in the Lightning Component Library

 The app builder needs to have NOT(ISBLANK([Lead].OwnerId)) in the criteria to ensure the process runs without error. This formula checks if the OwnerId field on the Lead object is not blank, which means that the lead is owned by a user or a queue. This will prevent the process from running on leads that are not owned by anyone, which could cause an error. Option A, B, and C are not formulas that can ensure the process runs without error.

When a record is submitted for approval, Salesforce automatically locks it, preventing further edits until it is approved, rejected, or recalled.

Why A (Record Lock) is correct:Exact Extract:“When a record is submitted for approval, Salesforce automatically locks the record to prevent users from editing it unless they have ‘Modify All Data’ permission or are designated as an approver.” — Salesforce Help | Approval Processes OverviewThus, the user will receive a message indicating that the record is locked and cannot be edited.

Why A (Record Lock) is correct:Exact Extract:“When a record is submitted for approval, Salesforce automatically locks the record to prevent users from editing it unless they have ‘Modify All Data’ permission or are designated as an approver.” — Salesforce Help | Approval Processes OverviewThus, the user will receive a message indicating that the record is locked and cannot be edited.

Why not B or C:Once locked, no field (including Description) is editable by the submitter.

Why not D:Ownership does not change upon approval submission.

 To create “with” or “without” reports on the new custom object, a custom report type is needed. A custom report type defines the relationship between one or more standard or custom objects for reporting purposes. It allows users to select which fields they want to display in their reports and filter by related objects. 

 An app builder can go to two places to see a list of available custom Lightning components in their org:

Lightning App Builder: This is a tool that allows an app builder to create and customize Lightning pages using drag-and-drop components. The app builder can see the list of custom Lightning components in the Custom section of the Lightning Components pane1.

Lightning Components in Setup: This is a setup menu that allows an app builder to view, create, edit, and delete custom Lightning components in their org. The app builder can see the list of custom Lightning components in the Lightning Components section of the Setup menu2. Option A and B are not places where an app builder can see a list of custom Lightning components.