All practice questions

1784 questions

Question 541Question

An administrator is setting up a new 'Enterprise Account' Record Type on the Account object for users assigned to the 'Enterprise Sales User' profile. The business requirement dictates that these users must see a dedicated page layout tailored for enterprise accounts and must only be able to select 'Tier 1 Enterprise' or 'Tier 2 Enterprise' from the standard 'Type' picklist field when working on records of this record type. Which TWO administrative actions are required in Setup to fulfill these requirements? (Choose 2 answers)

Select all that apply

Show answer & explanation

Answer: Navigate to the 'Enterprise Account' Record Type in Object Manager, edit the 'Type' picklist under Picklists Available for Editing, and select only the enterprise picklist values.; Access Page Layout Assignment on the Account object and map the 'Enterprise Sales User' profile and 'Enterprise Account' Record Type combination to the custom Enterprise Account Page Layout.

Answer

To satisfy both requirements, the administrator must configure picklist value availability directly on the 'Enterprise Account' Record Type detail page, and map the 'Enterprise Sales User' profile and 'Enterprise Account' Record Type to the designated page layout in the Page Layout Assignment matrix.
The correct requirements are fulfilled by editing the picklist values available for editing on the specific Record Type detail page in Object Manager, and updating the Page Layout Assignment matrix to link the target Profile and Record Type to the correct custom Page Layout.

Step-by-Step Solution

1
Configure Record Type Picklist Values
Only 'Tier 1 Enterprise' and 'Tier 2 Enterprise' options are visible in the 'Type' field when creating or editing an Enterprise Account.
Picklist values are customized per record type under Object Manager > Account > Record Types > Enterprise Account > Picklists Available for Editing.
2
Assign Page Layout by Profile and Record Type
Users with the 'Enterprise Sales User' profile see the customized Enterprise Account Page Layout when viewing Enterprise Account records.
The Page Layout Assignment matrix maps Page Layouts to specific Profile + Record Type combinations.

Key Concept

Page Layout assignment depends on the matrix of Profile and Record Type, while available picklist values are driven strictly by the Record Type configuration.
Question 542Question

An administrator at a non-profit organization manages grant allocations using a custom parent object, Donation_Grant__c, and individual payments using a custom child object, Grant_Disbursement__c. The two objects are currently connected through a standard Lookup relationship. The finance director requests a field on Donation_Grant__c that automatically calculates the total monetary sum of all related Grant_Disbursement__c records using standard platform capabilities without custom code. Which administrative action is required to implement a native Roll-Up Summary field on the parent object?

Show answer & explanation

Answer: Populate all lookup values on child records, convert the existing Lookup field on Grant_Disbursement__c to a Master-Detail relationship, and create a Roll-Up Summary field on Donation_Grant__c using the SUM function.

Answer

Populate all lookup values on child records, convert the existing Lookup field on Grant_Disbursement__c to a Master-Detail relationship, and create a Roll-Up Summary field on Donation_Grant__c using the SUM function.
Native Roll-Up Summary fields in Salesforce require a Master-Detail relationship between the parent and child objects. To convert an existing Lookup relationship field to a Master-Detail relationship, all existing child records must have a populated parent lookup value. Once converted, a Roll-Up Summary field can be created on the master object using the SUM aggregation operation.

Step-by-Step Solution

1
Analyze relationship requirements for Roll-Up Summary fields
Identify that Roll-Up Summary fields are exclusively available on parent objects in a Master-Detail relationship.
Lookup relationships do not support native declarative roll-up summary functionality.
2
Determine conversion requirements from Lookup to Master-Detail
Ensure all child Grant_Disbursement__c records contain a valid parent lookup reference prior to relationship type conversion.
Salesforce prevents converting a Lookup relationship to a Master-Detail relationship if any orphan child records exist without a parent.
3
Configure the Roll-Up Summary field
Create a new field on Donation_Grant__c of type Roll-Up Summary using the SUM aggregation function on the disbursement amount field.
This satisfies the business requirement of automatically summing child record values declaratively.

Key Concept

Roll-Up Summary Field Relationship Prerequisites
Question 543Question

A Salesforce administrator needs to configure fields to aggregate metrics and display related record information between custom objects. Which two statements correctly describe the characteristics and limitations of Roll-Up Summary and Formula fields? (Select 2)

Select all that apply

Show answer & explanation

Answer: Roll-Up Summary fields can only be created on the master object in a Master-Detail relationship to aggregate data from child detail records.; Formula fields can reference fields from related parent objects across relationships to display dynamic values on child records.

Answer

The correct statements are that Roll-Up Summary fields can only be created on the master object in a Master-Detail relationship, and Formula fields can reference fields from related parent objects across relationships.
Roll-Up Summary fields strictly require a Master-Detail relationship and must reside on the master object. Cross-object formula fields can span lookup or master-detail relationships to pull data from parent objects.

Step-by-Step Solution

1
Evaluate relationship requirements for Roll-Up Summary fields.
Confirm that Roll-Up Summary fields require a Master-Detail relationship on the parent master object.
Salesforce native roll-up summary functionality is strictly limited to Master-Detail relationships.
2
Evaluate cross-object capabilities of Formula fields.
Confirm that cross-object formulas can reference data from parent objects.
Formula fields support referencing fields from parent objects up to 10 relationships away.
3
Review Master-Detail deletion behavior.
Verify that deleting a master record deletes related detail records rather than preserving them as orphans.
Master-Detail relationships enforce cascading deletion on detail records upon deletion of the parent master record.

Key Concept

Roll-Up Summary and Formula Field Relationship Constraints and Capabilities
Question 544Question

A Salesforce Administrator at a cybersecurity firm must immediately revoke access for a departing DevOps Lead. However, attempting to deactivate the user account results in a system error because the user is currently designated as the Default Workflow User and is referenced in custom hierarchy fields. Which two administrative actions should be performed to satisfy the security requirement while cleanly resolving the system dependencies? (Select 2 answers)

Select all that apply

Show answer & explanation

Answer: Freeze the user account immediately to block system logins without interrupting background automated processes.; Reassign the Default Workflow User setting to another active administrator, then deactivate the original user account.

Answer

Freeze the user account immediately to block logins without disrupting automated processes, and reassign the Default Workflow User setting to another active administrator before deactivating the original user account.
Freezing a user account is the recommended immediate action when a user must be blocked from logging in right away but cannot be deactivated due to active system references (like being the Default Workflow User). Once those dependencies are manually reassigned to another active user, the administrator can deactivate the user account to release the Salesforce user license.

Step-by-Step Solution

1
Evaluate immediate access restriction requirement
Freezing the account immediately prevents login while system dependencies exist.
Freezing does not require removing references in system settings or hierarchy fields.
2
Resolve system configuration dependencies
Change the Default Workflow User to another active administrative user record.
Deactivation is blocked by Salesforce as long as the user is set as the Default Workflow User.
3
Deactivate the user account
Deactivate the user record to release the user license back to the organization pool.
Once critical dependencies are reassigned, deactivation can complete successfully.

Key Concept

Distinction between freezing (immediate access revocation without license release or dependency disruption) and deactivating (license release requiring manual dependency resolution).
Estimated Time:2m 0s
Question 545Question

Universal Containers has two distinct sales groups, Enterprise and SMB, both managing opportunities using the standard Opportunity record type. The administrator created a custom Lightning Record Page tailored specifically for Enterprise Account Executives. The requirements state that this custom page must appear only when Enterprise Account Executives access Opportunity records within the Enterprise Sales Lightning App, while all other users and apps must continue seeing the Org Default page. Which activation assignment option in the Lightning App Builder must the administrator use to satisfy this requirement?

Show answer & explanation

Answer: Activate the page as App, Record Type, and Profile, assigning it specifically to the Enterprise Sales App, the standard Opportunity record type, and the Enterprise Sales profile.

Answer

The administrator must activate the page using the 'App, Record Type, and Profile' activation level, selecting the Enterprise Sales App, the standard Opportunity record type, and the Enterprise Sales profile.
The 'App, Record Type, and Profile' activation option provides the most granular control in Lightning App Builder. It allows administrators to override both Org Default and App Default assignments for specific combinations of an App, a Record Type, and a User Profile.

Step-by-Step Solution

1
Analyze requirement scope
Identified that assignment depends on three explicit variables: the specific Lightning App (Enterprise Sales App), the Record Type (standard Opportunity record type), and the User Profile (Enterprise Sales profile).
Lightning App Builder supports three levels of page activation: Org Default, App Default, and App, Record Type, and Profile.
2
Evaluate activation levels
Org Default applies globally across all apps and users. App Default applies to all users within a given app regardless of profile. Only 'App, Record Type, and Profile' allows filtering by profile and app simultaneously.
Granular page distribution requires matching all three criteria in the activation wizard.
3
Select the correct configuration path
Assign the custom page under 'App, Record Type, and Profile' to meet the requirement without affecting SMB users or other apps.
This guarantees that users outside the Enterprise Sales profile or accessing records from other apps continue to see the Org Default page.

Key Concept

Lightning Record Page Activation Precedence and Assignments
Estimated Time:2m 0s
Question 546Question

A Salesforce administrator is tasked with updating the Lightning user experience for a global sales team. The business requirement states that users navigating the 'Western Region Sales' custom application must see a specialized Home page, while users in all other applications should continue viewing the standard org default Home page. Additionally, a specific performance metric chart component on this new Home page must only be displayed when a user accesses Salesforce from a desktop browser.

Which two actions should the administrator take in Lightning App Builder to satisfy these requirements? (Select 2 choices)

Select all that apply

Show answer & explanation

Answer: Activate the custom Home page and set it as the App Default for the 'Western Region Sales' app.; Set a Component Visibility filter on the performance metric component where Device equals Desktop.

Answer

To fulfill the requirements, the administrator must activate the page as the App Default for the 'Western Region Sales' app, and apply a Component Visibility filter setting Device equals Desktop on the specific component.
Activating the Home page as the App Default ensures that only users accessing the specified application view the tailored page, preserving the org default for everyone else. Adding a component filter matching Device equals Desktop dynamically restricts rendering of the performance chart to desktop clients.

Step-by-Step Solution

1
Determine the correct activation level for the Home page requirement.
Selected App Default activation for the 'Western Region Sales' app.
Home pages support Org Default, App Default, and App + Profile activation levels. Using App Default ensures only users within that specific app see the custom page while retaining the Org Default for all other apps.
2
Determine the mechanism to restrict component visibility by device.
Added a filter under Component Visibility set to Device = Desktop.
Lightning App Builder provides granular control over component display using filter criteria based on record fields, user attributes, or client device types.

Key Concept

Lightning Home Page Activation and Component Visibility Filters
Estimated Time:2m 0s
Question 547Question

A Salesforce administrator at a luxury resort management company is configuring custom field settings to support lead processing and reviewing field modification policies on custom objects. Which two statements accurately describe the behaviors and rules for custom field mappings and data type conversions in Salesforce? (Select 2)

Select all that apply

Show answer & explanation

Answer: Custom Lead fields can only be mapped to custom fields on the Account, Contact, or Opportunity objects during lead conversion.; Converting a custom Auto-Number field into a Text data type preserves existing field data while permitting manual editing going forward.

Answer

Custom Lead fields can only be mapped to custom fields on the Account, Contact, or Opportunity objects during lead conversion, and converting a custom Auto-Number field into a Text data type preserves existing field data while permitting manual editing going forward.
Mapping custom Lead fields requires custom target fields on the destination Account, Contact, or Opportunity object. Additionally, converting an Auto-Number field to a Text field preserves existing values in records without data loss while allowing users to manually edit the values in the future.

Step-by-Step Solution

1
Evaluate lead conversion field mapping rules.
Identify that custom fields on the Lead object can only map to custom fields on Account, Contact, or Opportunity records, not standard fields.
Salesforce custom field mapping configuration explicitly prohibits mapping custom lead fields to standard destination fields.
2
Analyze field data type conversion consequences for Auto-Number fields.
Determine that changing an Auto-Number data type to Text preserves current record string values and grants text editing capability.
Auto-Number values are stored as text strings, so converting to Text does not cause data loss and allows manual value updates.
3
Evaluate relationship limitations for Roll-Up Summary fields.
Confirm that Roll-Up Summary fields cannot aggregate records over Lookup relationships.
Roll-Up Summary capabilities strictly require a Master-Detail relationship.

Key Concept

Custom Field Data Type Behavior and Lead Mapping Constraints
Question 548Question

A Salesforce administrator is creating a custom landing page in Lightning App Builder to display company announcements and utility tools for internal team members. Which two actions can the administrator perform when constructing and activating this standalone Lightning App Page? (Select 2 choices)

Select all that apply

Show answer & explanation

Answer: Include both standard and custom Lightning components on the page canvas.; Activate the page by adding it as a navigation tab within specific Lightning Apps.

Answer

The administrator can include both standard and custom Lightning components on the page canvas, and activate the page by adding it as a navigation tab within specific Lightning Apps.
When designing a Lightning App Page, administrators can drag standard and custom components onto the design canvas to build the desired interface. Activation of App Pages is achieved by adding the page as a custom tab within specified Lightning Apps or mobile navigation menus.

Step-by-Step Solution

1
Identify the page type requirements
The requirement describes a standalone landing page, which corresponds to a Lightning App Page in Lightning App Builder.
App Pages provide custom layouts for general utilities or dashboards independent of specific object records.
2
Evaluate component composition capabilities
Standard components and custom Lightning components can be dragged onto the App Page regions.
Lightning App Builder supports full component flexibility across custom and standard libraries.
3
Determine the appropriate activation mechanism
Activation is completed by configuring Lightning App navigation tabs and mobile navigation items.
Unlike Record Pages which rely on Org/App/Record Type defaults, App Pages are deployed as navigation items within specific applications.

Key Concept

Lightning App Page Capabilities and Activation Scope
Question 549Question

A non-profit organization uses a custom object named Grant_Application__c to process confidential funding requests. Security rules dictate that staff members should only view and edit grant applications that they personally own. Additionally, because review committees operate independently, users holding higher management roles in the role hierarchy must NOT automatically receive access to records owned by their direct reports.

Which Organization-Wide Default (OWD) configuration should a Salesforce administrator implement on the Grant_Application__c object to satisfy these security mandates?

Show answer & explanation

Answer: Set Default Internal Access to Private and deselect the Grant Access Using Hierarchies checkbox.

Answer

Set Default Internal Access to Private and deselect the Grant Access Using Hierarchies option for the custom object.
Configuring the Default Internal Access of the custom object to Private ensures that only record owners (and those explicitly shared) have access. For custom objects, Salesforce enables 'Grant Access Using Hierarchies' by default; unchecking this option stops users higher in the role hierarchy from automatically inheriting access to records owned by subordinates.

Step-by-Step Solution

1
Determine the baseline access level required for record owners and non-owners.
Because non-owners should not automatically see or edit records owned by others, the baseline Organization-Wide Default (OWD) must be set to Private.
OWD sets the most restrictive baseline access for records across the organization.
2
Evaluate role hierarchy propagation requirements for the custom object.
By default, custom objects propagate record access up the role hierarchy via 'Grant Access Using Hierarchies'. Disabling this setting prevents manager roles from gaining access.
Unchecking 'Grant Access Using Hierarchies' stops implicit sharing roll-up to superior roles in the role hierarchy.

Key Concept

Organization-Wide Defaults (OWD) and Hierarchy Access Control on Custom Objects
Question 550Question

An administrator at a clinical research organization is designing a custom object named Subject_Visit__c to track patient evaluation sessions associated with a parent custom object named Clinical_Trial__c. The business requires that deleting a Clinical_Trial__c record automatically removes all associated Subject_Visit__c records, and that total completed visits must be displayed as an aggregate count on the Clinical_Trial__c record. Which two configuration considerations and object capabilities apply to this implementation? (Select 2)

Select all that apply

Show answer & explanation

Answer: A Master-Detail relationship must be created on Subject_Visit__c pointing to Clinical_Trial__c to enable native Roll-Up Summary fields on the parent object.; Standard system audit fields such as CreatedById, LastModifiedDate, and Name are automatically created when the Subject_Visit__c custom object is defined.

Answer

The correct selections are that a Master-Detail relationship must be created on Subject_Visit__c pointing to Clinical_Trial__c to enable native Roll-Up Summary fields, and that standard audit fields (such as CreatedById, LastModifiedDate, and Name) are automatically created when defining a custom object.
Master-Detail relationships inherently support native Roll-Up Summary fields on the parent master object and automatically enforce cascading deletion of child records when the master record is deleted. Additionally, whenever a new custom object is created in Salesforce, standard system fields (such as Name, CreatedById, LastModifiedDate, and CreatedDate) are automatically provisioned by the platform.

Step-by-Step Solution

1
Analyze the relationship and data aggregation requirements between Clinical_Trial__c and Subject_Visit__c.
Cascading deletion and native Roll-Up Summary field capabilities require a Master-Detail relationship rather than a Lookup relationship.
Lookup relationships do not natively support Roll-Up Summary fields on the parent object nor standard cascading record deletion.
2
Evaluate standard field creation behavior for new custom objects in Salesforce.
Creating any custom object automatically provisions standard system fields, including Name, CreatedById, CreatedDate, LastModifiedById, LastModifiedDate, and SystemModstamp.
Salesforce automatically establishes these system audit and identity fields to maintain record integrity and audit history.

Key Concept

Standard vs Custom Object Capabilities and Master-Detail Relationship Characteristics
Question 551Question

Universal Containers recently established a specialized regional support team in Tokyo and created a custom Business Hours record named 'APAC Support Hours' set to Monday–Friday, 09:00–18:00 JST. Support managers notice that when cases assigned to this regional team meet escalation criteria on Saturday morning, escalation actions fire immediately rather than pausing until Monday morning. What is the primary administrative configuration issue causing this timing mismatch?

Show answer & explanation

Answer: The Case Escalation Rule entries are configured to ignore business hours or use default organization business hours instead of case business hours.

Answer

The Case Escalation Rule entries are configured to ignore business hours or use default organization business hours instead of case business hours.
Escalation rule entries provide explicit settings governing how business hours are applied to escalation timers. If the entry is set to ignore business hours or is left at the default organization business hours (which default to 24 hours a day unless modified), escalation timers will run continuously throughout weekends.

Step-by-Step Solution

1
Analyze the escalation behavior.
Escalation actions fire during weekends when the support center is closed.
The system is executing escalation timers on a 24/7 basis or using a default organization schedule.
2
Review Case Escalation Rule entry settings in Setup.
Identify how business hours are specified on the escalation rule criteria entry.
Escalation Rule entries allow administrators to specify whether to use specified business hours, case business hours, or ignore business hours entirely.
3
Determine the required resolution.
Update the rule entry to set 'How business hours should be determined' to use case business hours or explicitly select 'APAC Support Hours'.
Ensures escalation timers pause outside defined business hours.

Key Concept

Business Hours in Case Escalation Rules
Question 552Question

Universal Containers utilizes Dynamic Forms on a custom Opportunity Lightning Record Page. An administrator configures a component visibility rule on the Sensitive_Margin__c field component to render only when StageName is set to 'Closed Won'. A sales user whose profile has Field-Level Security (FLS) Read access unchecked for Sensitive_Margin__c opens an Opportunity record that is in 'Closed Won' stage. The custom record page is activated as the App Default for the 'Sales Central' app. Which outcome will the sales user experience upon opening this record in the 'Sales Central' app?

Show answer & explanation

Answer: The user will not see the Sensitive_Margin__c field because Field-Level Security (FLS) restrictions supersede Lightning App Builder component visibility filters.

Answer

The user will not see the field because Field-Level Security restrictions supersede Lightning App Builder component visibility filters.
Field-Level Security (FLS) is enforced strictly at the database layer. Even if a field component's visibility conditions on a Dynamic Forms page are fully met, Salesforce will withhold the field from any user who lacks Read FLS permissions for that field.

Step-by-Step Solution

1
Evaluate the Field-Level Security (FLS) settings for the user profile.
The user profile has Read FLS access set to unchecked for the field.
Salesforce security architecture enforces FLS at the data level prior to rendering any presentation layer components.
2
Evaluate the Dynamic Forms component visibility filter on the Lightning Record Page.
The stage condition ('Closed Won') evaluates to true for the record.
Component visibility filter rules dictate when a component is eligible to appear in the UI.
3
Determine the final field visibility by combining FLS and UI component rules.
The field remains hidden from the user.
Component visibility cannot bypass or override FLS. If FLS restricts access, the field is hidden regardless of component visibility criteria.

Key Concept

Field-Level Security vs Dynamic Forms Component Visibility
Question 553Question

An administrator at a cloud software company manages a custom parent object, Software_License__c, and a custom child object, User_Assignment__c, which are currently linked by a Lookup relationship. The business requests a real-time summary field on Software_License__c to display the total count of related User_Assignment__c records. When attempting to create a Roll-Up Summary field on Software_License__c, the administrator notices that the Roll-Up Summary field type option is grayed out and unavailable. Which configuration change must the administrator make to enable native Roll-Up Summary fields on Software_License__c?

Show answer & explanation

Answer: Convert the Lookup relationship field on User_Assignment__c to a Master-Detail relationship after ensuring all existing child records have a populated lookup field value.

Answer

Convert the Lookup relationship field on User_Assignment__c to a Master-Detail relationship after ensuring all existing child records have a populated lookup field value.
Native Salesforce Roll-Up Summary fields require a Master-Detail relationship between objects. To convert a Lookup relationship into a Master-Detail relationship, all existing child records must have a value populated in the lookup field.

Step-by-Step Solution

1
Analyze relationship requirements for Roll-Up Summary fields
Identify that native Roll-Up Summary fields require a Master-Detail relationship between the parent (master) and child (detail) objects.
Salesforce declarative Roll-Up Summary fields cannot be created on parent objects connected strictly via a standard Lookup relationship.
2
Evaluate prerequisite steps for relationship conversion
Ensure that every existing child User_Assignment__c record contains a valid reference in the lookup field.
A Lookup relationship field cannot be converted to a Master-Detail relationship if any existing child records contain null values in that field.
3
Perform conversion and field creation
Change the relationship type to Master-Detail and create the Roll-Up Summary field on Software_License__c.
Once converted, the master object enables the creation of native aggregate fields such as COUNT, SUM, MIN, and MAX.

Key Concept

Master-Detail Relationship Requirement for Roll-Up Summary Fields
Question 554Question

An administrator created a customized Lightning Record Page for the Case object to streamline support workflows. The business requirement specifies that this custom page must only display to users assigned to the Tier 2 Support profile when they are viewing cases of the Technical Support record type while working inside the Service Console application. Which activation option should the administrator select in Lightning App Builder to satisfy this requirement?

Show answer & explanation

Answer: Assign the page as App, Record Type, and Profile, then select the Service Console app, Technical Support record type, and Tier 2 Support profile.

Answer

Assign the page as App, Record Type, and Profile, then select the Service Console app, Technical Support record type, and Tier 2 Support profile.
The correct option correctly identifies that Lightning App Builder provides an 'App, Record Type, and Profile' activation mode specifically designed to override default pages for precise combinations of an app, object record type, and user profile.

Step-by-Step Solution

1
Analyze the business requirements for Lightning Record Page activation scope.
The requirement specifies restrictions across three criteria: Application (Service Console), Record Type (Technical Support), and Profile (Tier 2 Support).
Identifying the required granularity of assignment determines which activation tier to use.
2
Evaluate Lightning App Builder page activation options.
The three activation options are Org Default, App Default, and App, Record Type, and Profile. The granular option is required to target specific combinations.
Org Default applies to everyone in the org, App Default applies to all users in a specific app, whereas App, Record Type, and Profile provides targeted override behavior.
3
Select the correct activation workflow in Lightning App Builder.
Choose App, Record Type, and Profile activation, assign the Service Console app, select the Technical Support record type, and select the Tier 2 Support profile.
This directly fulfills all three constraints of the business requirement.

Key Concept

Lightning Record Page Activation Levels (Org Default vs. App Default vs. App, Record Type, and Profile)
Question 555Question

A Salesforce administrator is reviewing user maintenance procedures for a company's sales team. Which two statements accurately describe the differences between freezing a user account and deactivating a user account? (Select 2 answers)

Select all that apply

Show answer & explanation

Answer: Freezing a user account prevents the user from logging in but keeps their user license allocated.; Deactivating a user account prevents the user from logging in and frees up their user license for reallocation.

Answer

Freezing a user account prevents login while keeping the user license allocated, whereas deactivating a user account prevents login and frees up the license for reallocation.
Freezing a user account blocks login access without releasing the license, which is useful when a user is involved in customization dependencies (such as default workflow users). Deactivating a user revokes access and releases their license for reassignment.

Step-by-Step Solution

1
Evaluate the impact of freezing a user account on system access and licensing.
Freezing blocks login access immediately but continues to consume a user license.
Freezing is used when a user cannot be deactivated immediately due to system dependencies, but access must be revoked right away.
2
Evaluate the impact of deactivating a user account on system access and licensing.
Deactivating blocks login access and releases the associated user license.
Deactivation allows the administrator to reuse the license for another user while preserving the user record and history.

Key Concept

Distinction between freezing and deactivating user accounts in Salesforce administration
Question 556Question

Apex Health tracks clinical research studies using a custom object named Trial_Participant__c. All Clinical Research Associates (CRAs) are assigned the standard 'CRA User' profile. Due to updated privacy guidelines, access to the sensitive custom field Patient_Identity_Hash__c on Trial_Participant__c must be hidden from most CRAs. However, two lead compliance auditors who share the 'CRA User' profile require Read and Edit access to this field. Additionally, security policy mandates that these two compliance auditors must be strictly prohibited from logging into Salesforce if they are outside the corporate network IP address range.

Which two configuration steps should the Salesforce Administrator perform to meet these requirements? (Choose 2 answers)

Select all that apply

Show answer & explanation

Answer: Deselect Read and Edit access for Patient_Identity_Hash__c in Field-Level Security on the CRA User profile, and assign a Permission Set granting Read and Edit access on the field to the two compliance auditors.; Create a dedicated profile for the two compliance auditors and specify the corporate network IP range under Login IP Ranges on that profile to deny login access outside the network.

Answer

The administrator should set Field-Level Security on the CRA User profile to hide the field and grant access to the compliance auditors via a Permission Set, while configuring Login IP Ranges on a profile assigned to the auditors to restrict login access outside the corporate network.
To grant additive access to a subset of users, Field-Level Security should be hidden at the profile baseline and granted additively using a Permission Set. To restrict login locations, Login IP Ranges must be specified on a Profile assigned to those users, as profile IP ranges enforce hard login restrictions.

Step-by-Step Solution

1
Evaluate field accessibility requirements for the broader user group versus the specific subset of users.
Identify that the base CRA User profile should have Field-Level Security for Patient_Identity_Hash__c set to restricted (hidden), adhering to the principle of least privilege.
Profiles establish baseline permissions for groups of users, while permission sets grant additive permissions to specific individuals without creating extra profiles.
2
Determine how to grant field access to the two compliance auditors.
Create a Permission Set with Read and Edit access on Patient_Identity_Hash__c and assign it to the two compliance auditors.
Permission sets are the recommended mechanism in Salesforce for granting selective additive field and object access.
3
Analyze login restriction requirements for the compliance auditors.
Configure Login IP Ranges on a dedicated profile assigned to the auditors to block logins outside corporate network IP boundaries.
Profile-level Login IP Ranges strictly enforce IP restriction by preventing authentication outside the specified ranges, whereas org-level Network Access settings only control multi-factor/identity verification challenges.

Key Concept

Combining Profile Field-Level Security with Permission Sets for additive field access, and using Profile Login IP Ranges for strict login restrictions.
Question 557Question

An administrator is configuring a custom object named Event_Registration__c to link with the standard Contact object. The business requirement states that if a Contact record is deleted, all associated Event_Registration__c records must be deleted automatically. Additionally, executive leadership requires displaying the total number of event registrations directly on the Contact record. Which two configuration settings or relationship choices satisfy these requirements? (Choose 2 answers)

Select all that apply

Show answer & explanation

Answer: Create a Master-Detail relationship field on Event_Registration__c pointing to Contact.; Create a Roll-Up Summary field on the Contact object to count related Event_Registration__c records.

Answer

Create a Master-Detail relationship field on the Event_Registration__c object pointing to Contact, and create a Roll-Up Summary field on the Contact object to calculate the total count of child records.
Defining a Master-Detail relationship on the child object (Event_Registration__c) linking to Contact ensures that deleting a Contact record cascades deletion to all associated registration records. Furthermore, establishing a Master-Detail relationship allows the creation of a native Roll-Up Summary field on the parent Contact object to count related registrations.

Step-by-Step Solution

1
Identify the deletion cascade requirement.
Determine that a Master-Detail relationship must be created on the detail object (Event_Registration__c) referencing Contact so that deleting a Contact record automatically deletes its related registrations.
Master-Detail relationships inherently control deletion cascade behavior.
2
Identify the metric aggregation requirement.
Determine that a Roll-Up Summary field must be placed on the parent/master object (Contact) to count related detail records.
Roll-Up Summary fields are natively supported on master objects in Master-Detail relationships.

Key Concept

Master-Detail Relationship and Roll-Up Summary Fields
Estimated Time:1m 0s
Question 558Question

An organization requires strict session controls for users assigned to the Customer Support Representative profile due to shared call-center workstations. Specifically, these users must be logged out automatically after 15 minutes of inactivity, and their sessions must terminate immediately upon timeout without allowing session extension. Other profiles in the organization should maintain the default 2-hour session timeout. Which administrative configuration should be modified to meet this requirement?

Show answer & explanation

Answer: Configure the Session Settings directly within the Customer Support Representative profile to set the inactivity timeout to 15 minutes and enable forced logout on session timeout.

Answer

Configure the Session Settings directly within the Customer Support Representative profile to set the inactivity timeout to 15 minutes and enable forced logout on session timeout.
Salesforce administrators can override Organization-Wide Session Settings at the Profile level. Modifying the Session Settings section on the Customer Support Representative profile allows setting a 15-minute inactivity timeout and enabling forced logout upon timeout specifically for assigned users without affecting standard organization settings.

Step-by-Step Solution

1
Identify the level of security enforcement required.
The requirement specifies session timeout rules targeted exclusively at users assigned to a specific profile (Customer Support Representative).
Salesforce allows administrators to override global session settings on a per-profile basis.
2
Evaluate supported location for session overrides.
Profile settings contain a dedicated Session Settings section where Timeout value and 'Force logout on session timeout' can be configured.
Permission sets and organization-wide network access ranges do not support defining session inactivity duration or logout triggers.
3
Confirm profile override precedence.
Profile-level session settings supersede the Organization-Wide Session Settings for users assigned to that profile.
This leaves the rest of the organization operating under the default 2-hour org-wide session setting while strictly enforcing 15-minute forced logout for support staff.

Key Concept

Profile-Level Session Settings Overrides
Estimated Time:1m 30s
Question 559Question

A Salesforce administrator at an educational institution is optimizing user access management across several administrative departments. Match each administrative security requirement to the appropriate Salesforce security component or feature.

Click a left item, then click its matching right item

Items

Grant Read and Edit access on the custom Student Support object to a select group of academic advisors for a 60-day audit window without altering baseline profile settings.
Bundle standard Sales and Service permission sets for regional managers while suppressing Delete permissions inherited from one of the bundled sets.
Provide ongoing, supplemental Create and Edit permissions on the Scholarship Application object to three specific financial officers who hold standard staff profiles.

Matches

Show answer & explanation

Answer

Temporary access for a specific window matches Permission Set Assignment with an Expiration Date; bundling permission sets with suppressed permissions matches a Permission Set Group containing a Muting Permission Set; providing specific additive permissions to targeted users matches a Standalone Permission Set assigned directly to the target users.
Each administrative requirement corresponds directly to a core capability of Salesforce's additive security model: permission set expiration dates cater to temporary access windows, Permission Set Groups with Muting Permission Sets facilitate complex bundling and selective restriction, and standalone permission sets extend baseline profile capabilities to specific subset users.

Step-by-Step Solution

1
Analyze requirement 1 (60-day audit window without altering baseline profile settings).
Identified the need for temporary additive access.
Salesforce permits setting expiration dates on user permission set assignments to automatically revoke access after the specified time frame.
2
Analyze requirement 2 (Bundling permission sets while suppressing specific inherited permissions).
Identified the need for permission consolidation with muted access.
Permission Set Groups consolidate multiple permission sets, while Muting Permission Sets enable removing specific permissions (like Delete) within the group scope.
3
Analyze requirement 3 (Supplemental Create and Edit access for specific users holding baseline staff profiles).
Identified the need for a targeted, permanent permission extension.
Standalone permission sets grant supplemental object-level and field-level access to individual users without altering underlying profile definitions.

Key Concept

Permission Sets, Permission Set Groups, and Muting Permission Sets in Salesforce security architecture
Question 560Question

An administrator is designing a custom data model to track logistics operations between a parent custom object, Shipment_Route__c, and a child custom object, Delivery_Hub__c. The business requires aggregate reporting of completed hubs directly on the route record and demands that deleting a shipment route automatically purges all connected hubs. However, several existing Delivery_Hub__c records currently lack an assigned parent.

Which two steps must the administrator take to establish this data model successfully? (Choose 2 answers)

Select all that apply

Show answer & explanation

Answer: Populate the parent reference field on all existing Delivery_Hub__c records before converting the relationship field to a Master-Detail type.; Create a Roll-Up Summary field on the Shipment_Route__c object to aggregate metrics from related Delivery_Hub__c records.

Answer

The administrator must populate the parent reference on all existing child records prior to converting the relationship to Master-Detail, and create a Roll-Up Summary field on the parent object.
Establishing a Master-Detail relationship satisfies the cascading deletion requirement and enables Roll-Up Summary fields on the parent object. Because existing child records lack parent references, those fields must be populated on every record before converting a lookup relationship to Master-Detail.

Step-by-Step Solution

1
Analyze data model requirements for cascading deletion and aggregate metrics
Determined that a Master-Detail relationship is required to support both cascading record deletion and Roll-Up Summary fields on the parent object.
Lookup relationships do not support native Roll-Up Summary fields and do not automatically delete child records when a parent is deleted.
2
Address data integrity constraints for converting/creating Master-Detail relationships on existing records
Identified that all existing child records must have a populated parent lookup field before converting the field definition to Master-Detail.
Salesforce enforces mandatory parent references on detail records in a Master-Detail relationship.
3
Configure the aggregate metric requirement
Created a Roll-Up Summary field on the parent Shipment_Route__c object to aggregate data from child records.
Master-Detail relationships allow parent objects to display native Roll-Up Summary fields for child record calculations.

Key Concept

Master-Detail Relationship Conversion Requirements and Roll-Up Summary Field Capabilities
Estimated Time:2m 0s
PreviousPage 28 / 90Next
All practice questions — Salesforce Certified Administrator | Examkin