Platform-App-Builder Questions and Answers

Schema Builder provides a graphical representation of all standard and custom objects and their field and relationship structure. It’s the best tool for visualizing how data objects are interconnected.

Why D (Schema Builder) is correct:Exact Extract:“Schema Builder provides a dynamic environment for viewing and modifying all the objects and relationships in your organization. You can add new custom objects, fields, and relationships directly in the schema.” — Salesforce Help | Schema Builder Overview

Why not A (Fields & Relationships):That section displays fields for a single object only, not overall relationships.

Why not B (Object Manager):The Object Manager allows object configuration but doesn’t visually display relationships.

Why not C (Lightning App Builder):That tool is for UI layout, not data model visualization.

 A roll-up summary field is a field that calculates values from related records. A roll-up summary field can be used to display the number of opportunities that are closed won with a close date within the last year on the account detail page by using a filter criteria on the field.

Putting the SC in the role hierarchy above the technicians whose work orders they review will provide the required access, given a private data model. The role hierarchy determines how users can access records they do not own. Users at any given role level can view, edit, and report on all data owned by or shared with users below them in the role hierarchy.

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

TODAY() is the function that should be used to return a date for calculating the difference between today and the date a marketing communication was sent. According to the Salesforce documentation, “TODAY() returns the current date as a Date value.” DATETIMEVALUE() converts a text value into a Date/Time value. DATEVALUE() converts a Date/Time value into a Date value. NOW() returns the current Date/Time value.

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 best solution to create a report to compare the number of support cases in each status and by priority is to use grouping. Grouping allows the app builder to summarize data by one or more fields, such as status and priority, and display them in rows and columns. Grouping also enables the app builder to use different chart types, such as stacked bar charts or matrix charts, to visualize the data. Bucket columns are not a suitable solution, as they are used to categorize data into predefined groups, such as high, medium, or low. Custom report types are not a suitable solution, as they are used to define the objects and fields available for a report, not how to display them. Filters are not a suitable solution, as they are used to limit the data shown in a report based on certain criteria, not how to compare them

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

To have automatic posts on a record whenever a travel request has been approved, feed tracking should be used. Feed tracking enables field updates to be displayed in the Chatter feed of a record or a user profile. Users can follow records or users to see updates in their own feed. Feed tracking can be enabled for standard or custom objects and selected fields.

To show Component as a related list on Product, a lookup relationship on Component to Product should be created. A lookup relationship creates a loose association between two objects and allows users to relate records from one object to another. A lookup relationship also allows users to add the related list of the child object to the parent object’s page layout.

To automate the submission of opportunities into the "Secure Commitment" stage and eliminate manual submission for approval, the best feature to use is:

Record-Triggered flow optimized for Actions and Related Records (D). This type of flow allows for complex automation that can include submitting records for approval based on specific criteria being met, such as reaching a particular stage in the opportunity lifecycle. It's particularly suitable for handling related record updates and other actions like submissions for approval, which are integral when an opportunity reaches a certain stage.

Record-Triggered Flow optimized for Fast Field Updates (A) is focused primarily on quick updates to fields and may not handle the complexity of submission for approval processes adequately. Custom button and screen flow (B) could be used to manually trigger processes but does not automate the submission. Platform Event-Triggered flow (C) is typically used for integrations and reacting to system-wide events, not for standard record lifecycle management.

Reference for using Flows in Salesforce, particularly for automating business processes like approval submissions:

Record-Triggered Flows: https://help.salesforce.com/articleView?id=sf.flow_considerations_trigger_record.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.

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.

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 app builder should validate the inbound change set to ensure a smooth deployment to production. Validating an inbound change set allows the app builder to test whether the change set can be deployed without errors in the target org. Validating an inbound change set does not affect any data or metadata in the target org.

 One of the easiest ways to display real-time stock price for each account is to install a solution from the AppExchange, such as Stock Price Lightning Component3. This component can be added to any record page using the Lightning App Builder.

Create a master-detail relationship field on Applicant__c to Application__c is what the app builder should recommend to meet the requirements of allowing the same applicant to apply for multiple open positions using a single application. This will create a many-to-many relationship between Applicant__c and Open_Position__c using Application__c as a junction object. Create a master-detail relationship on Open_Position__c to Application__c, create a master-detail relationship field on Application__c to Open_Position__c, and create a lookup relationship field on Applicant__c to Application__c are not valid or correct ways to create a many-to-many relationship.

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.

Managed packages from the AppExchange are designed to provide automatic updates, upgrades, and vendor support, minimizing the need for ongoing manual maintenance by the customer.

Why D (Managed Package from AppExchange) is correct:Exact Extract:“Managed packages are maintained by the provider and can be automatically upgraded. They’re ideal for apps distributed and maintained through AppExchange.” — Salesforce Help | Managed and Unmanaged Packages OverviewManaged packages allow publishers to push automatic updates and ensure compatibility with future Salesforce releases — minimizing maintenance effort.

Why D (Managed Package from AppExchange) is correct:Exact Extract:“Managed packages are maintained by the provider and can be automatically upgraded. They’re ideal for apps distributed and maintained through AppExchange.” — Salesforce Help | Managed and Unmanaged Packages OverviewManaged packages allow publishers to push automatic updates and ensure compatibility with future Salesforce releases — minimizing maintenance effort.

Why not A (Open-source custom development):Open-source code must be maintained internally by developers.

Why not B (Unmanaged package):Unmanaged packages are customer-controlled and do not receive automatic updates.

Why not C:Open-source unmanaged packages combine the same issue — no automated support or maintenance.

Updating the account search layouts search results columns displayed and updating the account search filter fields can improve an end user’s search experience by showing more relevant information and allowing more refined filtering. The view filter settings and the accounts tab columns displayed are not related to the search functionality

To import leads while preventing duplicates:

B. Data Import Wizard is the appropriate tool. The Data Import Wizard in Salesforce includes functionality to check for duplicates based on matching records by certain criteria (like email or lead ID) during the import process, thus preventing duplicate lead records from being created.

More details on using the Data Import Wizard can be found in the Salesforce Data Import Wizard guide.

The two options that the app builder should avoid to prevent recursion are setting a criteria node to No criteria-just execute the procedure and invocable processes. Setting a criteria node to No criteria-just execute the procedure means that the process will always execute the actions regardless of the record values, which can cause recursion if the process updates the same record that triggered it. Invocable processes are processes that can be invoked from another process or a flow, which can cause recursion if the invocable process updates the same record that triggered the parent process or flow. Option A is incorrect because IF statements are not an option in Process Builder, but rather a function that can be used in formulas or conditions. Option D is incorrect because the ISCHANGED function is not an option in Process Builder, but rather a function that can be used in formulas or conditions to check if a field value has changed.

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.

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. 

 To manually share individual records with specific people or group of people on a case by case basis, users can use public groups, roles, or users. Public groups are collections of users, roles, or other groups that can be used to share access to records. Roles define the level of access that users have to their organization’s data based on their position in the hierarchy. Users are individual people who log in to Salesforce and have access to records based on their profile, role, and sharing settings. 

The requirement is to auto-populate the “Last Maintenance Date” field on the Asset record whenever a Maintenance-type Work Order is closed. This can be achieved declaratively using Flow — specifically, a Record-Triggered Flow that updates the parent record (Asset).

Why D (Flow) is correct:Exact Extract:“Record-triggered flows can update related records when specific changes occur, such as when a Work Order’s status is updated to Closed.” — Salesforce Help | Record-Triggered FlowsIn this scenario, the flow can:

Why D (Flow) is correct:Exact Extract:“Record-triggered flows can update related records when specific changes occur, such as when a Work Order’s status is updated to Closed.” — Salesforce Help | Record-Triggered FlowsIn this scenario, the flow can:

Trigger when a Work Order is updated to “Closed.”

Check if Type = “Maintenance.”

Update the related Asset record’s Last Maintenance Date field with the Work Order’s Closed Date.

Why not B (Roll-up Summary):Roll-up summary fields can only summarize numeric or date values using MIN, MAX, COUNT, or SUM, but only on Master-Detail relationships. Work Order → Asset is a Lookup relationship, so roll-up summaries are not supported natively.

Why not A (Einstein Next Best Action):NBA provides recommendations, not field updates.

Why not C (Apex Trigger):Apex could achieve this, but Salesforce recommends Flow first as a best practice.

 The recommended solution to grant the customer service agent access to the field is creating a permission set that allows read-only access to the field via Field Level Security and assigning it to the agent. A permission set is a collection of settings and permissions that give users access to various tools and functions. Field Level Security (FLS) is a setting that controls the access level of fields for different profiles or permission sets. The app builder can create a permission set that grants read-only access to the custom field on the account object via FLS and assign it to the agent. Option B is incorrect because creating a new profile to allow for read-only access to the field via FLS and assigning it to the agent is not recommended, as profiles are used to define the baseline permissions and settings for a group of users, and creating multiple profiles for individual users can be hard to maintain. Option C is incorrect because updating the Customer Service Profile already assigned to the agent to allow for read-only access to the field via FLS is not recommended, as this will affect all users who have the same profile, which may violate the security policy. Option D is incorrect because updating the custom field’s FLS in setup to allow the agent read-only access to the field is not possible, as FLS can only be set at the profile or permission set level, not at the user level.

The functionality that should be used to set up packages is namespace. A namespace is a unique identifier that distinguishes one package from another and prevents naming conflicts with other packages or customizations. A namespace also allows developers to expose their code or components for use by other developers through APIs or web services. A description is not a functionality that should be used to set up packages, but a text field that provides information about the package contents or purpose. A description does not prevent conflicts with other packages or customizations. Allow sharing is not a functionality that should be used to set up packages, but a setting that controls whether users can share records owned by other users within their role hierarchy. Allow sharing does not prevent conflicts with other packages or customizations. Help setting is not a functionality that should be used to set up packages, but a setting that determines whether users can access help documentation for standard Salesforce features or custom features within a package. Help setting does not prevent conflicts with other packages or customizations.

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

The app builder should use a custom button and Flow to achieve the desired result. A custom button is a button that can invoke custom logic or actions when clicked by a user. A Flow is a type of automation tool that can guide users through a series of screens and perform actions based on user input. In this case, the app builder can create a custom button on the Account object that launches a Flow when clicked by a user. The Flow can display a popup window with questions for the user to answer and populate additional fields on the Account record based on the user input4. Option A, B, and C are not tools that can achieve this result.

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 best way to implement this requirement is to create a formula field on the Case object using the TEXT function. A formula field can display the value of another field from a related object, such as the Account object. The TEXT function can convert a picklist value into text, which can be displayed on the Case record. Creating a formula field on the Account object using the ISPICKVAL function is not a valid solution, as it does not show the value of Support Level on the Case record. The ISPICKVAL function is used to check if a picklist field has a certain value, not to display it. Creating a Process Builder and using a field update on the Case object is not an optimal solution, as it requires more configuration and maintenance than a formula field. A Process Builder may also introduce delays or errors in updating the field value. Creating a roll-up summary field using Support Level on the Account object is not a valid solution, as it does not show the value of Support Level on the Case record. A roll-up summary field is used to aggregate numeric values from child records, not to display picklist values.

A master-detail relationship between two objects automatically creates a report type that includes both objects. The app builder does not need to create a custom report type for this scenario. The report type will have the format of Parent object with Child object

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.

Component visibility filter is the feature on the Lightning app builder that should be utilized to restrict a Lightning component to mobile app users. According to the Salesforce documentation, “Use component visibility filters to show or hide components on a record page based on field values or user profile.” Chatter feed, highlights panel, and related list quick links are not features for controlling component visibility, but standard components that can be added to a record page.

The three reasons user A has access but user B is unable to access the record are:

User A is on the same account team as user C. Account teams are groups of users who work together on an account. Users who are on an account team can have access to the account and related records owned by other team members.

User C has manually shared the record with user A. Manual sharing is a way of granting access to individual users or groups by the record owner or someone above them in the role hierarchy.

User A is in a public group that has access via a sharing rule. Public groups are groups of users who can be used to share data or assign permissions. Sharing rules are automatic rules that grant access to groups of users based on certain criteria. Option B and D are not reasons for user A’s access.

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.

To test code against a subset of production data under 5 GB and to refresh the sandbox environment weekly, the most suitable type of sandbox is:

Partial Copy (B). A Partial Copy sandbox includes a copy of your production org’s metadata and a subset of your production data as defined by the sandbox template. It allows up to 5 GB of data and can be refreshed every 5 days, making it ideal for scenarios where a representative sample of production data is needed for testing without the storage and refresh limitations of a Full Copy sandbox.

Developer Pro (A) and Developer (D) sandboxes also allow for testing and development but do not include a subset of production data—they either have no data or only limited sample data. A Full Copy sandbox (C) provides a full replica of production data, far exceeding the 5 GB requirement and generally is refreshed less frequently due to larger data volume and longer copy times.

Reference for sandbox types and their capabilities:

Sandbox Types and Templates: https://help.salesforce.com/articleView?id=sf.data_sandbox_implementation_tips.htm &type=5

To start tracking how many shoe subscriptions have been sold for each shoe catalog, a roll-up summary field should be created. A roll-up summary field calculates values from related records on a master-detail relationship. It can count, sum, min, or max numeric values from child records on a parent record. 

Workflows that cause each other to fire back and forth recursively can result in workflow limits errors. For example, if workflow A updates a field that triggers workflow B, and workflow B updates a field that triggers workflow A, this can create an infinite loop of workflows that exceed the maximum number of workflow time triggers per hour.

Cloud Kicks needs to insert 25,000 records with deduplication for the Race_Track__c custom object. Here's the reasoning for choosing Data Loader:

Data Loader: This is the appropriate tool for importing large volumes of data (up to 5 million records) into Salesforce. It also provides deduplication options through Salesforce’s native matching rules or by implementing external checks. Data Loader is highly scalable, and for 25,000 records, it is well-suited because it can handle more than the Import Wizard's record limits.

Option A (Import Wizard): The Import Wizard is not a good choice here because it supports up to 50,000 records, which may seem acceptable. However, it is generally recommended for smaller data imports, and deduplication options are limited compared to what Data Loader offers. Additionally, for bulk operations like 25,000 records, Data Loader is more efficient and robust.

Import Wizard Limitations

Option B (Lightning Object Creator): This tool is used to create custom objects from spreadsheets and is not designed for bulk data loading or deduplication. It’s not appropriate for large data imports.

Option D (Schema Builder): Schema Builder is a tool used to view and modify the structure of objects and fields in Salesforce, not for data import or deduplication purposes.

In summary, Data Loader is the most appropriate tool for importing a large number of records with deduplication needs.

The selected objects in the sandbox template. This is correct because a partial sandbox only copies a subset of data from production, and the data to be copied is determined by the sandbox template. If the Shipping object was not selected in the template, then its data would not be copied to the sandbox

The app builder should verify that there is an Apex test that provides test coverage for the Flow. An Apex test is a unit test that verifies the functionality and quality of Apex code. Apex tests are required to deploy any change that contains Apex code or references Apex code, such as an auto launched flow3. The app builder should ensure that there is an Apex test that covers at least 75% of the Flow logic before deploying it to production in an active state4. Option B, C, and D are not things that the app builder should take into consideration when planning the deployment.

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

Making the Opportunity type a required field on the initial Opportunity page layout and using automation to fill in the type field to a record type is a way to limit the number of fields users are required to fill out when creating a new Opportunity. This way, the app builder can assign different page layouts for different record types based on the Opportunity type. The other options are not feasible or effective

 A formula field cannot be referenced by a roll-up summary field if it contains a cross-object field reference or a time-based function. A cross-object field reference is a reference to a field from a different object, such as Account. Name on a Contact object. A time-based function is a function that returns the current date or time, such as NOW() or TODAY(). Option A and C do not prevent a formula field from being referenced by a roll-up summary field.

 The two actions that an app builder should take to meet the requirements are: Implement a sharing rule. A sharing rule is a way to grant additional access to records based on certain criteria, such as record owner, role, profile, or field value. The app builder can create a sharing rule that grants read access to all accounts with the VIP Account field value to all users. This way, all users can view these accounts, but only the owners can edit them. Change organization-wide defaults. Organization-wide defaults are the baseline level of access that users have to records they do not own. The app builder can change the organization-wide default for accounts from Public Read Only to Private. This way, only the owners can view and edit their own accounts, unless additional access is granted by other means, such as sharing rules. Configuring a permission set is not a valid action, as it does not affect record-level access. A permission set is a way to grant additional permissions and access settings to users on top of their profile settings, such as object permissions, field permissions, app permissions, etc. Setting up an Account Team is not a valid action, as it does not restrict record-level access. An Account Team is a way to share an account and its related records with a group of users who work together on the account, such as sales reps, managers, or support agents. An Account Team grants additional access to team members based on predefined roles and access levels.

The best way to help the sales manager achieve their goal of reducing manual data entry from business cards is to research and evaluate data enrichment products on the AppExchange that can automate data entry. Data enrichment products can scan business cards, extract relevant information, and populate fields in Salesforce records. This can save time, improve data quality, and enhance productivity. Option B, C, and D are not effective solutions for this goal.

A text-only Visualforce page can be used to show a text notification on a case record page based on a condition. The Visualforce component can be dragged into the Case Lightning page and its visibility can be set to show when the account support level is platinum. This is the simplest and most flexible way to meet the requirement

 Setting email deliverability to no access would prevent outbound email sends during testing in a sandbox. This would ensure that no emails are sent to any users or external email addresses from the sandbox. Setting email deliverability to system email only would still allow some emails to be sent, such as password reset emails or new user emails. Configuring SMTP authentication or email relay would not affect email deliverability in a sandbox

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.

To add components to the utility bar of an existing app:

C. App Manager. This is where Salesforce apps are configured, including the utility bar which can house components like a chat tool, recent items list, or custom Lightning components.

Steps to edit an app's utility bar:

Navigate to Setup → App Manager.

Locate the desired app and click on the dropdown next to it → select Edit.

In the App Builder, navigate to the Utility Items tab.

Click 'Add' to include new components to the utility bar.

Configure the properties of the utility item as needed.

Save the app configuration.

For step-by-step instructions on modifying apps, see Salesforce's guide on Managing Apps in Lightning Experience.

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

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 custom button, a validation rule, and record types can be used to meet the requirement of hiding the convert button on leads until the lead status picklist is set to qualified. The custom button can replace the standard convert button and invoke a validation rule that checks the lead status. The record types can be used to assign different page layouts with different buttons for different lead statuses

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 full sandbox should be refreshed after each major release to production. This way, the full sandbox will have the most updated data and metadata from the production org, and can be used for final load and regression testing before the next release. Option A is incorrect because refreshing the full sandbox after user acceptance testing is complete is not necessary, as user acceptance testing can be done in the partial data sandbox or the production org. Option B is incorrect because refreshing the full sandbox after each push from the partial data sandbox is not necessary, as the full sandbox can receive configuration and code changes from the partial data sandbox without refreshing. Option D is incorrect because refreshing the full sandbox after a new user is added to production is not necessary, as adding a new user does not affect the data and metadata in the full sandbox.

 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. 

 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

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

Users will be unable to view the Account Interest records or the Interest records because they do not have read access to the Interest object. This is a standard behavior of Salesforce when a user does not have access to a related object.

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.

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.

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.

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.

Escalation rules and Process Builder are two automation processes that can be used to send a notification when a case stays in the ‘’ new’’ status for more than four business hours. Escalation rules can define criteria and actions for escalating cases based on time or other factors. Process Builder can create a time-based action that triggers an email alert when the case status is ‘’ new’’ for more than four business hours. Flow Builder and Scheduled Apex are not necessary for this requirement.

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.

Related record and Tabs. These are correct because the related record component allows service agents to view and edit fields from a related record on the same page, and the tabs component allows service agents to switch between different views of related lists or other components on the same page.

 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.

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

The best choice for capturing geographic location data, such as crossroads or location markers provided by customers, is the Geolocation field type. This field type stores latitude and longitude data, allowing accurate pinpointing of locations on a map. Geolocation fields are suitable for any application that needs to handle coordinates for mapping and proximity calculations.

A: Number field is not specific enough for geographical coordinates.

C: Reference fields link to other records, not geographical data.

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.

Formula fields in Salesforce can use various functions including text, mathematical, and logical functions to create simple or complex expressions. They can handle data from fields of the same record. Option C, "A combination of the Opportunity's Text and a Description fields," is a valid configuration for a formula field as it involves simple concatenation of text fields, which is supported.

Options A, B, and D exceed the capabilities of formula fields:

A: Hyperlinks to other objects using formula fields do not directly support navigation to parent records of a different object.

B: Rich Text and HTML formatting are not supported in formula fields.

 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

 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 communicate to the CK web service when a shoe’s inventory has changed, an app builder should use an after-save record-triggered flow. An after-save record-triggered flow is a type of flow that runs after a record is saved and can perform actions such as updating related records, sending emails, calling external services, etc. An after-save record-triggered flow can use an Apex action to invoke a SOAP web service using a WSDL file. [Source]

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.

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

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.

Record-triggered flow is the automation tool that the app builder should use to best address all these requests of sending an email to the finance manager and creating a task for the sales manager when a new client is won. According to the Salesforce documentation, “Record-triggered flows automate processes for you. They start when a record is created or updated, or when a platform event occurs.” A record-triggered flow can perform actions such as sending an email alert or creating a record based on criteria or conditions. Screen flow, Apex, and Approval process are not automation tools that can handle all these requests.

A (Feed Tracking) allows Salesforce to automatically post updates to the Opportunity feed when certain fields (like Close Date) change.Exact Extract:“Feed tracking lets users see updates to records they follow. When feed tracking is enabled on an object, field changes appear in the feed.” — Salesforce Help | Feed Tracking Overview

C (Record-Triggered Flow + Chatter Post) allows real-time automated notifications to specific users (e.g., Sales Managers) when the Close Date changes.Exact Extract:“You can automate notifications by creating a record-triggered flow that posts to Chatter or sends notifications when specified conditions are met.” — Salesforce Help | Flow Builder Notifications

Why not B:Outbound messages are used for system-to-system communication, not internal notifications.

Why not D:Historical Trending is for reporting over time, not notifications or tracking.

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.