All practice questions

1784 questions

Question 161Question

An administrator at a global enterprise is designing an automation strategy to satisfy two distinct business requirements while adhering to Salesforce architectural best practices:

1. Automatically calculate and update custom field values on the triggering Account record prior to database commit whenever an Account is created or modified.
2. Submit Opportunities with discount requests exceeding $100,000 through a multi-step authorization hierarchy while enforcing record locking during review.

Which TWO automation tools or configuration options should the administrator select to fulfill these requirements? (Select TWO)

Select all that apply

Show answer & explanation

Answer: A Record-Triggered Flow optimized for Fast Field Updates (Before-Save) to populate field values on the triggering Account record.; An Approval Process to lock Opportunity records and manage sequential, multi-step authorization requests.

Answer

The administrator should select a Record-Triggered Flow optimized for Fast Field Updates (Before-Save) for updating the triggering Account record, and an Approval Process for locking and routing high-value Opportunity discount approvals.
The combination of Fast Field Updates (Before-Save Flow) and Approval Processes directly matches Salesforce best practices. Fast Field Updates allow immediate field manipulation on the triggering record before database storage without incurring extra DML statements. An Approval Process is the dedicated declarative tool designed for multi-tier approvals requiring record locking during review.

Step-by-Step Solution

1
Analyze Requirement 1 for same-record updates prior to save.
Identify that updating fields on the triggering record before database write requires a Before-Save (Fast Field Updates) Record-Triggered Flow to optimize performance and prevent unnecessary DML executions.
Before-save flows run before the record is written to the database, making field modifications directly on the triggering record highly efficient.
2
Analyze Requirement 2 for record locking and multi-step authorization workflows.
Select an Approval Process as the native declarative framework for submission locking and hierarchical multi-step routing.
Approval processes natively support record locking, submission actions, and multi-step approval routing.
3
Evaluate and eliminate incorrect declarative choices.
Reject the After-Save Flow configuration for same-record updates due to DML overhead, and reject Roll-Up Summary fields over Lookup relationships due to platform relationship constraints.
After-save updates on triggering records consume extra governor limits, and roll-up summaries require a Master-Detail relationship.

Key Concept

Salesforce Declarative Automation Selection Guidelines
Question 162Question

A System Administrator is configuring user interface actions to streamline workflows across Salesforce. Match each business requirement with the correct action type or interface mechanism.

Click a left item, then click its matching right item

Items

Create a child Case record from an Account record page with pre-populated field values from the parent Account
Launch an interactive screen Flow from the global navigation header on any page without record context
Navigate users to an external web portal using URL parameters populated with field values from a Shipment record
Modify a targeted subset of fields on the current Opportunity record using a customized layout

Matches

Show answer & explanation

Answer

Each requirement matches its corresponding user interface mechanism: 1) Object-Specific Create Record Quick Action creates related records with predefined values; 2) Global Quick Action launches processes anywhere without record context; 3) Custom Detail Page Link opens external URLs with merge fields; 4) Object-Specific Update Record Quick Action provides customized field editing on the current record.
Each mechanism aligns with specific platform capabilities: Object-Specific Create Record actions have record context for pre-populating fields; Global Quick Actions operate context-free across the app; Custom Links construct dynamic URLs with merge fields; and Object-Specific Update actions streamline inline updates using dedicated action layouts.

Step-by-Step Solution

1
Analyze the requirement for creating child records from parent record context.
Identify that creating a related record with context and predefined field values requires an Object-Specific Create Record Quick Action.
Global actions cannot automatically establish parent-child relationships or reference parent field values, whereas object-specific actions have access to the parent context.
2
Evaluate the requirement for launching a global screen Flow from any page header.
Determine that a Global Quick Action is required.
Global actions exist independently of record pages and can be placed in global publisher layouts for universal access.
3
Assess the external URL navigation requirement with record token parameters.
Identify that a Custom Detail Page Link is the appropriate tool.
Custom Links allow constructible URLs that pull merge fields directly from the record detail page to pass data to third-party endpoints.
4
Examine the requirement to edit specific fields on the current record.
Map to Object-Specific Update Record Quick Action.
Update record quick actions provide a separate, concise layout to update fields on the primary object being viewed.

Key Concept

Selecting and configuring Quick Actions, Custom Buttons, and Links based on context and capability requirements
Estimated Time:1m 30s
Question 163Question

A Salesforce Administrator at a telecommunications company needs to design an automated solution on the standard Case object to meet two distinct business requirements:
1. Update target fields on the triggering Case record immediately before it is committed to the database to ensure optimal system performance.
2. Automatically create a child Task record assigned to the case owner and trigger an email notification when a high-priority Case is created.

Which TWO declarative automation solutions should the administrator implement to fulfill these requirements? (Select TWO)

Select all that apply

Show answer & explanation

Answer: A Fast Field Updates (Before-Save) Record-Triggered Flow to modify field values directly on the triggering Case record.; An Actions and Related Records (After-Save) Record-Triggered Flow to create the child Task record and execute the email alert.

Answer

The administrator should implement a Fast Field Updates (Before-Save) Record-Triggered Flow for same-record field updates and an Actions and Related Records (After-Save) Record-Triggered Flow to create the child Task and send the email notification.
The correct combination requires choosing the right Record-Triggered Flow execution optimization. Fast Field Updates (Before-Save) flows are explicitly designed for updating fields on the triggering record without incurring additional database write operations. Actions and Related Records (After-Save) flows run after the primary record save, providing access to system fields like CreatedDate/Id and granting capability to create related objects (such as Task) and execute external actions (such as Email Alerts).

Step-by-Step Solution

1
Analyze requirement 1 (same-record field updates prior to database commit).
Identify that Fast Field Updates (Before-Save Record-Triggered Flow) are designed for updating fields on the triggering record before it is saved, offering up to 10x performance gains.
Before-save flows run before validation rules and database save operations, avoiding unnecessary recursion.
2
Analyze requirement 2 (creating a child Task record and sending an email notification).
Identify that Actions and Related Records (After-Save Record-Triggered Flow) must be used when creating records on other objects or performing external side effects.
The triggering record must have a system-assigned ID and exist in the database before related child records can link to it or actions can reference it.
3
Evaluate alternative declarative options for validity and limitations.
Reject creating related records in a before-save flow and reject roll-up summary fields over lookup relationships.
Before-save flows lack DML support for creating non-triggering records, and native roll-up summary fields require master-detail relationships.

Key Concept

Selecting between Before-Save (Fast Field Updates) and After-Save (Actions and Related Records) Record-Triggered Flows based on trigger execution timing and record modification context.
Question 164Question

An administrator at a global logistics firm is configuring Einstein Activity Capture (EAC) for different user groups using Microsoft Exchange and Google Workspace. Match each business synchronization requirement to its corresponding EAC configuration setting.

Click a left item, then click its matching right item

Items

Capture email and event interactions for timeline visibility while storing data off-platform in AWS rather than generating standard Salesforce Task/Event database records.
Allow event updates made in Google Calendar to update Salesforce records, but prevent events created in Salesforce from syncing to Google Calendar.
Ensure contacts updated in Salesforce automatically update Microsoft Outlook contacts and vice versa.
Prevent specific sensitive communications with external vendor domains from being captured and logged on record activity timelines.

Matches

Show answer & explanation

Answer

The business sync requirements match the EAC configurations as follows: 1) Activity capture off-platform storage matches Einstein Activity Capture default activity storage model; 2) One-way event sync from Google to Salesforce matches Event Sync Direction configured to Google to Salesforce; 3) Bi-directional contact sync matches Contact Sync Direction configured to Both Ways; 4) Filtering sensitive vendor communications matches Excluded Addresses list configured with domain filters.
Each business requirement directly corresponds to a specific EAC configuration setting: storing activity data off-platform on AWS corresponds to the default EAC activity storage model; unidirectional sync from external calendars maps to the 'Google to Salesforce' direction; bi-directional contact management requires setting contact sync to 'Both Ways'; and preventing tracking of sensitive domains requires entries in the Excluded Addresses configuration list.

Step-by-Step Solution

1
Analyze requirement 1 regarding activity logging behavior and storage location.
Identify that EAC stores email and event activity data off-platform in secure AWS cloud infrastructure to render items on record timelines, avoiding standard Salesforce Task/Event record creation.
This off-platform architecture is the core design distinction between Einstein Activity Capture and standard activity management.
2
Evaluate requirement 2 regarding external calendar event flow into Salesforce.
Match the one-way inbound calendar sync requirement to the 'Google to Salesforce' Event Sync Direction setting.
Sync direction configurations explicitly control whether calendar data flows unidirectionally or bidirectionally.
3
Evaluate requirement 3 for maintaining identical contact lists across Outlook and Salesforce.
Select 'Both Ways' Contact Sync Direction.
Bi-directional contact synchronization ensures edits in either system propagate to the connected application.
4
Evaluate requirement 4 for restricting sensitive email and event tracking for vendor domains.
Associate domain privacy filtering with the Excluded Addresses feature.
The Excluded Addresses setting prevents EAC from syncing or capturing activity linked to specific internal or external domains.

Key Concept

Einstein Activity Capture Configurations and Synchronization Settings
Question 165Question

A Salesforce Administrator at a financial services firm is building a multi-tier Custom Report Type linking Accounts (Primary), Financial Accounts (Child), and Investment Transactions (Grandchild) to support wealth management analytics. During the configuration of the report type layout and object relationships, which two statements correctly describe the behavior and administration of Custom Report Types? (Select 2 options)

Select all that apply

Show answer & explanation

Answer: Fields from objects up to four levels away via lookup relationships can be added directly to the report layout section without adding those objects as main entity nodes in the object hierarchy.; Custom fields created on the Financial Account object after the Custom Report Type has been deployed are not automatically included in the report layout and must be added manually.

Answer

The two correct statements are that fields from objects up to four levels away via lookup relationships can be added directly to the report layout section without adding those objects as main entity nodes, and custom fields created on an object after the Custom Report Type has been deployed are not automatically included in the report layout.
Custom Report Types allow administrators to pull fields from related lookup objects up to 4 levels away via the 'Add fields related via lookup' button on the field layout editor. Furthermore, when new custom fields are created on an object after a Custom Report Type has been created, Salesforce does not automatically append those fields to the CRT layout; they must be added manually.

Step-by-Step Solution

1
Analyze Custom Report Type lookup field capabilities
Confirm that the 'Add fields related via lookup' feature permits referencing fields up to 4 relationship levels away without expanding the core object structure.
This enables administrative flexibility when reporting on referenced lookup data like Owner or Parent Account fields.
2
Evaluate field lifecycle management in existing Custom Report Types
Identify that newly added custom fields on an object are omitted from existing Custom Report Type layouts by default.
Administrators must edit the Custom Report Type layout to explicitly add new fields to report sections for user access.
3
Verify Deployment Status permissions and distractor claims
Disprove distractor options regarding formula conversions, lookup roll-up summary creation, and 'In Development' visibility.
'In Development' hides the report type from non-admin end users, roll-ups require master-detail relationships, and row-level formulas operate independently of record join logic.

Key Concept

Custom Report Type Layout Customization & Field Inheritance Rules
Estimated Time:2m 30s
Question 166Question

An administrator is configuring Einstein Activity Capture (EAC) for a team of sales executives who use Microsoft Exchange Online. The sales manager requires that emails and events sync bidirectionally between Exchange and Salesforce, and that users are properly authorized to use EAC features. Which two steps must the administrator take to fulfill these requirements? (Select two.)

Select all that apply

Show answer & explanation

Answer: Assign the Standard Einstein Activity Capture permission set to the sales executives.; Configure the sync direction settings within the EAC configuration to Sync Both Ways for emails and events.

Answer

Assign the Standard Einstein Activity Capture permission set to the sales executives, and configure the sync direction settings within the EAC configuration to Sync Both Ways for emails and events.
To properly set up Einstein Activity Capture, an administrator must assign the appropriate EAC permission set to grant feature access and configure the synchronization direction to 'Sync Both Ways' for emails and events to maintain bidirectional data alignment.

Step-by-Step Solution

1
Determine authorization requirements for EAC access
Identify that user access must be granted using permission sets such as Standard Einstein Activity Capture.
Salesforce mandates permission set assignments to grant individual users access to EAC licenses and settings.
2
Set up synchronization parameters
Set the email and event sync direction to Sync Both Ways in the active EAC configuration.
This fulfills the explicit requirement for bidirectional synchronization between Microsoft Exchange Online and Salesforce.

Key Concept

Einstein Activity Capture Configuration and Permission Set Provisioning
Estimated Time:2m 0s
Question 167Question

An administrator needs to create a single sales dashboard that automatically filters and displays data according to the logged-in user's individual record access permissions. Which setting should the administrator configure for the dashboard?

Show answer & explanation

Answer: Set the dashboard running user option to "Run as the viewing user".

Answer

Set the dashboard running user option to "Run as the viewing user".
Configuring a dashboard to "Run as the viewing user" creates a dynamic dashboard. In a dynamic dashboard, data is displayed according to the security access settings of the logged-in user who opens the dashboard.

Step-by-Step Solution

1
Identify the requirement
The requirement asks for a single dashboard that dynamically restricts shown data to each individual viewer's record access level.
Different users viewing the same dashboard should see metrics derived only from records they have permission to access.
2
Select the correct Dashboard Running User setting
Configuring the dashboard as a dynamic dashboard by setting the running user to "Run as the viewing user" enforces individual record security context.
Dynamic dashboards adjust data display dynamically based on the permissions of the logged-in user viewing the dashboard.

Key Concept

Dynamic Dashboards and Viewers' Security Context
Question 168Question

A company's customer support manager requests that a specific group of five Tier 2 support representatives be granted permission to create and edit custom Lightning email templates directly within the Salesforce Integration with Gmail. The administrator must implement this access for only these five users without modifying the access permissions of other support representatives who share the same base profile. Which configuration approach should the administrator use?

Show answer & explanation

Answer: Create a dedicated permission set containing the necessary email template permissions and assign it specifically to the five Tier 2 representatives.

Answer

Create a dedicated permission set containing the necessary email template permissions and assign it specifically to the five Tier 2 representatives.
Permission sets are designed specifically to grant additive permissions to select users without altering their underlying profile or affecting other users assigned to the same profile. This matches Salesforce security best practices for enabling specific email integration and template capabilities for a targeted subset of team members.

Step-by-Step Solution

1
Analyze the access requirement
Identified that extra capabilities must be granted to a subset of users sharing a common profile.
Profiles define baseline permissions for entire user groups, whereas sub-group extensions require additive permission mechanisms.
2
Evaluate Salesforce security best practices for additive access
Permission sets are the recommended mechanism to grant specific permissions to targeted individuals.
Creating a permission set prevents profile proliferation and keeps user management scalable.
3
Select the correct administrative action
Build a permission set with Lightning Email Template privileges and assign it to the five Tier 2 representatives.
This grants the required email integration and template capabilities strictly to the intended users.

Key Concept

Using Permission Sets for Additive Feature Access in Email Integrations
Question 169Question

An organization uses a custom object named Partner Deal Registration to track deal submissions from channel partners. When a Partner Deal Registration record is updated to a status of 'Submitted', a Salesforce Administrator needs to evaluate the submitted estimated revenue and automatically update a field named Priority Tier on the same triggering record before it is committed to the database. The solution must provide optimal system performance and adhere to Salesforce automation best practices. Which automation tool and configuration should the administrator select?

Show answer & explanation

Answer: A Record-Triggered Flow configured for Fast Field Updates (Before-Save).

Answer

A Record-Triggered Flow configured for Fast Field Updates (Before-Save).
Configuring a Record-Triggered Flow for Fast Field Updates (Before-Save) is the optimal choice for same-record updates. Because it fires before the record is saved to the database, Salesforce updates the fields directly on the triggering record without executing an additional DML update command or re-entering the order of execution.

Step-by-Step Solution

1
Analyze the automation requirement
The requirement specifies updating fields on the same record that triggered the automation prior to database commit.
Determining whether updates occur on the same record or related records dictates the trigger timing.
2
Evaluate execution timing for same-record updates
Before-save flows (Fast Field Updates) modify the record values directly in memory before saving to the database.
Before-save execution avoids additional DML operations, validation re-runs, and extra save cycles.
3
Select the appropriate declarative tool based on current Salesforce standards
Record-Triggered Flow with Fast Field Updates provides the fastest, recommended solution.
Salesforce designates Flow Builder as the primary declarative automation tool, deprecating legacy Workflow Rules.

Key Concept

Automation Tool Selection - Fast Field Updates (Before-Save Flow)
Question 170Question

OmniTech Robotics recently introduced two distinct business divisions: Enterprise Hardware and Managed Services. The Managed Services team follows a specialized sales lifecycle requiring a different sequence of Opportunity stages and win probabilities than the Enterprise Hardware team. Which two administrative steps must the Salesforce administrator take to configure the system for these division-specific lifecycle requirements? (Select 2)

Select all that apply

Show answer & explanation

Answer: Create a unique Sales Process for each division and select the appropriate Opportunity Stage picklist values for each process.; Create separate Opportunity Record Types for Enterprise Hardware and Managed Services, associating each Record Type with its corresponding Sales Process.

Answer

The administrator must create a distinct Sales Process for each business division to define available Opportunity stages, and then create corresponding Opportunity Record Types linked to each Sales Process.
To support different opportunity lifecycles on the Opportunity object, an administrator must create a Sales Process for each lifecycle to define the available stage values, and then create Opportunity Record Types linked to those Sales Processes so users can select the correct record type upon opportunity creation.

Step-by-Step Solution

1
Create Sales Processes
Two distinct Sales Processes are created, each containing the appropriate subset of Opportunity stage picklist values and probabilities for Enterprise Hardware and Managed Services.
Opportunity stage picklist values are governed by Sales Processes rather than standard picklist field editing.
2
Create Record Types and link to Sales Processes
Opportunity Record Types for Enterprise Hardware and Managed Services are created and each is assigned its respective Sales Process.
Record Types assign the Sales Process to users and control page layouts, picklists, and record creation workflows.

Key Concept

Sales Processes and Opportunity Stage Picklist Control via Record Types
Question 171Question

A Salesforce administrator is configuring the native Data Export Service in Setup to schedule routine data backups for compliance purposes. The organization requires inclusion of Chatter files and document attachments along with standard object records. Which behavior should the administrator expect regarding the execution and availability of these scheduled export files?

Show answer & explanation

Answer: The service generates downloadable zip files containing selected data and attachments, which remain available for download for 48 hours before being deleted.

Answer

The Data Export Service generates downloadable zip files containing record data and included attachments, which are available for download in Setup for 48 hours before being purged.
The Data Export Service in Salesforce Setup allows administrators to schedule weekly or monthly data backups, including CRM record data, Chatter files, and document attachments. Once processed, Salesforce sends an email notification with a link to download the zip archives, which remain available for download for 48 hours before being automatically removed.

Step-by-Step Solution

1
Identify the primary capabilities of the native Data Export Service.
The service supports automated weekly or monthly exports of standard/custom object data as well as Chatter images, documents, and attachments.
Administrators must select the appropriate native tool according to content scope requirements.
2
Evaluate file delivery and retention policies for exported data.
Salesforce generates compressed zip files accessible via a link in Setup and deletes these zip files after a 48-hour download window.
Temporary storage limits enforce a strict 48-hour retention window for generated export archives.

Key Concept

Data Export Service retention window and file inclusions
Question 172Question

A support manager at an industrial IoT equipment company requires newly created Web-to-Case submissions to be automatically routed to specific technical support queues based on the Product Category field. Additionally, if a High Priority case assigned to any queue remains unresolved for more than 4 hours, the system must automatically reassign the case to an Executive Escalation queue and send an email notification to the Director of Support. Which pair of features should the administrator configure to meet these requirements?

Show answer & explanation

Answer: Use a Case Assignment Rule to route incoming cases to regional queues upon creation, and a Case Escalation Rule with a 4-hour rule entry action to reassign the case and send the email notification.

Answer

Configure a Case Assignment Rule for initial routing to support queues upon case creation, and a Case Escalation Rule to automatically reassign cases and notify management after 4 hours of remaining unresolved.
Case Assignment Rules are designed to assign incoming cases to users or queues based on field criteria at the time of creation. Case Escalation Rules continuously monitor open cases and execute escalation actions—such as transferring ownership to an escalation queue and sending notification emails—when specified time limits (e.g., 4 hours) are exceeded.

Step-by-Step Solution

1
Identify initial case routing requirement
Determine that assigning new cases to queues based on record fields (Product Category) requires Case Assignment Rules.
Case Assignment Rules evaluate criteria when a case is generated to set initial owner or queue.
2
Identify time-based escalation and reassignment requirement
Determine that reassigning cases and sending notifications based on open duration (4 hours) requires Case Escalation Rules.
Case Escalation Rules evaluate open case age against SLA criteria and execute actions such as ownership transfer and email notification when thresholds are crossed.

Key Concept

Distinction between Case Assignment Rules (initial owner/queue routing) and Case Escalation Rules (time-based re-routing and notification based on case age)
Question 173Question

Match each Salesforce formula function commonly used in validation rules to its primary data quality enforcement function.

Click a left item, then click its matching right item

Items

ISBLANK(expression)
ISCHANGED(field)
PRIORVALUE(field)
REGEX(text, regex_text)

Matches

Show answer & explanation

Answer

ISBLANK(expression) matches with evaluating if an expression lacks a value; ISCHANGED(field) matches with checking if a field value was updated during the current transaction; PRIORVALUE(field) matches with returning the previous value of a field prior to saving; REGEX(text, regex_text) matches with checking if a text field matches a specified pattern.
Each validation rule function serves a unique purpose: ISBLANK verifies that required data is present, ISCHANGED detects modification during record updates, PRIORVALUE inspects pre-save field values, and REGEX verifies string formatting compliance.

Step-by-Step Solution

1
Identify the primary function of ISBLANK
ISBLANK checks for missing or empty field values.
It returns TRUE when an expression or field is blank.
2
Identify the primary function of ISCHANGED
ISCHANGED checks if a record field value was altered during edit.
It evaluates whether the value currently being saved differs from the record's existing stored value.
3
Identify the primary function of PRIORVALUE
PRIORVALUE retrieves the original field value.
It references the value of a field immediately before the current save transaction.
4
Identify the primary function of REGEX
REGEX compares text to a specified regular expression pattern.
It validates whether the string structure matches required syntax rules such as postal codes or phone numbers.

Key Concept

Salesforce Validation Rule Formula Functions
Question 174Question

A company offers warranty support agreements linked to specific customer hardware assets. The support team must track resolution time limits using Milestones, ensuring countdowns pause during non-working hours specified in customer contracts. Which TWO configurations are required to meet this requirement? Choose 2 answers.

Select all that apply

Show answer & explanation

Answer: Assign specific Business Hours to the Entitlement or Milestone criteria to control the countdown timer calculation.; Associate the Entitlement record with the customer's Account and Asset, and assign an active Entitlement Process to it.

Answer

Assign specific Business Hours to the Entitlement or Milestone criteria, and associate the Entitlement record with the customer's Account and Asset with an active Entitlement Process.
Assigning Business Hours to the Entitlement or Milestone ensures that target completion times pause outside of defined operating hours. Additionally, associating an active Entitlement Process with an Entitlement record linked to the customer's Account and Asset ensures that cases logged against that asset automatically apply the correct SLA milestones.

Step-by-Step Solution

1
Define working hours schedule for SLAs
Milestone countdown timers pause outside specified business hours
Business Hours settings govern time tracking for milestones so non-working hours are excluded.
2
Link Entitlement record to Account and Asset and attach Entitlement Process
Cases created for the Asset automatically inherit the Entitlement and Milestone tracking
Entitlement Processes apply SLA milestones to cases based on the entitlement associated with the case's asset and account.

Key Concept

Entitlement Management, Business Hours, and Milestone tracking in Salesforce Service Cloud
Question 175Question

A Salesforce Administrator is configuring record access and interface settings for a custom object. Match each administrative requirement on the left with the exact Salesforce configuration setting or location on the right.

Click a left item, then click its matching right item

Items

Determine which page layout is displayed to a specific user profile when viewing a record of a given record type
Filter the subset of selectable values in a custom picklist field for a specific record type
Define the record type automatically selected when a user creates a new record from their profile settings
Grant access to a newly created record type to specific users without altering their assigned profile

Matches

Show answer & explanation

Answer

The administrative requirements match as follows: Page layout display per profile and record type matches Page Layout Assignment matrix; Picklist value filtering per record type matches Picklist Values Available for Editing on the Record Type detail page; Default record type upon record creation matches Default Record Type in Profile/User Settings; Granting record type access without modifying profile matches Record Type Settings in a Permission Set.
Each requirement directly corresponds to its respective administrative interface in Salesforce. Page layout assignment uses the profile-to-record-type matrix; picklist customization is configured on the record type detail page; default record types are set in profile/user settings; and permission sets allow granting record type access flexibly.

Step-by-Step Solution

1
Analyze page layout assignment mechanisms.
Confirm that layout visibility depends on both the user's Profile and the Record Type of the record, configured via the Page Layout Assignment matrix.
Salesforce uses a matrix mapping Profiles and Record Types to determine which Page Layout to render.
2
Evaluate picklist customization per record type.
Identify that editing available picklist values is managed on the Record Type configuration detail page.
Record Types allow admins to show different picklist values for different business processes on the same object.
3
Review user default record type assignment and non-profile record type access expansion.
Link profile default settings to auto-selection during creation, and Permission Sets to extending record type availability.
Permission Sets provide flexible record type access without altering user profiles.

Key Concept

Page Layouts and Record Types Assignment Matrix & Permission Settings
Estimated Time:1m 30s
Question 176Question

An administrator needs to configure a Custom Report Type to support tracking customer subscription renewals. The report type must join Accounts as the primary object (Object A), Contracts as the secondary object (Object B), and Subscriptions as the tertiary object (Object C). Management requires the report to include all Accounts regardless of whether they have related Contracts, while Contracts should only appear if they have at least one related Subscription. Furthermore, report creators must be able to add the Account Owner's Manager's Name to reports without creating custom formula fields on the Account object. Which TWO configuration steps must the administrator complete when defining this Custom Report Type?

Select all that apply

Show answer & explanation

Answer: Set the Object A to Object B relationship to 'Each "A" record may or may not have related "B" records', and the Object B to Object C relationship to 'Each "B" record must have at least one related "C" record'.; Use the 'Add fields related via lookup' option in the Custom Report Type field layout editor to reference and add the Manager field from the User record linked to the Account Owner.

Answer

To satisfy the requirements, the administrator must configure the object relationships so that Accounts may or may not have related Contracts (outer join), while Contracts must have at least one related Subscription (inner join). Additionally, the administrator must use the 'Add fields related via lookup' feature in the Custom Report Type layout editor to add the Account Owner's Manager field.
The correct configuration steps involve setting the object relationship for Contracts to 'with or without' related records so that Accounts without Contracts are retained in report results, while setting Subscriptions to 'with' related records so that only Contracts possessing Subscriptions appear. Furthermore, utilizing the 'Add fields related via lookup' tool within the Custom Report Type layout interface enables fields up to 4 relationship levels away (such as the Account Owner's Manager) to be included directly in reports.

Step-by-Step Solution

1
Define Object Relationships
Configured Accounts (A) to Contracts (B) as 'with or without' (outer join), and Contracts (B) to Subscriptions (C) as 'with' (inner join).
Ensures all Accounts are listed regardless of Contract records, but only Contracts with at least one Subscription record are evaluated.
2
Customize Report Layout Fields
Accessed 'Edit Layout' on the Custom Report Type, clicked 'Add fields related via lookup', navigated from Account Owner to User Manager, and added the field to the layout.
Allows report builders to pull lookup fields up to 4 levels away directly onto reports without needing custom schema formula fields.

Key Concept

Custom Report Type Object Relationships and Field Layout Editing
Question 177Question

A Salesforce administrator at a global logistics company is selecting data administration tools for four distinct enterprise data tasks. Match each operational data requirement to the most appropriate Salesforce tool or tool configuration.

Click a left item, then click its matching right item

Items

Importing 35,000 Lead records from a logistics summit while executing active Lead Assignment Rules and applying duplicate matching rules.
Upserting 95,000 Opportunity records from an external ERP system using a custom External ID field to map parent Account relationships.
Permanently purging 18,000 obsolete custom compliance logs (`Audit_Log__c`) directly from the database to bypass the Recycle Bin.
Automating an unattended, scheduled nightly export of 250,000 Case records using scriptable execution.

Matches

Show answer & explanation

Answer

The 35,000 Lead import with assignment rules matches Data Import Wizard; the 95,000 Opportunity upsert matches Data Loader (Desktop GUI); the permanent compliance log purge matches Data Loader (Bulk API with Hard Delete); and the automated nightly export matches Data Loader Command Line Interface (CLI).
Each requirement aligns directly with specific utility capabilities: Data Import Wizard processes under 50,000 Leads while firing assignment rules; Data Loader Desktop GUI handles unsupported objects like Opportunities over 50,000 records; Data Loader with Bulk API enables hard delete; and Data Loader CLI supports script automation for scheduled tasks.

Step-by-Step Solution

1
Evaluate the Lead import scenario (35,000 records, Lead Assignment Rules, duplicate detection).
Data Import Wizard supports up to 50,000 records, handles standard Lead records, triggers Lead Assignment Rules, and applies duplicate checking.
Data Import Wizard satisfies all constraints for this scenario.
2
Evaluate the Opportunity upsert scenario (95,000 records, External ID matching).
Data Import Wizard does not support the Opportunity object and is capped at 50,000 records. Data Loader supports Opportunities and up to 5,000,000 records.
Data Loader (Desktop GUI) must be used due to object restrictions and volume size.
3
Evaluate the custom log purge scenario (18,000 records, bypass Recycle Bin).
Hard delete functionality requires Bulk API enablement in Data Loader settings.
Data Import Wizard only performs soft deletions to the Recycle Bin.
4
Evaluate the automated export scenario (250,000 Case records, script-driven schedule).
Automated headless execution via command-line scripts requires Data Loader CLI.
Interactive GUI tools cannot run scheduled unattended scripts natively.

Key Concept

Selecting between Data Import Wizard and Data Loader utilities based on object support, volume limits, operational requirements (hard delete, workflow triggers), and automation capabilities.
Question 178Question

An administrator at Cloudburst Security is setting up Lightning Sales Console productivity tools for inside sales representatives. The administrator creates a Macro designed to automatically update the Opportunity Stage field and log a task in a single click. When sales reps run the Macro on certain records, an error occurs stating that the selected stage value cannot be applied to the record type. Which action should the administrator take to ensure the Macro executes successfully?

Show answer & explanation

Answer: Verify that the target stage value is included in the Sales Process assigned to the Opportunity record type.

Answer

Verify that the target stage value is included in the Sales Process assigned to the Opportunity record type.
In Salesforce, Opportunity Stage picklist values are governed by Sales Processes. When a macro attempts to set an opportunity stage, the value must be part of the active Sales Process assigned to that record's record type; otherwise, validation fails.

Step-by-Step Solution

1
Identify why the macro failed on the record type.
The stage value specified in the macro is not valid for the record type's active stage picklist values.
Macros respect object security, record type rules, and available picklist values.
2
Review the Opportunity record type configuration.
Confirm which Sales Process is mapped to the target Opportunity record type.
Opportunity stage picklists are driven by Sales Processes associated with record types.
3
Update the Sales Process to include the missing stage value.
The stage becomes selectable for that record type, allowing the macro to update the field successfully.
Including the stage value in the Sales Process makes it available to both UI interactions and Macro execution.

Key Concept

Sales Console Macros & Sales Process Stage Picklist Governance
Question 179Question

A Salesforce Administrator needs to complete two separate data management operations for an enterprise application:
1. Import 7500075{}000 Opportunity records into the system.
2. Hard delete (permanently remove without placing in the Recycle Bin) 1200012{}000 obsolete custom object records.

Which two administrative utilities or configurations must the administrator select to execute these tasks? (Choose 2 options.)

Select all that apply

Show answer & explanation

Answer: Data Loader to import the Opportunity records, as Opportunities are not supported by the Data Import Wizard and the volume exceeds 50,000 records.; Data Loader to perform a Hard Delete operation on the custom object records.

Answer

The administrator must select Data Loader to import the Opportunity records (due to object limitations and the 50,000 record cap of the Data Import Wizard) and Data Loader to execute the Hard Delete operation (to bypass the Recycle Bin).
Data Loader is the appropriate tool for both operations. First, the Data Import Wizard is limited to 50,000 records and does not support importing Opportunity records. Data Loader can handle up to 5,000,000 records and supports all standard and custom objects. Second, hard deleting records to permanently bypass the Recycle Bin is a feature unique to Data Loader (when Bulk API is enabled), whereas Data Import Wizard cannot perform hard deletes.

Step-by-Step Solution

1
Evaluate the import task constraints: importing 7500075{}000 Opportunity records.
Identify that Data Import Wizard only supports up to 5000050{}000 records and does not support the Opportunity object. Therefore, Data Loader must be used.
Data Import Wizard is limited to standard objects like Accounts, Contacts, Leads, Solutions, and custom objects, up to 50,000 records.
2
Evaluate the deletion task constraints: permanently deleting 1200012{}000 custom object records without sending them to the Recycle Bin.
Identify that hard deleting records to bypass the Recycle Bin requires Data Loader with Bulk API enabled.
Data Import Wizard lacks hard delete functionality.

Key Concept

Tool selection criteria based on record volume limits, supported standard objects, and operational capabilities like hard deletion.
Estimated Time:1m 30s
Question 180Question

A Sales Operations Administrator at a commercial real estate firm needs to enable real estate brokers to quickly create a related 'Property Lease' record directly from an active 'Building' custom object record page. When creating the lease, the system must automatically populate the 'Lease Status' field as 'Draft' and copy the 'City' value from the parent Building record, while allowing brokers to modify other lease details before saving. Which configuration should the administrator use to satisfy this requirement in Lightning Experience?

Show answer & explanation

Answer: Create an Object-Specific Quick Action on the Building object that creates a Property Lease record, configure Predefined Field Values for Lease Status and City, and add the action to the Building Lightning page layout.

Answer

Create an Object-Specific Quick Action on the Building object that creates a Property Lease record, configure Predefined Field Values for Lease Status and City, and add the action to the Building Lightning page layout.
Object-Specific Quick Actions are designed specifically for creating child or related records directly from a parent record context. They allow administrators to define default values through Predefined Field Values using static values (such as 'Draft') or formulas that pull data directly from the parent record (such as copying the Building's City).

Step-by-Step Solution

1
Identify the required record context and creation requirements.
Creating a related Property Lease record directly from a parent Building record requires access to parent record field values.
Object-Specific Quick Actions run in the context of the source object, enabling access to the parent record's fields.
2
Configure predefined default values for the target object fields.
Set 'Lease Status' to 'Draft' and set 'City' using a formula referencing Building__c.City__c.
Predefined Field Values automatically populate fields on the action layout when the user clicks the quick action.
3
Expose the quick action to users.
Add the newly created Quick Action to the Salesforce Mobile and Lightning Experience Actions section of the Building Page Layout.
Quick actions must be assigned to the relevant page layout to be visible on record pages in Lightning Experience.

Key Concept

Object-Specific Quick Actions and Predefined Field Values
PreviousPage 9 / 90Next
All practice questions — Salesforce Certified Administrator | Examkin