Examkin

All practice questions

1784 questions

All types1,784Multiple choice918Multiple select587Matching142Ordering137
Question 1561Question →

A Salesforce Administrator at a SaaS enterprise is building an Account report for key account managers. The business requirements state that the report must display Accounts that belong to either the 'Healthcare' or 'Financial Services' industry, AND meet at least one of the following criteria: have an Annual Revenue exceeding $10,000,000 OR maintain an active 'Platinum' SLA subscription. The administrator configures the following report filters:

1. Industry EQUALS Healthcare
2. Industry EQUALS Financial Services
3. Annual Revenue GREATER THAN 10000000
4. SLA EQUALS Platinum

Which filter logic expression should the administrator apply to fulfill this exact business requirement?

Show answer & explanation

Answer: (1 OR 2) AND (3 OR 4)

Answer

The expression (1 OR 2) AND (3 OR 4) correctly groups the industry picklist options and the qualifier conditions.
The expression grouping filters 1 and 2 with an OR operator inside parentheses ensures the record matches either specified industry. Similarly, grouping filters 3 and 4 with an OR operator inside parentheses ensures the record fulfills at least one qualifying condition. Joining both parenthesized groups with an AND operator ensures that an account must satisfy both overarching requirements.

Step-by-Step Solution

1
Identify mutually exclusive field criteria requiring OR logic.
Industry equals Healthcare OR Financial Services -> (1 OR 2).
A single Account record cannot have two distinct picklist values simultaneously on a single picklist field.
2
Identify qualification criteria requiring OR logic.
Annual Revenue > $10M OR SLA equals Platinum -> (3 OR 4).
The business rule requires meeting at least one of these two financial/support conditions.
3
Combine both logical groups using AND operator.
(1 OR 2) AND (3 OR 4).
Parentheses enforce group precedence before evaluating the overall AND relationship.

Key Concept

Custom Filter Logic and Boolean Parenthesization in Salesforce Reports
Question 1562Question →

A Salesforce administrator at Pinnacle Operations is configuring a custom Duplicate Rule on the Lead object to improve data hygiene. Which two settings or actions can the administrator configure directly within the Duplicate Rule definition? (Select TWO answers)

Select all that apply

Show answer & explanation

Answer: Determining whether to block the save operation or display an alert allowing the user to proceed.; Selecting whether duplicate matching criteria enforce or bypass Organization-Wide Sharing Rules.

Answer

The correct settings configured directly within a Duplicate Rule are determining whether to block or alert on duplicates, and selecting whether to enforce or bypass sharing rules during duplicate matching.
In Salesforce, Duplicate Rules determine the operational behavior when potential duplicates are found—such as triggering an Alert, Blocking record saves, or generating Report logs—and let administrators choose whether matching enforces or bypasses sharing rules. Field matching algorithms (exact/fuzzy match) are handled separately by Matching Rules.

Step-by-Step Solution

1
Distinguish between Matching Rule capabilities and Duplicate Rule capabilities.
Matching Rules identify potential duplicate records using field comparison algorithms (exact or fuzzy matching).
Matching Rules evaluate data similarity between records, while Duplicate Rules control execution logic.
2
Identify settings configured directly inside a Duplicate Rule.
Duplicate Rules govern what happens when potential duplicates are found (Block vs. Allow/Alert, Report) and how security rules (Sharing Rules) apply to record matching.
Duplicate Rules determine enforcement behavior, user alerts, reporting logs, and security scoping when duplicate records are detected.

Key Concept

Duplicate Rule Configuration vs Matching Rule Configuration
Question 1563Question →

An administrator at a non-profit organization needs to automate a business process for a custom object named Volunteer Shift. When a Volunteer Shift record is created or updated and the Hours Completed field is filled, a custom field named Shift Status on the triggering record must automatically be set to Completed before the record is written to the database. The requirement specifies that this automation must deliver optimal performance without causing additional DML operations. Which automation tool configuration should the administrator select?

Show answer & explanation

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

Answer

Configure a Record-Triggered Flow optimized for Fast Field Updates (Before-Save)
Configuring a Record-Triggered Flow optimized for Fast Field Updates (Before-Save) is the correct choice because it updates fields on the triggering record before it is saved to the database. This approach executes significantly faster and avoids additional DML updates or secondary order-of-execution cycles.

Step-by-Step Solution

1
Analyze the automation requirement
The requirement specifies updating fields on the same record that triggered the automation before it is written to the database, prioritizing execution speed and performance.
Identifying trigger timing and target object dictates the appropriate declarative tool.
2
Evaluate available declarative automation tools
Fast Field Updates (Before-Save Record-Triggered Flow) update the triggering record's fields directly in memory before the save event is committed.
This avoids re-triggering the order of execution, validation rules, or unnecessary DML operations.
3
Select the optimal configuration
A Before-Save Record-Triggered Flow is up to 10 times faster than an After-Save flow or legacy tools for same-record updates.
It aligns fully with Salesforce best practices for same-record field updates.

Key Concept

Automation Tool Selection: Fast Field Updates (Before-Save Flow)
Question 1564Question →

An organization requires an automated process when a custom object record, Project__c, is updated to a status of 'Cancelled'. The requirements specify: sending an email notification to the project manager, updating the status of all related child Project_Task__c records to 'Cancelled', and removing all associated temporary draft logs from the system. Which limitation of Process Builder must the Salesforce Administrator account for when designing this solution?

Show answer & explanation

Answer: Process Builder cannot natively delete records, so deleting the temporary draft logs requires calling a Flow or Apex action.

Answer

Process Builder cannot natively delete records, so deleting the temporary draft logs requires calling a Flow or Apex action.
Process Builder provides native actions for updating related records, creating records, sending email alerts, and submitting records for approval. However, it lacks a native 'Delete Records' action. To delete records, an administrator must either invoke an autolaunched Flow or call Apex code from the process.

Step-by-Step Solution

1
Analyze the requirements against native Process Builder actions
Process Builder natively supports sending email alerts, creating records, updating records (including parent and child records), posting to Chatter, submitting for approval, and invoking Flows/Apex.
Identify which requested actions are natively supported and which are unsupported.
2
Identify the unsupported native action requirement
Deleting records is not available as a standard built-in action in Process Builder.
Determines the design constraint for deleting the temporary draft logs.
3
Select the correct implementation approach
To perform record deletion from Process Builder, the administrator must launch an autolaunched Flow or call an Apex method.
Extends Process Builder functionality to meet all business requirements.

Key Concept

Process Builder Native Capabilities and Limitations
Question 1565Question →

A Salesforce Administrator at a renewable energy company is tasked with configuring an Opportunity report for regional sales directors. The report must satisfy the following business requirements:
1. Categorize deals into three distinct size tiers based on the Amount field: 'Small' (< 20,000),′Medium′(20,000), 'Medium' ( 20,000 to 100,000),and′Large′(>100,000), and 'Large' (> 100,000).
2. Restrict the report results to show only Accounts that have at least one registered active installation record (a custom object related to Account via a lookup relationship).

Which TWO features should the administrator use to fulfill these report requirements?

Select all that apply

Show answer & explanation

Answer: Create a Bucket Field on the Amount numeric field to define the size tier ranges.; Add a Cross Filter on Accounts with Install Records and apply a secondary sub-filter where Active equals True.

Answer

The administrator should create a Bucket Field on the Amount field to categorize opportunity sizes and add a Cross Filter on Accounts with Install Records (with a sub-filter for Active equals True) to filter by related records.
Bucket fields are designed specifically to categorize numeric, picklist, or text values into custom buckets without writing formulas or adding custom object fields. Cross filters enable filtering parent object report rows by evaluating related child records (including across lookup relationships) and applying sub-filters to those child records.

Step-by-Step Solution

1
Determine how to group numeric values into categorical ranges in a report.
Use a Bucket Field on the Amount field to define ranges for Small, Medium, and Large.
Bucket fields allow inline reporting categorization of numeric fields without schema modifications.
2
Determine how to filter parent records based on child object presence and criteria over a lookup relationship.
Use a Cross Filter: Accounts WITH Install Records, filtered by Active = True.
Cross filters evaluate child record relationships dynamically within reports, including across lookup relationships.

Key Concept

Report Bucketing and Cross Filters
Question 1566Question →

An administrator at Borealis Energy created and activated a custom Matching Rule on the Account object using the Account Name and Tax ID fields. However, when sales representatives save new Account records containing values identical to existing accounts, Salesforce saves the records without displaying warnings, blocking creation, or generating entries in Duplicate Record Sets. Which of the following explains why duplicate records are still being created without any warning?

Show answer & explanation

Answer: The corresponding Duplicate Rule is inactive or lacks configured actions such as Alert or Report.

Answer

The corresponding Duplicate Rule is inactive or lacks configured actions such as Alert or Report.
In Salesforce Duplicate Management, Matching Rules define *how* potential duplicates are identified (the criteria), whereas Duplicate Rules define *when* to run duplicate checks and *what action* to take (Alert, Block, Report). Activating a Matching Rule has no visual or reporting effect until an active Duplicate Rule uses it.

Step-by-Step Solution

1
Differentiate between Matching Rules and Duplicate Rules in Salesforce.
Recognize that Matching Rules strictly specify the matching logic (fields and match types), while Duplicate Rules determine what happens when a match is found.
Activating a Matching Rule alone does not enforce duplicate checking until it is linked to an active Duplicate Rule.
2
Verify Duplicate Rule configuration settings.
Confirm that the Duplicate Rule must be set to Active and have designated execution options such as Alert, Block, and Report for Create or Edit operations.
If the Duplicate Rule is inactive or missing alert/report actions, Salesforce will evaluate nothing upon record save.

Key Concept

Separation of responsibilities between Matching Rules (identifying duplicates) and Duplicate Rules (enforcing actions).
Question 1567Question →

A Salesforce Administrator needs to automate a process for a custom object named Event Sponsorship. When an Event Sponsorship record's status is changed to 'Confirmed', the system must satisfy two requirements: (1) update a custom field named Discount_Rate__c on the triggering record prior to saving, and (2) create a related Task record assigned to the finance team. Which TWO automation approaches should the administrator combine to meet these requirements efficiently while adhering to Salesforce best practices? (Select TWO answers.)

Select all that apply

Show answer & explanation

Answer: Use a Record-Triggered Flow set to Fast Field Updates (before-save) to update the Discount_Rate__c field on the triggering Event Sponsorship record.; Use a Record-Triggered Flow set to Actions and Related Records (after-save) to create the related Task record for the finance team.

Answer

The administrator should use a Record-Triggered Flow configured for Fast Field Updates (before-save) to perform the same-record update on Discount_Rate__c, and a Record-Triggered Flow configured for Actions and Related Records (after-save) to create the related Task record.
Salesforce best practice mandates using a Fast Field Updates (before-save) Record-Triggered Flow when updating fields on the record that triggered the flow, as it performs updates significantly faster without extra DML steps. An Actions and Related Records (after-save) Record-Triggered Flow is appropriate for creating child or related records like Tasks because those require access to record IDs and relationship execution after the primary record save completes.

Step-by-Step Solution

1
Analyze the requirement for updating the triggering Event Sponsorship record's field.
Same-record field updates prior to save should use Fast Field Updates (before-save record-triggered flows) for optimal performance and no additional DML execution.
Before-save flows run before the record is written to the database, eliminating additional save cycles.
2
Analyze the requirement for creating a related Task record.
Creating related records requires an Actions and Related Records (after-save record-triggered flow) because the primary record must exist in the database with an assigned ID.
After-save flows are designed for operations involving related records or external system actions.

Key Concept

Selecting optimal record-triggered flow optimization types (Before-Save vs. After-Save) based on record update context and related object operations.
Question 1568Question →

An organization requires an automated process on the Asset object. When an Asset's status is updated to Obsolete, all related custom Maintenance Request records that are currently Open must have their status updated to Cancelled. To ensure optimal performance and avoid reaching governor limits, how should the administrator configure the Flow Builder elements?

Show answer & explanation

Answer: Execute a Get Records element to retrieve open Maintenance Requests, iterate through them using a Loop element, update the status field using an Assignment element to populate a record collection variable, and execute a single Update Records element after the loop.

Answer

The administrator should retrieve open Maintenance Requests using a Get Records element, process each record using a Loop and Assignment element to build an updated record collection, and execute a single Update Records element outside the loop.
To adhere to Salesforce bulkification best practices and governor limits, data manipulation elements (DML) such as Update Records must never be placed inside a Loop element. Instead, records should be modified in memory using Assignment elements, added to a collection variable, and updated in the database with a single Update Records element after the loop ends.

Step-by-Step Solution

1
Identify the performance and bulkification requirement
DML operations (such as Update Records) must be executed outside of loops to respect Salesforce governor limits.
Salesforce enforces strict governor limits per transaction on DML statements.
2
Construct the collection in Flow Builder
Use Get Records to fetch child records, loop through the collection, update values in an Assignment element, and append each updated item to a new collection variable.
This accumulates changes in memory without invoking database updates inside the loop iteration.
3
Execute database update
Pass the populated collection variable to a single Update Records element placed after the loop completes.
A single DML statement updates all records in the collection efficiently within governor limits.

Key Concept

Bulkification in Flow Builder using Assignment and Collection Variables outside of Loops
Estimated Time:1m 30s
Question 1569Question →

A support manager at Apex Global Services wants to calculate the elapsed business days between the Created Date and Closed Date for each individual support case listed in a detail report. The manager also wants to display these case records grouped by Product Family to analyze average turnaround times. Which solution should the Salesforce administrator implement to calculate the elapsed time for each individual case record within the report?

Show answer & explanation

Answer: Add a row-level formula to the report that evaluates the date difference on every detail record.

Answer

Add a row-level formula to the report that evaluates the date difference on every detail record.
Row-level formulas evaluate logic for every individual detail record (row) in a report. Because the support manager needs to calculate the elapsed days for each individual case record, a row-level formula in the report builder is the correct solution.

Step-by-Step Solution

1
Identify the level of evaluation required by the business requirement.
The requirement specifies calculating elapsed time for each individual record (row) in the report.
Calculations applied directly to individual records require row-level logic rather than aggregated summary logic.
2
Select the appropriate Salesforce report formula type.
A row-level formula allows writing logic that executes across detail rows within the report builder.
Summary formulas evaluate aggregated data at summary levels, whereas row-level formulas execute on individual record rows.

Key Concept

Row-level formulas vs. Summary formulas in Salesforce Reports
Question 1570Question →

A Salesforce administrator at Nexus Financial Services needs to configure duplicate management for Account records to prevent duplicate submissions based on a custom Tax Identification Number field. What is the correct sequence of steps required to build, configure, and activate this duplicate prevention process in Salesforce?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence starts with creating the custom Matching Rule, activating that Matching Rule, creating the Duplicate Rule and associating the active Matching Rule, configuring the Duplicate Rule enforcement actions (Alert/Block/Report), and finally activating the Duplicate Rule.
The correct sequence begins with building the matching criteria (Matching Rule creation) and activating it. Once active, the Duplicate Rule can be created, linked to the active Matching Rule, configured with execution actions (Block/Allow/Alert/Report), and finally activated for end users.

Step-by-Step Solution

1
Create the custom Matching Rule
Defines field-level logic for duplicate identification.
Matching criteria must exist before duplicate rules can evaluate records against them.
2
Activate the Matching Rule
Makes the matching criteria available for selection in Duplicate Rules.
Salesforce duplicate rules cannot select or utilize inactive matching rules.
3
Create the Duplicate Rule and associate the active Matching Rule
Links record-level duplicate actions with the matching logic.
Duplicate rules provide the container for execution rules and link to matching criteria.
4
Configure Duplicate Rule Actions
Specifies whether to Block, Allow, Alert, or Report duplicate record operations.
Administrators must define how Salesforce responds when a match is detected.
5
Activate the Duplicate Rule
Enforces duplicate detection live across the organization.
Duplicate rules do not run until explicitly activated.

Key Concept

Salesforce Duplicate Management setup workflow requires creating and activating a Matching Rule prior to referencing it within a Duplicate Rule, configuring its actions, and activating the Duplicate Rule.
Estimated Time:1m 30s
Question 1571Question →

An administrator is building an autolaunched flow to update the Stage of all open Renewal Opportunities associated with an Account whenever the Account's service tier changes. To ensure the flow adheres to Salesforce governor limits and bulkification best practices, which two elements or design choices should the administrator include in the flow logic?

Select all that apply

Show answer & explanation

Answer: An Assignment element inside the loop that adds each modified Opportunity record to a record collection variable.; A single Update Records element positioned outside and after the loop to update the record collection variable.

Answer

The administrator should use an Assignment element inside the loop to populate a record collection variable, and then execute a single Update Records element outside the loop to commit all updates in bulk.
Bulkifying flows requires keeping data manipulation (DML) elements out of loops. Correct flow design uses an Assignment element inside the loop to accumulate modified records into a record collection variable, followed by a single Update Records element placed outside the loop path to perform the update in a single bulk operation.

Step-by-Step Solution

1
Iterate through retrieved records
Each Opportunity record is processed individually in the loop.
Flow loops allow inspecting and modifying field values on individual items within a record collection.
2
Assign modified records to a collection variable inside the loop
Changes are stored in memory without invoking DML operations.
Using an Assignment element to add items to a record collection variable avoids performing database updates per iteration.
3
Perform a bulk update outside the loop
All record modifications in the collection are persisted in a single DML transaction.
Executing DML elements outside the loop ensures the flow stays well within Salesforce governor limits.

Key Concept

Bulkification in Flow Builder using Collection Variables and Assignment Elements
Question 1572Question →

Universal Freight Solutions requires an automated mechanism on a custom object named Vendor Compliance Review. Whenever a Vendor Compliance Review record is created or updated, the system must automatically set the Risk Index score field on the triggering record based on selected risk factors before the record is saved to the database. Which automation tool should the Salesforce administrator select to fulfill this requirement efficiently?

Show answer & explanation

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

Answer

Record-Triggered Flow optimized for Fast Field Updates (Before-Save)
A Record-Triggered Flow configured for Fast Field Updates (Before-Save) is the recommended tool when updating fields on the same record that triggers the automation. It evaluates and modifies the record prior to database commit, avoiding extra DML operations and offering significantly faster performance.

Step-by-Step Solution

1
Analyze the automation requirements and target record context
The update must occur on the same triggering record immediately upon creation or edit prior to database persistence.
Identifying the target object and timing is critical for selecting the correct declarative automation tool.
2
Evaluate declarative tool options based on Salesforce best practices
Fast Field Updates (Before-Save Record-Triggered Flow) update fields on the triggering record before it is saved to the database, executing up to 10 times faster than after-save flows without triggering extra DML operations or standard order of execution loops.
Before-Save flows are the Salesforce-recommended standard for same-record field updates.

Key Concept

Selecting the optimal declarative automation tool based on trigger context and execution performance recommendations
Question 1573Question →

A Salesforce Administrator is asked to automate several business actions when a Contract record status is updated to 'Activated'. The requirements include: creating a follow-up Task, posting an update to the related Account Chatter feed, sending an Email Alert to the contract owner, and deleting temporary draft attachment records associated with the contract. Which requirement CANNOT be accomplished using native Process Builder actions without invoking Apex code or Flow Builder?

Show answer & explanation

Answer: Deleting temporary draft attachment records associated with the contract

Answer

Deleting temporary draft attachment records associated with the contract
Process Builder lacks native functionality to perform DML delete operations on records. To automatically delete records upon criteria evaluation, an administrator must call an autolaunched Flow or use Apex code.

Step-by-Step Solution

1
Review the native action types available in Process Builder
Process Builder native actions include: Create a Record, Update Records, Send Email Alert, Post to Chatter, Submit for Approval, Call Code/Process, and Send Custom Notification.
Understanding out-of-the-box declarative boundaries helps identify missing capabilities.
2
Evaluate the deletion requirement against Process Builder capabilities
Process Builder cannot execute record deletion operations directly.
Record deletion requires record-triggered flows, autolaunched flows, or Apex triggers.

Key Concept

Process Builder Native Action Capabilities and Limitations
Estimated Time:1m 15s
Question 1574Question →

An organization tracks client retention through a custom object named Service Contract. When a Service Contract record is updated to a status of 'Renewed', the system must immediately set the Renewal Audit Status field on the same record to 'Completed' before saving to the database. Additionally, an automated email alert must be sent to the Account Owner immediately, and a renewal check-in task must be scheduled 30 days prior to the contract expiration date. Which TWO automation configurations should a Salesforce Administrator select to meet these requirements efficiently using declarative tools?

Select all that apply

Show answer & explanation

Answer: Configure a Record-Triggered Flow optimized for Fast Field Updates (before-save) to set the Renewal Audit Status field on the triggering record.; Configure an Actions and Related Records (after-save) Record-Triggered Flow with a Scheduled Path to handle the immediate email alert and schedule the check-in task 30 days before expiration.

Answer

The administrator should implement a Fast Field Updates (before-save) Record-Triggered Flow for the same-record field update, and an Actions and Related Records (after-save) Record-Triggered Flow with a Scheduled Path for the email alert and time-based task creation.
For same-record field updates upon record creation or update, a Fast Field Updates (before-save) record-triggered flow is the recommended best practice as it modifies record values before they are committed to the database without additional DML cycles. For sending external notifications and executing time-delayed actions relative to a date field (such as 30 days before expiration), an Actions and Related Records (after-save) record-triggered flow with a Scheduled Path is the appropriate solution.

Step-by-Step Solution

1
Analyze same-record field update requirement
Identified that updating a field on the record that triggered the automation before it writes to the database requires a Fast Field Updates (before-save) record-triggered flow.
Before-save flows execute much faster and avoid unnecessary DML operations or secondary order-of-execution cycles.
2
Analyze outbound email notification and time-based task scheduling requirements
Identified that sending email alerts and scheduling tasks 30 days prior to a date field require an Actions and Related Records flow containing a Scheduled Path.
Scheduled Paths within record-triggered flows replace legacy time-dependent workflow actions and allow time-offset execution.

Key Concept

Selecting optimal Flow Builder trigger types and execution paths based on record lifecycle events and performance best practices.
Estimated Time:1m 30s
Question 1575Question →

A Salesforce administrator at Orion Maritime Solutions created and activated a custom Matching Rule on the Contact object to compare email addresses and phone numbers. However, sales representatives report that the system still allows them to create identical Contact records without displaying any warning or alert. What is the most likely reason for this behavior?

Show answer & explanation

Answer: The active Matching Rule has not been associated with an active Duplicate Rule that defines the Action to alert or block users.

Answer

The active Matching Rule has not been associated with an active Duplicate Rule that defines the Action to alert or block users.
Matching rules define only the algorithm and field criteria used to identify duplicate records. In order to alert or block users when duplicates are detected during record creation or editing, the matching rule must be embedded into an active Duplicate Rule that explicitly sets the Action to Alert or Block.

Step-by-Step Solution

1
Analyze the roles of Matching Rules versus Duplicate Rules in Salesforce.
Matching Rules define the matching criteria (e.g., matching email and phone), whereas Duplicate Rules determine when and how matching rules are run and what action to take (Alert, Block, or Report).
Creating and activating a matching rule alone does not execute any enforcement behavior.
2
Identify the cause of the missing alerts during record creation.
Because no active Duplicate Rule is referencing the custom Matching Rule with an alert or block action configured, the system permits duplicate record creation.
Without an active Duplicate Rule to enforce the criteria, Salesforce will not prompt users with duplicate warnings.

Key Concept

Distinction between Matching Rules (identification criteria) and Duplicate Rules (enforcement actions)
Estimated Time:1m 15s
Question 1576Question →

A Salesforce administrator is tasked with building a custom report on Support Cases grouped by Support Tier. The VP of Customer Support requires two specific metrics: evaluating the duration in days between Created Date and Closed Date for every individual case record, and calculating the percentage of closed cases for each Support Tier relative to the grand total of all closed cases. Which two formula configurations should the administrator implement to meet these business requirements?

Select all that apply

Show answer & explanation

Answer: Add a row-level formula to the report that subtracts CreatedDate from ClosedDate to calculate duration on each record.; Add a summary formula using the PARENTGROUPVAL function to evaluate each Support Tier grouping against the grand total.

Answer

The administrator should add a row-level formula to compute the duration between ClosedDate and CreatedDate for each individual record, and use a summary formula with the PARENTGROUPVAL function to compare grouping totals against the grand total.
Row-level formulas execute record-by-record on report details, allowing administrators to subtract field values such as CreatedDate from ClosedDate for each case row. Summary formulas utilize functions like PARENTGROUPVAL to calculate ratios between specific grouping levels and grand totals.

Step-by-Step Solution

1
Determine the scope of the duration calculation requirement.
Since the duration must be evaluated for every individual case record row, a row-level formula is required.
Row-level formulas run record-by-record across detail rows within a report.
2
Determine the scope of the group-versus-grand-total percentage calculation.
A summary formula using PARENTGROUPVAL is required.
PARENTGROUPVAL calculates values relative to a parent group or grand total in summary and matrix report layouts.

Key Concept

Distinction between row-level formulas and summary formulas (including PARENTGROUPVAL) in Salesforce reports.
Estimated Time:1m 30s
Question 1577Question →

A Salesforce Administrator is reviewing declarative automation capabilities for business processes. Match each business automation requirement on the left with the correct Process Builder capability or platform limitation on the right.

Click a left item, then click its matching right item

Items

Automatically submit a record for an existing approval process when criteria are met
Create a follow-up Task record assigned to the Account Owner when an Opportunity is Closed Won
Hard delete inactive Lead records automatically 30 days after creation
Update fields on all related child Contact records when an Account rating changes to Hot

Matches

Show answer & explanation

Answer

Submitting for approval matches native Submit for Approval action; Creating a task matches native Create a Record action; Hard deleting leads matches unsupported capability requiring Flow or Apex; Updating child contacts matches native Update Records action for related records.
Process Builder natively supports submitting records for approval, creating records, and updating related child records. However, it lacks any native action for deleting records, which must be handled via Flow Builder or Apex code.

Step-by-Step Solution

1
Identify supported native actions in Process Builder
Process Builder supports creating records, updating triggering or related records, submitting for approval, posting to Chatter, launching flows, sending email alerts, and invoking Apex code.
Determines which scenario maps directly to a built-in Process Builder action.
2
Identify platform limitations in Process Builder
Process Builder lacks native record deletion capabilities and cannot perform complex background data cleanup like deleting records.
Distinguishes native capabilities from actions requiring Flow Builder or Apex.

Key Concept

Process Builder Capabilities and Limitations
Question 1578Question →

An administrator needs to build an autolaunched flow that calculates the total cost of all line items associated with a Work Order and updates a custom total field on the parent Work Order. Which design approach correctly utilizes flow resources and data elements while preventing SOQL and DML governor limit exceptions?

Show answer & explanation

Answer: Use a Get Records element to retrieve all related Work Order Line Items into a collection, use a Loop with an Assignment element to sum the line item costs into a currency variable, and place an Update Records element outside the loop.

Answer

Use a Get Records element to retrieve all related Work Order Line Items into a collection, use a Loop with an Assignment element to sum the line item costs into a currency variable, and place an Update Records element outside the loop.
The correct approach uses a single Get Records element to populate a record collection before looping. Inside the loop, an Assignment element accumulates the cost into a variable without invoking database calls. Finally, a single Update Records element updates the parent record outside the loop. This follows Salesforce bulkification design principles.

Step-by-Step Solution

1
Query related records bulkified
A single Get Records element retrieves the collection of Work Order Line Items before entering any loop.
Prevents hitting SOQL query governor limits by querying all required records in a single database transaction.
2
Aggregate values in memory
A Loop element iterates over the collection, using an Assignment element to add each line item cost to a number/currency flow variable.
Calculations and assignments occur in flow memory without issuing database calls.
3
Execute DML outside the loop
An Update Records element executes after loop completion to update the parent Work Order record.
Ensures DML operations are bulkified and executed only once per flow execution.

Key Concept

Flow Bulkification and Governor Limits
Question 1579Question →

A Salesforce administrator at Zenith Logistics is configuring duplicate management on the Lead object to improve data hygiene. The administrator has already built and activated a custom Matching Rule. Which two settings or actions are configured directly within a Duplicate Rule to control record processing and user notifications when duplicate records are detected?

Select all that apply

Show answer & explanation

Answer: Specify whether to Allow or Block the saving of a record identified as a duplicate during creation or editing.; Determine whether to display an Alert to the user and generate a Report when duplicates are found.

Answer

The settings configured directly within a Duplicate Rule are specifying whether to Allow or Block record saving and determining whether to Alert the user and Report on duplicate detection.
Duplicate Rules define the operational behavior whenever duplicate records are identified by a Matching Rule. Administrators configure whether the system should Allow or Block the record from being saved upon creation or edit, and whether to trigger an Alert to the user and log the occurrence for Reporting.

Step-by-Step Solution

1
Distinguish between Matching Rule responsibilities and Duplicate Rule responsibilities in Salesforce.
Matching Rules evaluate data using algorithms (exact/fuzzy) and criteria to identify duplicates. Duplicate Rules dictate the operational outcome once a match is found.
Clear separation of duties prevents misconfiguring execution behavior versus identification logic.
2
Identify duplicate handling outcomes available in a Duplicate Rule configuration.
Duplicate Rules allow setting actions on Create and Edit (Block or Allow), toggling on-screen Alerts, and generating Reports (Duplicate Record Sets).
These settings determine user interaction and administrative tracking when duplicate records are encountered.

Key Concept

Duplicate Rule vs Matching Rule Configuration Responsibilities
Estimated Time:1m 30s
Question 1580Question →

An operations manager at a technology firm requests a Salesforce report displaying Accounts and their associated active Assets. The manager requires a custom calculation that evaluates the purchase price of each individual Asset row to output a category label of 'High Value' if the price is greater than 50,000,or′Standard′ifitislessthanorequalto50,000, or 'Standard' if it is less than or equal to 50,000. Which solution should the Salesforce administrator implement to satisfy this requirement?

Show answer & explanation

Answer: Add a row-level formula to the report using an IF conditional logic statement to evaluate each Asset record individually.

Answer

Add a row-level formula to the report using an IF conditional logic statement to evaluate each Asset record individually.
Row-level formulas in Salesforce reports execute logic on every individual row in the report dataset. Using an IF statement within a row-level formula allows the administrator to evaluate each Asset's purchase price field directly and return a text string on a record-by-record basis.

Step-by-Step Solution

1
Determine the evaluation scope of the required calculation.
The requirement specifies calculating a label based on values within each individual Asset record row.
Understanding whether data needs to be evaluated row-by-row or across aggregate groupings dictates the formula type.
2
Select the appropriate Salesforce reporting calculation feature.
A row-level formula is selected because it evaluates each record in the report individually.
Summary formulas can only perform calculations on aggregated summary levels (such as group subtotals or grand totals).
3
Construct the formula logic using an IF expression.
An IF statement checks if the purchase price exceeds $50,000 and assigns 'High Value' or 'Standard'.
Conditional logic in row-level formulas can output text based on numeric field thresholds for individual rows.

Key Concept

Row-level formulas evaluate every individual record in a report, whereas summary formulas evaluate grouped or aggregated data.
Estimated Time:1m 30s
PreviousPage 79 / 90Next
All practice questions — Salesforce Certified Administrator | Examkin