Examkin

Tüm alıştırma soruları

142 soru

Tüm türler1,784Çoktan seçmeli918Çoklu seçim587Eşleştirme142Sıralama137
Soru 1Soru →

Match each security and access control scenario for Global Logistics Corp to the appropriate Salesforce profile or field-level security (FLS) configuration setting.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

Completely restrict visibility of the sensitive field 'Executive_Audit_Notes__c' across all standard users regardless of page layout modifications.
Grant Read-Only visibility of the custom field 'Credit_Limit__c' to the Standard User profile while allowing full edit capability on the Finance profile.
Prevent users assigned to a specific custom profile from logging into Salesforce entirely when outside corporate network IP ranges.
Allow Sales Representatives to create, view, and modify custom 'Freight_Contract__c' records while explicitly revoking their capability to delete them.

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Each scenario maps to its underlying security level in Salesforce: sensitive field access to FLS hiding, profile-specific field editing to FLS visibility/read-only controls, network login enforcement to Profile Login IP Ranges, and record deletion restrictions to Object Permissions (CRUD).
Each business requirement aligns directly with Salesforce security controls: Field-Level Security governs data access at the field level regardless of UI controls, Object Permissions define baseline record CRUD privileges on profiles, and Profile Login IP Ranges enforce absolute network login restrictions.

Adım Adım Çözüm

1
Analyze field-level security vs. page layout security requirements.
Field accessibility across APIs, reports, and search requires FLS settings rather than page layout adjustments.
Page layouts only hide fields on the user interface; FLS secures the field at the data layer.
2
Evaluate object-level CRUD permissions.
Disabling record deletion for a group of users requires unchecking Delete under Object Permissions on their assigned profile.
Object permissions define the baseline record operations (Create, Read, Edit, Delete) available to users with that profile.
3
Differentiate between Profile Login IP Ranges and Organization-Wide Trusted IP Ranges.
Profile Login IP Ranges restrict login access completely outside specified ranges, whereas Org-Wide Trusted IP Ranges only bypass multi-factor authentication challenges.
Profile-level IP restrictions strictly enforce network boundaries for authentication.

Anahtar Kavram

Profiles and Object/Field-Level Security
Tahmini Süre:2m 0s
Soru 2Soru →

Match each business scenario involving Salesforce Page Layouts and Record Types with its correct administrative configuration action or framework behavior.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

A custom object requires that a Support Team profile can create 'Internal Ticket' records with specific picklist values, while preventing them from selecting 'External Ticket'.
An administrator needs to modify which detail page layout is displayed when a System Administrator views existing records assigned to the 'Contract Maintenance' record type.
A user granted a Permission Set containing access to a new Record Type reports seeing the fields from their profile's standard page layout rather than a specialized layout designed for that record type.
A Sales Representative needs a specific Record Type automatically pre-selected whenever they initiate creation of a new Account record without being prompted to choose.

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Each scenario correctly pairs with its administrative mechanism: Restricting available record types and picklist values is configured in Profile Record Type Settings; Changing layout visibility across record types requires updating the Page Layout Assignment matrix; Page Layouts are assigned strictly by Profile rather than Permission Sets; Auto-selecting a record type on creation is controlled by the Profile/User Default Record Type setting.
In Salesforce, Record Types allow administrators to offer different business processes, picklist values, and page layouts to different users. Configuring available record types and picklist values is executed in Profile Record Type Settings. Page Layout assignment is governed by a matrix combining Profile and Record Type. Crucially, while Permission Sets can grant access to additional Record Types, they do not possess their own Page Layout assignment capabilities; page layout display is always driven by the Profile's matrix configuration. Lastly, setting a Default Record Type on a user's Profile automates record type selection during record creation.

Adım Adım Çözüm

1
Analyze profile record type visibility and picklist scoping requirements.
Identified that enabling specific record types and restricting picklist values is managed in Profile Record Type settings.
Record Types drive picklist value availability, and profile assignments dictate creation availability.
2
Determine how Page Layouts are mapped to Profiles and Record Types.
Mapped the requirement to update viewable page layouts to the Object Manager Page Layout Assignment matrix.
Salesforce uses a matrix of Profile × Record Type = Page Layout.
3
Evaluate the architectural distinction between Profile layout assignment and Permission Sets.
Recognized that Permission Sets grant record type access but do not assign Page Layouts.
Page layout assignments remain tied to the user's assigned Profile.
4
Identify default creation behavior configurations.
Matched pre-selection of record types to Default Record Type profile/user settings.
Setting a default record type skips the selection dialog on creation.

Anahtar Kavram

Page Layout and Record Type Assignment Architecture
Soru 3Soru →

Match each Salesforce Service Cloud administration component to its corresponding function when configuring case management.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

Support Process
Case Record Type
Page Layout
Case Status Picklist

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Support Process matches with defining lifecycle stage values before record type creation; Case Record Type matches with linking a Support Process to page layouts and picklist values; Page Layout matches with arranging fields, sections, and related lists on the detail page; Case Status Picklist matches with being the standard field governed by a Support Process.
Each component plays a distinct role in case setup: Support Processes configure the Case Status lifecycle options; Case Record Types link Support Processes to user profiles and page layouts; Page Layouts handle visual organization; and the Case Status field holds the lifecycle state governed by the Support Process.

Adım Adım Çözüm

1
Identify the prerequisite component for Case Status picklist customization
Recognize that Support Process defines available Status picklist values before creating a Case Record Type.
Salesforce requires a Support Process to determine the case lifecycle prior to associating it with a Record Type.
2
Determine the role of Case Record Types in case management
Connect Case Record Type with assigning Page Layouts and associating the Support Process.
Record types bridge business processes (Support Process) with user experience (Page Layouts and non-status picklist values).
3
Differentiate Page Layouts and Case Status Picklist roles
Map Page Layout to field positioning/UI design, and Case Status Picklist to the governed lifecycle field.
Page layouts determine visual UI elements, while the status picklist tracks stage progression.

Anahtar Kavram

Support Process and Case Record Type Dependencies
Soru 4Soru →

An administrator at a healthcare organization is configuring Salesforce Knowledge access and Data Category visibility for various internal and external user groups. Match each operational role requirement on the left to its corresponding Salesforce Knowledge configuration setting on the right.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

Care Coordinators who require capabilities to create, edit, publish, and archive internal clinical guidance articles.
Unauthenticated patients visiting the public portal who must only see published articles categorized under wellness and public health.
Financial Compliance Officers who must be guaranteed access to all articles across every Data Category Group regardless of default category restrictions.
Helpdesk Support Agents who possess Read access to Knowledge articles but are currently unable to view articles assigned to specific subtopics.

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Authoring and publishing articles requires assigning the Knowledge User feature license and object management permissions; public unauthenticated access relies on Guest User Profile Data Category Visibility combined with Public Channel publishing; unrestricted access across all categories is granted by setting Data Category Visibility to 'All'; and missing article access despite having Read permissions is resolved by adjusting Data Category Group Visibility settings on the user's Profile or Permission Set.
Salesforce Knowledge security uses a multi-layered model. Feature licenses enable authoring capabilities, object permissions grant baseline record interaction, channels control audience exposure (e.g., Public Channel for guest users), and Data Categories control row-level article visibility based on user profiles or permission sets.

Adım Adım Çözüm

1
Analyze Knowledge user licensing and permissions for authoring roles.
Care Coordinators need the Knowledge User feature license checkbox checked on their user detail page in addition to Create/Edit/Publish permissions.
Without the feature license, users cannot access Knowledge publishing tools regardless of profile permissions.
2
Evaluate unauthenticated portal guest access requirements.
Unauthenticated patients rely on the Guest User Profile for Data Category Visibility and require articles to be published to the Public Knowledge channel.
Guest access is controlled at the profile level and requires channel-specific publishing.
3
Determine configuration for total visibility across all category groups.
Set Data Category Visibility to 'All' for Financial Compliance Officers.
Explicitly setting visibility to 'All' grants access to all categories within a category group, overriding default restrictions.
4
Troubleshoot missing article visibility for support agents.
Adjust Data Category Group Visibility on the helpdesk agents' Profile or Permission Set.
Data Category visibility acts as a row-level filter; if a category is restricted (e.g., set to 'None'), users cannot view articles in that category even with object Read permission.

Anahtar Kavram

Salesforce Knowledge Data Category Visibility and License Management
Soru 5Soru →

A Salesforce administrator is configuring email integration features and template access controls across various department units. Match each enterprise business scenario on the left to its correct Salesforce technical configuration mechanism on the right.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

Sales representatives require the ability to create public Lightning Email Templates containing related object fields and manage shared template folder permissions.
Different sales teams using the Outlook Integration require customized action buttons and record detail layouts inside their Outlook side pane based on their user profile.
The IT security team mandates that all outbound emails originating from Salesforce must be routed through the organization's Microsoft Exchange server for DKIM compliance and auditing.
Sales representatives using Gmail require automatic background logging of sent and received emails to Salesforce records without manual user intervention, while excluding internal personal communications.

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

1. Public Lightning template creation and folder management matches granting the 'Create Lightning Email Templates' permission set and configuring folder access permissions.
2. Profile-specific Outlook panel customization matches creating Email Application Panes in Lightning App Builder and assigning them via Email Application Publisher Assignments.
3. Outbound corporate server email routing matches configuring Email Relay with Domain Filters.
4. Automated Gmail activity logging with domain exclusion matches deploying Einstein Activity Capture with Excluded Addresses lists.
Each administrative requirement corresponds directly to its dedicated Salesforce feature: Lightning Email Templates permissions govern shared template management; Email Application Panes customize the desktop add-in user interface; Email Relay directs mail through external corporate servers; and Einstein Activity Capture handles automated email sync with domain exclusion filters.

Adım Adım Çözüm

1
Analyze requirement 1: Creating and managing public Lightning Email Templates.
Identified that standard users cannot share or edit public Lightning templates without explicit permission ('Create Lightning Email Templates') and folder access setup.
Profile modifications for standard user permissions are restricted; permission sets and folder sharing controls are the standard administrative path.
2
Analyze requirement 2: Customizing side pane layouts in Outlook Integration by profile.
Identified Email Application Panes in Lightning App Builder as the component used to customize the side pane layout for Outlook/Gmail integration.
Email Application Publisher Assignments govern which profile sees which customized side pane layout in the integration add-in.
3
Analyze requirement 3: Routing outbound Salesforce mail through internal Microsoft Exchange server.
Identified Salesforce Email Relay as the feature designed to send outbound email through company SMTP servers.
Email Relay guarantees DKIM alignment and compliance by leveraging internal security infrastructure.
4
Analyze requirement 4: Automated email logging with domain exclusion rules for Gmail users.
Identified Einstein Activity Capture (EAC) as the solution for passive, automated sync, paired with Excluded Addresses to filter personal domains.
Standard Gmail Integration requires manual logging per email, whereas EAC provides automated sync with privacy filtering capabilities.

Anahtar Kavram

Salesforce Outlook and Gmail Integration Architecture and Email Template Administration
Soru 6Soru →

A Salesforce Administrator is evaluating different types of AppExchange productivity solutions to extend organizational functionality. How should each AppExchange solution type be matched to its primary technical characteristic and governance model?

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

Managed Package
Unmanaged Package
Salesforce Labs Package
Flow Solutions

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Managed Package pairs with upgradable solution with locked Apex code; Unmanaged Package pairs with non-upgradable container of editable components; Salesforce Labs Package pairs with free, open-source utilities created by Salesforce employees without official support; Flow Solutions pairs with pre-packaged automation templates and actions for Flow Builder.
Each AppExchange distribution model addresses specific technical and operational criteria: Managed Packages provide vendor maintenance and IP protection; Unmanaged Packages grant full ownership of editable components; Salesforce Labs offers unsupported free employee-built apps; and Flow Solutions expand declarative automation within Flow Builder.

Adım Adım Çözüm

1
Analyze the upgradeability and code visibility of commercial AppExchange packages.
Managed packages protect vendor IP and allow seamless upgrades, whereas unmanaged packages act like single-instance starter templates with fully exposed code.
This establishes the fundamental governance distinction between managed and unmanaged AppExchange distributions.
2
Evaluate the origin, support structure, and cost of Salesforce Labs offerings.
Salesforce Labs solutions are free, community-oriented tools developed by Salesforce employees, hosted on AppExchange without official support SLAs.
Salesforce Labs provides utility packages as open-source templates without standard product warranties.
3
Identify the functional target of Flow Solutions on AppExchange.
Flow Solutions explicitly provide pre-built flow elements and processes to accelerate declarative automation in Flow Builder.
Flow Solutions specifically enhance flow creation through pre-configured partner components.

Anahtar Kavram

AppExchange Solution Types and Packaging Governance
Soru 7Soru →

An administrator is configuring Einstein Activity Capture (EAC) settings for sales representatives using Microsoft Exchange. Match each EAC configuration setting to its corresponding operational behavior.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

Both ways sync direction
Exchange to Salesforce sync direction
Salesforce to Exchange sync direction
Excluded Addresses list

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Both ways sync direction matches bidirectional updates across both platforms; Exchange to Salesforce sync direction matches importing Exchange changes into Salesforce only; Salesforce to Exchange sync direction matches exporting Salesforce changes to Exchange only; Excluded Addresses list matches preventing specific domain or address activity from being logged.
Each Einstein Activity Capture configuration setting governs specific data transfer behavior: 'Both ways' provides bi-directional sync, 'Exchange to Salesforce' handles inbound-only sync, 'Salesforce to Exchange' handles outbound-only sync, and the 'Excluded Addresses' list enforces privacy filtering for targeted email domains and addresses.

Adım Adım Çözüm

1
Identify bidirectional synchronization requirements.
Map 'Both ways sync direction' to the option stating changes in either Salesforce or Exchange update both systems.
Bidirectional sync requires continuous parity between connected environments.
2
Identify inbound-only synchronization requirements.
Map 'Exchange to Salesforce sync direction' to the option where Exchange edits update Salesforce, but Salesforce edits do not push back.
Inbound sync prioritizes the external mail server as the single source of origin.
3
Identify outbound-only synchronization requirements.
Map 'Salesforce to Exchange sync direction' to the option where Salesforce edits push to Exchange, but direct Exchange edits are ignored.
Outbound sync uses Salesforce as the primary record source for external updating.
4
Identify privacy and exclusion configuration settings.
Map 'Excluded Addresses list' to preventing specific internal email domains or sensitive addresses from being automatically captured.
Exclusions explicitly prevent sensitive communications from showing up on record activity timelines.

Anahtar Kavram

Einstein Activity Capture Sync Directions and Exclusions
Soru 8Soru →

A Salesforce administrator is configuring automated case intake mechanisms to meet specific organizational security, infrastructure, and volume requirements. Match each case capture mechanism to its corresponding technical architecture or operational capability.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

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

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Web-to-Case matches with generating web form HTML with a default 5,000 daily request limit and default owner overflow routing. On-Demand Email-to-Case matches with processing emails entirely in the Salesforce cloud with a 25 MB maximum size limit. Email-to-Case Agent matches with requiring software installed behind the network firewall to keep traffic internal and handle attachments larger than 25 MB.
Web-to-Case provides HTML code generation with a 5,000 daily request ceiling and routes overflow to the default owner. On-Demand Email-to-Case processes emails up to 25 MB completely in the Salesforce cloud. Email-to-Case Agent uses installed software inside the corporate firewall to keep network traffic internal and handle attachments exceeding 25 MB.

Adım Adım Çözüm

1
Identify the attributes of Web-to-Case
Web-to-Case uses HTML forms embedded on web pages, enforces a default maximum limit of 5,000 requests daily, and directs invalid or overflow requests to the default case creation user.
Distinguish web-based intake mechanisms from email-based mechanisms.
2
Analyze On-Demand Email-to-Case architecture
On-Demand Email-to-Case processes incoming emails using Salesforce cloud infrastructure, removing the need for internal server agents while enforcing a 25 MB total email size limit.
Identify cloud-based email handling characteristics and limits.
3
Analyze Email-to-Case Agent architecture
The Email-to-Case Agent requires local software installed behind the corporate firewall, keeping traffic local and enabling support for email attachments over 25 MB.
Identify firewall and file size requirements unique to the installed agent approach.

Anahtar Kavram

Case Capture Mechanisms (Web-to-Case and Email-to-Case)
Soru 9Soru →

Match each Salesforce Chatter group role or member designation on the left with its corresponding functional permission or visibility behavior on the right. Which pairs correctly match each role to its operational capability?

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

Group Owner
Group Manager
Broadcast Group Manager / Owner
External Member (Customer/Partner)

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Group Owner pairs with full administrative control including group deletion and ownership transfer; Group Manager pairs with member and settings management excluding group deletion; Broadcast Group Manager/Owner pairs with exclusive post-authoring privileges in broadcast settings; and External Member pairs with the orange badge visual distinction and group-restricted visibility.
Each role correctly aligns with its Salesforce platform governance model: Group Owners possess full lifecycle rights including deletion; Group Managers handle daily administrative tasks; Broadcast group leads retain posting exclusivity; and external users receive visual highlighting alongside strict containerized access.

Adım Adım Çözüm

1
Analyze Group Owner capabilities
Group Owner is the highest authority level for a Chatter group, granting rights to delete the group and transfer ownership.
Salesforce security hierarchy enforces that only the owner or system administrator can perform destructive or ownership-changing actions.
2
Analyze Group Manager capabilities
Group Managers can adjust group information, promote regular members, and remove posts, but cannot delete the group.
Delegated group management allows operational support without granting destructive group permissions.
3
Evaluate Broadcast Group posting rules
In broadcast groups, regular members cannot start new posts; only owners and managers have post creation rights.
Broadcast groups are designed specifically for official announcements and top-down communications.
4
Identify External Member characteristics
External members are tagged with orange banners/badges and limited to content within their assigned group.
Salesforce Chatter privacy mechanisms ensure internal data is protected when collaborating with external users.

Anahtar Kavram

Chatter Group Roles, Capabilities, and Special Group Access Controls
Soru 10Soru →

A system administrator at a SaaS company is configuring Experience Cloud for customer self-service support. Match each business requirement to the correct Salesforce configuration or feature.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

Grant external users with standard Customer Community licenses read access to all Cases associated with their parent Account.
Prevent internal executive roles from automatically inheriting access to portal-owned records via role hierarchy when External OWD is Private.
Allow a client's designated manager to create new portal user accounts and reset passwords for contacts belonging to their company.
Enable unauthenticated website visitors to search and view published support Knowledge articles without prompting for a login.

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Matching pairings: 1) Account Case access for standard Customer Community licenses maps to Sharing Sets. 2) Restricting role hierarchy access maps to deselecting 'Grant Access Using Hierarchies'. 3) External user creation by customer managers maps to Customer Community Plus licenses with Delegated External User Administration. 4) Unauthenticated Knowledge search maps to enabling Public Access and configuring the Guest User Profile.
Each requirement correctly pairs with its Salesforce Experience Cloud capability: Customer Community record access across accounts requires Sharing Sets due to lack of role access; hierarchy access restrictions require deselecting 'Grant Access Using Hierarchies'; delegated admin features require Customer Community Plus licenses with roles; and unauthenticated access requires Experience Builder Public Access and Guest User Profile permissions.

Adım Adım Çözüm

1
Analyze license capabilities and record sharing mechanisms for Customer Community users.
Standard Customer Community users do not utilize roles or criteria-based sharing rules, requiring Sharing Sets to grant access to Cases associated with their Account.
Sharing Sets use account/contact lookup relationships to grant access to external community members efficiently.
2
Evaluate role hierarchy override settings for external sharing models.
Deselecting 'Grant Access Using Hierarchies' disables record visibility escalation up the internal role hierarchy for custom objects.
This enforces strict record privacy boundaries when External Org-Wide Defaults are set to Private.
3
Determine licensing requirements for delegated administrative capabilities.
Delegated External User Administration requires roles, which are supported by Customer Community Plus or Partner Community licenses.
Standard Customer Community licenses lack role functionality required for user administration privileges.
4
Review configuration steps for anonymous guest user access.
Public Access in Experience Builder combined with Guest User Profile permissions exposes published Knowledge articles to unauthenticated visitors.
Guest User Profiles define security access for unauthenticated portal traffic.

Anahtar Kavram

Experience Cloud Licensing Capabilities and External Security Architecture
Soru 11Soru →

A Salesforce administrator is reviewing data management requests across different departments. Match each operational requirement on the left with the appropriate native Salesforce data tool or configuration on the right.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

Upsert 4,000 Contact records while applying active matching rules to prevent duplicates and executing workflow rules directly within a browser interface.
Insert 75,000 Opportunity records from an external system mapped using a custom External ID field.
Permanently delete 120,000 archived Case records from the Salesforce database, completely bypassing the Recycle Bin.
Execute an unattended, scheduled nightly export of Account data saved directly to a local directory server file.

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

1. Upserting 4,000 Contacts with browser-based duplicate detection and workflow rules matches Data Import Wizard.
2. Inserting 75,000 Opportunities using an External ID matches Data Loader Desktop User Interface.
3. Permanently deleting 120,000 Cases bypassing the Recycle Bin matches Data Loader using Bulk API with Hard Delete enabled.
4. Scheduled unattended nightly exports match Data Loader Command Line Interface (CLI).
Each requirement directly aligns with key operational distinctions between native Salesforce utilities: Data Import Wizard is ideal for browser-driven tasks under 50,000 records with duplicate checking; Data Loader UI supports larger volumes (>50,000) and objects like Opportunities; Data Loader with Bulk API is required for hard deletes; and Data Loader CLI is required for scheduled automated script execution.

Adım Adım Çözüm

1
Analyze requirement 1 (4,000 Contacts, duplicate checking, browser-based, workflow execution).
Identify Data Import Wizard as the tool matching <50,000 volume limit, browser access, native Contact duplicate prevention, and workflow triggering.
Data Import Wizard is designed for browser-based operations under 50,000 records for specific standard objects (Accounts, Contacts, Leads, Solutions) and custom objects.
2
Analyze requirement 2 (75,000 Opportunities, External ID mapping).
Identify Data Loader Desktop UI because Opportunity is an unsupported standard object in Data Import Wizard, and the record volume exceeds 50,000.
Data Import Wizard cannot load Opportunities and has a hard limit of 50,000 records.
3
Analyze requirement 3 (120,000 soft-deleted Cases, purge from Recycle Bin).
Identify Data Loader using Bulk API with Hard Delete enabled.
Data Import Wizard cannot perform hard deletes. Hard delete requires Bulk API enabled in Data Loader settings along with administrative permissions.
4
Analyze requirement 4 (Unattended, automated nightly scheduled export).
Identify Data Loader CLI.
Data Import Wizard does not support command-line automation or scheduled background execution.

Anahtar Kavram

Selecting between Data Import Wizard and Data Loader based on record limits, supported objects, automation capabilities, operation types, and execution modes.
Tahmini Süre:3m 0s
Soru 12Soru →

An administrator at Nexus Industrial Solutions is configuring the Lightning Sales Console to increase the efficiency of inside sales representatives. Match each Salesforce sales productivity feature to the business requirement it fulfills.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

Macros
History Utility Component
Split View
Interaction Log

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Macros match with automating multi-step routine tasks in a single click; History Utility Component matches with reopening recently visited records from the bottom bar; Split View matches with working through a list of leads alongside open record details; Interaction Log matches with capturing call notes and activity details on the active record page.
Each feature corresponds precisely to its productivity function in Salesforce Sales Console: Macros execute multi-step user actions; History Utility component tracks and reopens recently viewed console tabs; Split View lets reps process list views alongside active record details; and Interaction Log provides inline call note taking on record pages.

Adım Adım Çözüm

1
Identify the core capability of Macros in Salesforce Console.
Macros execute predefined repetitive tasks automatically (e.g., updating fields, sending emails, creating tasks).
Matching Macros to automating multi-step routine tasks.
2
Identify the primary function of the History Utility Component.
It appears in the Utility Bar and keeps track of recent workspace items and tabs for fast navigation.
Matching History Utility Component to reopening recently visited records.
3
Analyze how Split View changes user navigation in Lightning Console.
Split View docks a collapsible list view on the left side of the workspace while the active record remains on the right.
Matching Split View to working through lead lists side-by-side with record details.
4
Analyze the purpose of the Interaction Log component.
It displays an inline panel on console record layouts specifically for logging call notes and activities.
Matching Interaction Log to capturing call notes on the active record.

Anahtar Kavram

Lightning Sales Console Productivity Features
Soru 13Soru →

A Salesforce Administrator is configuring Salesforce Knowledge access controls and article publishing settings for a global support team. Match each Salesforce Knowledge administration component on the left to its correct function or configuration requirement on the right.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

Knowledge User Feature License
Data Category Group Visibility
Article Action Permissions
Public Knowledge Channel Setting

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Knowledge User Feature License matches with enabling the checkbox on User records; Data Category Group Visibility matches with controlling access to classification hierarchies via Profiles, Permission Sets, or Roles; Article Action Permissions match with granting granular publishing lifecycle privileges; Public Knowledge Channel Setting matches with dictating article visibility for unauthenticated guest users.
Each Knowledge component serves a distinct administrative purpose: Feature Licenses unlock authoring tools on user records, Data Category Visibility controls taxonomic article access via profiles/permission sets/roles, Article Action Permissions grant granular lifecycle operations (Publish/Archive), and Channel Settings govern external audience exposure.

Adım Adım Çözüm

1
Identify user licensing requirements for Salesforce Knowledge authoring
Determine that authoring access requires the Knowledge User feature license checkbox enabled on the user record.
Object permissions alone do not grant article authoring capabilities without the feature license.
2
Evaluate classification security and visibility mechanisms
Associate Data Category Group Visibility with profile, permission set, or role configuration.
Data category visibility controls access to article classification trees independently of standard object permissions.
3
Differentiate between publication workflow permissions and distribution channels
Map Article Actions to publishing workflow privileges and Public Knowledge channels to guest user access.
Article Actions manage the internal content lifecycle while Channels manage target distribution endpoints.

Anahtar Kavram

Salesforce Knowledge Provisioning, Security, and Publication Channels
Soru 14Soru →

A Salesforce administrator needs to select the correct utility for several distinct data operations across the organization. Match each operational data requirement on the left with the most appropriate tool or capability on the right.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

Importing 30,000 Account records while enforcing duplicate checking and triggering workflow rules.
Permanently deleting 10,000 obsolete Case records so that they bypass the Recycle Bin.
Configuring an automated, unattended nightly export of 200,000 Opportunity records.
Upserting 120,000 Custom Object records using an External ID field to map relationships.

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Matching pairs: 1) Importing 30,000 Accounts with workflow and duplicate rules matches Data Import Wizard. 2) Hard deleting 10,000 Cases bypassing Recycle Bin matches Data Loader (GUI with 'Use Bulk API' and 'Hard Delete' setting). 3) Automated nightly export of 200,000 Opportunities matches Data Loader CLI (Command Line Interface). 4) Upserting 120,000 Custom Object records via External ID matches Data Loader (GUI with Bulk API enabled).
Each requirement correctly aligns with tool limits and feature sets: Data Import Wizard is limited to 50,000 records and supports duplicate checking and workflow triggers; Data Loader supports up to 5,000,000 records, hard deletion via Bulk API, command-line automation, and export operations.

Adım Adım Çözüm

1
Evaluate record volumes and standard feature requirements for import.
30,000 Accounts is under the 50,000 limit for Data Import Wizard, which specifically supports Accounts, duplicate checking, and workflow automation triggering.
Data Import Wizard is the best fit for browser-based imports under 50k records requiring duplicate prevention.
2
Evaluate hard delete requirements.
Only Data Loader supports delete and hard delete operations. Hard delete requires Bulk API enabled and special user permissions.
Data Import Wizard cannot delete records.
3
Evaluate automated scheduled operations and export requirements.
Data Loader CLI allows command-line parameters to be run automatically by operating system schedulers. Data Import Wizard does not support exports or automated scheduling.
Unattended automated data tasks require Data Loader CLI.
4
Evaluate large volume upsert requirements (>50,000 records).
120,000 records exceeds the Data Import Wizard limit of 50,000 records. Data Loader with Bulk API must be used.
Data Loader supports up to 5 million records and optimizes performance for >50k batches via Bulk API.

Anahtar Kavram

Selecting between Data Import Wizard and Data Loader based on record volume limits, operation types (import/export/delete/hard delete), duplicate detection, and automation capabilities.
Tahmini Süre:2m 0s
Soru 15Soru →

A Salesforce administrator is implementing data quality controls across various objects in an organization. Match each business requirement with the correct validation rule formula expression designed to enforce that data quality requirement.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

Prevent users from modifying the Discount Percentage field after an Opportunity has already reached the 'Closed Won' stage.
Enforce that a custom Tax Identification Number field matches a specific format of two uppercase letters followed by six numerical digits whenever it is populated.
Require the Phone field to be populated whenever a Lead record rating is set to 'Hot'.
Prevent a Project Target Completion Date from being set to a date prior to the record's creation date.

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Matching pairings: Preventing modifications to Discount Percentage after Closed Won matches AND(ISPICKVAL(PRIORVALUE(StageName), 'Closed Won'), ISCHANGED(Discount_Percentage__c)); Validating Tax ID format matches AND(NOT(ISBLANK(Tax_ID__c)), NOT(REGEX(Tax_ID__c, '[A-Z]{2}[0-9]{6}'))); Requiring Phone for Hot Leads matches AND(ISPICKVAL(Rating, 'Hot'), ISBLANK(Phone)); Enforcing Target Completion Date after CreatedDate matches Target_Completion_Date__c < DATEVALUE(CreatedDate).
Each validation formula expression correctly models the specific business requirement using Salesforce formula functions: PRIORVALUE and ISCHANGED monitor field edits relative to previous values; REGEX combined with NOT(ISBLANK) validates pattern compliance; ISPICKVAL combined with ISBLANK enforces mandatory inputs; and DATEVALUE normalizes DateTime fields for comparison.

Adım Adım Çözüm

1
Analyze requirement 1 (preventing changes after stage completion)
Identified that PRIORVALUE(StageName) checks historical state before edit, and ISCHANGED(Discount_Percentage__c) detects field edits.
Validation rules evaluate to TRUE to block saving; checking PRIORVALUE ensures past stage state is evaluated.
2
Analyze requirement 2 (pattern matching on populated text fields)
Identified REGEX for format matching and NOT(ISBLANK()) to skip blank entries.
Regular expressions allow precise pattern criteria matching such as two uppercase letters followed by six numbers.
3
Analyze requirement 3 (conditionally required fields based on picklist value)
Identified ISPICKVAL for picklist evaluation combined with ISBLANK for detecting null/missing phone values.
Validation rules trigger when formula condition evaluates to TRUE, meaning Rating is 'Hot' AND Phone is blank.
4
Analyze requirement 4 (date field comparison against system creation date)
Identified DATEVALUE function to convert CreatedDate (DateTime) to Date for direct comparison with Target_Completion_Date__c.
Date and DateTime fields cannot be compared directly without type conversion using DATEVALUE.

Anahtar Kavram

Salesforce Validation Rule Formula Functions and Data Quality Enforcement
Soru 16Soru →

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.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

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

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

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.

Adım Adım Çözüm

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.

Anahtar Kavram

Selecting and configuring Quick Actions, Custom Buttons, and Links based on context and capability requirements
Tahmini Süre:1m 30s
Soru 17Soru →

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.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

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.

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

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.

Adım Adım Çözüm

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.

Anahtar Kavram

Einstein Activity Capture Configurations and Synchronization Settings
Soru 18Soru →

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

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

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

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

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.

Adım Adım Çözüm

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.

Anahtar Kavram

Salesforce Validation Rule Formula Functions
Soru 19Soru →

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.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

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

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

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.

Adım Adım Çözüm

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.

Anahtar Kavram

Page Layouts and Record Types Assignment Matrix & Permission Settings
Tahmini Süre:1m 30s
Soru 20Soru →

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.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

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.

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

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.

Adım Adım Çözüm

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.

Anahtar Kavram

Selecting between Data Import Wizard and Data Loader utilities based on object support, volume limits, operational requirements (hard delete, workflow triggers), and automation capabilities.
Sayfa 1 / 8Sonraki
Tüm alıştırma soruları — Salesforce Certified Administrator | Examkin