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

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

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.

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: Number fields and C: Text fields can be set as External IDs. These field types are suitable for housing unique identifiers from external systems.References:

Salesforce Help - External ID Fields

 Create a formula field on the Case object using the TEXT function. This is correct because a formula field can reference a field from a related object using dot notation, and the TEXT function can convert a picklist value to text. This way, the case record will always show the current value of the Support Level field on the account record.

For reporting snapshots, the source report must be capable of grouping data, which is necessary for summarizing information at specific intervals. The acceptable formats for a source report in reporting snapshots are:

Summary format (B). This format groups rows of data by one or more criteria and can perform calculations such as sum, average, etc., on another column at each group level.

Matrix format (D). Similar to the summary format but arranges data in a grid format, allowing summarization by both rows and columns.

Tabular (A) and joined (C) formats are not suitable for reporting snapshots. Tabular reports do not include grouped or summarized data, and joined reports involve combining multiple report types, which are not compatible with how reporting snapshots need to structure data.

Reference for more information on reporting snapshots and report formats:

Reporting Snapshots: https://help.salesforce.com/articleView?id=reports_snapshots.htm &type=5

Report Formats: https://help.salesforce.com/articleView?id=reports_understanding_formats.htm &type=5

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

 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. 

Guided Action Flows on the record page can help service agents meet the requirement of confirming a user identity before providing support information over the phone. Guided Action Flows are a series of screens that guide agents through a predefined process, such as verifying user information, collecting case details, or resolving issues

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

To manage frequently changing picklist values effectively:

B. Set up Global Values in Picklist Value Sets. This approach allows for centralized management of picklist values that can be reused across multiple fields and objects. By using global value sets, inactive values can be efficiently managed and deactivated without impacting fields that use these sets.

For further information on managing picklists, check Salesforce's Picklist Management guide.

To make a custom component available for the utility bar in Salesforce, the component needs to be explicitly tagged for use in the utility bar. Salesforce components require specific configurations to be available in different parts of the application, such as the utility bar, record pages, or app pages.

Option C: For use on the utility bar: When a custom Lightning component is developed, it must include a specific target tag in its .js-meta.xml configuration file that marks it as usable in the utility bar. This is done by setting the target to "lightning__UtilityBar". Without this tag, the component will not appear as an option to add to the utility bar in the App Manager.

Example of how the component is tagged in the meta.xml file:

xml

Copy code

lightning__UtilityBar

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

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

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

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.

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

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.

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

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

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

As of the Winter '24 release, Salesforce introduced the ability to send outbound messages directly from Flow. This makes Flow the best choice for automating the notification to an external system when a lift is sold, fulfilling the need for both checking the custom To Be Installed checkbox and sending the notification the next day.

Flow: With this new functionality, Flow is now the most versatile automation tool for this use case. You can:

Create a scheduled path that triggers the next day after the lift is sold (e.g., when a record meets the criteria such as the checkbox being checked).

Send the outbound message to notify the external system about the lift installation.

Perform all of this declaratively, replacing the need for Workflow, which previously was the go-to for outbound messages.

Why not Workflow anymore? Although Workflow still supports outbound messages, Flow is the preferred tool now, as Salesforce is deprecating Workflow rules and Process Builder in favor of Flow. Flow also allows for more complex logic and actions, providing flexibility in future-proofing automation.

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

The app builder 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.

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.

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

The 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

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.

 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.

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.

 The app builder should use three features to meet the business requirements:

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 is in the Secure Commitment Stage, and then execute an action that submits it for approval.

Apex: This is a programming language that allows developers to execute complex logic on the Salesforce platform. Apex can be used to create triggers that run before or after certain events, such as insert, update, delete, or undelete of records. In this case, Apex can be used to create a trigger that runs before an opportunity is updated and submits it for approval if it is in the Secure Commitment Stage.

Flow: This is another type of automation tool that can guide users through a series of screens and perform actions based on user input. Flow can also be triggered by certain events, such as when a record is created or updated. In this case, Flow can be used to create a record-triggered flow that runs after an opportunity is updated and submits it for approval if it is in the Secure Commitment Stage. Option A and D are not features that can meet the business requirements.

The app builder should create a sharing rule that grants the users Read/Write access to the Application records. A sharing rule is a type of rule that can extend record access to groups of users based on certain criteria. In this case, the app builder can create a sharing rule that grants Read/Write access to the Application object to the recruiters based on their role, public group, or queue. This will allow them to edit the Application records related to any Internship record, regardless of the ownership. Option A, B, and C are not ways to configure the proper access.

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.

 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

To configure a custom Lightning component for use in a record page, the app builder needs to edit a record page using the Lightning App Builder and drag the component onto the page. The Page Layout editor and the App Manager are not used for this purpose

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 best way to show Asset Inventory as a related list on Asset is to create a lookup relationship on Asset Inventory to Asset. This will allow one-to-many relationship between Asset and Asset Inventory, and display the related records on the Asset page layout.

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

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

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

Roll-up summary fields can be used to count the number of related open cases for an account, including those from parent accounts if the relationship allows roll-up summaries.References:

[Salesforce Help - Roll-up Summary Fields](https://help.salesforce.com/s/articleView?id=sf.fields_about_roll_up up_summary_fields.htm&type=5)

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

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

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.

 A record-triggered flow can be used to automate actions when a record is created or updated. In this case, a record-triggered flow can be configured to create a new opportunity and send an email to the contracts team when an opportunity is marked as closed won.

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.

 AppExchange and Apex Code are two resources that can provide custom components for a Lightning app. AppExchange is a marketplace where developers can publish and sell their custom components or apps. Apex Code is a programming language that can be used to create custom components or logic for a Lightning app. Import Wizard and Visualforce are not resources for custom components, but tools for data import and web page development respectively.

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.

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.

 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

A Scheduled Triggered flow can be used to increment a custom field on the Case object each time the case is reopened, effectively tracking the number of reopenings.References:

Salesforce Help - Scheduled Flows

The Compact Layout in Salesforce mobile app configuration determines the fields that appear at the top of the record in the mobile app, providing quick access to key information.References:

Salesforce Help - Compact Layouts

The solution that the app builder should configure to meet these requirements is creating three lead record types each with its own page layout containing the relevant fields. This way, the app builder can customize the fields and sections that appear on each record type based on the source of the lead. Option B is incorrect because creating a partner community and a record type for web and trade show leads does not address the requirement of collecting information that is unique to each type of lead, as partner community users may have different fields and layouts than internal users. Option C is incorrect because creating three sections on the lead layout and instructing users to collapse the non-relevant fields does not address the requirement of collecting information that is unique to each type of lead, as users may still see or enter data in the wrong fields. Option D is incorrect because creating custom page layouts for each type of lead only containing the relevant fields does not address the requirement of collecting information that is applicable to all sources, as users may miss some common fields.

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

 Removing the Delete permission from the Shipper profile and using a permission set to remove the Delete permission are both valid ways to prevent users from deleting delivery records. Removing the delete button from the Delivery page layout will not prevent users from deleting records using other methods, such as list views or reports. Changing the organization-wide default of deliveries to Private will not affect the delete permission, but only the sharing settings.

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.

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.

An Approval Process is the appropriate functionality to ensure all free parts receive the marketing director's sign-off. It allows for setting up a process for record approval.References:

Salesforce Help - Approval Processes

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.

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.

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 validation rule should check if the user role is not Marketing, and if the Retail Opt In field has been changed to Yes. The ISCHANGED function returns true if the field value has been changed, and the ISPICKVAL function returns true if the field value matches a specified picklist value. 

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.

The solution that the app builder should use to meet DreamHouse Realty’s needs is Master-Detail Child Object. A master-detail relationship can be used to create 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 roll-up summary field on the parent object to calculate the highest value of all child records. Option B is incorrect because Text Area (Long) is a field type that allows users to enter up to 131,072 characters on one line, which is not suitable for this requirement. Option C is incorrect because Multi-select Picklist is a field type that allows users to select multiple values from a predefined list, which is not suitable for this requirement. Option D is incorrect because Lookup Object is not a valid term, but rather Lookup Relationship, which is a type of relationship that links two objects together, but does not support roll-up summary fields.

To import opportunities with the proper country currency, the app builder needs to include the currency ISO code in all currency fields in the import file, and use Data Loader to import the records. Data Loader supports importing multiple currencies, while Import Wizard does not. The currency ISO code column in the import file specifies the currency for each record

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

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

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

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.

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.

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.

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.

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.

 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

In the Lightning App Builder, the following standard components can be used to enhance the functionality of Lightning pages:

B. Rich text: Allows the inclusion of formatted text, links, and images on a page.

D. Report details: Enables embedding of specific report details directly on a page.

E. Recent items: Displays a list of recently accessed items relevant to the user.

Steps to add these components:

Open the Lightning App Builder via Setup → Edit Page or when creating a new Lightning page.

Drag and drop the Rich text, Report details, and Recent items components from the standard components section onto the page layout.

Configure each component as needed (e.g., selecting a specific report for the Report details component).

For more on using these components, refer to Salesforce's guide on Standard Lightning Components.

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.

For automatically updating contact statuses when an account type changes:

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

Steps to implement:

Navigate to Setup → Flows.

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

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

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

Activate the flow.

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

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

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

The 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

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.

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

Changing custom field types may result in data loss if the new field type is incompatible with the old one. For example, changing a text field to a number field may cause text values to be deleted. Field history tracking records value changes of 255 characters or less. If a rich text field value exceeds this limit, only the first 255 characters are tracked.

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.

 Partial Copy is the type of testing environment that the app builder should create to use a sandbox template for Accounts, Projects, and Project Milestones. According to the Salesforce documentation, “Partial Copy sandboxes copy your production org’s configuration (metadata) and some of your production org’s data as defined by a sandbox template.” Developer, Developer Pro, and Scratch Org are not types of testing environments that support sandbox templates.

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.