All practice questions

1784 questions

All types1,784 Multiple choice918 Multiple select587 Matching142 Ordering137

A Salesforce Administrator is configuring a Custom Report Type to analyze relationships between Accounts (Primary Object) and Partner Surveys (Secondary Custom Object). The management team wants full flexibility to traverse lookup relationships for field selection and ensure accurate record inclusion based on survey responses. Which TWO configuration capabilities or constraints apply when defining the object relationships and field layout for this Custom Report Type? (Select TWO answers)

Select all that apply

Fields from objects up to four levels away linked via lookup relationships can be explicitly added to the report layout using the 'Add fields related via lookup' feature.

Configuring the object relationship as 'Each record must have at least one related record' (with relationship) excludes parent Account records that have no associated Partner Surveys from appearing in reports.

Summary report format must be selected during Custom Report Type creation to evaluate row-level record calculations instead of summary formulas.

Defining a custom report type between Accounts and Partner Surveys automatically creates system roll-up summary fields on the Account object across lookup relationships.

Removing a field from the Custom Report Type layout grid restricts Field-Level Security and API read access for users assigned to standard profiles.

Show answer & explanation

Answer: Fields from objects up to four levels away linked via lookup relationships can be explicitly added to the report layout using the 'Add fields related via lookup' feature.; Configuring the object relationship as 'Each record must have at least one related record' (with relationship) excludes parent Account records that have no associated Partner Surveys from appearing in reports.

Answer

The two correct statements are that fields up to four levels away via lookup relationships can be added to the layout using 'Add fields related via lookup', and that choosing the 'with' relationship ('Each record must have at least one related record') excludes parent records without matching child records.

Custom Report Types allow administrators to traverse up to four levels of lookup relationships to pull related object fields directly into the report layout using the 'Add fields related via lookup' feature. Additionally, setting the object relationship to 'Each record must have at least one related record' creates an inner join, requiring parent records to have corresponding child records to be displayed in reports.

Step-by-Step Solution

Evaluate object relationship join behavior

Selecting 'Each record must have at least one related record' acts as an inner join, filtering out Accounts that lack associated Partner Survey records.

Custom report types offer inner join ('with') and outer join ('with or without') options controlling record visibility.

Evaluate lookup field expansion capabilities

Administrators can click 'Add fields related via lookup' in the layout editor to reference fields up to 4 levels away from the primary/secondary objects.

This allows reports built on the custom report type to display referenced lookup object fields without creating redundant formula fields.

Key Concept

Custom Report Type Object Relationships and Layout Field Customization

Question 82Question →

A financial services company requires an automated process on the Account object to update the Priority field to 'Critical' on all open child Case records whenever an Account is marked as 'High Risk'. Because an Account may have hundreds of associated open Cases, the solution must strictly adhere to Salesforce governor limits. Which Flow Builder design strategy should the administrator implement to accomplish this requirement efficiently?

Use a Get Records element to retrieve all related open Cases into a collection, iterate through the collection with a Loop element, modify field values using an Assignment element to accumulate updated records into a target collection, and invoke a single Update Records element after the loop finishes.

Use a Get Records element to fetch related open Cases, iterate through them using a Loop element, and place an Update Records element directly inside the loop path to modify each Case record individually on each iteration.

Create a Roll-Up Summary field on the Account object linked via a lookup relationship to iterate through child Cases, and use a Decision element to automatically update Case priorities.

Use an Assignment element to update the Priority field directly on the Account record type picklist assignment, relying on automated record type cascading to push changes to all child Cases.

Show answer & explanation

Answer: Use a Get Records element to retrieve all related open Cases into a collection, iterate through the collection with a Loop element, modify field values using an Assignment element to accumulate updated records into a target collection, and invoke a single Update Records element after the loop finishes.

Answer

Use a Get Records element to retrieve all related open Cases into a collection, iterate through the collection using a Loop element, update record values within an Assignment element that adds modified records to a second collection variable, and perform a single Update Records element outside the loop.

The correct approach bulkifies the flow by performing data manipulation in memory using Assignment elements and executing only a single Update Records operation after the Loop finishes. This design scales safely for large numbers of related records without exceeding transaction governor limits.

Step-by-Step Solution

Retrieve related child records into a collection variable

A single Get Records element fetches all open Case records linked to the triggering Account ID without executing queries inside a loop.

Bulkifying data retrieval conserves SOQL query governor limits.

Iterate over the record collection and modify field values in memory

A Loop element evaluates each loop item, and an Assignment element updates the Priority field on the current loop item before adding it to a new output collection variable.

In-memory variable assignment does not consume database DML operations.

Commit all updated records in a single DML operation after loop completion

An Update Records element targets the output collection variable along the 'After Last' path of the Loop element.

Executing DML outside the loop ensures only one DML transaction statement is consumed regardless of how many child records are modified.

Key Concept

Flow Bulkification and Governor Limits

Estimated Time:2m 0s

Question 83Question →

Universal Containers requires an automated approval process for custom Discount Request records. When a Discount Request enters the approval process or receives final approval, the system must perform specific automated actions. Which TWO action types can an administrator configure directly as native automated actions within an Approval Process? (Select 2 options)

Select all that apply

Field Update

Post to Chatter

Outbound Message

Create a Record

Show answer & explanation

Answer: Field Update; Outbound Message

Answer

The correct native actions available within a Salesforce Approval Process are Field Update and Outbound Message.

Salesforce Approval Processes natively support four specific automated action types across initial submission, approval steps, final approval, final rejection, and recall actions: Email Alerts, Field Updates, Tasks, and Outbound Messages. Therefore, selecting Field Update and Outbound Message correctly identifies standard approval actions.

Step-by-Step Solution

Identify the four native automated action types supported directly by Salesforce Approval Processes.

The standard actions are Email Alerts, Field Updates, Tasks, and Outbound Messages.

Approval processes share the exact same standard action framework as legacy Workflow Rules.

Evaluate each choice against the four standard approval actions.

Field Update and Outbound Message match the supported list, whereas Post to Chatter and Create a Record require Flow Builder or Apex.

Distinguishing between native approval process actions and Flow capabilities prevents misconfiguration.

Key Concept

Standard Approval Process Automated Actions

Question 84Question →

A wealth management firm recently configured the Salesforce Integration with Outlook for its advisory team. The sales administrator created custom Lightning Email Templates organized inside custom shared folders so that advisors can select company-approved messaging directly within the Outlook pane. However, advisors report that they cannot view or select any templates stored in these custom folders when inserting templates from Outlook. Which administrative action is required to resolve this issue?

Enable 'Folders and Enhanced Sharing for Lightning Email Templates' in Setup and grant advisors View access on the target template folder.

Assign a permission set containing the 'Manage Public Lightning Email Templates' administrative permission to all sales advisors.

Modify the Organization-Wide Defaults (OWD) for Activity Objects from Private to Public Read/Write.

Enable Feed Tracking on Email Messages and add the Email Template picklist field to the Outlook Publisher Layout.

Show answer & explanation

Answer: Enable 'Folders and Enhanced Sharing for Lightning Email Templates' in Setup and grant advisors View access on the target template folder.

Answer

Enable 'Folders and Enhanced Sharing for Lightning Email Templates' in Setup and grant advisors View access on the target template folder.

Enabling 'Folders and Enhanced Sharing for Lightning Email Templates' allows administrators to organize Lightning templates into folders and grant explicit access (View or Edit) to users, roles, or public groups. Once configured, sales advisors can view and select templates from those shared folders directly within the Salesforce Outlook Integration pane.

Step-by-Step Solution

Identify the feature controlling folder access for Lightning templates.

Recognize that Lightning Email Templates require Enhanced Folder Sharing to be organized and shared via folder-level permissions.

Without Enhanced Folder Sharing enabled, templates in custom folders remain inaccessible to end users in both Salesforce and integration panes like Outlook/Gmail.

Configure feature settings and folder permissions.

Enable 'Folders and Enhanced Sharing for Lightning Email Templates' in Lightning Email Template Settings and set folder access for advisors to View.

This allows advisors to browse and select the templates from the integration panel without granting unneeded editing or management privileges.

Key Concept

Lightning Email Template Enhanced Folder Sharing in Email Integrations

Question 85Question →

An organization tracks custom Project Milestone records linked to a parent Project object through a Lookup relationship. When a Project Milestone status changes to 'Completed', an administrator must update the parent Project's aggregated completion percentage and update a custom status field on all related open Project Task records. The automation must handle bulk data uploads of up to 200 Project Milestones simultaneously without exceeding transaction limits. Which Flow Builder design strategy correctly processes these record updates while adhering to Salesforce governor limits?

Create a Roll-Up Summary field on the parent Project object to calculate the total completed milestone weighting automatically, eliminating the need to query or loop over child milestone records in Flow Builder.

Use a Get Records element outside the loop to retrieve all related milestones, iterate through the collection with a Loop element using an Assignment element to sum the completion weighting into a variable, and execute a single Update Records element after loop execution finishes.

Iterate through each related Project Task inside a Loop element and place an Update Records element within the loop body to modify each task individually as it is processed.

Use a Loop element to update each Project Task's record type assignment directly by setting a custom picklist field value without verifying if the picklist value is assigned to that target Record Type.

Show answer & explanation

Answer: Use a Get Records element outside the loop to retrieve all related milestones, iterate through the collection with a Loop element using an Assignment element to sum the completion weighting into a variable, and execute a single Update Records element after loop execution finishes.

Answer

The administrator should perform data calculations in memory using a Loop and Assignment element, placing the Update Records element after the loop completes to execute a single bulkified DML operation.

Bulkifying a Flow requires isolating database interactions (Get Records, Update Records, Create Records, Delete Records) outside of Loop elements. By collecting data into memory, using Assignment elements within the loop to calculate totals or build record collections, and invoking a single Update Records element after the loop completes, the flow handles bulk operations efficiently within governor limits.

Step-by-Step Solution

Evaluate relationship constraints

Confirm that because the parent Project is connected via a Lookup relationship (not Master-Detail), standard Roll-Up Summary fields cannot be created on the parent object.

Roll-Up Summary fields are exclusively available for Master-Detail relationships.

Design data retrieval and iteration logic

Use a single Get Records element prior to entering the loop to fetch all child milestone records into a Record Collection variable.

Fetching collection data before looping avoids executing SOQL queries inside a loop iteration.

Perform aggregation in memory

Iterate over the collection with a Loop element and add values to an aggregation variable using an Assignment element.

Assignment elements modify variables in memory and do not consume DML or SOQL governor limits.

Execute database updates outside the loop

Place the Update Records element on the path exiting the loop ('After Last Item').

Consolidating DML operations into a single database update outside the loop ensures the flow stays within governor limits during bulk transactions.

Key Concept

Flow Bulkification and Governor Limits

Question 86Question →

An administrator is configuring Einstein Activity Capture (EAC) settings for sales representatives using Microsoft Exchange. Match each EAC configuration setting to its corresponding operational behavior.

Click a left item, then click its matching right item

Show answer & explanation

Answer

Both ways sync direction matches bidirectional updates across both platforms; Exchange to Salesforce sync direction matches importing Exchange changes into Salesforce only; Salesforce to Exchange sync direction matches exporting Salesforce changes to Exchange only; Excluded Addresses list matches preventing specific domain or address activity from being logged.

Each Einstein Activity Capture configuration setting governs specific data transfer behavior: 'Both ways' provides bi-directional sync, 'Exchange to Salesforce' handles inbound-only sync, 'Salesforce to Exchange' handles outbound-only sync, and the 'Excluded Addresses' list enforces privacy filtering for targeted email domains and addresses.

Step-by-Step Solution

Identify bidirectional synchronization requirements.

Map 'Both ways sync direction' to the option stating changes in either Salesforce or Exchange update both systems.

Bidirectional sync requires continuous parity between connected environments.

Identify inbound-only synchronization requirements.

Map 'Exchange to Salesforce sync direction' to the option where Exchange edits update Salesforce, but Salesforce edits do not push back.

Inbound sync prioritizes the external mail server as the single source of origin.

Identify outbound-only synchronization requirements.

Map 'Salesforce to Exchange sync direction' to the option where Salesforce edits push to Exchange, but direct Exchange edits are ignored.

Outbound sync uses Salesforce as the primary record source for external updating.

Identify privacy and exclusion configuration settings.

Map 'Excluded Addresses list' to preventing specific internal email domains or sensitive addresses from being automatically captured.

Exclusions explicitly prevent sensitive communications from showing up on record activity timelines.

Key Concept

Einstein Activity Capture Sync Directions and Exclusions

Question 87Question →

A system administrator is configuring a record-triggered flow to set a custom field value on an Account record at the time of creation. The field calculation only relies on data from the triggering Account record itself and must occur prior to the record being saved to the database. Which flow optimization setting should the administrator select?

Fast Field Updates

Actions and Related Records

Asynchronous Path

Scheduled Path

Show answer & explanation

Answer: Fast Field Updates

Answer

Fast Field Updates should be selected because updating fields on the record that triggered the flow before it is saved to the database is best handled by a before-save record-triggered flow (Fast Field Updates).

Fast Field Updates run before the record is saved to the database. This allows Salesforce to update fields on the triggering record directly in memory before the initial insert/update operation, resulting in significant performance gains and preventing additional recursive save cycles.

Step-by-Step Solution

Identify the target record being updated

The update is performed on the triggering Account record itself.

Updates to the triggering record can be optimized by executing before the database write operation.

Determine timing requirements

The change must take effect prior to saving the record to the database.

Before-save execution avoids standard re-triggering of workflow rules, validation rules, and extra DML statements.

Select the matching Salesforce Flow trigger optimization

Choose Fast Field Updates.

Fast Field Updates map to before-save triggers in Flow Builder.

Key Concept

Record-Triggered Flow Trigger Optimization (Before-Save vs. After-Save)

Question 88Question →

A company requires an automated process to update the status of multiple related Case records to 'Under Audit' and generate a follow-up Task for each Case owner whenever an Account's risk level increases. An administrator creates an autolaunched flow that retrieves the collection of related Cases using a Get Records element. To ensure the flow updates the Cases and creates the Tasks efficiently without exceeding Salesforce governor limits, how should the administrator structure the Flow elements and logic?

Iterate through the Case collection, update Case field values and construct Task record variables using Assignment elements to append them into collection variables, then execute a single Update Records element and a single Create Records element outside the loop.

Iterate through the Case collection using a Loop element, placing an Update Records element and a Create Records element directly inside the loop to process each record individually.

Use a Roll-up Summary calculation element within the loop to aggregate Case status values onto the parent Account record before inserting each Task.

Add a Decision element inside the loop to reassign picklist values based on record type before executing an immediate inline Create Records element for each Task.

Show answer & explanation

Answer: Iterate through the Case collection, update Case field values and construct Task record variables using Assignment elements to append them into collection variables, then execute a single Update Records element and a single Create Records element outside the loop.

Answer

The correct approach follows Salesforce bulkification best practices by using Assignment elements within the loop to populate record and collection variables in memory. DML elements (Update Records and Create Records) are placed after the loop finishes so that all changes and insertions occur in single, bulkified transactions.

Step-by-Step Solution

Retrieve related records into a collection variable

A collection containing all target Case records is fetched using a single Get Records element.

Bulkifying data retrieval avoids issuing multiple query calls.

Loop and assign variable values without DML operations

Each iteration uses Assignment elements to update field values on the current item and add new Task records to a Task collection variable.

Assignment elements perform in-memory operations and do not count against DML governor limits.

Execute DML operations outside the loop

A single Update Records element updates the Case collection, and a single Create Records element creates the Task collection.

Executing DML elements outside the loop ensures the flow uses only 2 DML operations regardless of the number of records processed.

Key Concept

Flow Bulkification and Governor Limits

Estimated Time:1m 30s

Question 89Question →

An automation specialist is designing an autolaunched flow in Flow Builder to update a custom field across a collection of renewal Contract records. The flow receives a collection variable containing multiple Contract records, needs to populate the Renewal_Manager__c field on each record in memory, and then commit all updates to the database. Which sequence of Flow elements and logic demonstrates the correct bulkified design pattern?

Iterate over the Contract collection using a Loop element; inside the loop, use an Assignment element to update the field on the loop item variable, use a second Assignment element to add the loop item to a new collection variable, and place an Update Records element after the loop using the new collection variable.

Iterate over the Contract collection using a Loop element; inside the loop, use an Assignment element to set the field on the loop item variable, and place an Update Records element immediately after the Assignment element inside the loop.

Iterate over the Contract collection using a Loop element; inside the loop, use a Get Records element to fetch each Contract individually before applying an Assignment element, followed by an Update Records element placed outside the loop.

Configure a Roll-Up Summary field on the parent Account object to calculate and assign the Renewal_Manager__c value across all child Contract records automatically, omitting Loop and Assignment elements.

Show answer & explanation

Answer: Iterate over the Contract collection using a Loop element; inside the loop, use an Assignment element to update the field on the loop item variable, use a second Assignment element to add the loop item to a new collection variable, and place an Update Records element after the loop using the new collection variable.

Answer

Iterate over the Contract collection using a Loop element, assign updated values to individual items and push them to a output collection variable inside the loop, and execute a single Update Records element outside the loop.

The correct pattern for bulk record modifications in Flow Builder involves using a Loop element to iterate through records, Assignment elements inside the loop to modify field values and append each record to a output collection variable, and a single Update Records element outside the loop to execute a bulk update.

Step-by-Step Solution

Loop through the input collection

Each record in the collection is processed individually in memory.

Looping allows field modifications on individual record variables without executing immediate database operations.

Assign updated field values and add to an output collection

The current loop item record variable has its Renewal_Manager__c field set, and the updated record is added to a separate output record collection variable.

Collecting modified items into a target collection variable prepares all updated records for a single bulk DML operation.

Execute Update Records element outside the loop

Salesforce updates all modified Contract records in the target collection variable in a single transaction step.

Placing data manipulation elements outside the loop ensures the flow executes only 1 DML statement regardless of collection size, respecting Salesforce governor limits.

Key Concept

Bulkification in Flow Builder using collections, loops, and assignment elements

Question 90Question →

A Salesforce Administrator at a nationwide logistics provider needs to configure a custom Cases report to analyze service operations. The report must satisfy the following business requirements:
1. Categorize records into three resolution timeframe categories based on the numeric custom field 'Age (Days)': 'Critical' (greater than 14 days), 'Moderate' (5 to 14 days), and 'Prompt' (less than 5 days).
2. Display only Accounts that have closed cases with a Priority of 'High', while explicitly excluding Accounts that currently have any open Escalated cases.

Which two report builder configurations should the administrator implement to meet these requirements? (Select two.)

Select all that apply

Add a Bucket Field based on the numeric 'Age (Days)' field, defining ranges for 'Critical', 'Moderate', and 'Prompt'.

Add two Cross Filters on the report: 'Accounts with Cases' filtered by Status equals Closed and Priority equals High, and 'Accounts without Cases' filtered by Escalated equals True and Closed equals False.

Create a Row-Level Formula on the report using a CASE() function to group records into timeframes because Bucket Fields do not support numeric field types.

Define standard field filter logic using '1 AND (2 OR NOT 3)' to evaluate cross-object case status and escalation criteria without using Cross Filters.

Show answer & explanation

Answer: Add a Bucket Field based on the numeric 'Age (Days)' field, defining ranges for 'Critical', 'Moderate', and 'Prompt'.; Add two Cross Filters on the report: 'Accounts with Cases' filtered by Status equals Closed and Priority equals High, and 'Accounts without Cases' filtered by Escalated equals True and Closed equals False.

Answer

The administrator should add a Bucket Field on the numeric 'Age (Days)' field to group resolution timeframes into ranges, and add two Cross Filters ('Accounts with Cases' and 'Accounts without Cases') with appropriate subfilters to evaluate related case relationships.

Adding a Bucket Field on the numeric 'Age (Days)' field effectively categorizes numerical ranges into custom categories without formulas. Utilizing two Cross Filters ('Accounts with Cases' with secondary subfilters for closed high-priority cases, and 'Accounts without Cases' with secondary subfilters for open escalated cases) correctly evaluates parent-child record relationships.

Step-by-Step Solution

Configure record bucketing for numerical ranges

Created a Bucket Field on the numeric 'Age (Days)' field specifying ranges: >14 ('Critical'), 5 to 14 ('Moderate'), and <5 ('Prompt').

Bucket fields support numeric data types and allow administrators to quickly group ranges of values without creating custom fields or formulas.

Apply the first Cross Filter for qualifying related records

Added Cross Filter 'Accounts with Cases' with subfilters: Status = Closed and Priority = High.

Ensures the report only includes parent Account records that have at least one matching closed high-priority case.

Apply the second Cross Filter for excluding related records

Added Cross Filter 'Accounts without Cases' with subfilters: Escalated = True and Closed = False.

Excludes parent Account records that have open escalated cases.

Key Concept

Report Filtering, Filter Logic, and Bucketing

Question 91Question →

Cloud Kicks needs to automate business logic for custom Warranty Claim records. When a claim is created or modified, two specific technical requirements must be satisfied:

1. Calculate an internal risk score and set the claim status on the triggering record prior to committing it to the database, without issuing additional DML statements or re-triggering object execution rules.
2. Create a related audit record and transmit an outbound email notification to an external vendor after the claim record has been successfully committed to the database.

Which two flow trigger configurations should the administrator combine to meet these requirements efficiently?

Select all that apply

A Fast Field Updates (Before-Save) Record-Triggered Flow to set the risk score and claim status directly on the triggering record before database commit.

An Actions and Related Records (After-Save) Record-Triggered Flow to create the related audit record and send the email notification.

An Actions and Related Records (After-Save) Record-Triggered Flow that uses an explicit Update Records element to modify fields on the triggering record before save.

A Schedule-Triggered Flow running every 15 minutes that queries new claims, updates fields in a loop, and creates related records.

Show answer & explanation

Answer: A Fast Field Updates (Before-Save) Record-Triggered Flow to set the risk score and claim status directly on the triggering record before database commit.; An Actions and Related Records (After-Save) Record-Triggered Flow to create the related audit record and send the email notification.

Answer

The administrator should implement a combination of a Fast Field Updates (Before-Save) Record-Triggered Flow to update the triggering record before commit, and an Actions and Related Records (After-Save) Record-Triggered Flow to generate related records and execute outbound actions after commit.

The scenario presents two distinct operational requirements: modifying fields on the triggering record before saving to the database, and performing post-commit record creation and external messaging. A Fast Field Updates (Before-Save) flow handles same-record field modifications in memory without DML overhead. An Actions and Related Records (After-Save) flow ensures that child audit records are created and outbound emails are sent only after the primary record has successfully passed database commit.

Step-by-Step Solution

Evaluate the requirement for same-record field updates before database commit.

Determine that updating fields on the record that launched the flow prior to saving requires a Fast Field Updates (Before-Save) Record-Triggered Flow.

Before-save flows run up to 10 times faster than after-save flows because values are assigned directly to the memory buffer without requiring explicit DML operations or re-triggering the order of execution.

Evaluate the requirement for creating child records and executing post-save communications.

Determine that creating related audit logs and sending external emails requires an Actions and Related Records (After-Save) Record-Triggered Flow.

Post-commit operations, such as creating records on other objects or notifying external services, must take place after the primary record has successfully passed system validation rules and database save.

Key Concept

Record-Triggered Flow Optimization: Before-Save vs. After-Save Triggers

Question 92Question →

A Salesforce administrator is configuring automated case intake mechanisms to meet specific organizational security, infrastructure, and volume requirements. Match each case capture mechanism to its corresponding technical architecture or operational capability.

Click a left item, then click its matching right item

Show answer & explanation

Answer

Web-to-Case matches with generating web form HTML with a default 5,000 daily request limit and default owner overflow routing. On-Demand Email-to-Case matches with processing emails entirely in the Salesforce cloud with a 25 MB maximum size limit. Email-to-Case Agent matches with requiring software installed behind the network firewall to keep traffic internal and handle attachments larger than 25 MB.

Web-to-Case provides HTML code generation with a 5,000 daily request ceiling and routes overflow to the default owner. On-Demand Email-to-Case processes emails up to 25 MB completely in the Salesforce cloud. Email-to-Case Agent uses installed software inside the corporate firewall to keep network traffic internal and handle attachments exceeding 25 MB.

Step-by-Step Solution

Identify the attributes of Web-to-Case

Web-to-Case uses HTML forms embedded on web pages, enforces a default maximum limit of 5,000 requests daily, and directs invalid or overflow requests to the default case creation user.

Distinguish web-based intake mechanisms from email-based mechanisms.

Analyze On-Demand Email-to-Case architecture

On-Demand Email-to-Case processes incoming emails using Salesforce cloud infrastructure, removing the need for internal server agents while enforcing a 25 MB total email size limit.

Identify cloud-based email handling characteristics and limits.

Analyze Email-to-Case Agent architecture

The Email-to-Case Agent requires local software installed behind the corporate firewall, keeping traffic local and enabling support for email attachments over 25 MB.

Identify firewall and file size requirements unique to the installed agent approach.

Key Concept

Case Capture Mechanisms (Web-to-Case and Email-to-Case)

Question 93Question →

A Salesforce administrator needs to automatically calculate and set a custom field value on a Lead record when the Lead is created or updated. The requirement specifies updating fields strictly on the triggering record itself with optimal performance before the data is committed to the database. Which automation tool and configuration should the administrator select?

Record-Triggered Flow optimized for Fast Field Updates (Before-Save)

Record-Triggered Flow optimized for Actions and Related Records (After-Save)

Roll-Up Summary Field configured on a related Lookup relationship

Approval Process utilizing an initial submission action

Show answer & explanation

Answer: Record-Triggered Flow optimized for Fast Field Updates (Before-Save)

Answer

The administrator should select a Record-Triggered Flow optimized for Fast Field Updates (Before-Save).

Record-Triggered Flows configured for Fast Field Updates execute before the record is saved to the database. This allows field values on the triggering record to be updated in memory before the SQL save operation, making it the most efficient and recommended approach.

Step-by-Step Solution

Analyze the automation requirement

The requirement specifies modifying fields on the triggering Lead record prior to database commit with maximum execution speed.

Understanding whether the automation targets the triggering record or related records determines the trigger configuration.

Evaluate Salesforce declarative automation tools

Record-Triggered Flows set to Fast Field Updates run before the save operation, updating the record in memory without additional SQL DML statements.

Before-save flows offer optimal performance for same-record modifications.

Key Concept

Selecting Fast Field Updates (Before-Save Record-Triggered Flow) for same-record updates

Question 94Question →

Aegis Solar Solutions enforces a Private sharing model for Opportunities. A Salesforce administrator configures an executive sales dashboard to run as a static user, specifically the VP of Sales. When sales representatives view this dashboard and interact with its components, which two statements accurately describe how data visibility and security are applied? (Select 2 options.)

Select all that apply

Dashboard components display summarized metrics reflecting all records accessible to the static running user, regardless of the viewer's individual sharing access.

Clicking a dashboard component opens the underlying source report, which displays only the records accessible to the logged-in viewer based on their own record-level security.

Drilling down into the source report temporarily expands the viewer's security access to match the running user's access for all detailed record rows.

Users who lack access to the dashboard folder can still view dashboard components if the static running user has Administrative access to the folder.

The static dashboard automatically converts to a dynamic dashboard when accessed by users who do not hold the View All Data permission.

Show answer & explanation

Answer: Dashboard components display summarized metrics reflecting all records accessible to the static running user, regardless of the viewer's individual sharing access.; Clicking a dashboard component opens the underlying source report, which displays only the records accessible to the logged-in viewer based on their own record-level security.

Answer

The correct statements are that dashboard components display summarized metrics reflecting all records accessible to the static running user, and clicking a component to open the source report restricts the detailed view to records accessible under the logged-in user's security context.

When a dashboard is set to run as a static user, the component summaries display data based on that running user's permissions, enabling viewers to see aggregated metrics for records beyond their personal sharing access. However, source reports always run under the logged-in user's security context. Therefore, when a user clicks a component to view the source report, Salesforce enforces the viewer's own Organization-Wide Defaults and sharing rules, displaying only the individual records they are authorized to see.

Step-by-Step Solution

Analyze how a static running user affects dashboard component visibility.

Dashboard components calculate and display aggregated data based strictly on the specified running user's (VP of Sales) object, field, and record access.

Static running users allow users with restrictive access to view high-level team performance metrics without granting broad record access.

Analyze what happens when a viewer drills down into the source report.

The source report executes under the logged-in user's context, evaluating Organization-Wide Defaults (OWD), sharing rules, and role hierarchy for that specific viewer.

Source reports never execute as the dashboard running user; they always enforce the active user's standard record-level security.

Key Concept

Static Dashboard Running User vs. Source Report Execution Context

Question 95Question →

A system administrator is configuring an approval step within an Approval Process for a custom Expense Report object. The finance director specifies that any expense claim exceeding $10,000 must be routed simultaneously to three designated executive managers. The requirement dictates that the approval step should be marked as approved only if all three managers grant approval. However, if any single manager rejects the request, the step must immediately fail and trigger the Final Rejection Actions without waiting for the remaining managers to respond. How should the administrator configure the approver assignment settings for this step?

Select 'Require unanimous approval from all selected approvers' and manually add the three executive manager users to the assigned approvers list.

Create a Queue containing the three executive managers, assign the approval step to the Queue, and select 'Require unanimous approval from all selected approvers'.

Select 'Approve or reject based on the FIRST response' and attach a Flow to evaluate and reject the process if any single rejection record is created.

Assign the step to a Public Group consisting of the three executive managers and check the 'Execute Final Rejection on First Disapproval' option.

Show answer & explanation

Answer: Select 'Require unanimous approval from all selected approvers' and manually add the three executive manager users to the assigned approvers list.

Answer

Select 'Require unanimous approval from all selected approvers' and manually add the three executive manager users to the assigned approvers list.

When multiple individual users are assigned to an approval step in Salesforce and 'Require unanimous approval from all selected approvers' is selected, Salesforce requires every assigned user to approve the request before moving forward. Crucially, as soon as any single assigned user rejects the request, Salesforce immediately short-circuits the evaluation, rejects the step, and executes the defined Final Rejection Actions.

Step-by-Step Solution

Analyze the requirement for multiple approvers.

Three specific users need to be assigned to the approval step simultaneously.

The business rule requires input from three executive managers.

Evaluate native Salesforce approval step voting options.

'Require unanimous approval from all selected approvers' satisfies both conditions: all must approve for success, and a single rejection triggers immediate step failure.

Salesforce standard behavior for unanimous voting short-circuits to rejection as soon as one user rejects.

Eliminate invalid approver types like Queues or Public Groups for unanimous multi-user voting.

Directly assign the three user records in the step configuration.

Queues resolve on first response by any queue member, and Public Groups cannot be directly assigned to approval steps.

Key Concept

Approval Step Multi-Approver Voting Rules

Estimated Time:2m 0s

Question 96Question →

An enterprise administrator needs to bulk-import thousands of new child Service Contract records and automatically link them to existing parent Account records using Data Loader. The parent Account records already contain a unique custom External ID field named Legacy_Account_ID__c. What is the correct sequence of steps the administrator must follow to successfully map and relate the child records to parent Accounts using Data Loader?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence starts with verifying parent record External IDs in Salesforce, preparing the child CSV file with parent External ID foreign keys, initializing the Data Loader Insert operation, mapping the CSV column to the Account:Legacy_Account_ID__c relationship reference field, and concluding with executing the operation and inspecting success/error logs.

The workflow requires establishing prerequisites first (ensuring parent External IDs exist in Salesforce), preparing the child CSV file with those external keys, configuring Data Loader for the child object insert, mapping the CSV key column to the related parent External ID syntax (Account:Legacy_Account_ID__c), and finally running the import while checking the execution log files.

Step-by-Step Solution

Ensure parent Account External IDs exist in Salesforce

Salesforce Accounts are properly indexed and ready for external key matching

Data Loader cannot resolve foreign key relationships if the target external identifier field is blank or missing on parent records.

Prepare child record CSV with parent External ID column

Source CSV contains accurate foreign key references for each child row

Data Loader relies on foreign key values in the import file to determine which Account each Service Contract belongs to.

Initialize Data Loader Insert wizard for Service Contract

Data Loader parses CSV headers and connects to the Service Contract object schema

Selecting the proper object and file establishes the baseline schema mapping context.

Map foreign key column to Account:Legacy_Account_ID__c

Field mapping establishes a relational lookup using the parent External ID

Data Loader syntax requires selecting the related object's External ID field (Account:Legacy_Account_ID__c) rather than standard Account ID.

Run operation and analyze output log files

Service Contract records are created in Salesforce linked to appropriate parent Accounts

Post-execution audit ensures all rows succeeded and errors are isolated for remediation.

Key Concept

Relating Child Records via External ID in Data Loader Mass Operations

Question 97Question →

An administrator at a renewable energy company needs to allow field engineers to create a related Inspection record directly from a Customer Site record. The new Inspection record must automatically populate the Site Location and Maintenance Region fields with data from the parent Customer Site record. Which solution should the administrator implement to meet this requirement?

Create an Object-Specific Quick Action on the Customer Site object with Predefined Field Values, and add it to the Customer Site page layout.

Create a Global Quick Action with Predefined Field Values, and add it to the Global Publisher Layout.

Create a Custom Detail Page Button using JavaScript to set the field values, and place it on the Customer Site page layout.

Create a Custom Link on the Inspection object that redirects to a standard record creation page.

Show answer & explanation

Answer: Create an Object-Specific Quick Action on the Customer Site object with Predefined Field Values, and add it to the Customer Site page layout.

Answer

Create an Object-Specific Quick Action on the Customer Site object with Predefined Field Values, and add it to the Customer Site page layout.

Creating an Object-Specific Quick Action on the source object (Customer Site) enables the administrator to define Predefined Field Values that reference the parent record's fields. Placed on the parent object layout, it provides a seamless, context-aware record creation flow in Lightning Experience.

Step-by-Step Solution

Identify the requirement for record creation within a specific record context.

The requirement calls for creating a child record from a parent record layout while copying field values from the parent.

Object-specific actions operate within the context of a specific record.

Configure predefined field values on the Object-Specific Action.

Field values for Site Location and Maintenance Region are automatically populated using formulas referencing the parent Customer Site fields.

Object-specific quick actions allow referencing fields on the source object in predefined value formulas.

Add the action to the Lightning page layout.

The action becomes available on the Customer Site record page for users.

Adding the action to the record page layout makes it accessible in Lightning Experience.

Key Concept

Object-Specific Quick Actions and Predefined Field Values

Question 98Question →

Match each Salesforce Chatter group role or member designation on the left with its corresponding functional permission or visibility behavior on the right. Which pairs correctly match each role to its operational capability?

Click a left item, then click its matching right item

Show answer & explanation

Answer

Group Owner pairs with full administrative control including group deletion and ownership transfer; Group Manager pairs with member and settings management excluding group deletion; Broadcast Group Manager/Owner pairs with exclusive post-authoring privileges in broadcast settings; and External Member pairs with the orange badge visual distinction and group-restricted visibility.

Each role correctly aligns with its Salesforce platform governance model: Group Owners possess full lifecycle rights including deletion; Group Managers handle daily administrative tasks; Broadcast group leads retain posting exclusivity; and external users receive visual highlighting alongside strict containerized access.

Step-by-Step Solution

Analyze Group Owner capabilities

Group Owner is the highest authority level for a Chatter group, granting rights to delete the group and transfer ownership.

Salesforce security hierarchy enforces that only the owner or system administrator can perform destructive or ownership-changing actions.

Analyze Group Manager capabilities

Group Managers can adjust group information, promote regular members, and remove posts, but cannot delete the group.

Delegated group management allows operational support without granting destructive group permissions.

Evaluate Broadcast Group posting rules

In broadcast groups, regular members cannot start new posts; only owners and managers have post creation rights.

Broadcast groups are designed specifically for official announcements and top-down communications.

Identify External Member characteristics

External members are tagged with orange banners/badges and limited to content within their assigned group.

Salesforce Chatter privacy mechanisms ensure internal data is protected when collaborating with external users.

Key Concept

Chatter Group Roles, Capabilities, and Special Group Access Controls

Question 99Question →

An administrator is setting up Einstein Activity Capture (EAC) for a newly onboarded sales team. Which two data types can be synchronized between connected Microsoft or Google accounts and Salesforce? (Select 2 answers)

Select all that apply

Contacts

Events

Cases

Chatter Posts

Show answer & explanation

Answer: Contacts; Events

Answer

Contacts and Events can be synchronized between connected email or calendar accounts and Salesforce using Einstein Activity Capture.

Einstein Activity Capture allows administrators to configure directional synchronization for Contacts and Events between Salesforce and connected Microsoft or Google services.

Step-by-Step Solution

Identify the standard data types supported by Einstein Activity Capture sync configurations.

EAC supports capture and sync configurations for Contacts and Events (as well as captured Emails stored on AWS).

Understanding supported data types ensures administrators configure productivity tools accurately within platform boundaries.

Key Concept

Einstein Activity Capture Supported Sync Objects

Estimated Time:45s

Question 100Question →

A system administrator at a logistics enterprise is tasked with executing two data maintenance operations: importing 80,000 custom object records named Equipment_Track__c, and deleting 5,000 obsolete Opportunity records from the org. Which two operational constraints dictate that Data Loader MUST be used instead of the Data Import Wizard? (Choose 2 options)

Select all that apply

The Data Import Wizard cannot process data load operations exceeding 50,000 total records in a single job.

The Data Import Wizard does not support delete operations or object management for Opportunities.

The Data Import Wizard is incapable of matching custom object records using External ID fields.

The Data Import Wizard automatically disables active validation rules during data load, necessitating Data Loader for data quality enforcement.

Show answer & explanation

Answer: The Data Import Wizard cannot process data load operations exceeding 50,000 total records in a single job.; The Data Import Wizard does not support delete operations or object management for Opportunities.

Answer

Data Loader must be used because the Data Import Wizard cannot process more than 50,000 records and cannot perform delete operations or process Opportunity records.

Data Loader is mandatory for this scenario because the Data Import Wizard is strictly limited to 50,000 records per job (making it unsuitable for 80,000 records) and lacks support for delete operations as well as unsupported standard objects like Opportunities.

Step-by-Step Solution

Evaluate record volume requirements against tool limits

The import batch consists of 80,000 records, which exceeds the maximum limit of 50,000 records supported by the Data Import Wizard, requiring Data Loader.

Data Import Wizard handles up to 50,000 records, while Data Loader supports up to 5,000,000 records.

Evaluate object and operation support requirements

The job requires deleting 5,000 Opportunity records. The Data Import Wizard does not support delete operations and does not support Opportunities.

Data Import Wizard supports insert, update, and upsert for specific standard objects (Accounts, Contacts, Leads, Solutions, Campaign Members) and custom objects, but does not perform record deletions or support Opportunities.

Key Concept

Data Import Wizard vs Data Loader Selection Criteria

PreviousPage 5 / 90Next

All practice questions

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept