Platform-App-Builder Salesforce Certified Platform App Builder (SU24) Questions and Answers

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.

The best type of sandbox for each team member to use is a developer sandbox. A developer sandbox is a copy of production that includes only the metadata, such as objects, fields, layouts, etc. It does not include any data, such as records or attachments. A developer sandbox is ideal for small projects that do not require data testing, such as developing new features or customizations. A developer sandbox has a storage limit of 200 MB and can be refreshed once per day. A developer sandbox is also cheaper than other types of sandboxes. A full sandbox is a copy of production that includes all the metadata and data. It is ideal for large projects that require data testing, such as performance testing or integration testing. A full sandbox has the same storage limit as production and can be refreshed every 29 days. A full sandbox is also the most expensive type of sandbox. A developer pro sandbox is similar to a developer sandbox, but it has a larger storage limit of 1 GB and can be refreshed every 5 days. It is ideal for projects that require some data testing, such as data migration or quality assurance testing. A partial sandbox is similar to a full sandbox, but it has a smaller storage limit of 5 GB and can be refreshed every 5 days. It is ideal for projects that require selective data testing, such as user acceptance testing or staging testing

 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.

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.

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

The three Salesforce functionalities that are ignored when processing field updates in workflow rules and approval processes are:

Field-Level Security: This means that the field update will occur regardless of the user’s profile or permission set settings that determine whether they can see or edit the field1.

Validation Rules: This means that the field update will bypass any validation rules that might otherwise prevent the record from being saved1.

Decimal places and character limits: This means that the field update will round or truncate the value to fit the field’s format, without throwing an error

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.

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

Send an email alert, update a related record, and create a child record are three capabilities of Process Builder that can improve productivity for the sales team. Process Builder can automate these actions based on criteria or events that occur on records or objects. Send an outbound message and delete a related record are not capabilities of Process Builder, but of other tools such as Workflow Rules or Apex.

 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

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.

The best Lightning component to add to the layout to display the ‘New Task’ custom action is Highlights panel. This component shows key information and actions for a record, such as its name, owner, and custom actions. Related record, related lists, and activities are not Lightning components that display custom actions. See [this article] for more information on Highlights panel.

To ensure sales reps input contacts into Salesforce rather than their personal devices:

C. Enable offline create, edit, and delete in Salesforce for Android and iOS. This feature allows sales reps to enter contact information directly into the Salesforce Mobile App even when they are offline, which syncs back to Salesforce once connectivity is restored.

Steps to enable offline capabilities:

Navigate to Setup → Mobile Administration → Salesforce Mobile App → Offline Settings.

Configure offline settings to allow for creating, editing, and deleting records.

Ensure that the Contact object is available for offline access.

This functionality encourages reps to use Salesforce directly by mitigating connectivity constraints.

For implementation details, refer to Salesforce Mobile App Offline.

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.

 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 inability to create a Roll-Up Summary field in this context can be attributed to:

B. The organization has Advanced Currency Management enabled. When Advanced Currency Management (ACM) is enabled, it affects how currency data is managed and aggregated, impacting the functionality of roll-up summary fields that involve currency amounts across different records.

To address this limitation, consider using custom reporting or a custom solution like a trigger or a scheduled batch class to manually calculate and update the total.

For more information on limitations with ACM, consult Salesforce's help article on Advanced Currency Management.

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

The best actions to take to avoid creating duplicate leads when uploading a list of 400 leads are to utilize a Lead Matching Rule and corresponding Duplicate Rule to block newly created duplicate leads, and to upload the lead list using the import wizard and select a Matching type to prevent duplicate lead creation. The Lead Matching Rule defines the criteria for identifying duplicate leads, and the Duplicate Rule defines the actions to take when a duplicate is detected. The import wizard allows users to choose a Matching type based on the Lead Matching Rule and block or allow duplicates. Using Data Loader’s update function or enabling Duplicate Matching in the Data Management section will not prevent duplicate lead creation.

A flow or a process can be used to assign a permission set to new users. A flow can be triggered by a record change or an invocable action, while a process can launch a flow as an immediate or scheduled action

Create a custom action is the recommended solution to meet the requirement of creating additional accounts to form a hierarchy from a Parent Account record. According to the Salesforce documentation, “Actions let users quickly create or update records, log calls, send emails, and more, in the context of a particular object.” A custom action can auto-populate fields based on the parent account and make it easier for users to create child accounts. Add Path on Account hierarchy, add a custom link on Account, and customize a Global Quick Action are not valid or feasible options.

The app builder should do three things to optimize mobile experience:

Use Global Actions to make it easy to perform vital functionality on mobile: Global actions are actions that allow users to create records or perform tasks from anywhere in Salesforce. They are displayed in various places in Salesforce mobile app, such as action bar, action menu, or publisher. By using global actions, the app builder can make it easy for the appraisal team to perform common tasks on mobile, such as creating a new appraisal record or logging a call.

Minimize the amount of formula fields and lookup fields to reduce page load time: Formula fields and lookup fields are types of fields that can affect the performance of Salesforce mobile app. Formula fields are fields that calculate a value based on an expression or formula. Lookup fields are fields that create a relationship between two objects and allow users to select a value from a list of records. Both types of fields can increase the page load time on mobile devices, especially if they are complex or reference many other fields. By minimizing the amount of formula fields and lookup fields, the app builder can optimize the mobile experience for the appraisal team.

Put the most important fields in the compact layout so they are easy to find: Compact layouts are layouts that display a record’s key information at a glance. They are used in various places in Salesforce mobile app, such as record highlights, list views, related lists, and lookup dialogs. By putting the most important fields in the compact layout, the app builder can ensure that the appraisal team can easily find the information they need on mobile devices. Option B and D are not things that an app builder should do to optimize mobile experience.

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.

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

The lead settings have an option to require validation for converted leads. If this option is unchecked, then the Account validation rules will not be enforced when a lead is converted to an Account. This could result in missing or incorrect information on the Account 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.

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.

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.

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

The best way to implement this request is to create a Lightning Web Component that can fetch the real-time stock price from an external API and display it on the Account record page. Installing a solution from the AppExchange may not be feasible as it may not match the exact requirements or may have additional costs. Building a Flow that uses API calls may not be efficient as it may consume API limits and may not be able to update the stock price in real-time. Using a scheduled Apex job may not be suitable as it may not be able to run frequently enough to reflect the real-time stock price

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

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

Steps to create a flow for this purpose:

Navigate to Setup → Flows.

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

Design the flow with Screen elements for each question.

Add logic to process responses as necessary.

Save and activate the flow.

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

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

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

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

The 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

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

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 troubleshoot the issue of a contact being unavailable for other users to see, an app builder should check the following things:

Confirm whether Default Organization-Wide Sharing Settings provide access to the Account. This setting determines the baseline level of access that users have to each other’s records.

Review the Contact record and ensure it is linked to an Account. Contacts that are not linked to an account are private and only visible to the owner and administrators.

Verify the users with the issue have access to the Contact object. Users need to have at least read permission on the Contact object to view contact records. Option A and E are not relevant for troubleshooting this issue.

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

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.

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.

C: Setting the component visibility based on an advanced filter type, using the contact field(s) to define dynamic criteria, allows displaying information relevant to specific account conditions without needing user interaction.References:

Salesforce Help - Dynamic Forms

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

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

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

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

 A summary report on the opportunity object should be created to add to the account page layout. A summary report groups rows of data by common values and allows users to create charts based on aggregate values. A summary report on the opportunity object can group opportunities by stage and display a chart of all related opportunities on the account detail 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.

An AppExchange solution is a pre-built application or component that can be installed from the Salesforce AppExchange, which is an online marketplace for Salesforce products. AppExchange solutions can help you meet your business needs quickly and efficiently, without requiring much development effort or expertise. You can browse and search for AppExchange solutions by category, industry, rating, price, and more.

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.

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 app builder should use two tools to automate this process:

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

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

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.

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

To ensure process compliance where cases cannot revert to an earlier status and certain fields are required based on specific case criteria, the recommended solution is:

Configure validation rules with help text (A). Validation rules enforce data integrity and business processes by preventing users from saving records if certain conditions are not met. For instance, a validation rule can prevent the status of a case from being changed back to an earlier status and can conditionally require fields based on other field values on the case.

Dependent picklists (B) ensure field values depend on another field’s value but do not enforce the inability to revert status. Approval processes (C) are used for step-by-step record approval and are not designed to prevent status reversion or conditionally require fields. Making fields required on the page layout (D) ensures they are always required when accessing the record through that layout but does not enforce conditional requirements based on other criteria.

Reference for creating validation rules in Salesforce:

Validation Rules: https://help.salesforce.com/articleView?id=sf.validation_rules.htm &type=5

The app builder should create a master-detail relationship field on the gift card object to support the requirement. A master-detail relationship field creates a parent-child relationship between two objects, where the master record controls certain behaviors of the detail record. In this case, the Account object would be the master and the gift card object would be the detail. By creating a master-detail relationship field, the app builder can meet these requirements:

Track the total number of gift cards opened and gift cards issued on an Account: This can be done by creating roll-up summary fields on the Account object that count or sum up the values from the gift card records related to each account.

Permanently ensure the gift cards are unable to be moved across any other Account once it is created: This can be done by making the master-detail relationship field required on the gift card object, which means that every gift card record must be associated with an account record and cannot be changed once set. Option B, C, and D are not types of fields that can support this requirement.

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

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

Creating a unique External ID field on the custom object and using Data Loader to upsert records prevents duplicates and ensures correct record updates by matching the unique ID.References:

Salesforce Help - External ID

The app builder should provision a Partial Data sandbox to the developer. A Partial Data sandbox can have up to 5 GB of data, which meets the requirement of having at least half a gigabyte of data. A Partial Data sandbox can also be refreshed every 5 days, which meets the requirement of refreshing after each three-day sprint. Option A is incorrect because a Developer sandbox can only have up to 200 MB of data, which does not meet the requirement. Option B is incorrect because a Full Copy sandbox can only be refreshed every 29 days, which does not meet the requirement. Option C is incorrect because a Developer Pro sandbox can only have up to 1 GB of data, which may not be enough for the requirement.

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

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

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

Steps to set up these features:

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

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

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

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.

Roll-up summary fields can only be created on master-detail relationships, and they can only calculate numeric fields, such as currency, percent, and number. Date and time fields are not supported for roll-up summary fields. Checkbox fields can be used in roll-up summary filters, but not in the field to aggregate

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.

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.

The correct method to upgrade an unmanaged package that is installed in a production environment is to use the update link provided on the Installed Packages page. This process ensures that any modifications or additions in the package are properly integrated without the need to uninstall the previous version, thus preserving existing customizations and data.

A: Uninstalling removes all associated data and customizations, which is not advisable.

B: The Install Wizard is used for initial installations, not upgrades.

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.

Customers who are invited to Chatter groups can only interact with members of their groups. They cannot invite other members, @mention accounts, or request access to public groups

 The two considerations that an app builder should keep in mind during the deployment process using change sets are: Change sets do not include all components and may have to perform some changes manually. Change sets are a way to deploy metadata changes from one Salesforce org to another, but they do not support all types of components, such as reports, dashboards, email templates, etc. The app builder may have to use other methods, such as unmanaged packages or manual configuration, to deploy these components. Users should be logged out of production when receiving inbound change sets. This is a best practice to avoid any errors or conflicts that may occur when deploying changes to production. Users may be working on records or components that are being updated by the change set, which may cause data loss or inconsistency. Salesforce Connect does not automatically establish a link between environments. Salesforce Connect is a feature that allows users to access data from external sources without storing it in Salesforce. It does not have anything to do with deploying changes between Salesforce orgs. Transactions will not revert if the deployment errors. Transactions are units of work that are either completed entirely or not at all. If a deployment error occurs during a transaction, the transaction will be rolled back and no changes will be made to the target org. However, this does not mean that the source org will revert to its previous state before the deployment.

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

The app builder should add the fields to the page layout on the object to ensure users can access the new object and fields. The page layout determines which fields are visible and editable on the record detail page. Option A, B, and C are not necessary for this purpose.

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

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.

Historical data will be updated to 12:00 timestamp when changing a Date field to Date/Time field. According to the Salesforce documentation, “When you convert a Date field to Date/Time, Salesforce appends “12:00” to existing data in your records.” The change will not be instant, but will require some time for processing. The field name will not change unless specified by the app builder. Data loss will not be experienced, but data accuracy might be affected.

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.

Email alert, task, and invocable flow are three action types that can be used in an approval process. Email alert can send an email message to one or more recipients. Task can assign a task to a user or queue. Invocable flow can launch a flow that performs complex logic and actions

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.

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.

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.

Approval Process is the feature that would be used to handle the requirement of signing off on major show retail deals with more than 30% discount. According to the Salesforce documentation, “An approval process automates how Salesforce records are approved in your org.” Email Alert, Field Update, and Workflow Rule are actions that can be triggered by an approval process, but they are not features for handling approvals.

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

A custom action on Account can be used to create additional accounts from a parent account record. A custom action can have predefined values for certain fields based on the parent record. A custom global action can be used to create records that do not have any relationship with other objects. A custom link on Account can be used to execute JavaScript or link to an external URL.

The two tools that an app builder could combine to display the number of open cases on the account page are Flow and Process Builder. Flow is a tool that allows the app builder to create a declarative automation that can query, manipulate, and display data from multiple objects. Process Builder is a tool that allows the app builder to create a trigger-based automation that can invoke a Flow when a record is created or updated. By using these two tools, the app builder can create a solution that can query the number of open cases for the account and parent account and display them on the account page using a screen element. Workflow is not a suitable tool, as it cannot query or display data from multiple objects. It can only perform actions such as field updates, email alerts, tasks, or outbound messages. Approval Process is not a suitable tool, as it is used to automate the approval of records based on certain criteria and predefined steps. It cannot query or display data from multiple objects.

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

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]

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.

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

Updating the existing change set with the new changes and redeploying is the most efficient way to move the updated components to the Developer Pro Sandbox.References:

Salesforce Help - Change Sets

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.