Examkin

All practice questions

1784 questions

All types1,784Multiple choice918Multiple select587Matching142Ordering137
Question 1321Question →

An administrator is defining an automated approval process in Salesforce for sales contract reviews. Sequence the standard stages of an approval process execution lifecycle from first to last.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence for an approval process execution lifecycle is: 1) The user clicks 'Submit for Approval', 2) Initial Submission Actions execute, 3) Approval Step criteria are evaluated, and 4) Final Approval Actions execute.
The approval process always starts with explicit record submission. Once submitted, Salesforce performs initial submission actions (such as locking the record). Following entry, approval step criteria are evaluated to route the item to an approver, and finally, after receiving approval, final approval actions execute.

Step-by-Step Solution

1
Identify the trigger event
Submission initiates the process.
An approval process cannot begin until a record submission event occurs.
2
Determine post-submission automation
Initial Submission Actions trigger immediately.
Locking the record and executing initial actions prevents modification while pending evaluation.
3
Evaluate step criteria
The record is routed to the designated approver.
Individual step entry criteria determine if and to whom the approval request is assigned.
4
Finalize approval outcome
Final Approval Actions run.
Completing all approval steps triggers final actions like field updates or email notifications.

Key Concept

Salesforce Approval Process Lifecycle
Question 1322Question →

Veritas Cyber Security operates two sales divisions: Direct Enterprise Sales and Managed Partner Sales. The Managed Partner team follows a abbreviated sales pipeline that skips initial discovery stages and introduces a unique custom stage called 'Partner Vetted'. An administrator adds the 'Partner Vetted' picklist value to the Stage field on the Opportunity object. However, when attempting to assign this stage while creating a new Record Type for Managed Partner Sales, the administrator discovers that the Stage picklist field cannot be customized directly within the Record Type picklist settings. Which sequence of administrative actions should the administrator perform to make the 'Partner Vetted' stage available on opportunities using the new Record Type?

Show answer & explanation

Answer: Create a dedicated Sales Process for Managed Partner Sales including the 'Partner Vetted' stage, and associate this Sales Process to the new Opportunity Record Type.

Answer

Create a dedicated Sales Process for Managed Partner Sales that includes the 'Partner Vetted' stage, and then assign this Sales Process when creating or editing the Managed Partner Opportunity Record Type.
In Salesforce, the Opportunity object utilizes Sales Processes to determine which stage picklist values are available for specific sales cycles. Unlike standard picklist fields, Opportunity stages cannot be filtered directly within a Record Type detail page. An administrator must first create a Sales Process containing the desired stages (including 'Partner Vetted') and then link that Sales Process to the Opportunity Record Type.

Step-by-Step Solution

1
Identify the underlying mechanism controlling Opportunity stages
Recognize that Opportunity Stage picklist values are determined by Sales Processes rather than standard object-level picklist configurations on Record Types.
Salesforce enforces sales methodology structure by routing Opportunity stages through Sales Processes.
2
Create a new Sales Process
Navigate to Setup > Sales Processes and create a new process named 'Managed Partner Sales Process', selecting 'Partner Vetted' along with other appropriate stages.
A Sales Process acts as a curated subset of stage picklist values specifically tailored for a business unit's sales workflow.
3
Link the Sales Process to the Opportunity Record Type
Create or edit the Opportunity Record Type and assign the newly created 'Managed Partner Sales Process' to it.
An Opportunity Record Type requires a Sales Process reference to know which stages to expose to users assigned to that record type.

Key Concept

Sales Processes and Opportunity Stage Linkage to Record Types
Estimated Time:1m 30s
Question 1323Question →

Universal Containers requires an automated solution for managing Case lifecycle events according to three key requirements:
1. Update a custom internal priority score on the Case record prior to saving it to the database.
2. Send a payload to an external REST Web API endpoint and create a follow-up Task record whenever a Case status is changed to Escalated.
3. Perform a weekly batch review of all open Case records inactive for more than 14 days and update their status to Pending Archive.

Which TWO flow types and trigger configurations should the administrator select to fulfill these requirements while adhering to Salesforce performance and governor limit best practices?

Select all that apply

Show answer & explanation

Answer: Configure a Fast Field Update (Before-Save) Record-Triggered Flow to set the custom internal priority score on the triggering Case record.; Configure a Schedule-Triggered Flow that runs weekly to filter inactive Case records and execute the status update.

Answer

The administrator should implement a Fast Field Update (Before-Save) Record-Triggered Flow for same-record updates before database commit, and a Schedule-Triggered Flow running weekly to handle scheduled batch processing of inactive records.
The solution requires matching business needs with optimal flow types: (1) Updating fields on the triggering record before database commit is best performed using a Fast Field Update (Before-Save) Record-Triggered Flow because it modifies the record in memory without an extra DML statement. (2) Performing routine interval-based evaluation of inactive records is best handled by a Schedule-Triggered Flow, which automatically processes records in batch mode at scheduled times.

Step-by-Step Solution

1
Analyze same-record field modification requirement prior to database save.
Identified that Fast Field Update (Before-Save) Record-Triggered Flow is optimal because it modifies values in memory prior to the database commit without incurring extra DML overhead.
Before-save flows are up to 10 times faster than after-save flows for same-record updates.
2
Analyze recurring time-based batch evaluation requirement.
Identified that a Schedule-Triggered Flow should be used to run at specified intervals (weekly) on target record datasets.
Schedule-triggered flows allow filtering records directly in the start element and running batch operations asynchronously.
3
Evaluate distractors involving after-save same-record updates and DML/callout operations in loops.
Eliminated choices that use after-save flows for same-record field updates or execute flow invocations inside iteration loops.
These improper patterns violate order of execution optimization rules and Salesforce governor limits.

Key Concept

Flow Trigger Types and Execution Optimization (Before-Save vs After-Save vs Schedule-Triggered)
Question 1324Question →

An administrator is configuring a multi-step Approval Process for custom Travel Expense records. When defining the approver assignment logic for an approval step, the business requires that expense requests be routed dynamically based on record data or user hierarchy attributes. Which TWO approver assignment configurations are natively supported within an approval step? (Choose 2 options)

Select all that apply

Show answer & explanation

Answer: Automatically assign to a standard or custom User lookup field present on the submitted record.; Automatically assign to the Manager user hierarchy field defined on the submitter's user record, with an option to permit the delegated approver to respond.

Answer

The valid approver assignment configurations are automatically assigning to a standard or custom User lookup field on the submitted record, and automatically assigning to the submitter's Manager field with delegated approver permissions.
Salesforce Approval Processes allow dynamic step routing by assigning requests to a User lookup field specified directly on the record being submitted, as well as assigning requests to the submitter's Manager (hierarchy field) with the option to allow the designated Delegated Approver to approve or reject.

Step-by-Step Solution

1
Analyze standard Salesforce Approval Process step approver capabilities.
Identified that approval steps support manual selection by submitter, automated assignment to specified users/queues, and dynamic assignment using User lookup fields.
Salesforce approval step routing supports user hierarchy relationships (Manager field) and object-level User lookup fields for dynamic routing.
2
Evaluate invalid assignment targets and non-native execution features.
Confirmed that Public Groups cannot be assigned approval requests directly and flows cannot insert dynamic step definitions at runtime.
Public Groups are used for sharing rules and folder access, not direct approval assignment. Approval steps rely on predefined standard step routing.

Key Concept

Approval Step Approver Assignment Options and Dynamic Routing
Question 1325Question →

A Salesforce Administrator needs to configure a flow to update the Status field to 'Audited' across all child Asset records linked to an Account. To ensure the flow follows bulkification best practices and avoids exceeding governor limits, in what sequence should the administrator place the Flow Builder elements from start to finish?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence begins with retrieving the records into a collection, looping over each item, updating field values in memory using an Assignment element, adding the modified item to a staging collection using a second Assignment element, and finally issuing a single bulkified Update Records operation after the loop finishes.
The standard pattern for bulkified collection processing in Salesforce Flow Builder requires retrieving records, iterating over them in a loop, assigning field changes to the current item in memory, adding that item to an update collection, and executing a single Update Records element after the loop exits.

Step-by-Step Solution

1
Query related child records
Obtain a collection of Asset records associated with the Account ID using a single Get Records query.
Data must be retrieved into memory prior to iteration to prevent executing SOQL inside loops.
2
Iterate through the collection
Enter the Loop element to access each Asset record one by one.
Looping exposes each record as a loop variable for individual attribute modification.
3
Assign updated field values
Set {!Loop_Asset.Status} to 'Audited' via an Assignment element.
Modifications must be made to the loop variable in memory.
4
Stage modified record into update collection
Add {!Loop_Asset} to {!varAssetsToUpdate} via an Assignment element.
Building a separate collection gathers all staged modifications for a bulk update.
5
Commit database updates outside the loop
Perform an Update Records operation on {!varAssetsToUpdate} after the loop path completes.
Executing DML outside of loop constructs enforces bulkification and adheres to Salesforce governor limits.

Key Concept

Flow Bulkification and Collection Processing
Question 1326Question →

An administrator is designing an autolaunched flow in Salesforce to update thousands of high-priority Account records and their associated Contacts whenever a custom status field changes. To meet performance guidelines and avoid hitting SOQL query and DML statement governor limits, the flow must handle data operations efficiently across collections. Which TWO actions should the administrator take to process these records without violating governor limits?

Select all that apply

Show answer & explanation

Answer: Execute a Get Records element before entering the loop to retrieve all necessary records into a Record Collection Variable.; Use an Assignment element inside the loop to add updated record variables to a Record Collection Variable, followed by a single Update Records element outside the loop.

Answer

The administrator should execute a Get Records element prior to the loop to populate a collection variable and use an Assignment element inside the loop to accumulate modified records into a collection, executing a single Update Records element outside the loop.
Bulkifying flows requires moving all database interactions outside of loop containers. Querying records before entering the loop retrieves data in a single SOQL statement, and gathering updated record variables into a collection variable via Assignment elements allows a single Update Records DML operation outside the loop to commit all updates simultaneously.

Step-by-Step Solution

1
Query records before processing
Obtain all targeted records in a single SOQL database operation stored within a Record Collection Variable.
Prevents running separate SOQL queries inside repeated loop iterations.
2
Loop and modify variables
Iterate through each item in the collection, updating field values on the loop item variable.
Modifies data in system memory without issuing DML calls to the database.
3
Stage modified records into an output collection
Use an Assignment element within the loop to add the modified loop item variable to a separate output Record Collection Variable.
Prepares all changed records into a unified collection for bulk processing.
4
Execute bulk DML operation outside the loop
Pass the output Record Collection Variable into a single Update Records element placed after the loop finishes.
Consumes only one DML statement out of the transaction governor limit regardless of record count.

Key Concept

Flow Bulkification and Governor Limits
Question 1327Question →

A support administrator is evaluating automated case intake mechanisms using Web-to-Case and On-Demand Email-to-Case. Which two statements correctly describe the native capabilities and architectural behavior of these case capture tools? (Select 2)

Select all that apply

Show answer & explanation

Answer: When the daily Web-to-Case request limit is exceeded, Salesforce emails the submitted case information to the Default Case Owner instead of creating a Case record.; On-Demand Email-to-Case processes incoming emails using Salesforce cloud services without requiring an agent application installed behind the corporate firewall.

Answer

The statement regarding daily Web-to-Case limit overflow sending emails to the Default Case Owner and the statement regarding On-Demand Email-to-Case relying on cloud services without a local server agent are both correct.
Exceeding daily Web-to-Case request limits causes submitted case details to be emailed directly to the Default Case Owner instead of creating database records. Additionally, On-Demand Email-to-Case handles incoming emails entirely through Salesforce cloud infrastructure via forwarding, eliminating the need to install and maintain an on-premises Email-to-Case Agent.

Step-by-Step Solution

1
Analyze Web-to-Case limit overflow handling
Salesforce forwards submitted case data to the Default Case Owner when daily request limits are reached.
Salesforce enforces daily Web-to-Case limits based on organization edition; overflow entries cannot create records directly in the database.
2
Evaluate On-Demand Email-to-Case deployment architecture
Emails are processed via cloud email services using email forwarding.
On-Demand Email-to-Case routes emails to Salesforce Apex email service endpoints, eliminating the requirement for behind-the-firewall agent software.

Key Concept

Web-to-Case and Email-to-Case Architecture and Limits
Question 1328Question →

An administrator is configuring a Workflow Rule on the Contract object to trigger an automated outbound message when a contract status changes to 'Activated', and to schedule an email alert 30 days before the contract end date. While attempting to add the time-dependent email action, the administrator finds that the option to add time triggers is unavailable in the rule builder. What is the root cause of this limitation, and how should the rule be reconfigured?

Show answer & explanation

Answer: The evaluation criteria is set to 'created, and every time it's edited', which prevents adding time-dependent actions; the administrator must change the evaluation criteria to 'created, and any time it's edited to subsequently meet criteria'.

Answer

The evaluation criteria is currently set to 'created, and every time it's edited', which restricts time triggers. Reconfiguring the evaluation criteria to 'created, and any time it's edited to subsequently meet criteria' enables time-dependent workflow actions.
Salesforce restricts time-dependent workflow actions on rules configured with the evaluation criteria set to 'created, and every time it's edited'. To enable time-based triggers for records that undergo updates, the evaluation criteria must be updated to 'created, and any time it's edited to subsequently meet criteria'.

Step-by-Step Solution

1
Analyze the restriction on time-dependent workflow rules in Salesforce Workflow configuration.
Salesforce systematically disables the 'Add Time Trigger' button when the evaluation criteria is set to 'created, and every time it's edited'.
This prevents recurring edits from causing unpredictable evaluation loops or infinitely appending duplicate time triggers in the background queue.
2
Determine the appropriate evaluation criteria for time-dependent execution upon status change.
Selecting 'created, and any time it's edited to subsequently meet criteria' resolves the constraint.
This evaluation criteria allows time triggers while ensuring actions are scheduled only when a record transitions into meeting the specified rule criteria.

Key Concept

Workflow Evaluation Criteria and Time-Trigger Restrictions
Question 1329Question →

A sales manager needs to calculate a discounted value for every individual line item record in an Opportunity report by multiplying the Opportunity Amount by a custom discount percentage field. Which reporting capability should the administrator configure to calculate this value record by record?

Show answer & explanation

Answer: A row-level formula

Answer

The administrator should use a row-level formula because it executes logic on each individual record line displayed in the report.
A row-level formula is specifically designed to perform calculations on each individual record displayed within a report run.

Step-by-Step Solution

1
Identify the requirement scope
The calculation must take place on every individual record line (record-by-record level).
Understanding whether data needs individual evaluation or group aggregation determines the correct formula tool.
2
Select the appropriate reporting tool
Choose a row-level formula.
Row-level formulas allow administrators to compute custom calculated fields for each detail row in a report without creating custom schema fields.

Key Concept

Row-Level Formula vs Summary Formula Scope
Estimated Time:45s
Question 1330Question →

A Salesforce Administrator is designing a record-triggered flow on the custom object Contract_Renewal__cContract\_Renewal\_\_c. When a renewal record is marked as 'High Risk', the flow must retrieve all related Contract_Line_Item__cContract\_Line\_Item\_\_c records linked via a lookup relationship, iterate through the retrieved records to sum the total value of active items using a currency variable, and update the triggering Contract_Renewal__cContract\_Renewal\_\_c record with the calculated total. Which element structure and configuration represents the most efficient, governor-limit-safe implementation in Flow Builder?

Show answer & explanation

Answer: Place a Decision element inside the Loop to verify if a line item is active, use an Assignment element inside the Loop to add the active item's value to a currency variable, and place an Update Records element outside the Loop to update the triggering contract renewal record.

Answer

Place a Decision element inside the Loop to check item status, accumulate the total value using an Assignment element inside the Loop, and execute a single Update Records element after the loop completes.
The design pattern of performing filtering with a Decision element and accumulation with an Assignment element inside a Loop, followed by a single Update Records element placed after the loop finishes, ensures that variable calculations occur in memory and database updates are bulkified without exceeding governor limits.

Step-by-Step Solution

1
Evaluate record relationship and aggregation requirements
Since Contract_Line_Item__cContract\_Line\_Item\_\_c is linked via a Lookup relationship, declarative Roll-Up Summary fields are unavailable.
Roll-up summary fields require a Master-Detail relationship.
2
Design loop iteration logic using Flow Builder elements
Filter items with a Decision element inside the Loop and add valid values to a variable via an Assignment element inside the Loop.
In-memory variable assignment allows calculations without database queries or updates.
3
Position database operations outside the loop construct
Perform the record update with an Update Records element on the path connected after the Loop finishes processing all items.
Placing data manipulation elements (DML) outside loops prevents reaching the limit of 150 DML statements per transaction.

Key Concept

Flow Builder Loop and Assignment Logic Bulkification
Question 1331Question →

A System Administrator is configuring a standard Asset report in Salesforce for a hospital network's biomedical engineering team. The report must evaluate medical devices for scheduled maintenance based on the following criteria:

1. Filter 1: Asset Status equals "In Use, Under Maintenance"
2. Filter 2: Warranty Expiration Date equals NEXT 30 DAYS
3. Filter 3: Last Maintenance Date less than LAST 180 DAYS

Business requirements dictate that all returned assets must have a status of either 'In Use' or 'Under Maintenance'. Additionally, an asset must meet at least one of the two time-based criteria (warranty expiring in 30 days OR last maintenance over 180 days ago). Finally, any assets that already have an open Work Order must be excluded from the report results.

The Administrator has added a Cross Filter for "Assets without Work Orders" to handle the open work order exclusion.

Which filter logic expression must the Administrator apply to criteria 1, 2, and 3 to satisfy the business requirements?

Show answer & explanation

Answer: 1 AND (2 OR 3)

Answer

The correct filter logic expression is 1 AND (2 OR 3).
The filter logic expression 1 AND (2 OR 3) correctly enforces that Filter 1 must always be true for every record, while requiring that at least one of Filter 2 or Filter 3 evaluates to true. Cross Filters operate independently of field filter logic to exclude Assets with Work Orders.

Step-by-Step Solution

1
Analyze the mandatory requirement for Asset Status.
Filter 1 must evaluate to TRUE for all returned records.
The requirement states all assets in the report must have a status of 'In Use' or 'Under Maintenance'.
2
Analyze the relationship between the time-based criteria.
Filter 2 and Filter 3 must be grouped with an OR operator: (2 OR 3).
The requirement states that an asset must meet at least one of the two date conditions.
3
Combine mandatory criteria with the grouped optional conditions.
The combined boolean statement across field filters is 1 AND (2 OR 3).
Parentheses ensure that Filter 1 is AND-ed with the combined result of Filter 2 OR Filter 3.

Key Concept

Report Filter Logic and Parentheses Grouping
Question 1332Question →

An administrator is configuring a multi-step approval process for custom Discount Request records. Place the automated system evaluation and action execution steps in the correct chronological sequence from initial submission to final approval completion.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct chronological sequence is: 1. Initial submission actions execute and lock the record; 2. System evaluates entry criteria for Step 1; 3. Step 1 is approved and step approval actions execute; 4. System evaluates entry criteria for Step 2; 5. Final approval actions execute and unlock the record.
In Salesforce approval processes, record submission immediately triggers initial submission actions (such as record locking). Next, the system evaluates entry criteria for Step 1. Upon approver action, Step 1 approval actions execute. The process then moves to evaluate Step 2 entry criteria. Finally, when all steps are completed, final approval actions execute to finalize field values and unlock the record.

Step-by-Step Solution

1
Identify Initial Submission Behavior
Initial submission actions run immediately when a user submits a record, locking the record by default.
Initial submission locks prevent users from changing record details while under review.
2
Evaluate First Step Entry Criteria
The system checks if the record meets the filter criteria for Step 1.
If entry criteria are met, the record is routed to the designated approver for Step 1.
3
Execute Step-Level Approval Actions
Upon Step 1 approval, step-specific actions run.
Step approval actions notify stakeholders or update status fields specific to completing that stage.
4
Evaluate Subsequent Step Entry Criteria
The system checks if the record meets entry criteria for Step 2.
Determines whether the approval process continues to the next assigned approver or proceeds directly to final approval.
5
Trigger Final Approval Actions
Final approval actions run and the record is unlocked.
Completes the process lifecycle by restoring record editing capability and finalizing field values.

Key Concept

Salesforce Approval Process Lifecycle and Execution Order
Question 1333Question →

A Customer Success Lead wants report creators to easily analyze Customer Satisfaction (CSAT) Survey records alongside attributes from the related Account and the Account Owner's User profile. The administrator is tasked with updating the existing Custom Report Type so that reporting users can access these related fields in a dedicated section with clear, business-friendly display names without creating redundant fields on the object. Which TWO actions should the administrator take within the Custom Report Type layout editor to meet these requirements?

Select all that apply

Show answer & explanation

Answer: Use the 'Add fields related via lookup' feature to traverse object relationships and bring Account Owner User fields onto the report layout.; Create a new section on the report layout and edit field properties to rename display labels for reporting clarity.

Answer

The administrator should use the 'Add fields related via lookup' functionality to bring related Account Owner User fields into the Custom Report Type layout, and create custom sections while editing field display labels within the layout editor for reporting clarity.
Using the 'Add fields related via lookup' feature in the Custom Report Type field layout editor allows administrators to traverse lookup relationships up to four levels deep to expose related object attributes. Additionally, creating custom sections and editing field properties inside the layout editor enables logical field grouping and customization of report display labels without changing actual field names on the underlying objects.

Step-by-Step Solution

1
Navigate to Setup > Custom Report Types and select the CSAT Survey Custom Report Type.
Access the report type configuration page and click Edit Layout.
The field layout editor controls which fields are available to report creators and how they are organized.
2
Click 'Add fields related via lookup' in the right-hand panel, traverse from Account to Account Owner (User), select required fields, and add them to the layout.
The related User fields are made available for reports based on this report type without creating custom fields on the object.
Salesforce Custom Report Types allow referencing fields up to 4 lookup levels away.
3
Create a new section (e.g., 'Account Owner Details'), drag the newly added lookup fields into this section, double-click the fields, and modify their display labels.
Fields are logically organized under a custom section and display user-friendly names in the report builder.
Renaming field display labels in the Custom Report Type layout changes how fields appear in reports without altering object schema labels.

Key Concept

Custom Report Type Layout Customization and Lookup Traversal
Question 1334Question →

A Salesforce administrator at an educational institution needs to import 25,000 historical Case records into Salesforce from a legacy ticketing system. Additionally, the administrator must set up an automated script to run this data import weekly via a command-line schedule. Which tool should the administrator choose to meet these operational requirements?

Show answer & explanation

Answer: Data Loader, because it supports importing Case records and enables command-line interface (CLI) automation.

Answer

Data Loader, because it supports importing Case records and enables command-line interface (CLI) automation.
Data Loader is the appropriate tool because it supports standard Case object imports and provides command-line interface (CLI) capabilities required for scheduling automated weekly jobs. Data Import Wizard cannot import Case records and lacks command-line automation features.

Step-by-Step Solution

1
Analyze Object Support Requirements
Identify that Case is a standard object not supported by the Data Import Wizard (which only supports Accounts, Contacts, Leads, Solutions, Campaign Members, and Custom Objects).
Tool selection depends on object compatibility.
2
Evaluate Automation and Scheduling Requirements
Determine that automated command-line execution requires Data Loader CLI capabilities.
Data Import Wizard requires manual user interaction via the web interface and cannot be run via command-line scripts.
3
Conclude Optimal Tool Choice
Select Data Loader as it fulfills both Case object support and command-line automated execution requirements.
Data Loader meets all functional and operational constraints specified in the scenario.

Key Concept

Data Import Wizard vs Data Loader Capabilities and Object Support
Estimated Time:1m 30s
Question 1335Question →

An administrator at a financial services firm is configuring Einstein Activity Capture (EAC) for a team of advisors using Google Workspace. Executive leadership requires events created in Google Calendar to automatically stream into Salesforce and link to related accounts, but events created directly within Salesforce must never sync back to the advisors' Google Calendars. Furthermore, the administrator needs to grant the advisors access to EAC capabilities. Which combination of administrative actions fulfills these requirements?

Show answer & explanation

Answer: Configure the Event Sync direction as Google to Salesforce in the EAC configuration settings and assign the Standard Einstein Activity Capture permission set to the advisors.

Answer

Configure the Event Sync direction as Google to Salesforce in the EAC configuration settings and assign the Standard Einstein Activity Capture permission set to the advisors.
To satisfy the requirement where external calendar events flow into Salesforce without pushing internal Salesforce events back to the external calendar, the administrator must choose the 'Google to Salesforce' sync direction. In addition, feature access for Einstein Activity Capture is managed by granting permission sets to individual users rather than altering core profiles.

Step-by-Step Solution

1
Analyze sync direction requirement
Events from Google Calendar must sync to Salesforce, but Salesforce events must not sync to Google Calendar. This dictates a one-way 'Google to Salesforce' event sync direction.
Choosing 'Both ways' or 'Salesforce to Google' would violate the business constraint of keeping Salesforce-created events out of Google Calendar.
2
Determine user access management approach
Assign the Standard Einstein Activity Capture permission set (or a custom permission set containing the permission) to the target users.
EAC features and licenses are assigned via permission sets, following the principle of additive access management rather than profile modifications.

Key Concept

Einstein Activity Capture Sync Directions and Access Provisioning
Question 1336Question →

The customer support team at Zenith Software Helpdesk handles high-priority technical cases. Support leadership notices that when agents open related Account and Contact records from a Case record page, those records open as separate primary tabs, causing workspace clutter. The administrator is tasked with ensuring that Account and Contact records automatically open as subtabs beneath the parent Case primary tab in the Lightning Service Console app. Which configuration step should the Salesforce Administrator perform to meet this requirement?

Show answer & explanation

Answer: Edit the Navigation Rules for the Service Console application in App Manager to set Account and Contact records as subtabs of Case.

Answer

Edit the Navigation Rules for the Service Console application in App Manager to set Account and Contact records as subtabs of Case.
In Salesforce Lightning Console applications, tab opening behavior is controlled via Navigation Rules inside App Manager. Specifying that related records such as Account or Contact open as subtabs of Case ensures that agents remain focused on the primary case context without cluttering the main console workspace.

Step-by-Step Solution

1
Navigate to Setup and search for App Manager.
Access the list of all Lightning and Classic applications in the organization.
Console application settings, including tab navigation structure, are managed within App Manager.
2
Locate the target Lightning Service Console application, click its action menu, and choose Edit.
Opens the Lightning App Builder settings wizard for the console app.
Modifying the app configuration allows access to navigation rules, utility bar, and user assignments.
3
Select Navigation Rules, locate Account and Contact objects, and set them to open as subtabs of Case.
Clicking linked Account or Contact records from a Case record page will open them neatly aligned under the parent Case primary tab.
Navigation Rules govern record tab hierarchy and opening behavior within Lightning Console apps.

Key Concept

Lightning Service Console Navigation Rules
Question 1337Question →

A Salesforce Administrator is building an autolaunched flow to process a list of Renewal Contracts. To ensure the flow executes efficiently without hitting SOQL or DML governor limits, which TWO design actions should the administrator take?

Select all that apply

Show answer & explanation

Answer: Execute a Get Records element prior to entering the Loop element to fetch the required dataset into a record collection variable.; Use an Assignment element inside the Loop to add updated record variables to a record collection, then execute an Update Records element after the Loop finishes.

Answer

The administrator should execute a Get Records element prior to entering the Loop to fetch records into a collection variable, and use an Assignment element inside the Loop to stage record changes into a collection before performing a single Update Records operation after the Loop finishes.
Bulkification requires moving data access and manipulation elements outside of iteration loops. Fetching records prior to entering the loop gathers the dataset in a single query. Staging updates into a collection variable via an Assignment element and running a single Update Records element after the loop completes ensures all database operations occur in bulk.

Step-by-Step Solution

1
Analyze database query strategy before entering a loop.
Identify that retrieving records before looping avoids issuing SOQL queries on every iteration.
SOQL queries inside loops consume governor limits rapidly.
2
Analyze record update strategy during iteration.
Determine that field changes should be assigned to an output collection variable inside the loop and committed via a single Update Records element after the loop completes.
DML operations inside loops violate the 150 DML statement governor limit per transaction.

Key Concept

Flow Bulkification Best Practices
Question 1338Question →

An administrator at Meridian BioTech is setting up analytics for the sales team. The VP of Sales requests two specific security behaviors: first, regional sales managers should view their operational dashboard components populated strictly with records they own or share according to record-level access settings; second, senior executives require a consolidated performance dashboard that always displays company-wide totals regardless of who views it. Which TWO configurations should the administrator implement to satisfy these security requirements?

Select all that apply

Show answer & explanation

Answer: Configure the regional sales manager dashboard as a dynamic dashboard by setting the running user to 'Run as the logged-in user'.; Configure the consolidated executive dashboard as a static dashboard with the VP of Sales specified as the running user.

Answer

The administrator must set the regional sales manager dashboard to run as the logged-in user (dynamic dashboard) and set the consolidated executive dashboard to run as a static running user (the VP of Sales).
The requirement for regional managers to see only their own accessible data is fulfilled by configuring a dynamic dashboard running as the logged-in user. The requirement for executives to view aggregated company totals regardless of their personal sharing permissions is met by setting a static running user with top-level data access, such as the VP of Sales.

Step-by-Step Solution

1
Analyze requirement 1: Regional managers must view data based on their individual security access.
Dynamic dashboards ('Run as the logged-in user') display component data customized to the security and sharing privileges of the user currently viewing the dashboard.
This guarantees that record-level security (OWD, sharing rules, role hierarchy) is strictly enforced per manager.
2
Analyze requirement 2: Senior executives must see company-wide totals summarized on one dashboard regardless of personal record sharing.
Static dashboards run using a designated user's security context (e.g., VP of Sales who has visibility into all records). All viewers see component metrics calculated through that running user's permissions.
Static dashboards allow broad metric aggregation without modifying underlying record-level sharing.

Key Concept

Dashboard Running User and Visibility Settings
Question 1339Question →

An administrator at Apex Financial needs to establish duplicate prevention for a custom object named Loan Application. The requirement mandates that any new Loan Application containing a Taxpayer Identification Number (TIN) identical to an existing record must be blocked upon saving and logged for audit reporting. What is the correct sequence of configuration steps the administrator must perform to satisfy this requirement?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence is: (1) Create the custom Matching Rule with exact matching on Taxpayer Identification Number, (2) Activate the custom Matching Rule, (3) Create the custom Duplicate Rule with Block and Report actions, (4) Associate the active Matching Rule inside the Duplicate Rule, and (5) Activate the custom Duplicate Rule.
In Salesforce Duplicate Management, configuration must follow a strict dependencies lifecycle: matching criteria (Matching Rule) must be created and activated first so that Salesforce builds the required match keys. Then, the enforcement policy (Duplicate Rule) is created with desired actions (Block/Report), linked to the activated Matching Rule, and finally activated to enforce real-time duplicate blocking.

Step-by-Step Solution

1
Define matching logic
A custom Matching Rule is created for the Loan Application object using the Taxpayer Identification Number field with exact matching.
Matching rules define how duplicates are identified by specifying the object, target fields, and matching algorithm.
2
Activate matching rule
The Matching Rule status updates to Active and match keys are generated.
A matching rule must be activated before it can be effectively assigned to and evaluated by duplicate rules.
3
Define enforcement actions
A custom Duplicate Rule is created with Action on Create set to Block and the Report checkbox enabled.
Duplicate rules govern the response behavior (Block, Allow, Alert, Report) when matching records are flagged.
4
Link matching criteria to duplicate rule
The activated custom Matching Rule is selected in the Duplicate Rule configuration.
The duplicate rule requires a designated active matching rule to execute comparisons.
5
Enable enforcement
The custom Duplicate Rule is activated.
Duplicate detection and blocking only occur once the duplicate rule itself is activated.

Key Concept

Order of Configuration for Salesforce Duplicate Management (Matching Rules vs. Duplicate Rules)
Question 1340Question →

A system administrator is configuring an approval process for Travel Expense custom object records in Salesforce. When a user submits an expense record for approval, which standard behavior occurs automatically by default during initial submission?

Show answer & explanation

Answer: The submitted record is locked to prevent editing while undergoing approval evaluation.

Answer

The submitted record is locked to prevent editing while undergoing approval evaluation.
When a record enters an approval process in Salesforce, the system automatically applies a record lock as part of default initial submission processing to prevent users from altering data while the review is pending.

Step-by-Step Solution

1
Identify the standard system action performed upon initial submission to an approval process.
Salesforce locks the record automatically upon entry.
Locking the record protects data integrity while approvers review the submission.

Key Concept

Approval Process Default Initial Submission Actions
PreviousPage 67 / 90Next
All practice questions — Salesforce Certified Administrator | Examkin