Salesforce Platform-App-Builder Salesforce Certified Platform App Builder (Plat-Admn-202) Exam Practice Test

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.

The app builder should recommend a workflow rule to automate this process. A workflow rule is a type of automation tool that can execute actions based on certain criteria. In this case, the workflow rule can have a criterion that evaluates if the DoNotCall checkbox is checked on a Contact record, and then execute a field update action that sets the Phone field to null. Option A, B, and C are not automation tools that can perform this task.

The app builder should use two tools to automate this process:

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

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

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

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 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 requirement specifies:

Subset of production data (not all data)

Under 5 GB of data

Periodic refresh (every weekend)

A Partial Copy sandbox fits these requirements perfectly — it includes sample data defined by a sandbox template, up to 5 GB, and has a refresh interval of 5 days (the shortest interval available besides Developer types).

Why A (Partial Copy) is correct:Exact Extract:“A Partial Copy sandbox includes your organization’s metadata and a sample of your production data as defined by a sandbox template. The maximum size is 5 GB and the refresh interval is 5 days.” — Salesforce Help | Sandbox Types and Templates

Why not B (Full Copy):Full Copy includes all production data and has a 29-day refresh interval.

Why not C or D:Developer and Developer Pro sandboxes contain metadata only and no production data.

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.

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.

To facilitate quick managerial sign-off on discounted opportunities:

B. Dynamic Actions: Allows the display of specific actions on the Opportunity record page based on certain conditions, like the discount percentage.

D. Approval Process: Configures a formal sign-off process for records meeting specific criteria, such as discount ranges between 20% to 30%.

Steps to set up:

Configure an approval process for opportunities where the discount is between 20% and 30%.

Use Dynamic Actions to conditionally show the approval action directly on the Opportunity record page based on the discount percentage.

This setup allows sales managers to efficiently review and approve discounted deals directly from the Opportunity record page.

For guidance on setting up approval processes and dynamic actions, refer to Dynamic Actions in Salesforce.

 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.

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.

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

To display a weather map component on a Lightning record page conditionally:

A. Component visibility should be used. This feature in the Lightning App Builder allows components on a Lightning page to be displayed based on specific criteria, such as field values or user attributes. In this case, the app builder can set the visibility of the weather map component to only appear when a house is scheduled for a showing based on the relevant field values.

For more details on setting up conditional component visibility, review the guide on Dynamic Lightning Pages.

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

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.

Managed packages from the AppExchange are designed to provide automatic updates, upgrades, and vendor support, minimizing the need for ongoing manual maintenance by the customer.

Why D (Managed Package from AppExchange) is correct:Exact Extract:“Managed packages are maintained by the provider and can be automatically upgraded. They’re ideal for apps distributed and maintained through AppExchange.” — Salesforce Help | Managed and Unmanaged Packages OverviewManaged packages allow publishers to push automatic updates and ensure compatibility with future Salesforce releases — minimizing maintenance effort.

Why D (Managed Package from AppExchange) is correct:Exact Extract:“Managed packages are maintained by the provider and can be automatically upgraded. They’re ideal for apps distributed and maintained through AppExchange.” — Salesforce Help | Managed and Unmanaged Packages OverviewManaged packages allow publishers to push automatic updates and ensure compatibility with future Salesforce releases — minimizing maintenance effort.

Why not A (Open-source custom development):Open-source code must be maintained internally by developers.

Why not B (Unmanaged package):Unmanaged packages are customer-controlled and do not receive automatic updates.

Why not C:Open-source unmanaged packages combine the same issue — no automated support or maintenance.

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

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

The new custom object (“Installation__c”) must store installation details that are related to an Opportunity. Since each installation should be tied directly to a single opportunity, and inherit ownership and visibility from that opportunity (as per “sales reps should have visibility”), a Master-Detail relationship is appropriate.

Why B (Master-Detail) is correct:Exact Extract:“In a master-detail relationship, the detail record inherits the sharing and security settings of its master record.” — Salesforce Help | Relationships OverviewBecause Opportunities already have ownership and sharing settings that determine sales reps’ visibility, making Installation__c the detail record ensures that sales reps automatically see related installations.Exact Extract:“The master-detail relationship closely links objects so that the master record controls certain behaviors of the detail record, such as record ownership, sharing, and deletion.” — Salesforce Help | Master-Detail Relationships

Why B (Master-Detail) is correct:Exact Extract:“In a master-detail relationship, the detail record inherits the sharing and security settings of its master record.” — Salesforce Help | Relationships OverviewBecause Opportunities already have ownership and sharing settings that determine sales reps’ visibility, making Installation__c the detail record ensures that sales reps automatically see related installations.Exact Extract:“The master-detail relationship closely links objects so that the master record controls certain behaviors of the detail record, such as record ownership, sharing, and deletion.” — Salesforce Help | Master-Detail Relationships

Why not A (Many to Many):Many-to-many relationships are only used when multiple records on both sides need to relate (e.g., Opportunities linked to multiple Installations and vice versa). That is not described here.

Why not C (Hierarchical):Hierarchical relationships are only available on the User object.

Why not D (Lookup):Lookup relationships do not automatically grant visibility or inherit ownership, so sales reps might not see all related installations.

References (Salesforce Platform App Builder documentation / Study Guide topics):

Salesforce Help | Relationships Overview

Salesforce Help | Master-Detail Relationships

Salesforce Platform App Builder Exam Guide | Data Modeling and Management

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

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.

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

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

Steps to enable offline capabilities:

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

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

Ensure that the Contact object is available for offline access.

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

For implementation details, refer to Salesforce Mobile App Offline.

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.

Roll-up summaries allow MAX, MIN, SUM, COUNT, and AVG functions on numeric fields from child records related by a master-detail relationship. Roll-up summaries are limited to master-detail relationships and cannot be used with lookup relationships. An object can have up to 40 roll-up summary fields, not 25. An object can have up to 25 relationship fields (master-detail or lookup), not 20.

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.

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

Process Builder: This is a type of automation tool that can execute actions based on certain criteria. In this case, the process builder can have a criteria that evaluates if an opportunity is in the Secure Commitment Stage, and then execute an action that submits it for approval.

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

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

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

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.

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

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.

 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.

 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

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.

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

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

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

Steps to set up these features:

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

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

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

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

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

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

To connect Testimonial__c records with both the submitter’s Contact record and Account record, an app builder should create a master-detail relationship from Testimonial__c to Account and a lookup relationship from Testimonial__c to Contact. A master-detail relationship creates a parent-child relationship between two objects and allows for roll-up summary fields, sharing settings, and cascading actions. A lookup relationship creates a loose association between two objects and allows users to relate records from one object to another. Source

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.

Opportunities are in a master-detail-like relationship with Accounts (standard lookup behaves with special roll-up capabilities). Salesforce provides a standard roll-up summary feature on the Account object to count related Opportunities.

Why B (Roll-up Summary) is correct:Exact Extract:“Use a roll-up summary field to automatically display a value from related detail records on a master record. You can count related records, or calculate the sum, min, or max of a field on those records.” — Salesforce Help | Roll-Up Summary FieldsOn Account, you can create a roll-up summary field to COUNT related Opportunities.

Why B (Roll-up Summary) is correct:Exact Extract:“Use a roll-up summary field to automatically display a value from related detail records on a master record. You can count related records, or calculate the sum, min, or max of a field on those records.” — Salesforce Help | Roll-Up Summary FieldsOn Account, you can create a roll-up summary field to COUNT related Opportunities.

Why not A:Formula fields cannot count related records.

Why not C:AppExchange is not required; Salesforce provides native functionality.

Why not D:A lookup only links records—it does not perform aggregation.

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

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

Steps to create a flow for this purpose:

Navigate to Setup → Flows.

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

Design the flow with Screen elements for each question.

Add logic to process responses as necessary.

Save and activate the flow.

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

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

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

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

When a field is added to an object, it doesn’t automatically appear in custom report types — even if the field is visible and reportable. The app builder must manually add the field to the custom report type layout to make it available in reports.

Why D (Add the field to the custom report type field layout) is correct:Exact Extract:“If a new custom field isn’t available in your report builder, edit the custom report type layout and add the field. Fields created after the report type was built must be added manually.” — Salesforce Help | Custom Report Types

Why not A:Field-level security controls visibility but not inclusion in the report type layout.

Why not B:“Allow Reports” affects whether the entire object is reportable, not individual fields.

Why not C:The “Manage Public Reports” permission allows editing public reports but doesn’t influence field visibility.

To test a picklist field in a formula, ISPICKVAL must be used. To check if the CloseDate is within 7 days of the current date, you can use simple date arithmetic (CloseDate - 7 < TODAY()).

Why A is correct:Exact Extract:“Use ISPICKVAL to determine if a picklist field has a specific value.” — Salesforce Help | ISPICKVAL Function“Date formulas can use arithmetic to compare a date to TODAY(). For example, CloseDate - 7 < TODAY() returns TRUE if CloseDate is within the next week.” — Salesforce Help | Date Functions and Operators

Why not B:Picklist fields cannot be compared with =; this formula would fail to compile.

Why not C or D:The function DAY() returns the day of the month from a date — not a duration. DAY(7) is invalid in this context.

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

Schema Builder is a tool that presents a comprehensive view of all relationships in one place. It allows app builders to see how objects are connected and create new relationships. Lightning Object Creator, Object Manager, and Lightning Record Page are not tools for viewing relationships, but for creating objects, managing fields, and customizing record pages respectively.

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)

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

 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.

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

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

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

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

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

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

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

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

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

Winter '24 Flow Outbound Message

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

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

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

xml

Copy code

lightning__UtilityBar

Utility Bar Components Documentation

Option A: For use on record pages: This tag makes the component available only on record pages, but not the utility bar. The component would have a target for lightning__RecordPage in this case.

Option B: For use in Lightning App Builder: This option would allow the component to be used in the Lightning App Builder, but it wouldn't make the component available for the utility bar. App Builder placement is typically for page layouts.

Option D: For use in App Manager: This is incorrect, as App Manager is used for managing apps and not for tagging components for availability.

In summary, to make the component available for the utility bar, it needs to be specifically tagged for that purpose using the lightning__UtilityBar target in the component's metadata file.

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

Schema Builder provides a graphical representation of all standard and custom objects and their field and relationship structure. It’s the best tool for visualizing how data objects are interconnected.

Why D (Schema Builder) is correct:Exact Extract:“Schema Builder provides a dynamic environment for viewing and modifying all the objects and relationships in your organization. You can add new custom objects, fields, and relationships directly in the schema.” — Salesforce Help | Schema Builder Overview

Why not A (Fields & Relationships):That section displays fields for a single object only, not overall relationships.

Why not B (Object Manager):The Object Manager allows object configuration but doesn’t visually display relationships.

Why not C (Lightning App Builder):That tool is for UI layout, not data model visualization.

This formula concatenates the four custom fields for the Galactic Vendor’s location into a single text value, separated by commas and spaces. The formula also uses the BR function to insert a line break after the second field, creating two lines of text. Option A, B, and D are not formulas that fulfill the requirement.

The validation rule should be AND(ISNEW(), ISBLANK(Lead.Owner:User.Id)). This rule will prevent saving a new lead record if the owner is not a user. This will ensure that campaign members have a sales owner. Option A is incorrect because it will prevent saving any lead record if the owner is blank, which is not the requirement. Option B is incorrect because it will prevent saving an existing lead record if the owner is a queue, which is not the requirement. Option D is incorrect because it will prevent saving any lead record if the owner is a queue, which is not the requirement.

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

To 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

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

A flow is an application that automates a business process by collecting data and performing operations in your org or an external system. Flows can also manipulate data in your org by creating, updating, deleting, or submitting records for approval. You can use flows to update fields on related records when a certain event occurs, such as closing a work order. In this case, a flow can be used to update the last maintenance date field on the Asset record when a maintenance work order gets closed.

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.

 Marking stage dependent fields as required on the Opportunity page layout is a good solution to improve efficiency and data quality, as it ensures that users enter the necessary information for each stage of the sales process. Adding a Path component with fields and instructions aligning to stages on the Opportunity is another good solution to improve efficiency and collaboration, as it provides guidance and best practices for users to move the Opportunity along the sales cycle. Using two Tabs components to separate record information from activities may not be an optimal solution, as it may reduce the visibility and accessibility of important data. Setting up an approval process requiring manager consent at each stage of the Opportunity may not be a feasible solution, as it may introduce unnecessary delays and complexity in the sales process

The requirement is to automatically grant record visibility to all users in a specific role (Service Manager) based on record criteria (“Opportunity Type = Service Agreement”).

This is a textbook case for a criteria-based sharing rule.

Why C (Criteria-Based Sharing Rule) is correct:Exact Extract:“A criteria-based sharing rule determines which records to share based on field values, rather than who owns the record.” — Salesforce Help | Sharing Rules OverviewYou can define the rule to share all Opportunities where Type = 'Service Agreement' with all users in the Service Manager role.Exact Extract:“Use criteria-based sharing rules to share records based on record field values with roles, roles and subordinates, or public groups.” — Salesforce Help | Criteria-Based Sharing Rules

Why C (Criteria-Based Sharing Rule) is correct:Exact Extract:“A criteria-based sharing rule determines which records to share based on field values, rather than who owns the record.” — Salesforce Help | Sharing Rules OverviewYou can define the rule to share all Opportunities where Type = 'Service Agreement' with all users in the Service Manager role.Exact Extract:“Use criteria-based sharing rules to share records based on record field values with roles, roles and subordinates, or public groups.” — Salesforce Help | Criteria-Based Sharing Rules

Why not A (Manual Sharing):Manual sharing requires a user to share each record individually — it is not automated.

Why not B (Owner-Based Sharing Rule):Owner-based rules share records based on who owns them, not on a record field value.

Why not D (Apex Sharing Rule):Apex sharing is used only when declarative sharing rules cannot meet the requirement. In this case, a standard criteria-based rule is sufficient.

References (Salesforce Platform App Builder documentation / Study Guide topics):

Salesforce Help | Sharing Rules Overview

Salesforce Help | Criteria-Based Sharing Rules

Salesforce Platform App Builder Exam Guide | Security

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

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

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

Reference for creating validation rules in Salesforce:

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

To troubleshoot the issue of a contact being unavailable for other users to see, an app builder should check the following things:

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

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

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

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 requirement is to copy the parent Account’s Billing State onto a custom field on Opportunity at the moment the Opportunity is created, and keep that value static thereafter.

Why not Formula (B): A formula would always recalculate, so the value would change if the Account’s Billing State later changes.Exact Extract: “Formula fields are read-only fields that automatically recalculate their values when any referenced fields change.” — Salesforce Help | Formula Fields

Why not Roll-Up Summary (A): Roll-up summary fields only summarize child records onto a master (parent) record; they do not copy values from a parent (Account) down to a child (Opportunity), and they can’t summarize a text/state value.Exact Extract: “A roll-up summary field calculates values from related records, such as those in a related list, on a master record.” — Salesforce Help | Roll-Up Summary Fields

Why Flow (C) is correct: A Record-Triggered Flow on Opportunity (when a record is created) can set a field value by referencing the related Account (e.g., Opportunity.Account.BillingState) and writing it into a dedicated “snapshot” field (e.g., Billing State at Create__c). Because this is a one-time assignment on create, the value remains static unless intentionally updated by further automation.Exact Extract 1: “Use Flow Builder to automate business processes by collecting data and performing actions in your Salesforce org.” — Salesforce Help | Flow BuilderExact Extract 2: “Record-triggered flows launch when a record is created, updated, or deleted, and can update fields on the triggering record.” — Salesforce Help | Record-Triggered Flows

Why Apex (D) is not preferred: While Apex could do the same copy-on-create, Salesforce’s recommended approach is to use declarative automation (Flow) when possible.Exact Extract: “Before considering Apex, evaluate whether your solution can be implemented with declarative tools such as Flow.” — Salesforce Architect Guidance | Clicks, Not Code

Implementation note (for clarity): Create a custom text field on Opportunity, e.g., Billing State at Create (Billing_State_at_Create__c). Build a Record-Triggered Flow:

Trigger: Opportunity — “A record is created”

Get or use the related Account from the $Record.AccountId relationship

Update the new Opportunity field with Account.BillingState

Do not run the flow on updates

References (Salesforce Platform App Builder documents / Study Guide topics):

Salesforce Help — Formula Fields

Salesforce Help — Roll-Up Summary Fields

Salesforce Help — Flow Builder

Salesforce Help — Record-Triggered Flows

Salesforce Architect Guidance — Clicks, Not Code

Salesforce Platform App Builder Exam Guide — Business Logic and Process Automation

A: Setting Sharing Settings to Read Only on both Master-Detail relationship fields ensures that users can view but not edit the master records from the junction object.

One of the limitations when using the Schema Builder for creating fields is:

C. Cannot add fields to page layouts. While Schema Builder allows for easy visualization and creation of fields and objects, it does not support placing these fields onto specific page layouts directly from the Schema Builder interface.

To place fields on page layouts, you need to:

Navigate to Setup → Object Manager → select your object.

Click on Page Layouts, choose the appropriate layout, and manually add the newly created fields.

This step is necessary to ensure fields are visible and properly arranged on user interfaces.

For more details, Salesforce's Schema Builder documentation outlines its capabilities and limitations.

The app builder needs to do two steps to make the custom Lightning App available to the internal users at Universal Containers:

Create a subdomain using My Domain: My Domain is a feature that allows an organization to set up a custom domain name for their Salesforce instance. This is required to use custom Lightning components and apps in Salesforce1.

Build a Custom Tab for the app: A custom tab is a tab that displays any custom object or web page in Salesforce. This is required to make the custom Lightning App accessible from the navigation menu or app launcher2. Option A and B are not necessary steps to make the custom Lightning App available to the internal users.

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

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

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

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.

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

 The app builder should use Sum as the type of summary in the roll-up summary field. A Sum type of summary allows the app builder to calculate the total value of a numeric field from the child records related to a parent record by a master-detail relationship. The app builder can create a roll-up summary field on the Account object that sums the Amount field from the won Opportunities related to each Account. Count is not a valid type of summary, as it does not calculate the total value of a numeric field. A Count type of summary allows the app builder to count the number of child records related to a parent record by a master-detail relationship. Max is not a valid type of summary, as it does not calculate the total value of a numeric field. A Max type of summary allows the app builder to display the largest value of a numeric or date field from the child records related to a parent record by a master-detail relationship. Min is not a valid type of summary, as it does not calculate the total value of a numeric field. A Min type of summary allows the app builder to display the smallest value of a numeric or date field from the child records related to a parent record by a master-detail relationship.

The Highlights Panel in the Lightning Record Page displays key fields and record actions prominently at the top of the page, exactly as described in the requirement.

Why A (Highlights Panel) is correct:Exact Extract:“The highlights panel displays important fields and key record actions at the top of the record page in Lightning Experience.” — Salesforce Help | Highlights Panel

Why not B:Path is used to visualize progress through stages (e.g., Opportunity Stage), not display multiple fields.

Why not C:A custom component is unnecessary since the standard Highlights Panel fulfills the requirement.

Why not D:Accordion is used to organize information in collapsible sections, not display key fields at the top.

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

Configuring a validation rule to require a field for a specific record type is the best way to ensure that important fields are entered and formatted correctly. Updating the important fields to be required on the page layout will not prevent users from entering invalid data using other methods, such as data loader or quick actions. Making a formula field to check the format of the important fields will not prevent users from entering invalid data, but only display a message or an indicator. Creating a workflow rule to check the fields are formatted correctly will not prevent users from entering invalid data, but only trigger an action after the data is saved.

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.

 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.

A validation rule can enforce process compliance by preventing users from saving records that do not meet certain criteria. In this case, a validation rule can prevent users from reverting to an earlier case status or leaving certain fields blank when specific case criteria are met

UMS wants each Application to connect both to a Job Candidate and an Open Position, where:

One Job Candidate can apply for multiple Open Positions.

One Open Position can receive multiple Applications.This is a many-to-many relationship, which in Salesforce is implemented by using a junction object.

In this case, Application__c serves as the junction object between Job_Candidate__c and Open_Position__c.

Exact Extract:

“To create a many-to-many relationship, create two master-detail relationships on the junction object. Each master-detail relationship links the junction object to one of the objects you want to relate.” — Salesforce Help | Create a Many-to-Many Relationship

Step 1: On Application__c, create a Master-Detail relationship to Job_Candidate__c (Answer C).

Step 2: On Application__c, create a Master-Detail relationship to Open_Position__c (Answer D).

This setup allows:

Viewing all Applications related to a given Job Candidate.

Viewing all Applications related to a given Open Position.

Exact Extract:

“A junction object is a custom object with two master-detail relationships, and it is the key to building many-to-many relationships between two objects.” — Salesforce Help | Junction Object Concepts

References (Salesforce Platform App Builder documentation / Study Guide topics):

Salesforce Help | Create a Many-to-Many Relationship

Salesforce Help | Junction Object Concepts

Salesforce Platform App Builder Exam Guide | Data Modeling and Management

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