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

Changing the data type of a field used in an apex class from number to text will require the app builder to perform additional steps in order to retain existing functionalities. This is because changing the data type of a field may affect the apex code that references or manipulates the field value, and may cause compilation errors or unexpected results. The app builder will need to update the apex code to handle the new data type and ensure that the logic and calculations are still correct. Option B is incorrect because changing the data type of a field used in a report from a text to an encrypted field will not require additional steps, as encrypted fields can still be used in reports with some limitations. Option C is incorrect because changing the data type of a field used as an external id from number to text will not require additional steps, as external id fields can be either number or text. Option D is incorrect because changing the data type of a field used in lead conversion from number to text will not require additional steps, as lead conversion fields can be mapped regardless of their data types.

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.

To display a weather map component on a Lightning record page conditionally:

A. Component visibility should be used. This feature in the Lightning App Builder allows components on a Lightning page to be displayed based on specific criteria, such as field values or user attributes. In this case, the app builder can set the visibility of the weather map component to only appear when a house is scheduled for a showing based on the relevant field values.

For more details on setting up conditional component visibility, review the guide on Dynamic Lightning Pages.

 The app builder should use the Path component to meet the requirement of tracking different fields at each stage of the Opportunity sales process. The Path component is a Lightning component that displays the key fields and guidance for each stage of a standard or custom picklist field, such as the Opportunity Stage field. The app builder can configure the Path component to show the fields that need to be filled out and provide recommendations and sales strategies for each stage3. Option A, B, and C are not configuration steps that can meet this requirement.

 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.

To restrict visibility of the Jupiter field on the Solar System object specifically to users with the Outer Planets profile:

C. Field-level security (FLS). This allows the app builder to control access to fields based on user profiles.

Steps to set up field-level security:

Navigate to Setup → Object Manager → Solar System.

Select Fields & Relationships → Jupiter field.

Click Field-Level Security.

For all profiles except Outer Planets, set the Visible option to unchecked, ensuring these users cannot see the field.

For the Outer Planets profile, check Visible to grant access.

This configuration ensures that only users with the Outer Planets profile can view the Jupiter field.

For more information on field-level security, check Salesforce's guide on Field-Level Security.

A managed package from AppExchange is a custom solution that is developed by a third-party provider and can be installed in Salesforce. A managed package can be easily updated by the provider without affecting the existing functionality or customizations. This makes it suitable for the app builder’s requirement of ease of updates. Option B, C, and D are not as easy to update as a managed package.

The formula for creating a visual indicator flag on each case based on the case priority should use the IMAGE and CASE functions. The IMAGE function returns an image for a given URL, and the CASE function evaluates an expression and returns a value based on that expression. Option A and D use these functions correctly, while option B and C do not.

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.

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.

If an employee attempts to edit the description field after submitting an opportunity for approval, they will be presented with a ‘Record Lock’ notification. This means that the record is locked for editing while it is in the approval process and only users with the “Modify All” permission or users above them in the role hierarchy can edit it. [Source]

Sales reps are forgetting to manually submit the record for approval. The correct declarative solution is to automate the submission when conditions are met — in this case, when the Opportunity Close Date is pushed more than 30 days.

This can be achieved using Flow Builder or Process Builder (deprecated) to automatically submit the record into the existing approval process.

Why C (Submit the record for approval from an automated process) is correct:Exact Extract:“You can automatically submit a record for approval from a process or flow when specified criteria are met.” — Salesforce Help | Automate Record Approval with FlowThis ensures the approval process runs automatically whenever the rule is triggered, eliminating user dependency.

Why C (Submit the record for approval from an automated process) is correct:Exact Extract:“You can automatically submit a record for approval from a process or flow when specified criteria are met.” — Salesforce Help | Automate Record Approval with FlowThis ensures the approval process runs automatically whenever the rule is triggered, eliminating user dependency.

Why not A:The “API Enabled” permission allows programmatic access; it has no impact on triggering approvals.

Why not B:A validation rule and email alert only notify; they do not submit the record into the approval process.

Why not D:Changing entry criteria doesn’t auto-submit; it only defines which records can enter if submitted.

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.

To create a custom object along with multiple fields and relationships efficiently from a single interface, the Schema Builder is the ideal tool:

A. Schema Builder. This graphical tool provides a drag-and-drop interface for creating and modifying objects and fields in Salesforce, allowing for a visual layout of database schema.

Steps to use Schema Builder:

Go to Setup → Schema Builder.

Drag the 'Object' element into the schema area to create a new custom object.

Define the object's properties (e.g., label, API name).

Drag field elements like Text, Number, or Lookup into the object to create fields.

Configure each field's properties according to your requirements.

Connect objects via lookup or master-detail relationships by dragging the relationship fields between them.

Save the layout to create all elements in Salesforce.

For more information, review Salesforce's Schema Builder documentation.

 Global actions can be accessed anywhere actions are pages, feed and Chatter groups. This is correct because global actions are not tied to a specific object, and they can be added to any page that supports actions, such as record pages, home pages, feed pages, and Chatter groups.

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.

AppExchange is a marketplace where app builders can find prebuilt resources to help with migration and adoption projects. AppExchange offers apps, components, solutions, and consulting services that can assist with moving from Classic to Lightning Experience. Import Wizard, Lightning Object Creator, and Flow Builder are not sources of prebuilt resources, but tools for data import, object creation, and automation respectively.

When a field is added to an object, it doesn’t automatically appear in custom report types — even if the field is visible and reportable. The app builder must manually add the field to the custom report type layout to make it available in reports.

Why D (Add the field to the custom report type field layout) is correct:Exact Extract:“If a new custom field isn’t available in your report builder, edit the custom report type layout and add the field. Fields created after the report type was built must be added manually.” — Salesforce Help | Custom Report Types

Why not A:Field-level security controls visibility but not inclusion in the report type layout.

Why not B:“Allow Reports” affects whether the entire object is reportable, not individual fields.

Why not C:The “Manage Public Reports” permission allows editing public reports but doesn’t influence field visibility.

The solution that should meet this requirement is updating the support team profile to remove the Bronze record type. This way, the support team users will not be able to create new cases with the Bronze record type, as it will not appear in their record type selection list. Option A is incorrect because updating the organization-wide defaults to private for Case does not affect the record type availability, but rather the record access level. Option C is incorrect because creating permission set group for Case that includes Platinum and Diamond record types does not prevent the support team users from creating new cases with the Bronze record type, as they may still have access to it through their profile. Option D is incorrect because making the record type hidden to support users and updating sharing roles to private does not prevent the support team users from creating new cases with the Bronze record type, as they may still have access to it through their profile.

The steps that the app builder should take to meet these requirements are creating a Partial Copy Sandbox and using a sandbox template. A Partial Copy Sandbox can include data records, exclude confidential objects, and be refreshed weekly. A sandbox template can specify which objects and data are copied from the production org to the sandbox org. Option A is incorrect because creating a Full Sandbox and using a sandbox template is not necessary for this requirement, as Full Sandboxes copy all data and metadata from the production org and can only be refreshed every 29 days. Option B is incorrect because creating a Developer Pro Sandbox and scheduling Data Loader to download selected object data weekly is not feasible for this requirement, as Developer Pro Sandboxes do not include data records by default and Data Loader cannot be scheduled to run weekly. Option D is incorrect because creating a Developer Sandbox and scheduling Data Loader to download selected object data weekly is not feasible for this requirement, as Developer Sandboxes do not include data records by default and Data Loader cannot be scheduled to run weekly.

When multiple objects require the same picklist values, the correct approach is to create a Global Picklist Value Set (also called a Global Value Set). This allows an organization to maintain one centralized list of picklist values that can be reused across multiple picklist fields on different objects.

Why C is correct:Exact Extract:“Global value sets let you share the same picklist values with more than one picklist field. A global value set is a set of shared values that you define once and use in multiple custom picklist fields.” — Salesforce Help | Global Value SetsThis ensures consistent data values, simplifies maintenance, and makes changes automatically available wherever the global picklist is used.

Why C is correct:Exact Extract:“Global value sets let you share the same picklist values with more than one picklist field. A global value set is a set of shared values that you define once and use in multiple custom picklist fields.” — Salesforce Help | Global Value SetsThis ensures consistent data values, simplifies maintenance, and makes changes automatically available wherever the global picklist is used.

Why not A (Related Picklist):“Related Picklist” is not a valid Salesforce feature.

Why not B (Shared Custom Field):Salesforce does not provide a “Shared Custom Field” functionality. Each field belongs to a specific object.

Why not D (Dependent Picklist):Dependent picklists control available values based on another field’s value. They do not allow reuse of a single value list across multiple objects.

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

Salesforce Help | Global Value Sets

Salesforce Help | Picklist Fields

Salesforce Platform App Builder Exam Guide | Data Modeling and Management

A quick action on the Account object can be used to create Opportunity records related to an Account. The quick action can pre-populate some fields based on the Account record, and also allow the user to input some fields. This would improve the process of creating Opportunity records

Set up a delegated approver for the manager is the recommended solution to ensure all of the appropriate deals are reviewed and the leaderboard is up to date. According to the Salesforce documentation, “A delegated approver can approve records that are submitted for approval by users below them in the role hierarchy.” Forwarding the approval request to the manager’s assistant, having the manager log on and reassign the approval request, and using Process Builder to assign a delegated approver are not valid or feasible options.

Lookup is the type of relationship that would be set up to meet the specification of pairing experienced Realtors with new Realtors. According to the Salesforce documentation, “A lookup relationship creates a loose association between objects. The lookup field allows users to select a record from another object.” Indirect lookup is used for junction objects on different platforms. Many-to-many is not a type of relationship, but a result of using junction objects. Master-detail is used for creating parent-child relationships.

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

 Preexisting information will remain even if it was over 255 characters if the app builder tries to convert a preexisting long text area field to text area. However, users will not be able to edit or save records with more than 255 characters in that field until they reduce the number of characters. Preexisting information will not truncate, be lost, or cause an error message.

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.

Sharing rules can be used to extend access to records owned by certain users or roles to other users or roles. In this case, a sharing rule can grant read-only or read/write access to sales-owned accounts to the marketing team

 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.

Configuring a validation rule to require a field for a specific record type is the best way to ensure that important fields are entered and formatted correctly. Updating the important fields to be required on the page layout will not prevent users from entering invalid data using other methods, such as data loader or quick actions. Making a formula field to check the format of the important fields will not prevent users from entering invalid data, but only display a message or an indicator. Creating a workflow rule to check the fields are formatted correctly will not prevent users from entering invalid data, but only trigger an action after the data is saved.

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 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 app builder should recommend a workflow rule to automate this process. A workflow rule is a type of automation tool that can execute actions based on certain criteria. In this case, the workflow rule can have a criterion that evaluates if the DoNotCall checkbox is checked on a Contact record, and then execute a field update action that sets the Phone field to null. Option A, B, and C are not automation tools that can perform this task.

Workflow rule and an outbound message or Process Builder and Apex Code are two ways to integrate Salesforce with an external web service. Workflow rule can define criteria and actions for triggering an outbound message, which is an XML message sent to a designated endpoint URL. Process Builder can invoke Apex Code, which is a programming language that can make callouts to external web services using HTTP requests. Flow Builder and an outbound message or Process Builder and an outbound message are not possible combinations.

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.

The opportunity standard fields that are available to be configured directly are Stage, Lead Source, and Type. These fields can be modified by editing their picklist values, adding or removing values, or changing their default values. Option A is incorrect because Forecast Category is not a standard field on the opportunity object, but rather a system field that is automatically derived from the Stage field.

Research and evaluate products available on AppExchange to send mass emails is the action that the app builder should take to meet the requirement of broadcasting an email to 7,000 contacts in Salesforce on a regular basis. AppExchange is a marketplace where app builders can find products or solutions that can extend Salesforce functionality. There are many products on AppExchange that can send mass emails without hitting the Salesforce limit. Request Salesforce increase the number of maximum daily emails, develop Apex code and Lightning web component to send daily emails, and export Contacts to a CSV file and use an email client to send the emails are not valid or recommended actions.

Schema Builder is a tool that presents a comprehensive view of all relationships in one place. It allows app builders to see how objects are connected and create new relationships. Lightning Object Creator, Object Manager, and Lightning Record Page are not tools for viewing relationships, but for creating objects, managing fields, and customizing record pages respectively.

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.

 An external ID field can be a number field or a text field, but not a URL field or a phone field. A URL field is used to store web addresses and a phone field is used to store phone numbers. An external ID field is used to store unique identifiers from an external system and it can be used for upsert operations

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.

The primary object selection is locked once the custom report type has been saved. This means that the app builder cannot change the primary object later. The other options are not true.

Add the standard Chatter feed component is how an app builder can add the Chatter feed to a custom object record page. According to the Salesforce documentation, “The Chatter Feed component displays updates about records in your org.” Add the standard related list component, add a custom Chatter feed component, and add the Chatter feed component from the AppExchange are not valid or necessary options.

To deploy a new account detail page layout from sandbox to production, an app builder should include three components in the change set:

Detail page layout: The page layout defines the arrangement of fields, buttons, related lists, and other components on a record detail or edit page. It also controls which fields are required or read-only for users. Source

Custom fields: Custom fields are fields that are created by users to store additional information on standard or custom objects. Custom fields can have different data types, such as text, number, date, picklist, etc. Source

Custom actions: Custom actions are actions that are created by users to extend the functionality of standard or custom objects. Custom actions can be global or object-specific, and they can invoke different tools such as Lightning components, Visualforce pages, flows, etc. [Source]

 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.

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

Since there is a master-detail relationship between Property__c (master) and Offer__c (detail), Salesforce natively supports using Roll-up Summary fields on the master object to summarize values from the related child records.

Why A (Roll-up Summary) is correct:Exact Extract:“A roll-up summary field calculates values from related records, such as those in a related list, on a master record. You can count the number of related records, determine the sum, minimum, or maximum value of a field in the related records.” — Salesforce Help | Roll-Up Summary FieldsTherefore, DR can create a Roll-up Summary field on Property__c that uses the MAX function on the “Offer Value” field from Offer__c.

Why A (Roll-up Summary) is correct:Exact Extract:“A roll-up summary field calculates values from related records, such as those in a related list, on a master record. You can count the number of related records, determine the sum, minimum, or maximum value of a field in the related records.” — Salesforce Help | Roll-Up Summary FieldsTherefore, DR can create a Roll-up Summary field on Property__c that uses the MAX function on the “Offer Value” field from Offer__c.

Why not B, C, or D:

Rich Text Area and Text Area (Long) store text, not calculated numeric data.

Multi-select Picklist is used for multiple selectable text options, not calculations.

When configuring an approval process, the available initial submission actions (triggered when a record is first submitted for approval) include sending notifications, creating tasks, and sending outbound messages.

Why A (Outbound Message) is correct:Exact Extract:“Outbound messages can be configured as approval actions to send information to external systems when a record is submitted or approved.” — Salesforce Help | Approval Processes Overview

Why C (Task) is correct:Exact Extract:“Approval processes can create tasks for users as part of approval actions to ensure follow-up on record changes.” — Salesforce Help | Approval Actions

Why D (Email Alert) is correct:Exact Extract:“Email alerts can be sent automatically when a record is submitted, approved, rejected, or recalled.” — Salesforce Help | Approval Processes Overview

Why not B (Invocable Flow):Invocable Flows are not selectable as approval actions — they are used in Process Builder or Flow itself, not Approval Process configuration.

Why not E (Decision Element):Decision elements are Flow components, not part of the Approval Process action set.

The feature that the app builder should use to solve this issue is component visibility filter. A component visibility filter is a setting that can be applied to a Lightning component on a record page to control when the component is hidden or displayed based on certain conditions. The app builder can use a component visibility filter to hide the component from users with a Marketing profile. Option A is incorrect because detail page layouts are not related to Lightning components, but rather the fields and related lists that appear on record detail pages. Option C is incorrect because field-level security is not related to Lightning components, but rather the access level of fields for different profiles or permission sets. Option D is incorrect because AppExchange is not related to Lightning components, but rather an online marketplace where users can find and install apps and components.

To ensure auditing users can access records in the Case_Issue__c junction object, the correct data permissions on related records must be established:

D. Read-Only access on Case and Issue__c. Users need read-only access to both Case and Issue__c objects to view associated Case_Issue__c junction object records properly. This is because access to junction object records in Salesforce is determined by the user's access levels to the parent records in a relationship.

Steps to configure access:

Navigate to Setup → Profiles or Permission Sets.

Select the profile or permission set of the auditing users.

Under Object Settings, adjust the permissions for Case and Issue__c to at least 'Read-Only'.

Ensure that users have visibility to the Case_Issue__c object itself.

This configuration allows users to view the details of cases and issues as they audit the junction object records.

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.

The best way to solve this problem is to filter components by device using Form Factor. Form Factor is an attribute that can be applied to components on a Lightning record page to control their visibility based on the device type, such as desktop, phone, or tablet. By using Form Factor, the app builder can hide some components that are not relevant for mobile users, such as charts or reports, and show only the components that are necessary for data entry, such as fields or actions. This way, the mobile users do not have to scroll through all the components and can enter data more easily. Reordering the fields may not solve the problem completely, as there may still be too many components on the page for mobile users. Updating the training documentation may not help either, as it does not address the root cause of the problem, which is the layout of the page. Deselecting the phone radio button on the Lightning record page assignment may not be desirable, as it will prevent mobile users from accessing the record page at all, which may affect their productivity and functionality.

The app builder should know that a field type change is included in the change set and that it can cause a delay in the deployment. A field type change is a change that modifies the data type of an existing field, such as changing a text field to a number field. A field type change can affect many aspects of Salesforce functionality, such as validation rules, formulas, workflows, reports, dashboards, and more. Therefore, deploying a change set that contains a field type change can take longer than usual and require more testing and verification. Option A, C, and D are not changes that can cause a delay in the deployment.

The new object should have a lookup relationship to the Opportunity object. A lookup relationship creates a link between two objects and allows related records to be viewed in a related list. This can be used to track installation information for each opportunity and give sales reps visibility of all the installations associated with their opportunities. Option B, C, and D are not appropriate for this requirement.

Ursa Major Solar requires a new field called Planet Details on the Planet object, where users can write detailed descriptions that can include pictures and links. The Rich Text Area field type is the best fit for this requirement.

Option B (Rich Text Area): A Rich Text Area field allows users to enter text with formatting options such as bold, italics, bullets, and numbering. Additionally, it supports inserting images and hyperlinks, which matches the requirement of including pictures and links in the description.

Rich Text Area Fields

Option A (Long Text Area): A Long Text Area field allows for lengthy text input but does not support formatting or embedding of images and links, which are necessary in this case.

Option C (Multi-Select Picklist): A Multi-Select Picklist allows users to select multiple values from a list but is not suitable for detailed descriptions or embedding images and links.

Option D (URL): A URL field is used to store and display a link but does not support text input or embedding images.

In summary, the Rich Text Area field type should be used because it allows formatted text, images, and links, which are required for the Planet Details field.

 To control access to the Review custom object such that only the HR department and the submitting employee can see the reviews, the following steps should be taken:

A. Disable Grant Access Using Hierarchies:By default, Salesforce allows users higher in the role hierarchy to access records owned by users lower in the hierarchy. Since reviews should only be visible to HR and the submitting employee, you need to disable Grant Access Using Hierarchies on the Review object to prevent anyone else in the hierarchy from automatically gaining access to these records.

Record Access and Role Hierarchies

C. Create a criteria-based Sharing Rule for the HR Department:With the organization-wide default (OWD) set to Private, you’ll need to create a criteria-based sharing rule to ensure that HR users can view the Review records. This rule would give HR access to the records based on a specified condition, such as all records of the Review object.

Guided Action Flows (Screen Flows embedded in Lightning record pages) can walk agents through required steps — such as verifying identity — before proceeding.

Why A (Guided Action Flows) is correct:Exact Extract:“Use Guided Action Flows in Lightning App Builder to help agents complete processes in a step-by-step format directly on a record page.” — Salesforce Help | Guided Action FlowsThe app builder can embed a Screen Flow that prompts the agent to verify identity (e.g., asking security questions), then allows access or marks verification complete.

Why A (Guided Action Flows) is correct:Exact Extract:“Use Guided Action Flows in Lightning App Builder to help agents complete processes in a step-by-step format directly on a record page.” — Salesforce Help | Guided Action FlowsThe app builder can embed a Screen Flow that prompts the agent to verify identity (e.g., asking security questions), then allows access or marks verification complete.

Why not B:Path helps users track record stages, not enforce procedural steps.

Why not C:Surveys are used for feedback collection after cases, not real-time identity verification.

Why not D:Validation Rules enforce data quality on record save, not process guidance.

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. 

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

 Creating a formula field on the Contact object and setting the value of the formula to TEXT(Account.Account_Region__c) would reflect the region of the related account on the contact record and stay in sync if the value changes on the account. This is the most efficient and maintainable way to meet the requirement. Creating a workflow rule or a picklist field would require additional configuration and complexity

 Create a page layout with the field and use field-level security to hide the field from all other users is how the app builder should meet the requirement of making the comment field on Review private to anyone outside of HR department. Field-level security can control which profiles can view or edit a field on a record. Create an Apex sharing rule, create a sharing rule to share the field with VP of HR with Role and Subordinates, and create a page layout with the field for HR users and another page layout without the field for all other users are not valid or feasible solutions for this requirement.

To meet the requirement of summarizing the number of open and closed cases on an Account, two potential automation solutions can be used:

Option A (AppExchange): Salesforce AppExchange offers various pre-built apps and components, including those for case management, which could provide the functionality to summarize cases and categorize customer support utilization. Many apps can handle complex business requirements like case summary roll-ups and could meet the needs without custom development.

Salesforce AppExchange

Option D (Apex): Apex is Salesforce’s programming language that allows developers to implement custom logic. In this scenario, Apex could be used to create a trigger or scheduled job that calculates the number of open and closed cases and updates the Account record accordingly. Apex would allow full customization of how the open/closed case numbers are calculated and how customer support utilization (high, medium, low) is determined.

The app builder should use the Path feature to provide the functionality that the VP of Sales wants. The Path feature allows an app builder to create a visual representation of the stages in a business process, such as the Opportunity sales process. The app builder can also add key fields, guidance, and resources for each stage to help sales reps gather information and complete tasks4. Option A, C, and D are not features that can provide this functionality.

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

To connect Testimonial__c records with both the submitter’s Contact record and Account record, an app builder should create a master-detail relationship from Testimonial__c to Account and a lookup relationship from Testimonial__c to Contact. A master-detail relationship creates a parent-child relationship between two objects and allows for roll-up summary fields, sharing settings, and cascading actions. A lookup relationship creates a loose association between two objects and allows users to relate records from one object to another. Source

The solution that an app builder should use for this request is a lookup field. A lookup field is a type of relationship field that links two objects together and allows users to select a record from another object. The app builder can create a lookup field on the account object that references the user object and allows users to assign a customer service manager (CSM) to the account. Option A is incorrect because a multi-select picklist field is not suitable for this request, as multi-select picklist fields allow users to select multiple values from a predefined list, not from another object. Option B is incorrect because a picklist field is not suitable for this request, as picklist fields allow users to select one value from a predefined list, not from another object. Option D is incorrect because a text field is not suitable for this request, as text fields allow users to enter any alphanumeric characters, not from another object.

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.

This formula concatenates the four custom fields for the Galactic Vendor’s location into a single text value, separated by commas and spaces. The formula also uses the BR function to insert a line break after the second field, creating two lines of text. Option A, B, and D are not formulas that fulfill the requirement.

To track the total number of trails associated with a park without writing code, the correct actions to take are:

Use a roll-up summary field on the Park record to show the total number of Trails (B). Roll-up summary fields calculate and display a value in a master record based on the values of fields in a detail record. They are used to count, sum, average, or get the minimum/maximum of values in related detail records.

Use a master-detail relationship between the Park and Trail objects (C). Master-detail relationships are necessary for roll-up summary fields as they allow the master object to control certain behaviors of the detail object and summarize data from those detail records.

A formula field (A) cannot dynamically count related records unless those records are linked via a master-detail relationship, and it cannot alone handle counts across related records without such a relationship. A lookup relationship (D) does not support roll-up summaries unless combined with additional tools like triggers or third-party apps, which involve coding or extra configuration outside standard object setup.

For more details, refer to the Salesforce Help documentation on master-detail relationships and roll-up summary fields:

Master-Detail Relationship: https://help.salesforce.com/articleView?id=relationships_considerations.htm &type=5

Roll-Up Summary Fields: https://help.salesforce.com/articleView?id=fields_about_roll_up_summary_fields.htm &type=5

To view a junction object record, a user must have at least read access to both master objects. This is because the junction object inherits the sharing and security settings from both master objects

The app builder should use Web-to-Case to enable visitors to the website to open cases. Web-to-Case is a feature that allows users to create an HTML form that can be embedded into a public-facing website. When visitors fill out and submit the form, a new case is automatically created in Salesforce with the information from the form fields. Web-to-Case can also assign cases to queues or users based on predefined rules and criteria. Outbound message is not a valid tool, as it does not enable visitors to open cases. An outbound message is a type of workflow action that sends a secure XML message to a designated endpoint URL when a record meets certain criteria. An outbound message can be used to integrate Salesforce with external systems or applications. Screen flow is not a valid tool, as it does not enable visitors to open cases from a public-facing website. A screen flow is a type of flow that allows users to create an interactive guided process that can collect, display, and update data from multiple objects within Salesforce. A screen flow can be embedded into Lightning pages or Visualforce pages, but it cannot be exposed to unauthenticated users on a public website. Email-to-Case is not a valid tool, as it does not enable visitors to open cases from a website. Email-to-Case is a feature that allows users to create cases from email messages sent to a specific email address. Email-to-Case can also capture email attachments and thread information and associate them with the case.

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.

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.

The new custom object (“Installation__c”) must store installation details that are related to an Opportunity. Since each installation should be tied directly to a single opportunity, and inherit ownership and visibility from that opportunity (as per “sales reps should have visibility”), a Master-Detail relationship is appropriate.

Why B (Master-Detail) is correct:Exact Extract:“In a master-detail relationship, the detail record inherits the sharing and security settings of its master record.” — Salesforce Help | Relationships OverviewBecause Opportunities already have ownership and sharing settings that determine sales reps’ visibility, making Installation__c the detail record ensures that sales reps automatically see related installations.Exact Extract:“The master-detail relationship closely links objects so that the master record controls certain behaviors of the detail record, such as record ownership, sharing, and deletion.” — Salesforce Help | Master-Detail Relationships

Why B (Master-Detail) is correct:Exact Extract:“In a master-detail relationship, the detail record inherits the sharing and security settings of its master record.” — Salesforce Help | Relationships OverviewBecause Opportunities already have ownership and sharing settings that determine sales reps’ visibility, making Installation__c the detail record ensures that sales reps automatically see related installations.Exact Extract:“The master-detail relationship closely links objects so that the master record controls certain behaviors of the detail record, such as record ownership, sharing, and deletion.” — Salesforce Help | Master-Detail Relationships

Why not A (Many to Many):Many-to-many relationships are only used when multiple records on both sides need to relate (e.g., Opportunities linked to multiple Installations and vice versa). That is not described here.

Why not C (Hierarchical):Hierarchical relationships are only available on the User object.

Why not D (Lookup):Lookup relationships do not automatically grant visibility or inherit ownership, so sales reps might not see all related installations.

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

Salesforce Help | Relationships Overview

Salesforce Help | Master-Detail Relationships

Salesforce Platform App Builder Exam Guide | Data Modeling and Management

The setting for the visibility of custom tabs is default off for all users when they are deployed via change sets without including the profile settings or permission sets. This means that the custom tabs are not visible in any apps or navigation menus for any users unless they are manually added by each user or by an administrator3. Option B, C, and D are not correct settings for the visibility of custom tabs.

 The two recommended solutions for the app builder to give the users appropriate access are creating a criteria based sharing rule to all opportunities with the sales operations public group and adding a permission set with ‘View All" and ‘Modify All’’ opportunity permissions enabled. A criteria based sharing rule can grant read and write access to all opportunities that meet certain criteria to a specified group of users. A permission set can grant additional object-level permissions to users without changing their profiles. Option B is incorrect because adding a manual share for all opportunities with each user on the sales operations team is not scalable or maintainable. Option D is incorrect because creating a criteria-based sharing rule to share all opportunities with the sales operations private group is redundant, as private groups are used to manually share records with individual users or other groups.

An Approval Process is the appropriate feature to manage and enforce that new vendors accept terms on agreements before an opportunity can be closed. This process can be configured to require approvals from designated approvers when certain conditions are met, ensuring that all necessary agreements are in place and validated before proceeding.

A: Email Alert cannot enforce acceptance of terms.

B: Dynamic Action primarily adjusts the user interface based on field values, not process management.

Dynamic actions are a new feature that allow app builders to create custom buttons or actions that can call Lightning Web Components and display them conditionally based on field values or other criteria. Formula fields, AppExchange products, and custom links are not able to call Lightning Web Components.

 A permission set containing the salary record type and assigning it to the appropriate users would allow only those users to create salary applicant records, while still allowing all users to view all applicant records. This is the most granular and flexible way to meet the requirement

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

 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. 

The "Sharing" button should be added to the Account page layout to allow sales reps to view the sharing details of an account record. This button enables users to see how access to the record is granted via roles, groups, and manual sharing.

A: Sharing Hierarchy provides a view of the role hierarchy but does not specifically detail record access.

B: New Task is unrelated to sharing visibility.

D: "Fait" is not recognized in Salesforce context as a valid component or feature. Reference: Sharing an Account in Salesforce Help Documentation

The requirement is time-based (Case in New status > 4 business hours) and requires a notification.

Escalation Rules can monitor case age and trigger escalation or notifications after a specified period.

Flow Builder (Scheduled Path or Scheduled Trigger Flow) can be used to evaluate business hours and send alerts.

Why B (Escalation Rules) is correct:Exact Extract:“Escalation rules automatically escalate cases when they meet certain criteria, such as the age of the case, and can notify users or change ownership.” — Salesforce Help | Case Escalation RulesEscalation rules are ideal for service teams and time-based escalation scenarios.

Why B (Escalation Rules) is correct:Exact Extract:“Escalation rules automatically escalate cases when they meet certain criteria, such as the age of the case, and can notify users or change ownership.” — Salesforce Help | Case Escalation RulesEscalation rules are ideal for service teams and time-based escalation scenarios.

Why D (Flow Builder) is correct:Exact Extract:“Use scheduled paths in record-triggered flows to perform actions after a certain amount of time has passed since the record was created or updated.” — Salesforce Help | Scheduled Paths in Flow BuilderA Scheduled Path in a record-triggered flow can evaluate the Case’s age in hours and send an email alert if the Status remains “New.”

Why D (Flow Builder) is correct:Exact Extract:“Use scheduled paths in record-triggered flows to perform actions after a certain amount of time has passed since the record was created or updated.” — Salesforce Help | Scheduled Paths in Flow BuilderA Scheduled Path in a record-triggered flow can evaluate the Case’s age in hours and send an email alert if the Status remains “New.”

Why not A:Validation Rules prevent saving invalid data but cannot evaluate elapsed time.

Why not C:Scheduled Apex would work technically but is a code-based solution; declarative automation (Flow or Escalation) is preferred for App Builder certification.

Roll-up summaries allow MAX, MIN, SUM, COUNT, and AVG functions on numeric fields from child records related by a master-detail relationship. Roll-up summaries are limited to master-detail relationships and cannot be used with lookup relationships. An object can have up to 40 roll-up summary fields, not 25. An object can have up to 25 relationship fields (master-detail or lookup), not 20.

An indirect lookup relationship is a custom relationship between two objects that are linked by an external ID field. The external ID field must be a custom field on the parent object that has the “External ID” attribute enabled. The child object must be a standard or custom object that is on the detail side of a master-detail or lookup relationship.