Examkin

All practice questions

1784 questions

All types1,784Multiple choice918Multiple select587Matching142Ordering137
Question 1381Question →

Luminary Media Group needs to implement a tailored sales lifecycle for its new Custom Event Sponsorship division, which requires a unique sequence of opportunity stages compared to standard subscription sales. Which sequence of administrative steps must an administrator take to make these custom stages available only on sponsorship opportunities?

Show answer & explanation

Answer: Create the new stage values in the master Stage picklist field, create a new Sales Process selecting those stages, create a new Opportunity Record Type linked to the Sales Process, and assign the Record Type to user profiles.

Answer

Create the new stage values in the master Stage picklist field, create a new Sales Process selecting those stages, create a new Opportunity Record Type linked to the Sales Process, and assign the Record Type to user profiles.
To present a custom set of Opportunity Stages for a distinct sales channel, an administrator must complete a four-step administrative process: 1) Add any missing stage values to the master Stage picklist, 2) Create a Sales Process selecting the specific stages for that lifecycle, 3) Associate the Sales Process with a new Opportunity Record Type, and 4) Assign the Record Type to target user profiles. This guarantees that users working on sponsorship opportunities see only the relevant stages.

Step-by-Step Solution

1
Ensure all required Opportunity Stage picklist values exist in the master Stage picklist field settings.
The master picklist includes all stage values needed across all business processes.
Sales Processes can only select from active master stage values defined on the Opportunity object.
2
Create a new Sales Process and select the specific subset of stage values applicable to Custom Event Sponsorships.
A dedicated stage lifecycle is established for the sponsorship business process.
Salesforce uses Sales Processes specifically to govern available Stage picklist values on Opportunities.
3
Create a new Opportunity Record Type and link it to the newly created Sales Process.
The Record Type encapsulates the specific Sales Process along with page layout assignments.
Record Types serve as the administrative link connecting the Sales Process to profile assignments and UI layouts.
4
Assign the new Opportunity Record Type to the target user profiles.
Users can select the Custom Event Sponsorship record type when creating opportunities and access the tailored stage picklist sequence.
Profile assignment determines record type availability for users.

Key Concept

Sales Processes and Opportunity Record Type Association
Question 1382Question →

Match each Salesforce case capture mechanism to its corresponding architectural design or operational behavior.

Click a left item, then click its matching right item

Items

Web-to-Case
On-Demand Email-to-Case
Email-to-Case Agent

Matches

Show answer & explanation

Answer

Web-to-Case matches with generating HTML form code and routing daily overflow to the default case owner. On-Demand Email-to-Case matches with processing emails entirely in the cloud without local software installation. Email-to-Case Agent matches with requiring an executable installed behind the firewall to keep traffic internal and process large attachments.
Web-to-Case creates web forms and sends overflow submissions exceeding daily limits to the default case owner. On-Demand Email-to-Case routes emails through Salesforce cloud servers without local software. Email-to-Case Agent requires local software installed behind the corporate firewall to keep network traffic internal and process large attachments.

Step-by-Step Solution

1
Analyze Web-to-Case capabilities
Identify that Web-to-Case generates HTML code for forms and relies on the default case owner when daily request limits are exceeded.
Web-to-Case is a web-form mechanism capped at 5,000 daily cases, using email notification to the default case owner as an overflow mechanism.
2
Differentiate On-Demand Email-to-Case from the Email-to-Case Agent
Determine that On-Demand handles processing in the cloud, while the Agent requires local behind-the-firewall installation.
On-Demand Email-to-Case eliminates the need for internal server agents, whereas Email-to-Case Agent keeps traffic inside the corporate network.
3
Match each feature to its corresponding term
Pair Web-to-Case with HTML form overflow handling, On-Demand Email-to-Case with cloud email processing, and Email-to-Case Agent with behind-the-firewall executable setup.
Matches align directly with official Salesforce Service Cloud case capture architecture.

Key Concept

Salesforce Case Capture Mechanisms (Web-to-Case vs. On-Demand Email-to-Case vs. Email-to-Case Agent)
Question 1383Question →

Zephyr Aerospace is introducing a dedicated Strategic Accounts division with a customized sales cycle that requires a specific subset of opportunity stages. In which sequential order should a Salesforce administrator perform the administrative setup steps to configure and deploy this new sales workflow?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order of setup steps is: 1. Create necessary Opportunity stage picklist values in Object Manager; 2. Create a new Sales Process and select the required stages; 3. Create a new Opportunity Record Type and assign the Sales Process; 4. Assign the Record Type to user profiles or permission sets.
The configuration sequence strictly follows underlying dependency rules in Salesforce: global picklist values must exist before a Sales Process can group them; a Sales Process must exist before an Opportunity Record Type can reference it; and the finished Record Type must exist before it is provisioned to user profiles or permission sets.

Step-by-Step Solution

1
Define new stage picklist values
The master Opportunity Stage field contains all potential stages needed across the organization.
Sales processes cannot include stage values that do not yet exist in the master Opportunity object picklist definition.
2
Create and configure the Sales Process
A customized Sales Process is created containing only the stages specific to the Strategic Accounts team.
The Sales Process determines the stage lifecycle before it can be linked to a record type.
3
Create the Record Type and link the Sales Process
The Strategic Accounts Record Type is instantiated with its governing Sales Process.
On standard objects like Opportunity, creating a Record Type mandatorily requires selecting an underlying Sales Process.
4
Grant user access via Profiles or Permission Sets
Target sales representatives gain access to select the new record type when creating opportunities.
Record type deployment must occur after the record type and associated business process are fully assembled.

Key Concept

Sales Process and Record Type configuration sequence in Salesforce Opportunity management
Question 1384Question →

A telecommunications enterprise is designing a multi-tier Experience Cloud self-service and support strategy. Match each Experience Cloud license or access type on the left to the corresponding business requirement on the right.

Click a left item, then click its matching right item

Items

Customer Community License
Customer Community Plus License
Partner Community License
Guest User Profile

Matches

Show answer & explanation

Answer

Customer Community License matches high-volume B2C users relying on Sharing Sets without Role Hierarchies; Customer Community Plus License matches external users needing Role Hierarchies and advanced sharing features; Partner Community License matches B2B partners needing access to Leads and Opportunities; Guest User Profile matches unauthenticated public visitors accessing public Knowledge and Web-to-Case.
Each Experience Cloud access model directly aligns with specific security and functionality boundaries: Customer Community covers high-volume B2C users using Sharing Sets; Customer Community Plus adds Roles, Reports, and advanced sharing; Partner Community grants access to Sales objects like Leads and Opportunities; Guest User Profile controls public, unauthenticated access.

Step-by-Step Solution

1
Identify high-volume consumer self-service requirements
Determine that high-volume B2C users without role hierarchy needs correspond to the Customer Community License.
Customer Community is cost-effective for large-volume B2C portals utilizing Sharing Sets.
2
Evaluate advanced sharing and role hierarchy needs
Map Customer Community Plus License to requirements needing Role Hierarchies, Reports, and Apex/Manual sharing.
Customer Community Plus adds backend CRM object access features and role-based sharing models.
3
Evaluate B2B partner sales and service requirements
Map Partner Community License to requirements involving Leads and Opportunities.
Partner Community licenses extend access to CRM sales objects alongside Service capabilities.
4
Identify unauthenticated access requirements
Map Guest User Profile to public unauthenticated access to Knowledge articles and Web-to-Case.
Unauthenticated site visitors interact with Experience Cloud sites through the site's Guest User Profile.

Key Concept

Experience Cloud Licensing and User Access Security Models
Estimated Time:1m 30s
Question 1385Question →

Apex Global operates a customer support portal that utilizes Web-to-Case to automatically generate support tickets. During an unexpected product announcement, the portal experiences a sudden surge in web traffic, causing the total number of submitted Web-to-Case forms to exceed the organization's daily Web-to-Case limit. How does Salesforce handle the Web-to-Case request submissions that occur after the daily limit has been reached?

Show answer & explanation

Answer: The excess submissions are emailed to the Default Case Owner specified in Web-to-Case settings, containing the submitted case data for manual entry.

Answer

The submitted case data for requests exceeding the daily limit is sent in an email to the Default Case Owner designated in Web-to-Case setup.
When an organization reaches its daily Web-to-Case request limit, Salesforce stops creating Case records automatically. To avoid losing customer submission data, the system sends an email containing the form data directly to the designated Default Case Owner, allowing support administrators to manually review or process the requests.

Step-by-Step Solution

1
Identify the Case capture feature and condition described in the scenario.
The scenario describes Web-to-Case reaching its maximum daily request limit during a traffic surge.
Salesforce enforces standard daily governor limits on Web-to-Case submissions based on organization edition and limits.
2
Evaluate the system behavior for overflow Web-to-Case requests.
Salesforce halts automatic Case record creation and forwards the raw form data via email to the Default Case Owner.
This prevents data loss while maintaining system guardrails against excessive web requests.

Key Concept

Web-to-Case Daily Limits and Default Case Owner Fallback
Question 1386Question →

Vanguard Global Tech is launching a dedicated OEM Partner sales division. The OEM Partner team follows a streamlined sales lifecycle that requires a distinct subset of Opportunity Stage picklist values compared to the standard stages used by the Direct Sales team. Which set of administrative steps should the Salesforce administrator take to implement this requirement for the OEM Partner team?

Show answer & explanation

Answer: Create the new Opportunity stage picklist values, create a new Sales Process to select the required stages, create an Opportunity Record Type associated with the new Sales Process, and assign the Record Type to the OEM Partner profile.

Answer

The correct sequence of actions is to create the new stage picklist values, create a new Sales Process containing those stages, create an Opportunity Record Type linked to the Sales Process, and assign the Record Type to the OEM Partner profile.
To display a customized set of Opportunity Stages to a specific business unit, an administrator must follow the required setup chain: create the stage values on the object, group those stage values within a Sales Process, associate the Sales Process with an Opportunity Record Type, and finally assign that Record Type to the appropriate user profiles.

Step-by-Step Solution

1
Add custom Stage picklist values
The necessary stage values are available on the Opportunity object.
Opportunity stages are standard picklist values that must exist on the object level before being assigned to processes.
2
Create a Sales Process
A specific sequence of opportunity stages is defined for the OEM sales cycle.
Sales Processes determine which Stage picklist values are available for specific sales lifecycles.
3
Create an Opportunity Record Type and link it to the Sales Process
The Record Type encapsulates the specific Sales Process alongside page layout definitions.
Record Types on the Opportunity object require a Sales Process association to control stage selection.
4
Assign the Record Type to user profiles
Users with the OEM Partner profile are granted access to create and manage opportunities using the customized sales lifecycle.
Profile assignment determines which Record Types (and associated Sales Processes) are accessible to users.

Key Concept

Opportunity Sales Process and Record Type Linkage
Estimated Time:1m 30s
Question 1387Question →

An automotive fleet management company uses an Experience Cloud site with Customer Community licenses to allow client fleet managers to log and view support requests. The external Organization-Wide Default (OWD) for Cases is set to Private. The administrator must ensure that external community users can view and edit all Cases associated with their specific Account record, while preventing visibility into Cases belonging to other companies.

Which configuration should the administrator implement to meet this requirement?

Show answer & explanation

Answer: Create a Sharing Set that maps the User Contact Account to the Case Account.

Answer

The administrator should create a Sharing Set that maps the user's Contact Account to the Case Account.
Creating a Sharing Set is the correct method to grant record-level access to users with Customer Community licenses. Since these users do not have Salesforce roles and cannot participate in standard sharing rules, Sharing Sets allow administrators to grant access to records (like Cases) based on matching fields between the user's Contact record and the target record.

Step-by-Step Solution

1
Analyze license capabilities and sharing limitations
Customer Community licenses use high-volume portal access controls and do not support standard role-based sharing rules.
Standard sharing rules require Salesforce roles, which Customer Community users lack.
2
Evaluate record access requirements
The requirement is to grant access to Case records linked to the user's account under a Private OWD setting.
Private OWD restricts record visibility unless explicit sharing mechanism is applied.
3
Select appropriate Experience Cloud access mechanism
Configure a Sharing Set mapping User:Contact.Account = Case:Account with Read/Write permissions.
Sharing Sets are specifically designed to extend record access to high-volume community users based on account or contact relationships.

Key Concept

Experience Cloud Sharing Sets for High-Volume Portal Licenses
Question 1388Question →

A Salesforce administrator at Horizon Financial is configuring activity management settings for wealth management advisors who frequently conduct joint client meetings. The administrator enables 'Allow Users to Relate Multiple Contacts to Tasks and Events' (Shared Activities). Which two statements correctly describe the behavior and limitations of Shared Activities in Salesforce? (Choose 2)

Select all that apply

Show answer & explanation

Answer: Up to 50 contacts can be related to a single task or event record.; One contact must be designated as the primary contact, which determines the related Account for the activity.

Answer

Up to 50 contacts can be related to a single task or event record, and one contact must be designated as the primary contact, which determines the related Account for the activity.
Enabling Shared Activities allows users to link up to 50 contacts to a single task or event. Among the linked contacts, one contact is designated as the primary contact, which connects the activity to that contact's parent account. The system maintains a single activity record linked to multiple contact records.

Step-by-Step Solution

1
Evaluate contact capacity for Shared Activities.
Confirm that Salesforce allows up to 50 contacts to be associated with a single task or event.
Salesforce documentation defines the limit for Shared Activities (Shared Contacts) as 50.
2
Evaluate Account association rules for Shared Activities.
Identify that one contact serves as the primary contact and drives the Account relationship.
Salesforce relates the activity to the account of the primary contact specified on the activity record.
3
Verify multi-account and duplicate record misconceptions.
Confirm that activities cannot relate to multiple accounts and do not create separate duplicate records per contact.
Shared Activities applies exclusively to relating multiple contacts to a single record, maintaining a single activity object.

Key Concept

Shared Activities capabilities and system limits in Salesforce
Question 1389Question →

An administrator at Global Logistics Inc. is configuring Activity Settings in Salesforce. The sales director wants account representatives to log a single meeting event that involves multiple client contacts and associate that meeting with an ongoing sales opportunity. Which statement accurately describes the system behavior and limits when Shared Activities ('Allow Users to Relate Multiple Contacts to Tasks and Events') is enabled?

Show answer & explanation

Answer: The event can be related to up to 50 contacts via the Name (WhoId) field, but can only be related to a single object record (such as an Opportunity) via the Related To (WhatId) field.

Answer

The event can be related to up to 50 contacts via the Name (WhoId) field, but can only be related to a single object record (such as an Opportunity) via the Related To (WhatId) field.
When Shared Activities is enabled, users can relate up to 50 contacts (or leads) to a single task or event record via the Name (WhoId) field. However, the Related To (WhatId) field can still only be linked to one primary non-contact record, such as a single Account, Opportunity, or Case.

Step-by-Step Solution

1
Identify the feature being evaluated.
The feature is Shared Activities ('Allow Users to Relate Multiple Contacts to Tasks and Events').
This setting dictates how tasks and events can be linked to multiple contact records in Salesforce.
2
Evaluate relationship limits for the Name (WhoId) field under Shared Activities.
A single task or event can be related to up to 50 contacts (or leads).
Salesforce Shared Activities enforces a limit of 50 contacts/leads per activity.
3
Evaluate relationship limits for the Related To (WhatId) field under Shared Activities.
The Related To field can only accept a single record (e.g., one Opportunity, Account, or Case).
Shared Activities does not extend the WhatId relationship; it strictly enables multiple WhoId relationships.

Key Concept

Shared Activities Limits (WhoId vs WhatId)
Question 1390Question →

A Salesforce Administrator is configuring Web-to-Case to capture support requests directly from the company website. Which two statements regarding Web-to-Case capabilities and limit behaviors are correct? (Select 2)

Select all that apply

Show answer & explanation

Answer: Submissions exceeding the daily Web-to-Case limit are emailed directly to the Default Case Owner rather than creating Case records.; Both standard fields and custom fields on the Case object can be selected when generating the Web-to-Case HTML code.

Answer

Web-to-Case routes submissions exceeding daily limits to the Default Case Owner via email, and the Web-to-Case HTML generator allows selecting both standard and custom fields for the form.
Web-to-Case handles overflow submissions exceeding the daily quota by emailing the form contents directly to the Default Case Owner. Additionally, administrators can include both standard and custom Case fields when generating the HTML form code via Salesforce Setup.

Step-by-Step Solution

1
Analyze Web-to-Case limit handling behavior
Salesforce enforces a daily request limit for Web-to-Case (typically 5,000 requests per 24 hours). Excess submissions are sent to the default web/case owner email address.
This guarantees customer inquiry data is not lost even during volume spikes.
2
Evaluate standard HTML generator capabilities
The setup wizard generates HTML containing selected standard and custom fields on the Case object.
Administrators can capture specific custom data points required by business processes directly from web submissions.
3
Verify limitations regarding attachments and contact creation
Standard Web-to-Case HTML does not support file upload fields, and unmatched emails leave the Contact field blank on the newly created Case.
Prevents database clutter from unverified contact auto-creation and avoids web server security vulnerabilities associated with unauthenticated file uploads.

Key Concept

Web-to-Case limits, field generation, and automated handling rules
Question 1391Question →

A healthcare organization recently deployed Einstein Activity Capture (EAC) to track client communications automatically. The compliance team mandates that, by default, emails and calendar events automatically captured for the patient outreach team must remain private to each individual user rather than being shared with all users across the organization. Which action should an administrator take to enforce this requirement?

Show answer & explanation

Answer: Configure the default Activity Sharing setting to Don't Share within the Einstein Activity Capture configuration assigned to the outreach team.

Answer

Configure the default Activity Sharing setting to Don't Share within the Einstein Activity Capture configuration assigned to the outreach team.
In Salesforce, Einstein Activity Capture sharing behavior (such as Share with Everyone, Don't Share, or Share with Groups) is defined directly within the EAC Configuration settings. Assigning the outreach team to a configuration set to 'Don't Share' ensures their captured emails and events default to private.

Step-by-Step Solution

1
Identify where Einstein Activity Capture sharing settings are controlled.
Recognize that activity sharing settings (e.g., Share with Everyone, Don't Share, Share with Groups) are configured at the EAC Configuration level in Setup.
EAC controls how captured emails and calendar events are shared across the timeline via specific configuration assignments rather than standard object OWD or profiles.
2
Evaluate the compliance requirement against configuration options.
Setting the default sharing mode to 'Don't Share' inside the specific EAC configuration ensures activities captured for assigned users remain private by default.
This satisfies the business requirement directly without impacting non-EAC standard records or other user groups.

Key Concept

Einstein Activity Capture Configuration and Activity Sharing Settings
Question 1392Question →

A biotechnology equipment vendor provides a self-service Experience Cloud site using the Customer Service template for university research laboratories. External laboratory managers log into the site with Customer Community licenses. The company wants to allow laboratory managers to view all support cases logged by other researchers affiliated with their same university (Account), while also enabling automated solution article suggestions when users create new support cases. Which two configuration steps should the administrator take to meet these requirements?

Select all that apply

Show answer & explanation

Answer: Configure a Sharing Set for the Customer Community profile that grants Read access to Cases where User:Contact.Account equals Case:Account.; Add the Case Deflection component to the Create Case page layout in Experience Builder and configure Knowledge Data Category visibility for external profiles.

Answer

The administrator should configure a Sharing Set for the Customer Community profile mapping the User's Contact Account to the Case Account, and add the Case Deflection component to the Create Case page in Experience Builder while ensuring Knowledge Data Category visibility is set.
To grant Customer Community users access to cases owned by others at the same Account, an administrator must create a Sharing Set that maps the user's Contact Account field to the Case Account field. For automated article recommendations during case creation, the Case Deflection component must be placed on the Experience Builder case creation page, combined with appropriate Data Category visibility settings.

Step-by-Step Solution

1
Determine the record access mechanism for Customer Community licenses
Identify that Customer Community users do not utilize roles and require Sharing Sets to gain record access to cases associated with their Account.
Customer Community licenses use high-volume portal user access rules where Sharing Sets bridge OWD restrictions based on account/contact relationships.
2
Determine the case deflection and self-service Knowledge configuration
Place the Case Deflection component on the case creation page in Experience Builder and verify Data Category Visibility.
Case Deflection searches published Knowledge articles dynamically as users type case details, which requires both the Experience Builder component and Data Category access.

Key Concept

Experience Cloud Sharing Sets and Case Deflection setup for Customer Community users
Question 1393Question →

Cloud Kicks needs to process incoming customer support emails that routinely contain large log attachments exceeding 30 MB. Additionally, company security policies require that email traffic remains within their corporate network firewall rather than being processed directly by external cloud email servers. Which case capture mechanism should the Salesforce Administrator implement?

Show answer & explanation

Answer: Email-to-Case using the installed Email-to-Case Agent software behind the corporate firewall

Answer

Email-to-Case using the installed Email-to-Case Agent software behind the corporate firewall
Standard Email-to-Case requires installing an Email-to-Case Agent behind the company's network firewall. This architecture keeps email processing within the corporate network and allows the system to accept attachments larger than the 25 MB limit imposed by On-Demand Email-to-Case.

Step-by-Step Solution

1
Analyze attachment size requirements.
The requirement specifies attachments exceeding 30 MB. On-Demand Email-to-Case has a fixed maximum size limit of 25 MB per email.
Standard Email-to-Case (using the local agent) is required to handle email attachments over 25 MB.
2
Analyze network security constraints.
The company requires email traffic to stay behind the corporate firewall.
Standard Email-to-Case runs an agent behind the firewall to poll the local mail server, whereas On-Demand Email-to-Case routes emails through external Salesforce Apex email services.

Key Concept

Email-to-Case Agent vs. On-Demand Email-to-Case Architecture and Limits
Question 1394Question →

A Salesforce Administrator is configuring Einstein Activity Capture (EAC) sync settings and platform data behaviors to align with specific departmental requirements. Match each business requirement on the left with the correct EAC sync configuration setting or platform storage behavior on the right.

Click a left item, then click its matching right item

Items

Calendar events created in Salesforce must sync out to external calendars, but external events must not sync into Salesforce.
External calendar events must be automatically imported into Salesforce, but Salesforce-created events should remain local.
Emails and calendar events must stay synchronized seamlessly across both Salesforce and external servers regardless of origin.
Captured email and event data must display on record timelines without consuming standard Salesforce relational data storage.

Matches

Show answer & explanation

Answer

The business requirements match their respective EAC settings: Salesforce to Exchange handles outbound-only synchronization, Exchange to Salesforce handles inbound-only synchronization, Both Ways maintains bidirectional sync, and AWS Off-Core Activity Storage handles timeline rendering without consuming standard CRM data storage.
Each requirement directly corresponds to core EAC capabilities: Salesforce to Exchange supports outbound sync, Exchange to Salesforce supports inbound sync, Both Ways maintains symmetric updates, and AWS Off-Core Activity Storage enables high-volume activity capture without using standard Salesforce database storage allocation.

Step-by-Step Solution

1
Review the synchronization direction requirements for calendar and email integration in EAC configurations.
Determine unidirectionality versus bidirectionality for each departmental use case.
Configuring sync direction ensures data flow matches security and administrative policies without duplicating or overwriting events.
2
Examine the underlying data storage architecture of Einstein Activity Capture.
Identify that EAC activities are maintained in off-core AWS storage rather than creating standard Task and Event records.
Understanding off-core storage explains why captured activities appear on record timelines without impacting standard Salesforce organization data limits.

Key Concept

Einstein Activity Capture Sync Directions and Architecture
Question 1395Question →

A sales administrator at Summit Peak Energy enables 'Allow Users to Relate Multiple Contacts to Tasks and Events' (Shared Activities) in Activity Settings. A sales executive asks whether a single post-meeting Event can be linked simultaneously to multiple client contacts and multiple Accounts.

Which statement accurately describes the capability of Shared Activities in Salesforce?

Show answer & explanation

Answer: The Event can be related to up to 50 Contacts, but it can only be related to a single Account.

Answer

The Event can be related to up to 50 Contacts, but it can only be related to a single Account.
With Shared Activities enabled, Salesforce allows users to relate up to 50 Contacts (or Leads) to a single Task or Event using the Name field. However, the activity can still only be linked to one Account (or other Related To record) at a time.

Step-by-Step Solution

1
Analyze the Shared Activities feature settings and capabilities in Salesforce.
Shared Activities enables relating up to 50 Contacts or Leads to a single Task or Event record via the Name (WhoId) field.
Salesforce Activity Management allows multi-contact association to track meeting participants.
2
Evaluate the relationship restriction for Accounts and other related records (WhatId).
The Related To (WhatId) field continues to support linking to only one record, such as a single Account, Opportunity, or Case.
Shared Activities does not support multi-object or multi-Account relationship linking on a single activity record.

Key Concept

Shared Activities (Relating Multiple Contacts to Tasks and Events)
Estimated Time:1m 15s
Question 1396Question →

A system administrator needs to grant Einstein Activity Capture (EAC) features to a newly formed sales team so their Google Workspace emails and calendar events automatically sync with Salesforce. The administrator attempts to configure EAC access directly on the sales team's user profiles, but discovers that EAC sync settings and user provisioning cannot be assigned at the profile level. What is the correct administrative approach to provision Einstein Activity Capture access for these specific sales representatives?

Show answer & explanation

Answer: Assign the Standard Einstein Activity Capture permission set to the designated sales representatives.

Answer

Assign the Standard Einstein Activity Capture permission set to the designated sales representatives.
The correct answer correctly identifies that Einstein Activity Capture access and sync configurations are managed by assigning the Standard Einstein Activity Capture permission set (or custom EAC permission sets) to users. User profiles do not contain settings for activating EAC sync functionality.

Step-by-Step Solution

1
Identify the administrative requirement for feature provisioning.
Determine that specific users need access to Einstein Activity Capture (EAC) sync functionality.
EAC functionality is licensed and assigned to individual users or user subsets.
2
Evaluate the mechanism for granting EAC privileges in Salesforce.
Confirm that permission sets (such as the Standard Einstein Activity Capture permission set) control user inclusion in EAC configurations.
Profiles manage baseline credentials and layout assignments, whereas additive feature licenses and sync configurations are managed through permission sets.
3
Assign the appropriate permission set to the target sales reps.
The sales reps gain access to EAC sync settings and activity capture functionality.
Assigning the permission set activates user licensing and includes them in active EAC configuration rules.

Key Concept

Einstein Activity Capture User Provisioning via Permission Sets
Question 1397Question →

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

Click a left item, then click its matching right item

Items

Web-to-Case
On-Demand Email-to-Case
Email-to-Case Agent
Default Case Owner

Matches

Show answer & explanation

Answer

Web-to-Case corresponds to HTML web submissions with a 5,000 daily request limit. On-Demand Email-to-Case corresponds to cloud email processing with a 25 MB attachment limit. Email-to-Case Agent corresponds to local firewall deployment handling attachments over 25 MB. Default Case Owner corresponds to receiving unassigned cases when assignment rules fail.
Each item accurately aligns with official Salesforce Administrator specifications: Web-to-Case is form-driven with a 5,000 daily request cap; On-Demand Email-to-Case uses cloud email services capped at 25 MB attachments; Email-to-Case Agent runs locally behind a firewall for internal traffic and larger attachments; Default Case Owner functions as the automated fallback recipient when rule criteria are unmet.

Step-by-Step Solution

1
Identify Web-to-Case specifications
Web-to-Case generates HTML form code and enforces a default daily maximum of 5,000 cases per 24-hour window.
This mechanism captures website form inputs without requiring external installed software.
2
Distinguish between On-Demand Email-to-Case and Email-to-Case Agent
On-Demand handles cloud traffic up to 25 MB attachments; Email-to-Case Agent runs behind a local firewall to process files larger than 25 MB.
Salesforce restricts cloud email service attachment sizes to 25 MB, necessitating an on-premise agent for higher volume or larger files.
3
Determine the role of the Default Case Owner
Serves as the fallback assignee when automated case assignment rules do not match.
Prevents newly generated cases from remaining unowned.

Key Concept

Salesforce Case Capture Mechanism Architecture and Limitations
Question 1398Question →

A Salesforce administrator at a software publishing company is setting up a validation rule on the custom object Bug_Report__c. The business requirement mandates that whenever the picklist field Severity__c is set to "Critical", the text field Resolution_Plan__c must not be left blank before saving the record. Which formula should the administrator use to enforce this data quality requirement?

Show answer & explanation

Answer: AND(ISPICKVAL(Severity__c, "Critical"), ISBLANK(Resolution_Plan__c))

Answer

AND(ISPICKVAL(Severity__c, "Critical"), ISBLANK(Resolution_Plan__c))
The correct formula uses ISPICKVAL() to evaluate the picklist field Severity__c against the target value 'Critical' and combines it with ISBLANK(Resolution_Plan__c) inside an AND() function. When both conditions are met (Severity is Critical and Resolution Plan is empty), the formula returns TRUE, preventing the record from being saved without a resolution plan.

Step-by-Step Solution

1
Identify the field types and required condition functions
Severity__c is a picklist field requiring ISPICKVAL(), and Resolution_Plan__c is a text field requiring ISBLANK() to check for missing input.
Salesforce formula syntax requires ISPICKVAL() to evaluate picklist values and ISBLANK() to accurately detect null or empty text values.
2
Combine the conditions into a single logical AND function
The validation rule formula AND(ISPICKVAL(Severity__c, "Critical"), ISBLANK(Resolution_Plan__c)) returns TRUE when Severity is Critical AND Resolution Plan is blank.
Validation rules display an error message when the formula expression evaluates to TRUE.

Key Concept

Validation Rule Logic and Picklist/Null Evaluation
Question 1399Question →

A Salesforce Administrator is setting up Einstein Activity Capture (EAC) for a team of sales executives using Microsoft 365. The company requires that emails and calendar events automatically sync between Microsoft 365 and Salesforce, while maintaining central control over sync directions and user access.

Which two steps must the administrator take to complete this setup? (Select 2 answers)

Select all that apply

Show answer & explanation

Answer: Assign the Standard Einstein Activity Capture permission set (or a custom permission set with EAC permissions) to the sales executives.; Create and configure an Einstein Activity Capture configuration setting to define sync direction and object sync behavior for the user group.

Answer

Assigning the standard or custom Einstein Activity Capture permission set to the users, and creating an Einstein Activity Capture configuration to define sync direction and object behavior.
Setting up Einstein Activity Capture requires two core administrative steps: granting user access via permission sets and defining the sync behavior (direction and data types) within an EAC configuration in Setup.

Step-by-Step Solution

1
Grant user permissions
Assigned users receive access to Einstein Activity Capture functionality.
EAC functionality requires license and permission entitlement, which is assigned via permission sets.
2
Define sync configurations
Sync direction (both ways, Salesforce to Exchange, or Exchange to Salesforce) and synced objects (emails, events, contacts) are established.
EAC configuration settings control how data flows between Salesforce and connected email and calendar accounts.

Key Concept

Einstein Activity Capture Provisioning and Sync Configurations
Question 1400Question →

An administrator is preparing Salesforce for an upcoming promotional event and wants to ensure support operations remain functional if customer inquiries spike. The administrator needs to verify how Salesforce handles web-generated cases if the organization exceeds its daily Web-to-Case limit.

Which statement accurately describes the system behavior when the daily Web-to-Case submission limit is exceeded?

Show answer & explanation

Answer: Submissions over the limit are rejected from online record creation, and the submitted case information is emailed to the Default Case Owner.

Answer

Submissions over the limit are rejected from online record creation, and the submitted case information is emailed to the Default Case Owner.
When an organization exceeds its daily Web-to-Case submission limit, Salesforce halts automatic case record creation in the database. To prevent customer inquiry loss, the system generates an email notification containing the submitted form data and sends it directly to the email address associated with the Default Case Owner specified in Web-to-Case settings.

Step-by-Step Solution

1
Identify the daily limit mechanism for Web-to-Case in Salesforce.
Salesforce imposes a maximum limit of 500 Web-to-Case submissions per 24-hour period (unless additional capacity is granted).
Governor limits ensure system stability across multi-tenant environments.
2
Determine the fallback mechanism configured in Web-to-Case settings.
Salesforce routes overflow submission data via email notification to the specified Default Case Owner rather than creating database records.
This prevents data loss during high-volume spikes while maintaining database governor limits.

Key Concept

Web-to-Case Daily Limits and Overflow Handling
PreviousPage 70 / 90Next
All practice questions — Salesforce Certified Administrator | Examkin