Examkin

All practice questions

1784 questions

All types1,784Multiple choice918Multiple select587Matching142Ordering137
Question 41Question →

BrightPath Health requires strict data privacy for sensitive patient information on a custom object named Patient Record. Currently, all 40 clinical coordinators share the custom 'Clinical Coordinator' profile. The management team requires that only 4 compliance auditors can view and edit the national_insurance_id__c field. Furthermore, access to this field must be restricted at the API and reporting levels, not just on the user interface. Which two steps should the Salesforce Administrator take to meet these security requirements? (Choose 2 answers.)

Select all that apply

Show answer & explanation

Answer: Set Field-Level Security on the national_insurance_id__c field to remove Read and Edit access from the Clinical Coordinator profile.; Create a Permission Set that grants Read and Edit access to national_insurance_id__c and assign it to the 4 compliance auditors.

Answer

The administrator should restrict access on the base profile using Field-Level Security (FLS) and extend field permissions to the four compliance auditors using a Permission Set.
Field-Level Security (FLS) on the base profile secures the field across all interfaces (UI, API, reports). A Permission Set is then used to grant additive read/edit access specifically to the users who need it, adhering to Salesforce security best practices.

Step-by-Step Solution

1
Configure Field-Level Security on the Clinical Coordinator profile
Field access to national_insurance_id__c is restricted for all clinical coordinators across UI, reports, and API.
FLS enforces field-level security across all data access channels in Salesforce.
2
Create and assign a Permission Set for the compliance auditors
The four compliance auditors are granted Read and Edit permissions for national_insurance_id__c.
Permission sets add permissions on top of profile access for specific individuals.

Key Concept

Profiles restrict base Field-Level Security while Permission Sets extend field permissions to specific users.
Question 42Question →

An administrator at Northern Trail Outfitters is enhancing the Lightning Sales Console to increase rep efficiency when managing Accounts and child Opportunities. Sales reps need to inspect related Account details and Contact records as subtabs under the main Opportunity workspace tab, while also executing standardized multi-step record updates with a single click from the console footer. Which combination of configurations meets these requirements?

Show answer & explanation

Answer: Configure console tab navigation rules to open Account and Contact records as subtabs of the Opportunity workspace tab, and add the Macros component to the Sales Console Utility Bar.

Answer

Configure console tab navigation rules to open Account and Contact records as subtabs of the Opportunity workspace tab, and add the Macros component to the Sales Console Utility Bar.
The correct answer configures console tab navigation rules in the App Manager to open child/related records as subtabs under the main workspace tab, and adds the Macros component to the Utility Bar for rapid execution of repetitive multi-step actions.

Step-by-Step Solution

1
Identify workspace tab and subtab requirements
Console navigation rules must be configured in App Manager so related Account/Contact records open as subtabs under the Opportunity workspace tab.
This keeps reps within a single focused workspace tab while reviewing related context.
2
Identify productivity tool for repetitive multi-step updates
Add the Macros utility to the Utility Bar of the Sales Console App.
Macros allow sales reps to automate common multi-step tasks (such as updating field values and sending emails) directly from the console footer.

Key Concept

Sales Console navigation rules and Macros utility integration
Question 43Question →

Solaris Energy is expanding its Service Cloud capabilities by establishing a dedicated Warranty Claims team alongside its existing Customer Care team. The Warranty Claims team requires a unique set of Case Status values to track RMA approvals and replacement shipments, as well as a customized page layout. The administrator created the new custom page layout and defined the required Case Status picklist values on the Case object. However, when support representatives create a new Warranty Claim case, the newly added status values do not appear in the Status picklist. Which two configuration steps must the administrator complete to make the new Case Status values available? (Choose 2 answers)

Select all that apply

Show answer & explanation

Answer: Create a new Support Process that includes the specific Case Status values required for Warranty Claims.; Associate the newly created Support Process with the Warranty Claims Case Record Type.

Answer

The administrator must create a new Support Process containing the required Case Status values and then assign that Support Process to the Warranty Claims Case Record Type.
On the Case object, the Case Status field is controlled by a Support Process. To display custom Case Status values on a specific record type, an administrator must first create a Support Process containing those values and subsequently assign that Support Process to the corresponding Case Record Type.

Step-by-Step Solution

1
Identify the dependency mechanism for Case Status picklist values in Salesforce.
Case Status values are controlled strictly by Support Processes, which serve as master picklist filters for different business lifecycles.
Standard picklist configuration on the object level is insufficient for Case Status because it depends on Support Process definitions.
2
Define a new Support Process for Warranty Claims.
A customized Support Process is configured containing only the specific Case Status lifecycle stages needed by the Warranty Claims team.
Support Processes must exist prior to creating or configuring Case Record Types that rely on customized status flows.
3
Link the Support Process to the Case Record Type.
The Warranty Claims Case Record Type is assigned the newly defined Support Process and linked to its respective Page Layout.
A Case Record Type cannot display unique Case Status values until it is linked to a valid Support Process.

Key Concept

Support Processes and Case Record Types
Question 44Question →

A Salesforce administrator at a renewable energy company is setting up a new data model to manage customer service agreements. The design involves establishing relationships between the standard Account object and a newly created custom object named Solar_Tracker__c. Which TWO statements correctly describe the capabilities and limitations of standard objects versus custom objects in Salesforce? (Select 2)

Select all that apply

Show answer & explanation

Answer: Standard objects can act as the master side in a master-detail relationship, but cannot be the detail child object in a master-detail relationship with a custom object.; Custom objects can be deleted from an organization, whereas standard objects cannot be deleted.

Answer

Standard objects can serve as the master parent but cannot be the detail child object in a master-detail relationship with a custom object, and custom objects can be deleted whereas standard objects cannot be deleted.
Standard objects can serve as the master parent object in a master-detail relationship with a custom detail object, but standard objects can never be on the detail side of a master-detail relationship. Additionally, custom objects can be deleted from an org if they are not referenced elsewhere, while standard objects cannot be deleted.

Step-by-Step Solution

1
Evaluate relationship hierarchy constraints between standard and custom objects.
Standard objects can exist on the master side of a master-detail relationship with custom child objects, but a standard object cannot be made a child detail object to a custom master object.
Salesforce architecture restricts standard objects from being dependent detail records under custom objects.
2
Evaluate deletion lifecycle rules for standard vs custom objects.
Custom objects can be deleted when no longer required, but standard objects cannot be deleted from an org.
Standard objects are foundational components of the Salesforce core application.
3
Verify roll-up summary field prerequisites and cascading deletion behavior.
Roll-up summaries require master-detail relationships, not lookups. Deleting detail records does not delete parent master records.
Roll-up calculations depend on master-detail relationship coupling, and deletion cascades top-down, not bottom-up.

Key Concept

Standard vs Custom Object Relationship and Lifecycle Constraints
Question 45Question →

Vanguard Global Tech needs to restrict access to a sensitive custom field, Base_Salary__c, on the Employee__c object so that only two HR Specialists out of fifty HR team members can view and edit it. Additionally, compliance mandates that all users assigned to the Standard HR Profile must be blocked from logging into Salesforce if they are outside the corporate network IP range. Which two administrative actions should the Salesforce Administrator take to satisfy these security requirements? (Choose 2 answers)

Select all that apply

Show answer & explanation

Answer: Create a Permission Set granting Read and Edit access for the Base_Salary__c field and assign it exclusively to the two HR Specialists.; Specify the corporate network IP range in the Login IP Ranges settings of the Standard HR Profile.

Answer

The correct administrative actions are creating a Permission Set granting Read and Edit access to the sensitive field for the two HR Specialists, and defining the corporate network IP range under Login IP Ranges on the Standard HR Profile.
Creating a Permission Set allows the administrator to selectively grant Read and Edit Field-Level Security (FLS) to the two HR Specialists without altering the access of other users on the Standard HR Profile. Configuring Login IP Ranges directly on the Standard HR Profile enforces hard restrictions that prevent any user with that profile from logging in outside the designated corporate network IPs.

Step-by-Step Solution

1
Evaluate field-level security requirements for a subset of users on the same profile.
Keep field-level security restricted (no access) on the base profile for all fifty HR team members, and create a Permission Set with Read and Edit access assigned only to the two HR Specialists.
Permission sets provide additive permissions for specific users, avoiding profile proliferation.
2
Evaluate login restriction requirements for all users on the Standard HR Profile.
Configure the corporate IP range within the Login IP Ranges section of the Standard HR Profile.
Profile-level Login IP Ranges enforce strict login blocking outside the designated ranges.

Key Concept

Profiles control base restrictions (such as Login IP Ranges), while Permission Sets extend additive access (such as Field-Level Security) to subset user groups.
Estimated Time:1m 30s
Question 46Question →

An administrator at Global Logistics needs to ensure that incoming support records are automatically routed to specific support queues based on the product area specified by the customer upon record creation. Which automation feature should be configured to accomplish this?

Show answer & explanation

Answer: Case Assignment Rules

Answer

Case Assignment Rules should be configured to automatically route incoming cases to specific queues based on case criteria.
Case Assignment Rules specify conditions that automatically assign case ownership to queues or users when records are submitted.

Step-by-Step Solution

1
Identify the primary administration requirement
The requirement calls for automatically assigning case record ownership to designated queues based on custom criteria during case creation.
Initial ownership allocation is controlled by case routing automation.
2
Evaluate Salesforce support automation capabilities
Case Assignment Rules evaluate incoming case attributes and automatically assign the record to the appropriate queue or user.
Escalation rules monitor unresolved time thresholds, auto-response rules send outbound customer emails, and validation rules restrict data entry.

Key Concept

Case Assignment Rules criteria and queue routing
Question 47Question →

An administrator needs to configure different available stage values for a new sales team using a custom Opportunity record type. Which administrative component must be created first to define the selected opportunity stages before linking them to the record type?

Show answer & explanation

Answer: A custom Sales Process containing the required opportunity stage values

Answer

A custom Sales Process containing the required opportunity stage values must be created first.
In Salesforce, the Opportunity Stage picklist is a special picklist controlled by Sales Processes. An administrator must first create a Sales Process to select the subset of stages needed, and then assign that Sales Process when creating or editing the Opportunity record type.

Step-by-Step Solution

1
Identify the mechanism that controls Opportunity Stage picklist values for record types.
Determine that Opportunity Stage picklist values are governed by Sales Processes.
Opportunity Stage is a special picklist field whose available values cannot be assigned directly to record types without a Sales Process.
2
Create and configure the custom Sales Process.
Select the specific stages and probabilities needed for the sales team.
The Sales Process defines the exact life-cycle stages for opportunities associated with it.
3
Associate the Sales Process with the Opportunity Record Type.
The custom record type now displays only the stages selected in the Sales Process.
Each Opportunity record type requires an assigned Sales Process to display its stage picklist values.

Key Concept

Sales Processes and Opportunity Stage Picklist Mapping
Estimated Time:1m 0s
Question 48Question →

A support administrator at a financial services firm is troubleshooting case automation behavior. When a High-Priority case is created via Web-to-Case, the active Case Assignment Rule successfully routes the record to the 'Tier 2 Support Queue', the Escalation Rule (configured with criteria 'Case Owner equals Tier 2 Support Queue') escalates the record after two hours of inactivity, and the Auto-Response Rule sends an automated email acknowledgment to the contact. However, when a support agent manually creates a High-Priority case in Salesforce on behalf of a customer, the case remains owned by the agent, fails to escalate after two hours, and no auto-response email is sent. What explains why these three automation behaviors occurred for the manually created case, and what is the native Salesforce capability regarding these rules?

Show answer & explanation

Answer: The agent did not check the 'Assign using active assignment rule' checkbox during manual creation, leaving the agent as the owner and failing the Escalation Rule criteria; additionally, Auto-Response Rules natively execute only for cases generated via Web-to-Case, Email-to-Case, or API, and do not trigger on manual UI creation.

Answer

The agent did not check the 'Assign using active assignment rule' checkbox during manual creation, leaving the agent as the owner and failing the Escalation Rule criteria; additionally, Auto-Response Rules natively execute only for cases generated via Web-to-Case, Email-to-Case, or API, and do not trigger on manual UI creation.
For cases created manually in the Salesforce UI, Case Assignment Rules only execute if the user selects the 'Assign using active assignment rule' checkbox (or if configured to be checked by default on the page layout). Because this checkbox was not used, ownership remained with the creating agent. This caused the Escalation Rule to fail its entry criteria ('Case Owner equals Tier 2 Support Queue'). Furthermore, Salesforce Auto-Response Rules natively only fire for automated case capture tools (Web-to-Case, Email-to-Case) and never fire during manual UI creation.

Step-by-Step Solution

1
Analyze why Case Assignment Rules did not fire during manual creation.
In Salesforce, manually created cases default ownership to the creating user unless the 'Assign using active assignment rule' checkbox is enabled on the page layout or manually checked during creation.
Case Assignment Rules execute automatically on Web-to-Case / Email-to-Case, but require explicit user opt-in or default layout settings for manual UI creation.
2
Evaluate why Escalation Rules failed to trigger.
The Escalation Rule entry criteria required 'Case Owner equals Tier 2 Support Queue'. Because the assignment rule did not fire, ownership remained with the creating agent, causing the case to fail the escalation criteria.
Escalation Rules evaluate criteria against current record attributes; failing entry criteria prevents SLA timers from scheduling.
3
Determine the operational limits of Auto-Response Rules.
Salesforce Auto-Response Rules are specifically designed for automated lead and case capture mechanisms (Web-to-Case, Email-to-Case, Portal). They do not trigger for records created manually via the standard user interface.
Auto-response emails prevent duplicate or unnecessary automatic replies when an internal agent is directly creating the record in the app.

Key Concept

Case Automation Execution Contexts and Rule Trigger Mechanisms
Question 49Question →

Apex Freight Services needs to restrict access to a sensitive custom field, Contract_Value__c, on the Account object. Most users assigned to the standard Sales User profile should be prevented from viewing or editing this field. However, three regional Finance Managers who are also assigned the Sales User profile require both Read and Edit access. Which two steps should the administrator take to meet these security requirements while adhering to Salesforce best practices?

Select all that apply

Show answer & explanation

Answer: Set the Field-Level Security for Contract_Value__c on the Sales User profile to clear both Read Access and Edit Access.; Create a Permission Set that grants Read Access and Edit Access for Contract_Value__c, and assign it to the three regional Finance Managers.

Answer

The administrator should restrict Field-Level Security (FLS) on the Sales User profile by removing Read and Edit access for Contract_Value__c, and create a Permission Set granting Read and Edit FLS for Contract_Value__c to assign to the three regional Finance Managers.
Field-Level Security (FLS) controls field access at the platform data layer, ensuring fields are hidden in reports, API integrations, list views, and page layouts. Clearing Read and Edit access on the Sales User profile secures the field by default for all standard sales users. Creating a Permission Set with Read and Edit access and assigning it to the three Finance Managers follows the fundamental Salesforce principle of using profiles for baseline restrictions and permission sets for additive access.

Step-by-Step Solution

1
Evaluate the baseline security restriction
Determine that Field-Level Security (FLS) on the Sales User profile must be restricted so that the default behavior for users on that profile is to hide Contract_Value__c across all platform interfaces (UI, API, reports).
Profiles establish the foundational, most restrictive level of field access needed for the majority group.
2
Determine the optimal mechanism for granting selective access
Identify that a Permission Set granting Read and Edit FLS for Contract_Value__c should be assigned to the three regional Finance Managers.
Salesforce security best practices dictate using Permission Sets for additive permissions to avoid profile proliferation.
3
Reject non-secure or redundant configuration methods
Rule out Page Layout/Dynamic Forms visibility adjustments (UI-only) and Profile Cloning (causes unnecessary administrative overhead).
Field visibility on Lightning pages does not enforce data security, and profile cloning for small user groups creates unnecessary maintenance.

Key Concept

Field-Level Security (FLS) and Additive Access via Permission Sets
Question 50Question →

An administrator needs to configure a specialized sales pipeline that utilizes a unique set of stage picklist values on the Opportunity object. Which two administrative setup steps are required to make these stage values available to users on Opportunity records? (Select 2 answers)

Select all that apply

Show answer & explanation

Answer: Create a new Sales Process and select the required stage picklist values.; Create a new Opportunity Record Type and associate it with the newly created Sales Process.

Answer

The administrator must create a new Sales Process to select the active stage values, and then create an Opportunity Record Type linked to that Sales Process.
To display a customized list of stage picklist values on Opportunity records, an administrator must perform two primary steps: first, create a Sales Process containing the specific stages needed for the sales pipeline; second, create an Opportunity Record Type and link it to that Sales Process so users can select those stages.

Step-by-Step Solution

1
Create a Sales Process.
Selects and defines the specific subset of Opportunity stage picklist values for the sales workflow.
Opportunity stage picklists are unique because their available values are governed by Sales Processes rather than standard record type picklist edits.
2
Create an Opportunity Record Type and assign the Sales Process.
Associates the Sales Process and stage selections with the record type.
Record Types make the configured Sales Process accessible to designated user profiles on Opportunity page layouts.

Key Concept

Sales Process and Record Type configuration for Opportunity stages
Question 51Question →

Nova Health System tracks third-party compliance assessments using a custom object named Vendor_Security_Review__c. The Organization-Wide Default (OWD) sharing setting for Vendor_Security_Review__c is set to Private. During initial object configuration, a system administrator cleared the 'Grant Access Using Hierarchies' checkbox for this object. Later, a Compliance Manager created several assessment records. The VP of Compliance, who occupies a higher position in the role hierarchy above the Compliance Manager, is unable to view or edit these records. Which configuration change should the administrator make to allow the VP of Compliance to access these records without changing the OWD to public?

Show answer & explanation

Answer: Select the 'Grant Access Using Hierarchies' checkbox on the Vendor_Security_Review__c custom object definition.

Answer

Select the 'Grant Access Using Hierarchies' checkbox on the Vendor_Security_Review__c custom object definition.
For custom objects, the 'Grant Access Using Hierarchies' option determines whether users higher in the role hierarchy receive access to records owned by or shared with subordinates. Selecting this checkbox on the object definition resolves the issue while keeping Organization-Wide Defaults Private.

Step-by-Step Solution

1
Analyze the access issue
The VP of Compliance sits above the record creator in the role hierarchy, but cannot view records despite being higher in the hierarchy.
For standard objects, hierarchy access is mandatory and cannot be disabled. For custom objects, hierarchy access can be toggled off via the 'Grant Access Using Hierarchies' setting.
2
Identify the cause of disabled access
The administrator explicitly unchecked 'Grant Access Using Hierarchies' on the custom object definition.
Deselecting this option prevents managers and executive roles from automatically receiving implicit access to records owned by subordinates.
3
Determine the optimal administrative solution
Re-enable 'Grant Access Using Hierarchies' on the object definition.
Enabling this checkbox allows users higher in the role hierarchy to inherit record access while leaving the Organization-Wide Default setting at Private.

Key Concept

Role Hierarchy Access Inheritance on Custom Objects
Question 52Question →

A system administrator at a global financial advisory firm is configuring Salesforce Knowledge for internal wealth managers. The administrator assigned Knowledge User feature licenses to all wealth managers, created a Data Category Group called "Investment_Products", published several internal articles, and mapped them to categories within this group. Wealth managers have Read, Create, and Edit access on the Knowledge object, and object-level Organization-Wide Defaults (OWD) are set to Public Read-Only. However, wealth managers report that searching for published articles yields zero results, whereas system administrators can view and read all articles without issue. Which omitted configuration step is causing wealth managers to be unable to view these published Knowledge articles?

Show answer & explanation

Answer: Data Category visibility for the "Investment_Products" category group was not assigned to the wealth managers' roles, profiles, or permission sets.

Answer

Data Category visibility for the "Investment_Products" category group was not assigned to the wealth managers' roles, profiles, or permission sets.
In Salesforce Knowledge, article visibility is controlled by Data Category visibility rules assigned through User Roles, Profiles, or Permission Sets. If an administrator creates a Data Category Group and assigns articles to it without granting category visibility to the target user group, those users cannot see or search for those articles regardless of their object-level permissions.

Step-by-Step Solution

1
Evaluate Object and User License Access
Wealth managers have Knowledge User feature licenses and Read/Create/Edit object permissions, confirming baseline object and feature access is intact.
Knowledge accessibility requires feature licensing and CRUD permissions before evaluating article filtering.
2
Evaluate Data Category Visibility Architecture
In Salesforce Knowledge, visibility of categorized articles is driven by Data Category Group visibility settings assigned at the Role, Profile, or Permission Set level.
Even with Public Read-Only OWD and full object access, users cannot see articles if they lack Data Category visibility for the category group.
3
Identify Missing Administrative Configuration
The administrator must grant visibility (e.g., All Categories, Custom, or Parent-Child visibility) for the "Investment_Products" category group to the target users' roles, profiles, or permission sets.
Granting Data Category visibility exposes the published articles associated with those category paths.

Key Concept

Salesforce Knowledge Data Category Visibility
Estimated Time:2m 0s
Question 53Question →

A system administrator at a global fintech company is configuring Salesforce Knowledge access for the financial compliance team. The compliance specialists currently have standard user licenses and read access to Knowledge articles, but they require the ability to create, edit, and publish compliance articles. Additionally, they must be able to view articles mapped to the restricted 'Global Regulatory Compliance' Data Category Group. Which TWO administration steps must be performed to fulfill these requirements? (Select 2 options)

Select all that apply

Show answer & explanation

Answer: Enable the 'Knowledge User' feature license checkbox on each compliance specialist's user detail record.; Configure Data Category Visibility for the 'Global Regulatory Compliance' group on the compliance specialists' profile or assigned permission set.

Answer

To grant full authoring/publishing capabilities and article access, the administrator must enable the Knowledge User feature license checkbox on the user record and configure Data Category Visibility for the 'Global Regulatory Compliance' group on the user's profile or permission set.
Publishing and managing Salesforce Knowledge articles requires two separate configuration areas: first, enabling the 'Knowledge User' feature license checkbox on the individual user record to unlock publishing capabilities; second, setting up Data Category Visibility for 'Global Regulatory Compliance' on the user's profile or permission set so the published articles in that category can be viewed.

Step-by-Step Solution

1
Identify the license requirement for Knowledge authoring and publishing.
Determined that the 'Knowledge User' feature license checkbox must be selected on each user record to allow creating, editing, publishing, and archiving articles.
Standard object permissions alone are insufficient for article management actions without the feature license.
2
Determine article visibility requirements.
Identified that Data Category Visibility must be explicitly set to 'All' or assigned specific categories for 'Global Regulatory Compliance' on the profile or permission set.
Knowledge article visibility is controlled by Data Category settings, which operate independently of Organization-Wide Defaults or standard profile object access.

Key Concept

Salesforce Knowledge Setup, Feature Licenses, and Data Category Visibility
Question 54Question →

A Salesforce administrator at a renewable energy company is troubleshooting article visibility for field service technicians. The technicians have the Knowledge User feature license enabled and Object-level Read permissions on Knowledge articles via an assigned permission set. However, when searching for published articles within the Service Console, they cannot view any articles under the 'Solar Inverters' category group. Upon investigation, the administrator finds that visibility for the 'Solar Inverters' Data Category Group is configured as 'Custom' for the Support Operations role hierarchy branch, whereas the Field Service Technician role resides in an independent branch where default category visibility is set to 'None'. Which administrative action will grant field service technicians access to articles in the 'Solar Inverters' category?

Show answer & explanation

Answer: Configure the Data Category Visibility settings for the Field Service Technician role or permission set to grant explicit access to the Solar Inverters category group.

Answer

Configure the Data Category Visibility settings for the Field Service Technician role or permission set to grant explicit access to the Solar Inverters category group.
In Salesforce Knowledge, visibility of published articles is governed by a combination of Object permissions, Knowledge User licensing, and Data Category Visibility. Even when users possess the Knowledge User feature license and Read permissions on Knowledge, setting Data Category visibility to 'None' for their role branch completely hides articles mapped to those categories. Explicitly configuring Data Category Visibility for the target role or permission set resolves the visibility issue directly.

Step-by-Step Solution

1
Analyze the access layer restricting article visibility.
Technicians already have the Knowledge User license and Object-level Read permission, ruling out license or CRUD access issues.
Knowledge article access requires both object/user permissions AND Data Category visibility.
2
Evaluate the Data Category Visibility configuration.
The Field Service Technician role inherits a default category visibility of 'None' because it lies outside the Customer Support role hierarchy branch.
When category visibility is set to 'None', users in that role cannot view any articles assigned to that Data Category regardless of object permissions or OWD.
3
Determine the appropriate resolution.
Adjust Data Category Visibility at the role, profile, or permission set level to grant access to 'Solar Inverters'.
Explicitly setting Data Category visibility grants access to articles in those categories without altering administrative permissions or unrelated record-level sharing.

Key Concept

Salesforce Knowledge Data Category Visibility Layering
Question 55Question →

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.

Click a left item, then click its matching right item

Items

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.

Matches

Show answer & explanation

Answer

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.

Step-by-Step Solution

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.

Key Concept

Salesforce Knowledge Data Category Visibility and License Management
Question 56Question →

Aura Solar Solutions uses a custom object named Installation_Project__c to track engineering projects. The Organization-Wide Default (OWD) for Installation_Project__c is set to Private, and the 'Grant Access Using Hierarchies' setting is currently unchecked on the object definition.

Management requires the following access configuration:
1. Regional Operations Managers must regain automatic access to Installation_Project__c records owned by users below them in the role hierarchy.
2. Members of the Safety Compliance Team must receive Read access to any Installation_Project__c record where the Risk_Level__c field is set to 'High', regardless of record ownership.

Which TWO configurations should the System Administrator implement to meet these access requirements?

Select all that apply

Show answer & explanation

Answer: Select the 'Grant Access Using Hierarchies' checkbox on the Installation_Project__c object definition.; Create a criteria-based sharing rule on Installation_Project__c where Risk_Level__c equals 'High' to share Read access with the Safety Compliance public group.

Answer

The administrator must enable 'Grant Access Using Hierarchies' on the Installation_Project__c custom object and create a criteria-based sharing rule granting Read access to the Safety Compliance public group when Risk_Level__c equals 'High'.
To restore manager access up the role hierarchy, the 'Grant Access Using Hierarchies' option must be enabled on the object configuration. To conditionally share specific records based on a field value ('Risk_Level__c = High'), a criteria-based sharing rule targeting the appropriate public group is the exact recommended mechanism.

Step-by-Step Solution

1
Address role hierarchy access for managers.
Checking 'Grant Access Using Hierarchies' on the object settings enables automatic upward access propagation along the role hierarchy for custom objects.
When unchecked, custom object records are not shared with users higher in the role hierarchy unless explicit sharing rules or OWD changes are made.
2
Address selective access based on record field values.
Configure a criteria-based sharing rule on Installation_Project__c checking if Risk_Level__c equals 'High' and sharing Read access with the Safety Compliance Team public group.
Criteria-based sharing rules evaluate field criteria on individual records to grant access to designated public groups or roles without altering baseline OWD settings.

Key Concept

Role Hierarchy propagation settings and Criteria-Based Sharing Rules
Estimated Time:1m 30s
Question 57Question →

A Salesforce administrator at a medical equipment manufacturer is configuring Salesforce Knowledge for internal customer service teams. Tier 1 Support agents report that they are unable to search for or view published Knowledge articles categorized under the 'Surgical Systems' Data Category and assigned to the 'Field Diagnostics' record type, even though they can view articles in other categories. Which two actions must the administrator take to ensure these support agents can access the missing articles? (Select 2 options)

Select all that apply

Show answer & explanation

Answer: Grant visibility to the Surgical Systems Data Category within the Data Category Visibility settings for the agents' profile or assigned permission set.; Assign the Field Diagnostics Knowledge record type to the agents' profile or assigned permission set.

Answer

To resolve the article visibility issue, the administrator must grant access to the 'Surgical Systems' Data Category via Data Category Visibility settings and assign the 'Field Diagnostics' Knowledge record type to the agents' profile or permission set.
Published Salesforce Knowledge article access is governed by both Data Category Visibility and Knowledge Record Type accessibility. Granting access to the 'Surgical Systems' category in Data Category Visibility settings and assigning the 'Field Diagnostics' record type on the Knowledge object to the support agents' profile or permission set ensures the articles can be searched and viewed.

Step-by-Step Solution

1
Analyze Data Category visibility requirements
Identify that Data Category visibility controls user access to articles mapped to specific categories.
Articles belonging to a hidden or unassigned Data Category will not be visible in search results or article views for affected profiles.
2
Verify Knowledge record type assignments
Ensure the target record type ('Field Diagnostics') is accessible to the support team.
When multiple Knowledge record types exist, users must have record type access granted on their Profile or Permission Set to view and interact with articles of that record type.
3
Evaluate feature licensing and sharing model distractors
Rule out feature licenses and standard object OWD adjustments.
Viewing published Knowledge articles does not require a Knowledge User feature license, nor does it rely on setting standard OWD to Public Read/Write.

Key Concept

Salesforce Knowledge article visibility depends on Data Category Visibility rules and Knowledge Record Type profile/permission set assignments.
Question 58Question →

AeroSpace Tech Solutions recently added a custom field named Background_Check_Status__c to the Contact object to track candidate security clearance details. Management requires that only three HR managers have visibility and edit access to this sensitive field. All other employees, including standard users and sales representatives, must be prevented from seeing or modifying this field anywhere in Salesforce, including reports, list views, and API queries. Which configuration should the System Administrator implement to meet this requirement efficiently?

Show answer & explanation

Answer: Remove Read and Edit access for the field across all profiles via Field-Level Security, create a Permission Set granting Read and Edit access to the field, and assign the Permission Set to the three HR managers.

Answer

Remove Read and Edit access for the field across all profiles using Field-Level Security, create a Permission Set granting Read and Edit access for the field, and assign the Permission Set to the three HR managers.
The correct approach enforces field restriction at the data level by setting Field-Level Security (FLS) to hidden for all base profiles, and then granting Read and Edit access to the three HR managers using a Permission Set. This adheres to Salesforce best practices for granting additive permissions without causing profile sprawl.

Step-by-Step Solution

1
Restrict field access globally via Field-Level Security (FLS).
Uncheck Read and Edit access for Background_Check_Status__c across all profiles so no user receives access by default.
FLS enforces data-level security across all access points including reports, list views, and API queries.
2
Create a dedicated Permission Set.
Create a Permission Set and grant Read and Edit permissions for Background_Check_Status__c under Object Settings.
Permission Sets allow administrators to grant additive permissions to specific users without modifying base profiles.
3
Assign the Permission Set to the target users.
Assign the created Permission Set specifically to the three HR managers.
Only the assigned users gain access while all other users remain restricted.

Key Concept

Profiles and Field-Level Security vs. Permission Sets
Question 59Question →

An administrator is configuring collaboration and field audit visibility for a custom object named Asset_Maintenance__c. The requirement specifies that whenever the Status__c or Technician_Notes__c fields are modified, automated record updates must appear in the record's Chatter feed. Additionally, users need the ability to quickly create a related Maintenance_Log__c record directly from the Chatter publisher on the Asset_Maintenance__c record page. Which TWO administrative configurations are required to satisfy these business requirements?

Select all that apply

Show answer & explanation

Answer: Enable Feed Tracking for the Asset_Maintenance__c object in Setup and select the Status__c and Technician_Notes__c fields.; Create an Object-Specific Quick Action on Asset_Maintenance__c to create a Maintenance_Log__c record and add it to the Salesforce Mobile and Lightning Experience Actions section of the Asset_Maintenance__c Page Layout.

Answer

To meet the requirements, the administrator must enable Feed Tracking on the Asset_Maintenance__c object for the specific fields, and create an Object-Specific Quick Action added to the object's page layout under Salesforce Mobile and Lightning Experience Actions.
Enabling Feed Tracking at the object level for specific fields generates system posts whenever those fields change. To provide an action on an object's feed publisher, an Object-Specific Quick Action must be created and added to that object's page layout within the Salesforce Mobile and Lightning Experience Actions section.

Step-by-Step Solution

1
Configure Feed Tracking
Navigate to Setup > Feed Tracking, select Asset_Maintenance__c, check 'Enable Feed Tracking', and check Status__c and Technician_Notes__c (up to 20 fields total).
Automated Chatter posts for field changes require Feed Tracking to be explicitly enabled for the target object and fields.
2
Create and Expose Publisher Action
Create an Object-Specific Quick Action of type 'Create a Record' for Maintenance_Log__c on Asset_Maintenance__c, then add it to the Salesforce Mobile and Lightning Experience Actions section of the Asset_Maintenance__c Page Layout.
Object-specific actions allow creation of related records within the context of the current record and appear on the record page publisher.

Key Concept

Chatter Feed Tracking and Publisher Layout Administration
Question 60Question →

Global Wealth Financial is enhancing its Service Cloud Console for high-net-worth client support agents. Currently, when agents view a Case, related Account and Contact records open as independent primary tabs, fragmenting the workspace. Furthermore, agents require a custom interaction widget that remains persistently accessible at the bottom of the screen regardless of which record tab or subtab is currently focused. Which TWO administrative actions must the Salesforce Administrator perform in Lightning Experience to fulfill these requirements?

Select all that apply

Show answer & explanation

Answer: Configure Navigation Rules within the App Manager for the Service Console application to open child records (Case, Contact) as subtabs of the primary Account record.; Add the custom component to the App Utility Bar in App Manager so it displays as a persistent footer component across all console workspaces.

Answer

The administrator must configure Navigation Rules in App Manager to set related records as subtabs under the primary Account tab, and add the custom interaction component to the App Utility Bar for persistent access.
Configuring Navigation Rules in the App Manager allows administrators to nest related child records (such as Cases or Contacts) under a parent primary tab (such as Account), preventing workspace clutter. Adding a custom component to the App Utility Bar ensures it stays anchored in the bottom bar, making it available regardless of active tabs.

Step-by-Step Solution

1
Navigate to Setup > App Manager, edit the target Lightning Service Console app, and locate the Navigation Rules section.
Defines how records open within the console architecture (e.g., setting Case and Contact to open as subtabs of Account).
Prevents workspace fragmentation by grouping child records under the parent primary tab.
2
Select the Utility Items tab within the App Manager setup wizard and add the custom Aura or Lightning Web Component.
Places the component in the fixed Utility Bar at the bottom of the Lightning Service Console UI.
Provides agents with a persistent tool accessible across all open tabs without taking up main workspace real estate.

Key Concept

Service Cloud Console Navigation Rules and Utility Bar Configuration
Estimated Time:3m 0s
PreviousPage 3 / 90Next
All practice questions — Salesforce Certified Administrator | Examkin