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

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.

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

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.

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

 The app builder wants to create a formula field on an Account to include data from related Contacts but cannot find the relationship in the formula editor. This limitation occurs because formula fields in Salesforce cannot reference child records directly.

Option A (Unable to reference the child records): In Salesforce, formula fields can reference parent objects but not child objects. In this case, Contacts are child records of Accounts in a lookup relationship, and Account is the parent. This is why the formula editor does not provide access to the child records (Contacts) from the Account.

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.

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

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

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

Reference for managing fields in custom report types:

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

The two reasons to create an unmanaged package are to distribute open-source projects on the AppExchange and to deploy from a Developer Edition environment. An unmanaged package is a collection of components that can be installed in any Salesforce org but cannot be upgraded or controlled by the developer. An unmanaged package can be used to share open-source projects or to deploy components from a Developer Edition environment to another org.

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

The automation solution that would meet these requirements is Process Builder. Process Builder is a tool that can create and update records, send email alerts, submit records for approval, invoke flows, call Apex classes, and post to Chatter based on certain criteria and actions. The app builder can use Process Builder to create a process that starts when an opportunity is marked as closed won, creates a new opportunity record for the renewal with pre-populated fields, and sends an email alert to the contracts team. Option A is incorrect because an approval process is not suitable for this requirement, as approval processes are used to define the steps and criteria for approving records. Option B is incorrect because a validation rule is not suitable for this requirement, as validation rules are used to enforce data quality and prevent users from saving invalid records. Option D is incorrect because a workflow rule is not suitable for this requirement, as workflow rules are considered legacy tools and have limitations compared to Process Builder.

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

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

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

 A flow is a powerful automation tool that can perform complex logic and data manipulation. A flow can be used to delete rejected quotes by using a record-triggered flow that runs when a quote is updated, or by using a scheduled flow that runs at a specified time.

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

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.

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

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

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

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

 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.

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.

A report type that is in a status of In Development is not available for users to select when creating a new report. The app builder needs to change the status to Deployed to make it visible to users

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

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

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

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

Criteria-based sharing rules are the best tool to use for automatically sharing records based on specific criteria, such as the opportunity type being "Service Agreement." This rule can share opportunities with all users in a particular role, such as the Service Manager role, when the criteria are met, thereby adhering to the private sharing model while still providing necessary access.

A: Owner-based sharing rules focus on the record owner's role or group, not the record type.

C: Apex sharing is used for more complex scenarios not easily handled by declarative sharing settings.

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

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.

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.

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.

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

 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.

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

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

Creating and editing custom objects and fields

Creating and editing relationships between objects

Showing selected objects on a page

Editing custom settings

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

 The lookup relationship will need to be converted to a master-detail relationship before a roll-up summary field can be created. This is correct because roll-up summary fields are only available on the master object in a master-detail relationship, and a lookup relationship does not establish a parent-child hierarchy between the objects

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

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

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.

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

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

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

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

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

 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.

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

 Before replacing workflow rules and Apex triggers with Process Builders, the app builder should consider avoiding generating infinite loops and combining actions when possible. Infinite loops can occur when a process updates a record that causes another process to run on the same record, and so on. Combining actions can reduce the number of processes and improve performance and maintainability

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

 NOT(ISBLANK(Job_Accepted__c)) && ISCHANGED(Hire_Date__c) is the validation formula that the app builder should use to meet the requirement of preventing changes to Hire Date after Job Accepted is entered. This formula will return TRUE if Job Accepted is not blank and Hire Date is changed, which will display an error message and prevent saving the record. The other formulas are not correct or valid.

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

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.

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

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

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

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

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

Reference for automating processes with Salesforce Flow:

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

To display the actions on the Lightning record page, two components could be included on the layout:

Highlights panel: The highlights panel displays key information and actions for a record based on the compact layout. Users can see and perform actions such as edit, clone, delete, follow, etc. from the highlights panel. [Source]

Activities: The activities component displays tasks and events related to a record. Users can also create new tasks and events, log calls, send emails, and view past activities from this component. 

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

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.

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.

For Universal Containers to understand the return on investment (ROI) for their latest advertising buy while using a private security model, the best recommendation is to use Campaign Hierarchies and Campaign statistics.

Campaign Hierarchies and Campaign Statistics: Campaign hierarchies allow Universal Containers to track the effectiveness and ROI of marketing efforts by grouping related campaigns (e.g., advertising buys) under a parent campaign and rolling up key metrics like responses, converted leads, and won opportunities. Campaign statistics provide detailed insights into individual and aggregate campaign performance, helping calculate ROI.

This method works well within a private security model since it respects existing sharing rules and access controls, ensuring that only authorized users can see the campaign data.

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

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

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

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

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

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

Steps to create a custom action:

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

Click Buttons, Links, and Actions → New Action.

Set Action Type to 'Update a Record'.

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

Add the action to the Salesforce Mobile layout.

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

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

The app builder 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 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 email button item will not be visible on the Lightning record page if the page layout includes the case feed component or if the email button contains JavaScript. The case feed component replaces the standard buttons on the page layout with actions in the feed. The email button item will not work if it contains JavaScript because JavaScript buttons are not supported in Lightning Experience.

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

For managers to respond to approval requests for opportunities above $50,000 in the Salesforce mobile app:

B. In-App Notification: Managers receive notifications within the Salesforce mobile app when there is an approval request, allowing them to approve or reject directly from the notification.

C. Record Detail: Managers can access the approval request directly from the Opportunity's detail page in the mobile app, where they can review and respond to the request.

Steps to configure approval process notifications:

Navigate to Setup → Approval Processes → select the relevant approval process.

Ensure the process is active and configured to send notifications to approvers.

Managers need to have the Salesforce mobile app configured to receive notifications.

For best practices on managing approvals in Salesforce, see Approvals in Salesforce.

An update record action with a related record component on the Opportunity layout allows users to edit related Account records directly.References:

Salesforce Help - Creating Quick Actions

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

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.

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.

It lacks setting up field-level security and adding fields to the page layout, so you have to choose the manual way of field creation. Adds another layer of risk with changes in Schema Builder since it is deployed in real-time.

Salesforce Schema Builder is a powerful tool for visualizing and creating objects, fields, and relationships in Salesforce, but it has certain limitations when building custom objects.

Option B (Fields and relationships can be created, but they will be unable to add the fields to the page layout from the canvas): In Schema Builder, while you can create new custom objects, fields, and relationships, you cannot directly add fields to the page layout from within the Schema Builder interface. After creating a field, you need to navigate to the Page Layout Editor to manually place the new field on the layout.

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

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

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.

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

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

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.

Using 'Add Fields Related Via Lookup' in the report type configuration allows adding fields from the Account object to the Opportunity report, including the Account Rating.References:

Salesforce Help - Custom Report Types

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

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

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.

The feature that the app builder should use to allow users to create the opportunity is a quick action. A quick action is a type of custom button or link that can create or update records, log calls, send emails, or launch flows from a record page or a global menu. The app builder can create a quick action on the account object that creates an opportunity record with pre-populated fields. Option B is incorrect because a default action is not a valid term, but rather a standard action that appears on every record page by default, such as Edit or Delete. Option C is incorrect because a custom button is not suitable for this requirement, as custom buttons can only display a URL or execute JavaScript when clicked. Option D is incorrect because a custom link is not suitable for this requirement, as custom links can only display a URL or execute JavaScript when clicked.

 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