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

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

 Disable Grant Access Using Hierarchies, Create a criteria-based Sharing Rule for the HR Department, and Remove Review Read permission from non-HR profiles. These are correct because disabling Grant Access Using Hierarchies prevents users above the record owner in the role hierarchy from viewing the Review records, creating a criteria-based Sharing Rule for the HR Department allows users in that group to view all Review records, and removing Review Read permission from non-HR profiles prevents users in other profiles from viewing any Review records.

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

The app builder should use Data Loader to quickly insert a list of over 60,000 net new Accounts. Data Loader is a tool that allows users to insert, update, delete, or export large amounts of data from Salesforce using CSV files or database connections. Data Loader can handle up to 5 million records at a time and supports features such as bulk API, batch operations, mapping files, etc. Data Loader is ideal for loading large data sets into Salesforce quickly and efficiently. Lightning Object Creator is not a valid tool, as it cannot insert data into existing objects. Lightning Object Creator is a tool that allows users to create custom objects from spreadsheet data by uploading a file and mapping columns to fields. It cannot load data into existing objects or handle more than 500 records at a time. Import Wizard is not a valid tool, as it cannot handle more than 50,000 records at a time. Import Wizard is a tool that allows users to insert, update, or delete data from Salesforce using CSV files or Excel files. Import Wizard supports standard objects and some custom objects and provides features such as field mapping, duplicate detection, data validation, etc. Import Wizard is ideal for loading small data sets into Salesforce with more control and accuracy.

 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.

Feed Tracking is the Chatter feature that allows field value changes for certain fields to show up on Chatter. Thanks, Publisher Actions, and Topics are other Chatter features, but they do not relate to field value changes.

The two considerations that should be made are: The Star records are all required to have an existing value in their Galaxy field. This is a prerequisite for converting a lookup relationship to a master-detail relationship. A lookup relationship is an optional relationship that links two objects together, but does not enforce referential integrity or cascade delete. A master-detail relationship is a required relationship that links two objects together and enforces referential integrity and cascade delete. To convert a lookup relationship to a master-detail relationship, all child records must have a value in their lookup field that references an existing parent record. The Galaxy object has fewer than two existing master-detail relationships. This is another prerequisite for converting a lookup relationship to a master-detail relationship. An object can have up to two master-detail relationships with other objects and can act as both the parent and child in different relationships. To convert a lookup relationship to a master-detail relationship, the parent object must have fewer than two existing master-detail relationships with other objects. The Galaxy object is required to contain existing roll-up summary fields is not a valid consideration, as it is not related to converting a lookup relationship to a master-detail relationship. 

The field attribute that should be selected are Unique and External ID. Unique means that the field will not allow duplicate values. External ID means that the field can be used as a foreign key for data imports and upserts. Option B is incorrect because Required means that the field must have a value and cannot be left blank, which is not necessary for this requirement. Option D is incorrect because Text (encrypted) means that the field will store sensitive data in an encrypted format, which is not necessary for this requirement.

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

 The app builder should recommend configuring Campaign Hierarchies and Campaign statistics to understand return on investment for the latest advertising buy. Campaign Hierarchies allow users to organize campaigns into parent-child relationships based on common goals or themes, such as product lines or marketing channels. Campaign statistics allow users to track and measure key metrics for campaigns and campaign hierarchies, such as budgeted cost, actual cost, expected revenue, number of leads, number of contacts, etc. By using these features, users can calculate return on investment for each campaign and campaign hierarchy by comparing actual cost and expected revenue. Utilizing Account Hierarchies and Roll-Up Summary fields is not a valid recommendation, as it does not relate to campaigns or advertising buys. Account Hierarchies allow users to organize accounts into parent-child relationships based on business structure or affiliation, such as subsidiaries or partners. Roll-Up Summary fields allow users to aggregate numeric values from child records related to a parent record by a master-detail relationship. Running an opportunities pipeline report is not a valid recommendation, as it does not provide information about campaigns or advertising buys. An opportunities pipeline report shows the stages and amounts of opportunities in the sales process, such as prospecting, qualification, negotiation, etc. Changing to a public security model is not a valid recommendation, as it does not affect the ability to track and measure campaigns or advertising buys. A public security model is a type of organization-wide default that determines the baseline level of access that users have to records they do not own. A public security model grants all users read or read/write access to all records, regardless of ownership.

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

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

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

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

Reference for sandbox types and their capabilities:

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

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.

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

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

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

 Sales rep B has implicit access to the Account because of the manual sharing of the Opportunity. Implicit sharing grants access to parent records when a user has access to a child record. Sales rep B was not added to the Account team, sharing set is not applicable for private sharing model, and Account was not manually shared.

The Owner field on the Master record determines the ownership and sharing access of the detail record in a master-detail relationship. According to the Salesforce documentation, “The detail record inherits the sharing and security settings of its master record.” The default owner is not set in the parent object’s settings, the Owner field on the Detail record does not exist, and the owner is not set independently on the detail object’s settings.

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

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.

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

The best solution to enable reps to see and access the most-used components from anywhere within the app without leaving the page they are working on is Utility bar. This is a footer that can be added to any Lightning app and can contain tools such as history, notes, or softphone. Favorites, home page, and global actions are not solutions that provide access to components from anywhere within the app. See [this article] for more information on Utility bar.

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.

Sharing the dashboard folder with roles and subordinates of the US Sales Director and sharing the report folder with the role of US Sales Director will ensure that only the US sales directors can see the data in the component and view its source report, while all US sales reps can view the US Team dashboard. Making the US Sales Director the running user will show only his or her data in the component, not the whole team’s data. Making the dashboard dynamic will show different data depending on who is viewing it, not based on their role. Sharing the dashboard with the public group US Sales Reps and sharing the dashboard source reports folder with the US Sales Director profile will not prevent other profiles from accessing the reports if they have access to the report folder.

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.

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

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

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

 The app builder should use two options to ensure all contracts route for the correct approval and also prevent the sales rep from making changes to the record while it is being approved:

• Create an approval process on the Contract object with criteria set on a second approval step set as ‘Amount__c > 10,000’ and set the approver as director. An approval process is a type of process that automates how Salesforce records are approved in an organization. An approval process can have multiple steps with different criteria and approvers. In this case, the app builder can create an approval process on the Contract object with two steps: one for the sales manager approval and one for the director approval if the contract amount is over $10,0001.
• Create a validation rule on the Contract object that prevents updates to the contract record while it is being reviewed. A validation rule is a type of rule that checks data quality by verifying that the data in a record meets certain standards before it can be saved. A validation rule can prevent users from making changes to a record that is in a certain status or stage. In this case, the app builder can create a validation rule on the Contract object that prevents updates to the contract record if its Approval Status field is not equal to Not Submitted2. Option B and D are not options that can ensure all contracts route for the correct approval and also prevent the sales rep from making changes to the record while it is being approved.

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)

• Data Export Service is the appropriate tool for initiating scheduled or immediate backups of Salesforce data.References:
• Salesforce Help - Data Export Service

To insert a list of 25,000 records using deduplication for the Race_Track__c custom object, an app builder should use Data Loader. Data Loader is a tool that allows users to insert, update, delete, or export large amounts of data in Salesforce. Data Loader can also perform deduplication by matching records based on external ID fields or Salesforce record IDs. [Source]

 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.

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.

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.

When activating a Lightning page from the Lightning App Builder, three options are available:

• Assign the page to a combination of apps and profiles. This option allows users to specify which apps and profiles will see the custom Lightning page instead of the default page.
• Make the page the org default. This option makes the custom Lightning page the default for all users in the org regardless of their app or profile.
• Make the page the default homepage for specific apps. This option allows users to set different homepages for different apps in Lightning Experience. [Source]

 Launch a new approval process that has automatic submission enabled as an initial submission action, and Create a new approval process that has automatic submission enabled in the entry criteria. These are correct because both options allow the deals to be automatically submitted for approval without requiring any action from the sales rep. The automatic submission can be configured either as an initial submission action or as part of the entry criteria

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.

 The app builder would enable this ability in Chatter Settings. Chatter Settings is a setup menu that allows an app builder to configure various aspects of Chatter functionality, such as feeds, groups, email notifications, and more. One of the options in Chatter Settings is Enable Approvals via Chatter, which allows users to approve or reject requests from their team via Chatter posts or comments. Option A, B, and D are not places where an app builder would enable this ability.

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

Schema Builder allows users to create custom objects, fields, and relationships using a drag-and-drop interface. However, one of the limitations of Schema Builder is that fields and relationships can be created, but they will be unable to add the fields to the page layout from the canvas. Users will need to go to the Lightning Object Manager or Setup to edit the page layout and add the fields.

 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.

The correct validation rule formula to ensure that the Scheduled Ship Date field is properly filled out before setting the Opportunity to Closed Won is:

OR(ISPICKVAL( StageName ,“Closed Won”) && ( Scheduled_Ship_Date_cCloseDate)>14,ISBLANK(Scheduled_Ship_Date_c))

This formula checks two conditions: if the StageName is Closed Won and the Scheduled Ship Date is more than 14 days after the Close Date, or if the Scheduled Ship Date is blank. If either condition is true, the validation rule will fire and prevent saving the record. The other formulas are incorrect because they either use incorrect syntax (such as “=” instead of “,” or missing parentheses) or incorrect logic (such as checking if the Scheduled Ship Date is less than 14 days after the Close Date)

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

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.

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

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

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

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

• User A is on the same account team as user C. Account teams are groups of users who work together on an account. Users who are on an account team can have access to the account and related records owned by other team members.
• User C has manually shared the record with user A. Manual sharing is a way of granting access to individual users or groups by the record owner or someone above them in the role hierarchy.
• User A is in a public group that has access via a sharing rule. Public groups are groups of users who can be used to share data or assign permissions. Sharing rules are automatic rules that grant access to groups of users based on certain criteria. Option B and D are not reasons for user A’s access.

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

• Track the total number of gift cards opened and gift cards issued on an Account: This can be done by creating roll-up summary fields on the Account object that count or sum up the values from the gift card records related to each account.
• Permanently ensure the gift cards are unable to be moved across any other Account once it is created: This can be done by making the master-detail relationship field required on the gift card object, which means that every gift card record must be associated with an account record and cannot be changed once set. Option B, C, and D are not types of fields that can support this requirement.

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

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

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

 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.

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

 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

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

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

The Account record includes Invoice roll-up summary fields. This is correct because roll-up summary fields are only available on the master object in a master-detail relationship, and changing the field type to lookup would delete the roll-up summary fields

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.

 It will fail if there is a feature only available in the next version. According to the Salesforce documentation, “If your sandbox is on a newer version than your production org, you can’t deploy any components that are new in the sandbox version.” The change set components will not be upgraded to the next version in production, the change set will not be automatically deployed when production is upgraded, and the deployment is possible if there are no new features involved.

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

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

 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 solution that an app builder should use to meet this requirement is creating a custom report type with converted leads as the primary object. A custom report type is a template that defines the objects and fields that are available for a report. The app builder can create a custom report type that has converted leads as the primary object and includes fields from related objects, such as accounts, contacts, and opportunities. This way, sales reps can create reports on converted leads and see their related information. Option A is incorrect because enabling preserve lead status in the lead conversion settings does not affect the reporting on converted leads, but rather allows users to retain the original lead status after conversion. Option B is incorrect because assigning the representative view and edit converted leads permission does not affect the reporting on converted leads, but rather allows users to view and edit converted lead records. Option C is incorrect because ensuring the representative has read access to the original lead records does not affect the reporting on converted leads, but rather allows users to view the original lead records.

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. 

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

• 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

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

• Use Global Actions to make it easy to perform vital functionality on mobile: Global actions are actions that allow users to create records or perform tasks from anywhere in Salesforce. They are displayed in various places in Salesforce mobile app, such as action bar, action menu, or publisher. By using global actions, the app builder can make it easy for the appraisal team to perform common tasks on mobile, such as creating a new appraisal record or logging a call.
• Minimize the amount of formula fields and lookup fields to reduce page load time: Formula fields and lookup fields are types of fields that can affect the performance of Salesforce mobile app. Formula fields are fields that calculate a value based on an expression or formula. Lookup fields are fields that create a relationship between two objects and allow users to select a value from a list of records. Both types of fields can increase the page load time on mobile devices, especially if they are complex or reference many other fields. By minimizing the amount of formula fields and lookup fields, the app builder can optimize the mobile experience for the appraisal team.
• Put the most important fields in the compact layout so they are easy to find: Compact layouts are layouts that display a record’s key information at a glance. They are used in various places in Salesforce mobile app, such as record highlights, list views, related lists, and lookup dialogs. By putting the most important fields in the compact layout, the app builder can ensure that the appraisal team can easily find the information they need on mobile devices. Option B and D are not things that an app builder should do to optimize mobile experience.

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