Salesforce Platform-App-Builder Salesforce Certified Platform App Builder(SP23) Exam Practice Test

Create a Chatter stream. This is correct because a Chatter stream allows users to follow multiple records and people in one feed, and filter the feed by selecting a stream.

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

When attempting to change a master-detail relationship to a lookup relationship, Salesforce imposes specific restrictions to maintain data integrity:

• C. The Account record includes Parks roll-up summary fields. Master-detail relationships allow roll-up summary fields to aggregate data from child records onto the parent record. If any roll-up summary fields are present on the master object (Account in this case) that depend on the detail records (Parks), the relationship cannot be changed to lookup until these roll-up summary fields are removed.

To resolve this, follow these steps:

• Identify and delete all roll-up summary fields on the Account object that reference the Park object.
• Convert the master-detail relationship to a lookup relationship.
• Recreate any necessary roll-ups using declarative tools like Process Builder or Flow if needed, as lookups do not support native roll-up summaries.

For more guidance, review Salesforce's documentation on Changing Field Types.

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

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.

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

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.

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.

 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.

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.

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.

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

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

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

The common items that can be moved using a change set are custom object, Apex class, and custom field. These are metadata components that can be deployed from one environment to another using change sets. Web-to-lead and standard fields are not metadata components that can be moved using change sets.

• 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

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

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.

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

The app builder should use a global picklist value set to share the list of values for the Status field across each object. A global picklist value set is a set of values that can be used by multiple picklist fields on different objects. This can ensure data consistency and reduce maintenance efforts. Option A, C, and D are not features that can share picklist values across objects.

Apex unit test failures can cause a package installation to fail. According to the Salesforce documentation, “If your package contains Apex code, all tests must complete successfully for your package to install.” Incorrect license types, package features not compatible, and object limits exceeded are not valid reasons for a package installation failure.

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

 Formulas cannot reference child records, only parent records. This is a limitation of formulas that could be causing the issue. To include data from related child records, the app builder could use roll-up summary fields or Apex triggers instead

The app builder should recommend UC use Salesforce Connect to access the assets in real-time data in Salesforce. Salesforce Connect is a feature that allows users to view, search, and modify data that is stored outside Salesforce, such as in an external system. Salesforce Connect uses external objects and external data sources to integrate data from various sources without copying or synchronizing it2. This can help UC access their assets in real-time without consuming data storage limits in Salesforce. Option A, C, and D are not features that can meet this requirement.

The best way to calculate an overdue date that is two months after a task due date is to use a formula field with the ADDMONTHS() function. This function adds a specified number of months to a date value, and returns a new date value. See [this article] for more information on formula fields.

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.

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

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

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

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

 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.

 Big objects and external objects can be used to archive historical data and reduce data storage in Salesforce, while still allowing users to access the archived data using reports, queries, and lookups. Big objects store data within Salesforce, while external objects store data outside Salesforce and integrate it with Salesforce using an external data source

Standard buttons can be overridden with a Visualforce page to provide custom functionality or user interface. For example, you can override the New button on an object to display a custom Visualforce page instead of the standard page layout3. Standard buttons that are not available for overrides can still be hidden on page layouts to prevent users from accessing them. For example, you can hide the Delete button on an object to prevent users from deleting records

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.

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.

For tracking whether contracts have been sent for Opportunities:

• D. Checkbox. This field type allows users to clearly indicate (Yes/No) whether a contract has been sent. This binary nature of checkboxes makes it simple to filter and report on Opportunities based on whether a contract was sent.

Steps to configure this field:

• Navigate to Setup → Object Manager → Opportunity.
• Click Fields & Relationships → New → Checkbox.
• Define the field with a label (e.g., Contract Sent).
• Set the default value to false (unchecked).
• Add the field to the relevant page layouts.

This setup facilitates accurate reporting and ensures that opportunities cannot be marked as "Closed Won" without indicating whether a contract was sent.

For guidance on creating fields, see Salesforce's documentation on Custom Field Creation.

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 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 ensure that only the sales reps and their manager’s executive can view the rep’s evaluation record but the reps should not be able to view the executive comment field on their review, a private sharing model granting record access using hierarchy and field-level security should be used. A private sharing model means that only the owner of a record and users above them in the role hierarchy can view the record by default. Record access can be granted to other users using manual sharing, sharing rules, or Apex sharing. Field-level security controls which fields are visible or editable for different profiles or permission sets.

The import wizard only allows values to be imported into a dependent picklist if they match the appropriate controlling field. This ensures data integrity and prevents invalid values from being imported. Custom picklist fields can be either controlling or dependent fields. This allows the app builder to create custom dependencies between custom picklists. Checkbox fields can be controlling fields but not dependent fields. This allows the app builder to create dependencies based on checkbox values, such as true or false. Multi-select picklist fields can be dependent picklist fields but not controlling fields. This allows the app builder to create dependencies based on multiple values selected in a multi-select picklist field. Standard and custom picklist fields can be dependent fields, but not all standard picklist fields can be controlling fields. Some standard picklist fields, such as Lead Status or Opportunity Stage, cannot be controlling fields because they are used in other processes, such as lead conversion or sales path

The app builder should use the CASESAFEID(Id) formula to create this new field. The CASESAFEID function returns the 18-digit case-insensitive version of the record ID, which is unique for each record in Salesforce. The 18-digit record ID is useful for exporting data to external systems that require case-sensitive IDs1. Option A, C, and D are not formulas that can return the 18-digit record ID.

LEFT(Account.Zip_Code_c, 5) is the correct formula to display only the first five digits of Zip Code from the parent Account. LEFT function returns the specified number of characters from the left side of a text string. Account.Zip_Code_c is the custom text field that stores the Zip Code on Account object. 5 is the number of characters to return from the left side of the Zip Code. The other options are not valid formulas or functions.

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. 

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

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.

To manage frequently changing picklist values effectively:

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

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

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.

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

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

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

The best way to show Asset Inventory as a related list on Asset is to create a lookup relationship on Asset Inventory to Asset. This will allow one-to-many relationship between Asset and Asset Inventory, and display the related records on the Asset page layout.

 The best way to configure Account sharing so that community users only see their own Account is to set the account external OWD to private. This will restrict the access to Account records for external users based on the sharing rules and criteria. Creating an account record type, defining an owner-based sharing rule, or defining a permission set will not prevent community users from seeing other accounts.

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.

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.

To track the total number of trails associated with a park without writing code, the correct actions to take are:

• Use a roll-up summary field on the Park record to show the total number of Trails (B). Roll-up summary fields calculate and display a value in a master record based on the values of fields in a detail record. They are used to count, sum, average, or get the minimum/maximum of values in related detail records.
• Use a master-detail relationship between the Park and Trail objects (C). Master-detail relationships are necessary for roll-up summary fields as they allow the master object to control certain behaviors of the detail object and summarize data from those detail records.

A formula field (A) cannot dynamically count related records unless those records are linked via a master-detail relationship, and it cannot alone handle counts across related records without such a relationship. A lookup relationship (D) does not support roll-up summaries unless combined with additional tools like triggers or third-party apps, which involve coding or extra configuration outside standard object setup.

For more details, refer to the Salesforce Help documentation on master-detail relationships and roll-up summary fields:

• Master-Detail Relationship: https://help.salesforce.com/articleView?id=relationships_considerations.htm&type=5
• Roll-Up Summary Fields: https://help.salesforce.com/articleView?id=fields_about_roll_up_summary_fields.htm&type=5

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.

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.

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.

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]

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

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

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

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

• A: Highlights panel is used for displaying key record information at the top of the page and is not designed for managing multiple fields.
• B: Record detail displays all fields on a single layout, which does not suit the requirement to break up the fields.
• C: Field section does not exist as a standard Lightning component. Reference: Accordion Component in the Lightning Component Library

The feature that the app builder should use to solve this issue is component visibility filter. A component visibility filter is a setting that can be applied to a Lightning component on a record page to control when the component is hidden or displayed based on certain conditions. The app builder can use a component visibility filter to hide the component from users with a Marketing profile. Option A is incorrect because detail page layouts are not related to Lightning components, but rather the fields and related lists that appear on record detail pages. Option C is incorrect because field-level security is not related to Lightning components, but rather the access level of fields for different profiles or permission sets. Option D is incorrect because AppExchange is not related to Lightning components, but rather an online marketplace where users can find and install apps and components.

Create mobile navigation menus for both the sales and marketing profiles. This is correct because mobile navigation menus allow users to customize the items that appear in the navigation bar of the Salesforce mobile app, and they can be assigned to different profiles.

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

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.

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.

• A: Changing the Lead Matching Rule to 'Block on create' will directly prevent duplicates at the point of lead creation based on defined criteria.
• C: Changing the Lead Duplicate Rule to 'Bypass Sharing Rules' allows the system to compare leads across the entire organization regardless of the user's access level, which is crucial especially when OWD is set to 'Private'.References:
• Salesforce Help - Duplicate Management

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

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

To ensure auditing users can access records in the Case_Issue__c junction object, the correct data permissions on related records must be established:

• D. Read-Only access on Case and Issue__c. Users need read-only access to both Case and Issue__c objects to view associated Case_Issue__c junction object records properly. This is because access to junction object records in Salesforce is determined by the user's access levels to the parent records in a relationship.

Steps to configure access:

• Navigate to Setup → Profiles or Permission Sets.
• Select the profile or permission set of the auditing users.
• Under Object Settings, adjust the permissions for Case and Issue__c to at least 'Read-Only'.
• Ensure that users have visibility to the Case_Issue__c object itself.

This configuration allows users to view the details of cases and issues as they audit the junction object records.

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

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

The app builder should add the field to the custom report type field layout to troubleshoot this issue. A custom report type is a type of report that defines which objects and fields are available for reporting. The app builder can customize which fields are included in each custom report type by editing its field layout. If a new field is added to an object that is part of an unmanaged package, it will not be automatically added to the custom report type field layout. The app builder needs to manually add it to make it available as an option to add as a column in reports based on that custom report type. Option A, B, and D are not steps that can troubleshoot this issue.

The Invoice Number field should be a Text field and marked as a unique external ID field. This will allow the migration of invoices from an external system while maintaining their original Invoice Number. It will also ensure that each new Invoice created in Salesforce has a unique Invoice Number.

To 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

If the app builder tries to convert a preexisting long text area field to text area, preexisting information will truncate to the first 255 characters. This means that any information beyond 255 characters will be lost. Option B is incorrect because preexisting information will not remain if it was over 255 characters. Option C is incorrect because preexisting information will not cause an error message to pop up. Option D is incorrect because preexisting information in the field will not be completely lost, only truncated.

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

 The two features of Chatter that would meet CK’s business needs are: Set up new public Chatter groups. A public Chatter group is a way to create a collaborative space for users to share information, files, polls, and ideas around a common topic or interest. A public Chatter group can be joined by any user in the organization and can be seen by anyone who has access to Chatter. By setting up new public Chatter groups, CK can enable users to socialize and collaborate around customer accounts and discuss various topics. Use post action on the Account object. A post action is a type of quick action that allows users to create a post on a record’s feed or on their own feed. A post can include text, mentions, hashtags, topics, links, files, or images. By using post action on the Account object, CK can enable users to share updates, feedback, or questions about customer accounts and engage with other users who follow the accounts. Set up new private Chatter groups is not a valid feature, as it does not meet CK’s business needs. A private Chatter group is a way to create a collaborative space for users to share information, files, polls, and ideas around a confidential or sensitive topic or interest. A private Chatter group can only be joined by invitation and can only be seen by the group members. By setting up new private Chatter groups, CK would limit the visibility and accessibility of the conversations around customer accounts. Use Chatter actions to create tasks to complete is not a valid feature, as it does not meet CK’s business needs. A Chatter action is a type of quick action that allows users to create a task from a record’s feed or from their own feed. A task can include subject, due date, priority, status, assigned to, etc. By using Chatter actions to create tasks to complete, CK would enable users to track and manage their work related to customer accounts, but not to socialize and collaborate with other users.

• The deployed permission set will merge with the existing permission set in production, meaning changes made in the sandbox will be added to the existing permission set after deployment.References:
• Salesforce Help - Permission Sets

For automatically updating contact statuses when an account type changes:

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

Steps to implement:

• Navigate to Setup → Flows.
• Create a new Flow and choose the record-triggered flow type.
• Configure the flow to trigger when the Account record is updated to 'Past-Customer'.
• Add an Update Records element to modify all related contacts, setting their status to 'Re-Market'.
• Activate the flow.

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

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

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

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

 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.

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.