All practice questions

1784 questions

Question 1401Question

An analytics manager needs to display closed-won deal totals grouped simultaneously by Sales Region along the rows and by Fiscal Quarter along the columns to summarize performance across two distinct axes in a single grid view. Which report format must be selected to fulfill this requirement?

Show answer & explanation

Answer: Matrix Report

Answer

The Matrix Report format should be chosen because it enables grouping records by both rows and columns simultaneously.
A Matrix report allows administrators to aggregate data across both rows and columns simultaneously, producing a two-dimensional grid format ideal for analyzing metrics like revenue by region and fiscal quarter.

Step-by-Step Solution

1
Analyze the reporting requirement
Identified the requirement to group data across two independent dimensions (rows by Sales Region and columns by Fiscal Quarter).
Understanding the required dimensions determines the necessary report structure.
2
Evaluate available Salesforce report formats
Tabular provides no groupings; Summary provides row groupings only; Matrix provides row and column groupings; Joined combines multiple report blocks.
Comparing capabilities against business needs narrows down the proper report format.
3
Select the matching report format
Matrix Report fulfills the exact double-grouping grid criteria.
Only Matrix reports support simultaneous row and column summaries.

Key Concept

Report Formats and Grouping Capabilities
Estimated Time:1m 0s
Question 1402Question

A company's sales operations team requires automatic synchronization of Microsoft Outlook calendar events to Salesforce for all regional account managers. To comply with strict corporate governance, calendar events created or updated in Salesforce must NOT sync back to Outlook, and access must be granted only to designated users without altering their base user profiles. Which administrative setup satisfies these requirements?

Show answer & explanation

Answer: Assign the Standard Einstein Activity Capture permission set to the regional account managers and set the event sync direction to Exchange to Salesforce within an Einstein Activity Capture configuration.

Answer

Assign the Standard Einstein Activity Capture permission set to the regional account managers and set the event sync direction to Exchange to Salesforce within an Einstein Activity Capture configuration.
To satisfy both requirements, the administrator must assign the Standard Einstein Activity Capture permission set to specific users, maintaining clean profile administration. Furthermore, setting the event sync direction to Exchange to Salesforce ensures that events automatically move from Outlook to Salesforce while preventing any back-syncing from Salesforce to Outlook.

Step-by-Step Solution

1
Determine the permission assignment strategy.
Use the Standard Einstein Activity Capture permission set to grant access selectively without creating or modifying user profiles.
Salesforce best practice requires using permission sets rather than profiles for additive user capabilities.
2
Select the correct sync direction for events.
Configure the event synchronization direction as Exchange to Salesforce.
This configuration allows events created in Outlook to flow into Salesforce while ensuring Salesforce events are not pushed back to Outlook.

Key Concept

Einstein Activity Capture Sync Directions and Permission Set Provisioning
Question 1403Question

A company uses Web-to-Case to capture service inquiries submitted through its public website. Which two actions occur when Web-to-Case processing limits are exceeded or when a web submission fails custom validation rules? (Select 2)

Select all that apply

Show answer & explanation

Answer: Submissions exceeding the daily request limit are sent as email notifications containing the case data to the Default Case Owner.; Submissions that fail custom validation rules generate an email containing error details and form values sent to the Default Case Owner.

Answer

Submissions exceeding the daily request limit are sent as email notifications containing the case data to the Default Case Owner, and submissions that fail custom validation rules generate an email containing error details and form values sent to the Default Case Owner.
When Web-to-Case reaches its daily organization limit or when a submitted payload fails validation rules during record creation, Salesforce sends an email containing the submitted values (and any error messages) to the designated Default Case Owner rather than creating a Case record or returning errors to the end user.

Step-by-Step Solution

1
Analyze Web-to-Case limit overflow handling.
Salesforce sends the submitted case details directly to the Default Case Owner via email when daily request limits are exceeded.
This guarantees that customer inquiry data is not lost during high-volume traffic spikes.
2
Analyze Web-to-Case custom validation failure handling.
Salesforce emails the form data and error logs to the Default Case Owner without creating the record or displaying error messages to the website visitor.
Because Web-to-Case generates HTML forms for external websites, backend validation errors cannot be safely rendered to end users and are delegated to the administrator/owner for manual resolution.

Key Concept

Web-to-Case limit overflow and validation error fallback mechanisms via the Default Case Owner.
Question 1404Question

A Salesforce administrator at a consulting firm needs to enforce data quality on the Lead object. The business requirement states that whenever a lead's Lead Source picklist is set to "Web", the Email field must be populated before the record can be saved or converted. Which configuration or formula should the administrator implement to meet this requirement?

Show answer & explanation

Answer: Create a validation rule on the Lead object with the formula: AND( ISPICKVAL(LeadSource, "Web"), ISBLANK(Email) )

Answer

Create a validation rule on the Lead object with the formula: AND( ISPICKVAL(LeadSource, "Web"), ISBLANK(Email) )
The correct choice utilizes the validation rule formula AND( ISPICKVAL(LeadSource, "Web"), ISBLANK(Email) ). In Salesforce validation rules, formulas return true when data is invalid. Using ISPICKVAL evaluates picklist values correctly, and ISBLANK verifies whether the email field has been left unpopulated.

Step-by-Step Solution

1
Identify the criteria required for validation
Validation must trigger when LeadSource is set to "Web" AND Email is blank.
Validation rules evaluate to TRUE when data is invalid to display an error message.
2
Select appropriate Salesforce formula functions for picklist and null evaluation
Use ISPICKVAL(LeadSource, "Web") for the picklist field and ISBLANK(Email) for the text field.
Picklist fields in validation rules require ISPICKVAL() or TEXT() functions, and ISBLANK() accurately detects missing values across text and email field types.
3
Combine conditions using the AND function
Formulate AND( ISPICKVAL(LeadSource, "Web"), ISBLANK(Email) ).
The rule must fire only when both conditions occur simultaneously.

Key Concept

Validation Rules and Data Quality Enforcement
Question 1405Question

A Salesforce administrator is tasked with setting up an automated process to update a custom field on a Contact record immediately before the record is saved to the database. Which flow trigger optimization should the administrator select when configuring the Record-Triggered Flow?

Show answer & explanation

Answer: Fast Field Updates

Answer

The administrator should select Fast Field Updates when configuring the Record-Triggered Flow.
Fast Field Updates (before-save record-triggered flows) execute before the record is saved to the database. This allows field values on the triggering record to be modified seamlessly as part of the initial save operation without requiring additional DML statements.

Step-by-Step Solution

1
Identify the record automation target
The target is the triggering record itself (the Contact record).
The requirement specifies updating a custom field on the Contact record that initiates the trigger.
2
Determine the optimal trigger timing
Select Fast Field Updates (Before-Save).
Before-save flows run prior to database commit, updating the triggering record up to 10 times faster than after-save flows without triggering extra DML operations.

Key Concept

Record-Triggered Flow Optimizations (Before-Save vs After-Save)
Question 1406Question

A Salesforce Administrator is configuring a Custom Report Type to analyze Partner Accounts and their related Asset records for maintenance contract renewals. The business requires report builders to see all Partner Accounts, regardless of whether they currently have associated Asset records. Additionally, administrators need to make specific fields from the Account Owner's User object available by default in the report builder field layout without adding additional object blocks. Which TWO configuration steps should the administrator take to fulfill these requirements?

Select all that apply

Show answer & explanation

Answer: Set the object relationship between Accounts and Assets to "Each 'A' record may or may not have related 'B' records".; Edit the Custom Report Type field layout and select "Add fields related via lookup" to include fields from the Account Owner object.

Answer

The administrator must set the primary and secondary object relationship to 'Each A record may or may not have related B records' to include Accounts without Assets, and use the 'Add fields related via lookup' option within the Custom Report Type layout editor to make Account Owner User fields available to report builders.
Configuring the relationship as 'Each A record may or may not have related B records' performs a left outer join between Accounts and Assets, preserving Accounts that lack Assets. Using 'Add fields related via lookup' in the Custom Report Type field layout allows administrators to traverse lookup relationships up to 4 levels deep (such as Account Owner fields) and add them to the report field palette.

Step-by-Step Solution

1
Determine the required object join condition.
Configure the relationship as 'with or without' (left outer join) between Accounts (Primary) and Assets (Secondary) so Accounts missing Asset records are retained in report results.
Choosing 'with' (inner join) would exclude Accounts that do not currently have related Assets.
2
Configure the report type field layout for lookup traversal.
In the Custom Report Type field layout section, click 'Add fields related via lookup', navigate from Account to Account Owner (User), and select the required fields.
This exposes fields from lookup-related objects directly into the field palette for report creators without needing separate object relationship blocks.

Key Concept

Custom Report Type Object Relationships and Lookup Field Expansion
Question 1407Question

A Salesforce administrator at Nexus Biotech is configuring activity settings to allow medical sales representatives to log interaction events that involve several client stakeholders simultaneously. The administrator enables 'Allow Users to Relate Multiple Contacts to Tasks and Events' (Shared Activities). Which two statements accurately describe the standard system capabilities and record relationship rules when Shared Activities is enabled? (Select 2)

Select all that apply

Show answer & explanation

Answer: A single event or task can be related to up to 50 contacts.; One contact must be designated as the primary contact on the activity record.

Answer

With Shared Activities enabled, a single task or event can be related to up to 50 contacts (or leads), and one contact must be designated as the primary contact.
Enabling Shared Activities allows users to relate up to 50 contacts or leads to a single event or task. Within those related contacts, one must be designated as the primary contact for reporting and record display purposes.

Step-by-Step Solution

1
Analyze the limits of Shared Activities for Contact relationships
Salesforce Shared Activities allows relating up to 50 contacts or leads to a single activity record.
This enables sales representatives to track interactions with multiple stakeholders within one task or event without duplicating records.
2
Identify primary contact designation requirement
Salesforce requires selecting one primary contact among the related contacts.
The primary contact relationship determines default account rollup behavior and main contact association.
3
Evaluate WhatId (Related To) restrictions vs WhoId (Name) capabilities
Shared Activities expands the WhoId relationship (up to 50 contacts), but maintains the single WhatId restriction (one Account, Opportunity, Case, etc.).
Relating a task to multiple Accounts simultaneously is not supported by standard Shared Activities.

Key Concept

Shared Activities limits and behavior (WhoId vs WhatId restrictions)
Question 1408Question

A Salesforce Administrator is tasked with updating the navigation items available within a specific custom Lightning App accessed by field representatives on the Salesforce Mobile App. In what order should the administrator perform the steps in Setup to accomplish this?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence to customize navigation items for a Lightning App in the Salesforce Mobile App is: 1) Navigate to App Manager in Setup, 2) Edit the target Lightning App, 3) Select Navigation Items in App Settings, 4) Add and arrange items from Available Items to Selected Items, and 5) Save the changes.
Customizing the navigation experience for a custom Lightning App on the Salesforce Mobile App requires navigating to Setup > App Manager, editing the relevant Lightning App, modifying the Navigation Items settings by choosing and ordering items from Available to Selected, and saving the settings.

Step-by-Step Solution

1
Access App Manager in Setup
Displays the list of all standard and custom apps configured in the organization.
App Manager is the centralized administration tool for managing app navigation and properties.
2
Edit the Lightning App
Opens the App Settings interface for the specified app.
App-specific settings, including navigation tabs and utility bars, are modified within the Lightning App edit mode.
3
Select Navigation Items from App Settings
Opens the item selection pane.
Navigation Items dictates which tabs appear on desktop and mobile containers for users working in this app.
4
Add and reorder items from Available to Selected Items
Sets the precise set and sequence of tabs shown to mobile users.
First items in the selected list become primary navigation items on mobile devices.
5
Save the configuration
Applies changes across desktop and mobile app instances.
Configurations are not live until explicitly saved in the App Settings panel.

Key Concept

Lightning App Navigation Customization for Salesforce Mobile App
Estimated Time:1m 30s
Question 1409Question

A Salesforce administrator is implementing validation rules on custom objects to enforce data quality standards across the organization. Which TWO statements accurately describe the key behavior and configuration rules of Salesforce validation rules? (Select TWO answers)

Select all that apply

Show answer & explanation

Answer: A validation rule formula must evaluate to TRUE in order to display the error message and prevent the record from saving.; The ISBLANK() function should be preferred over ISNULL() in validation formulas because ISBLANK() supports text fields and picklists in addition to numeric fields.

Answer

Validation rules prevent record saving by displaying an error when the formula evaluates to TRUE, and administrators should use ISBLANK() rather than ISNULL() for comprehensive null checking across field types.
Salesforce validation rules halt record creation or editing whenever the rule formula evaluates to TRUE. Additionally, Salesforce standard practice dictates using the ISBLANK() function instead of ISNULL() because ISBLANK() reliably handles text strings and picklist fields in addition to numeric values.

Step-by-Step Solution

1
Analyze how Salesforce validation rules trigger error states.
Confirm that validation formulas must evaluate to TRUE to block record creation or updates and render the user error message.
When a validation rule formula resolves to true, it indicates that an error condition exists.
2
Evaluate recommended formula functions for data quality enforcement.
Identify that ISBLANK() is the modern Salesforce standard for null checking across text, picklist, and numeric fields.
ISNULL() does not properly support text fields, making ISBLANK() the preferred choice.
3
Evaluate common misconceptions regarding Lead conversion and Record Types.
Rule out options asserting automatic bypass during lead conversion or record type picklist filtering.
Validation rules run during lead conversion on target objects, and record type picklist assignments are managed separately.

Key Concept

Validation Rule Logic Evaluation and Best Practices
Estimated Time:1m 30s
Question 1410Question

An administrator is configuring Web-to-Case for a company's customer service portal. During a seasonal product promotion, the volume of web form submissions exceeds the organization's daily Web-to-Case request limit. Which system behavior occurs for the web submissions that exceed this limit?

Show answer & explanation

Answer: The excess case information is emailed directly to the Default Case Owner rather than generating Case records.

Answer

The excess case information is emailed directly to the Default Case Owner rather than generating Case records.
When Web-to-Case daily request limits are exceeded, Salesforce prevents loss of customer inquiries by emailing the form submission details to the Default Case Owner designated in Web-to-Case settings. These overflow inquiries do not create Case records automatically.

Step-by-Step Solution

1
Identify the Case Capture mechanism and limit condition.
Web-to-Case has reached its daily governor limit for form submissions.
Salesforce imposes daily limits on Web-to-Case requests based on organization tier and settings.
2
Determine how Salesforce handles overflow submissions.
Form details are sent via email to the Default Case Owner.
To prevent data loss while respecting daily transaction limits, Salesforce emails the submitted text directly to the designated Default Case Owner email address.

Key Concept

Web-to-Case Daily Request Limits and Overflow Handling
Question 1411Question

A Sales Operations Analyst needs a report displaying all Accounts and their related Support Cases. The report must include Account records even if they do not have any associated Support Cases. Additionally, the report metrics must be grouped simultaneously by Account Industry along the rows and by Case Status along the columns. Which combination of report type configuration and report format meets these requirements?

Show answer & explanation

Answer: Create a Custom Report Type with Accounts as the primary object and Cases as the secondary object defined with 'with or without' related records, then select the Matrix report format.

Answer

Create a Custom Report Type with Accounts as the primary object and Cases as the secondary object defined with 'with or without' related records, then select the Matrix report format.
To display primary records regardless of whether they have related secondary records, a Custom Report Type must be created specifying that 'A' records may or may not have related 'B' records (an outer join). To group data simultaneously along two axes (rows and columns), the Matrix report format is required.

Step-by-Step Solution

1
Determine the required object relationship join type.
An outer join ('with or without' relationship) configured in a Custom Report Type is required to show parent Account records even when no child Case records exist.
Standard report types for parent-child objects enforce an inner join, which excludes parent records that lack child records.
2
Select the appropriate report format based on grouping requirements.
The Matrix format must be chosen to group data across both rows (Account Industry) and columns (Case Status).
Tabular reports do not allow groupings, and Summary reports only allow row-level groupings.

Key Concept

Custom Report Type Object Relationships and Report Formats
Question 1412Question

An administrator is evaluating automation design options for custom Renewal Notice records. Which two considerations correctly describe the capabilities and behavior of Fast Field Updates (Before-Save) record-triggered flows?

Select all that apply

Show answer & explanation

Answer: Field updates on the triggering record occur before the record is saved to the database, reducing overall execution overhead.; Modifications made to the triggering record ($Record) fields are automatically applied without requiring an explicit Update Records element.

Answer

Fast Field Updates (before-save) record-triggered flows execute before database commit to optimize field updates on the triggering record, and changes assigned to the $Record variable are automatically saved without an Update Records element.
Fast Field Updates (Before-Save flows) execute before the triggering record is saved to the database. This timing makes field modifications on the triggering record up to 10 times faster than after-save automations. Additionally, any field assignments made to the $Record global variable are automatically written to the database without needing an explicit Update Records DML element.

Step-by-Step Solution

1
Identify the primary purpose of Fast Field Updates (Before-Save) flows.
Before-save flows are specifically designed to set or modify field values on the triggering record prior to saving it to the database.
This timing avoids extra database updates, trigger re-entry, and recursive workflow execution.
2
Evaluate how data changes are saved in Fast Field Updates.
Field values updated on the global $Record variable are saved automatically when the flow finishes.
An Update Records element is unnecessary and not recommended for same-record updates in before-save flows.
3
Evaluate restrictions on before-save flows compared to after-save flows.
Before-save flows cannot create related records or leverage scheduled paths.
Actions involving related objects, external callouts, or scheduled execution paths require an Actions and Related Records (after-save) flow.

Key Concept

Fast Field Updates vs Actions and Related Records in Record-Triggered Flows
Estimated Time:1m 0s
Question 1413Question

An administrator needs to update the visual identity of the Salesforce Mobile App across the organization to match a recent corporate rebrand. The requirements specify setting a custom Header Background Color and uploading a custom Loading Screen Logo. The administrator is evaluating whether to configure these settings globally or create individual user profiles to assign distinct mobile themes. Which statement correctly describes how Salesforce Mobile App branding is configured and applied?

Show answer & explanation

Answer: Salesforce Mobile App branding settings, including the header background color and loading screen logo, are configured globally under Salesforce Branding in Setup and apply org-wide.

Answer

Salesforce Mobile App branding settings, including the header background color and loading screen logo, are configured globally under Salesforce Branding in Setup and apply org-wide.
In Salesforce, mobile application branding settings—such as the Header Background Color, Loading Screen Background Color, and Loading Screen Logo—are managed under 'Salesforce Branding' (or Salesforce Mobile App Branding) in Setup. These settings establish a unified visual identity and apply globally across the organization to all users accessing the standard Salesforce Mobile App.

Step-by-Step Solution

1
Identify the administrative feature for customizing the mobile app visual appearance.
Determine that Salesforce provides 'Salesforce Branding' within Quick Find in Setup specifically for mobile visual identity.
Branding elements like loading screen logos and primary header colors apply universally to mobile app sessions.
2
Evaluate scope and assignment mechanisms for Mobile Branding.
Confirm that Mobile Branding is an organization-wide setting rather than a profile-based or object-based configuration.
Salesforce Mobile App branding does not rely on User Profiles or Permission Sets for display.

Key Concept

Salesforce Mobile App Branding Configuration
Question 1414Question

Match each Salesforce case capture feature or configuration mechanism with its corresponding technical requirement or operational behavior.

Click a left item, then click its matching right item

Items

Web-to-Case Daily Submission Limit Reached
On-Demand Email-to-Case Service
Email-to-Case Agent Application
Web-to-Case reCAPTCHA Verification

Matches

Show answer & explanation

Answer

Web-to-Case Daily Submission Limit Reached matches with sending excess submission details in an email to the Default Case Owner. On-Demand Email-to-Case Service matches with processing email attachments in the cloud limited to 25 MB. Email-to-Case Agent Application matches with running behind the firewall to support attachments larger than 25 MB. Web-to-Case reCAPTCHA Verification matches with validating user requests inside the browser client before sending data to Salesforce.
Each feature corresponds to its documented Salesforce system behavior: Web-to-Case daily limit overflow forwards submission details via email to the Default Case Owner; On-Demand Email-to-Case processes cloud emails up to 25 MB; Email-to-Case Agent operates behind a firewall to process attachments larger than 25 MB; and reCAPTCHA provides client-side browser validation.

Step-by-Step Solution

1
Analyze Web-to-Case daily limit overflow mechanisms
Identify that submissions over the daily limit trigger email notifications containing the submitted data sent directly to the Default Case Owner.
Salesforce ensures business continuity without dropping form data when daily limits are hit.
2
Compare Email-to-Case deployment models and attachment thresholds
Distinguish On-Demand Email-to-Case (cloud-native, 25 MB maximum) from Email-to-Case Agent (installed behind network firewall, >25 MB capacity).
Infrastructure location directly determines security boundary and attachment size capabilities.
3
Evaluate client-side vs server-side web form validation
Confirm reCAPTCHA executes at the browser layer to block illegitimate traffic prior to server processing.
Client-side execution prevents unverified payload traffic from reaching Salesforce endpoint services.

Key Concept

Salesforce Case Capture Mechanisms (Web-to-Case vs Email-to-Case Architecture and Limits)
Estimated Time:1m 30s
Question 1415Question

A Operations Manager at a solar installation enterprise requires that whenever a custom object record named Work_Order__c has its Status__c picklist field set to "Closed", both the Completion_Date__c date field and the Resolution_Summary__c text field must contain data. If either field is missing a value when the status is Closed, the record must fail validation and present an error message to the user. Which formula should be configured in the validation rule to enforce this data quality standard?

Show answer & explanation

Answer: AND(ISPICKVAL(Status__c, "Closed"), OR(ISBLANK(Completion_Date__c), ISBLANK(Resolution_Summary__c)))

Answer

The validation rule formula using AND(ISPICKVAL(Status__c, "Closed"), OR(ISBLANK(Completion_Date__c), ISBLANK(Resolution_Summary__c))) correctly enforces the requirement.
The correct formula uses ISPICKVAL to evaluate the picklist field Status__c and checks if either Completion_Date__c or Resolution_Summary__c is blank using OR(ISBLANK(...), ISBLANK(...)). Combining these within an AND statement ensures the validation rule evaluates to true—and blocks record saving—only when the status is Closed and one or both mandatory fields lack values.

Step-by-Step Solution

1
Identify the condition when the validation error should trigger.
The rule must trigger when Status__c is set to "Closed". In Salesforce formula syntax, picklist values are checked using ISPICKVAL(Status__c, "Closed").
Direct text comparison on picklist fields in validation formulas requires the ISPICKVAL function.
2
Identify the condition for missing mandatory fields.
Either Completion_Date__c is blank OR Resolution_Summary__c is blank, represented by OR(ISBLANK(Completion_Date__c), ISBLANK(Resolution_Summary__c)).
ISBLANK is the standard and recommended function for checking blank/null values across text and date fields.
3
Combine the conditions into a complete validation logic statement.
AND(ISPICKVAL(Status__c, "Closed"), OR(ISBLANK(Completion_Date__c), ISBLANK(Resolution_Summary__c))).
Validation rules fire when the formula evaluates to TRUE, so the formula must evaluate to true when the status is Closed AND at least one required field is blank.

Key Concept

Validation Rule Syntax and Data Quality Enforcement
Estimated Time:1m 30s
Question 1416Question

A sales manager at a professional services company wants a Salesforce administrator to set up activity management for their team. The manager has two specific requirements: first, assign an identical follow-up action item to five team members where each person tracks and closes their own task independently; second, allow representatives to log a single client meeting against multiple client contacts present at the meeting. Which two capabilities and limitations should the administrator explain regarding this setup? (Select 2)

Select all that apply

Show answer & explanation

Answer: Enabling 'Allow Users to Relate Multiple Contacts to Tasks and Events' allows a single task or event to be associated with up to 50 contacts.; Assigning a task to a group or multiple individual users creates an independent copy of the task for each assigned user.

Answer

The administrator should explain that enabling Shared Activities permits linking up to 50 contacts to a single activity, and that assigning a task to multiple users generates an independent task copy for each assigned individual.
The option stating that Shared Activities allows relating up to 50 contacts to a single activity correctly identifies the system limit for multi-contact activity logging. Additionally, the option explaining that assigning a task to multiple users creates independent copies accurately reflects how Salesforce handles group task assignments for individual completion tracking.

Step-by-Step Solution

1
Analyze the requirement for logging a single meeting against multiple contacts.
Confirm that Salesforce Shared Activities (Allow Users to Relate Multiple Contacts to Tasks and Events) supports linking up to 50 contacts to one task or event.
Shared Activities extends the Name (WhoId) lookup capabilities to support multiple contact relations.
2
Analyze the requirement for assigning identical tasks to multiple team members for independent tracking.
Confirm that creating a multi-user task automatically instantiates individual task copies for each assigned team member.
Each copy functions independently so users can track their specific progress without impacting peers.
3
Evaluate distractor capabilities regarding Accounts and Task status sync.
Identify that Shared Activities does not apply to multiple Accounts (WhatId) and task copies do not automatically synchronize status updates across users.
WhatId relationships remain single-record lookups, and multi-user task copies are completely unlinked in terms of status progress.

Key Concept

Activity Management: Shared Activities and Multi-User Task Assignment
Question 1417Question

A Field Service Administrator is building a Custom Report Type with 'Work Orders' as the primary object and 'Service Appointments' as the secondary object. The Field Operations Manager requires reports that list all Work Orders regardless of whether they have associated Service Appointments. Additionally, report creators must be able to display the Service Territory Name from the related Service Resource record on the report layout. Which TWO actions should the administrator take within the Custom Report Type setup to satisfy these requirements? (Select 2 answers.)

Select all that apply

Show answer & explanation

Answer: Set the object relationship between Work Orders and Service Appointments to 'Each record ("A") may or may not have related records ("B")'.; Edit the Custom Report Type field layout and use 'Add fields related via lookup' to include the Service Territory field.

Answer

The administrator must set the object relationship between Work Orders and Service Appointments to 'Each record ("A") may or may not have related records ("B")' (outer join) and edit the Custom Report Type layout using 'Add fields related via lookup' to bring in the Service Territory field.
To include primary object records regardless of whether secondary child records exist, the administrator must choose the 'may or may not have related records' (outer join) option in the custom report type definition. To make fields from lookup-related objects available for reporting without custom fields, the administrator must edit the layout of the Custom Report Type and use 'Add fields related via lookup'.

Step-by-Step Solution

1
Configure the object relationship for outer join behavior
Work Orders without related Service Appointments remain visible in reports built from this report type.
Choosing 'Each record ("A") may or may not have related records ("B")' performs an left outer join instead of an inner join ('must have at least one related record').
2
Traverse lookup relationships in the Custom Report Type field layout
The Service Territory field is added to the report field layout.
The 'Add fields related via lookup' link in the report layout editor permits navigating up to 4 levels of lookup relationships to reference fields not directly present on the primary or secondary object.

Key Concept

Custom Report Type Object Relationships and Field Layout Lookup Traversal
Estimated Time:1m 30s
Question 1418Question

Beacon Logistics Corp enforces an Organization-Wide Default (OWD) sharing setting of Private for the Opportunity object. A Salesforce administrator builds a company-wide executive dashboard and configures the running user as the VP of Sales, who has access to all corporate records. A regional sales representative who owns and has access to only 10 regional opportunities opens the shared dashboard and views a component showing 150 total opportunities nationwide.

What occurs when the regional sales representative clicks this dashboard component to drill down into the underlying source report?

Show answer & explanation

Answer: The source report opens and displays only the 10 opportunities that the regional sales representative has permission to access.

Answer

The source report opens and displays only the 10 opportunities that the regional sales representative has permission to access.
In Salesforce, while a dashboard component displays data based on the running user specified in the dashboard settings (in this case, the VP of Sales), clicking the component to view the underlying source report forces the report to execute under the security context of the logged-in user. Because the Organization-Wide Default for Opportunities is set to Private and the sales representative only has access to 10 records, the source report will strictly display those 10 records.

Step-by-Step Solution

1
Analyze the dashboard security context
The dashboard component runs under the VP of Sales' security context (static running user), rendering aggregate metrics for 150 opportunities.
Dashboard components display data according to the permissions of the configured running user.
2
Analyze the source report security context upon drill-down
When navigating to the source report, Salesforce switches to the logged-in user's security context.
Reports always run using the logged-in user's Organization-Wide Defaults, role hierarchy, and explicit sharing rules.
3
Determine final record visibility in the report
The sales representative sees only their 10 accessible opportunities.
Because OWD is Private and the rep only has access to 10 records, the report filters out all remaining unshared records.

Key Concept

Static Dashboard Running User vs. Source Report Execution Context
Question 1419Question

A sales organization's field representatives use the Salesforce Mobile App on their smartphones to manage client relationships on the go. The sales director asks the Salesforce Administrator to make two updates to the mobile experience for Account records:
1. Ensure key fields such as Account Name, Annual Revenue, Phone, and Account Owner are prominent at the top header card when viewing an Account record on mobile.
2. Enable reps to create a follow-up task directly from the mobile action bar at the bottom of the screen when viewing an Account record.

Which two configuration actions should the administrator perform to fulfill these requirements? (Select 2)

Select all that apply

Show answer & explanation

Answer: Customize the Account Compact Layout to include the required header fields.; Add the Create Task Quick Action to the Salesforce Mobile and Lightning Experience Actions section on the Account Page Layout.

Answer

To meet both requirements, the administrator must customize the Account Compact Layout to display key header fields in the mobile app, and add the Create Task action to the Salesforce Mobile and Lightning Experience Actions section of the Account Page Layout.
Compact Layouts determine which fields appear in the highlights panel of a record, which serves as the top record header card in the Salesforce Mobile App. Adding quick actions to the 'Salesforce Mobile and Lightning Experience Actions' section on an object's page layout ensures those actions are exposed in the mobile app's action bar at the bottom of the screen.

Step-by-Step Solution

1
Configure the mobile record header view
Create or edit an Account Compact Layout in Object Manager and populate it with Account Name, Annual Revenue, Phone, and Account Owner.
Compact Layouts dictate the fields displayed in the highlights panel and header card on mobile devices.
2
Configure mobile action bar buttons
Edit the Account Page Layout and drag the Create Task quick action into the Salesforce Mobile and Lightning Experience Actions publisher section.
This section determines which quick actions are rendered in the mobile action bar at the bottom of the device screen.

Key Concept

Salesforce Mobile App Record Customization using Compact Layouts and Mobile Quick Actions
Estimated Time:1m 30s
Question 1420Question

A Salesforce administrator is configuring validation rules on a custom object named Asset_Maintenance__c to enforce data quality standards. Match each business validation requirement with its corresponding validation rule formula syntax.

Click a left item, then click its matching right item

Items

Require the Resolution_Summary__c field to be populated only when the Status__c picklist field is changed to 'Completed'.
Validate that the custom text field Serial_Number__c conforms to a format of exactly two uppercase letters followed by six numerical digits.
Prevent users from entering a Completion_Date__c that occurs in the future whenever the Status__c picklist field is set to 'Completed'.
Require Manager_Approval_Notes__c when updating an existing record if the Discount_Percentage__c exceeds 20%.

Matches

Show answer & explanation

Answer

The correct pairings match each validation scenario to its proper formula logic: (1) Requiring resolution summary on status change maps to AND(ISCHANGED(Status__c), ISPICKVAL(Status__c, 'Completed'), ISBLANK(Resolution_Summary__c)); (2) Formatting serial numbers maps to AND(NOT(ISBLANK(Serial_Number__c)), NOT(REGEX(Serial_Number__c, '^[A-Z]{2}[0-9]{6}$'))); (3) Restricting future completion dates maps to AND(ISPICKVAL(Status__c, 'Completed'), Completion_Date__c > TODAY()); (4) Requiring manager notes on updates maps to AND(NOT(ISNEW()), Discount_Percentage__c > 0.20, ISBLANK(Manager_Approval_Notes__c)).
Each business requirement relies on standard Salesforce formula functions: ISCHANGED() checks if a picklist field was altered in the current transaction; REGEX() validates string patterns when negated with NOT(); date logic compares custom date fields against TODAY(); and NOT(ISNEW()) ensures validation logic applies exclusively to existing record edits rather than initial inserts.

Step-by-Step Solution

1
Analyze requirement 1 (Status change to Completed requires Resolution Summary).
Identify that detecting a field state change requires ISCHANGED(), testing picklist values requires ISPICKVAL(), and checking missing values requires ISBLANK(). Combining these in AND() triggers the error when the condition is violated.
Validation rules evaluate to TRUE to block saving and display an error message.
2
Analyze requirement 2 (Serial number regex pattern validation).
Use REGEX(Serial_Number__c, '^[A-Z]{2}[0-9]{6}$') wrapped in NOT() so that non-matching formats return TRUE, firing the validation error.
REGEX tests string structure, and wrapping with NOT ensures non-conforming strings trigger the error.
3
Analyze requirement 3 (Preventing future completion dates).
Evaluate Completion_Date__c > TODAY() combined with ISPICKVAL(Status__c, 'Completed').
Date comparisons evaluate directly against system functions like TODAY().
4
Analyze requirement 4 (Existing record updates with discount threshold).
Combine NOT(ISNEW()) to bypass newly created records, Discount_Percentage__c > 0.20 for the threshold, and ISBLANK(Manager_Approval_Notes__c) to enforce mandatory notes.
ISNEW() evaluates to TRUE during record insertion; wrapping it in NOT() isolates update operations.

Key Concept

Validation Rules and Data Quality Enforcement
PreviousPage 71 / 90Next
All practice questions — Salesforce Certified Administrator | Examkin