All practice questions

1784 questions

Question 381Question

A Salesforce administrator at a renewable energy company needs to update custom field configurations on the custom object Installation_Project__c and set up field tracking for prospective client leads. The administrator plans to convert an existing custom Text field to a Picklist field and configure custom lead field mapping for lead conversion. Which TWO statements accurately describe the technical considerations and limitations for these field changes?

Select all that apply

Show answer & explanation

Answer: Converting a custom field from Text to Picklist preserves data, but values that do not match defined picklist entries will be lost if not explicitly added to the picklist value set.; Custom lead fields can only be mapped to custom fields on the Account, Contact, or Opportunity objects during standard lead conversion.

Answer

The correct statements are that converting a Text field to a Picklist field risks data loss for values not defined in the picklist value set, and custom lead fields can only be mapped to custom fields on the Account, Contact, or Opportunity objects during lead conversion.
Converting a custom Text field to a Picklist requires caution as data values not defined in the picklist set may be lost. Furthermore, standard lead conversion only maps custom lead fields to custom fields residing on the Account, Contact, or Opportunity objects.

Step-by-Step Solution

1
Analyze field conversion implications for Text to Picklist changes.
Changing field types from Text to Picklist requires existing values to match the target picklist values, otherwise data loss occurs.
Salesforce enforces picklist validation upon data type conversion.
2
Evaluate Lead Conversion mapping capabilities.
Lead Conversion mapping explicitly transfers data to Account, Contact, and Opportunity custom fields.
Standard lead conversion does not support direct mapping to custom objects like Installation_Project__c.

Key Concept

Custom Field Data Type Conversion and Lead Field Mapping Capabilities
Question 382Question

A System Administrator needs to immediately restrict access for a departing System Integrator who is currently configured as the default owner for Web-to-Lead records, the running user for several scheduled Apex jobs, and selected as the manager in custom hierarchy fields. The administrator must prevent login immediately without disrupting ongoing system automation or record routing. Which two administrative actions and behaviors correctly address this requirement? (Select 2 answers)

Select all that apply

Show answer & explanation

Answer: Freeze the user account immediately to block system login while allowing scheduled jobs and automated routing processes assigned to the user to continue operating.; Reassign system automation roles and default record ownership prior to deactivating the user account to permanently release the user license.

Answer

The administrator should freeze the user account immediately to block login access while preserving background operations, and reassign automation references before deactivating the user to release the user license.
Freezing a user account is designed for situations where access must be immediately revoked but the account cannot be deactivated right away due to dependencies like scheduled jobs, default lead ownership, or hierarchy fields. Deactivating the user is the proper step to free up the license once those dependencies have been safely reassigned.

Step-by-Step Solution

1
Evaluate immediate access restriction vs. system dependency
Freezing the user stops login instantly without breaking scheduled jobs or record routing dependencies.
Freezing prevents authentication without altering record relationships or user configuration references.
2
Evaluate license management and long-term resolution
Deactivating the user is necessary to release the user license, but dependencies like default Web-to-Lead owner must first be reassigned.
Deactivating a user associated with active workflow processes or default ownership can cause system errors if references are not remapped.

Key Concept

User Freezing vs. User Deactivation in Salesforce Administration
Question 383Question

A Salesforce Administrator at a financial services enterprise must resolve two urgent user management requirements:

1. A temporary internal Risk Auditor requires read-only access to custom Compliance Audit records for 90 days. This access must not be granted to other users assigned to the standard auditor profile.
2. An active Risk Manager who serves as a default record owner in automated Lead routing rules and is referenced in custom user hierarchy fields must have their system login access blocked immediately.

Which TWO administrative actions should be taken to satisfy these requirements while adhering to Salesforce best practices? (Select TWO)

Select all that apply

Show answer & explanation

Answer: Assign a permission set granting Read access to Compliance Audit records to the Risk Auditor and set an expiration date on the permission set assignment.; Freeze the Risk Manager's user record from Setup to instantly prevent user login while preserving automated processes and hierarchy references.

Answer

The correct actions are assigning a permission set with an expiration date to the temporary Risk Auditor and freezing the Risk Manager's user account from Setup.
The correct options state that assigning a permission set with an expiration date grants temporary object permissions efficiently without modifying base profiles, and freezing the user account immediately blocks login capability without disrupting automated Lead routing rules or custom hierarchy references.

Step-by-Step Solution

1
Evaluate provision requirements for temporary, additive object access.
Identify that Permission Sets support expiration dates for individual user assignments, whereas Profiles do not support expiration dates and should not be used for user-specific permission additions.
Salesforce security best practices mandate using Permission Sets and Permission Set Groups for temporary or user-specific permission grants.
2
Evaluate access block requirements for users tied to automated system features.
Determine that freezing the user account blocks authentication immediately while preventing configuration failures in Lead routing or custom hierarchy references.
User deactivation is blocked or causes runtime errors when the target user is referenced as a default owner in active automation or custom hierarchy fields.

Key Concept

User Provisioning via Permission Set Expiration and User Freezing vs Deactivation
Question 384Question

An administrator at Apex Horizon Media is configuring login security restrictions for employees assigned to the Support Specialist profile. The administrator defines profile-level Login IP Ranges as 192.168.10.1 - 192.168.10.100. Separately, the organization's Network Access settings list 10.0.0.1 - 10.0.0.255 as Trusted IP Ranges. Which two statements accurately describe the login access behavior for users assigned to this profile? (Select 2 answers)

Select all that apply

Show answer & explanation

Answer: Users attempting to log in from an IP address outside 192.168.10.1 - 192.168.10.100 are denied access entirely, even if their IP address is included in the organization's Network Access trusted ranges.; Users logging in from an IP address within 192.168.10.1 - 192.168.10.100 can log in successfully without receiving an identity verification prompt.

Answer

Users attempting to log in from outside the profile's designated Login IP Ranges are completely blocked regardless of organization Network Access settings, while users logging in within the profile's Login IP Ranges log in without identity verification prompts.
Profile-level Login IP Ranges define strict boundaries for access: users outside the specified range are completely denied access, regardless of organization-wide settings. Furthermore, users logging in within defined profile IP ranges are trusted and do not require identity verification.

Step-by-Step Solution

1
Analyze the impact of profile-level Login IP Ranges
Profile-level Login IP Ranges enforce a strict access policy. When configured on a profile, any login attempt from an IP address outside the specified range is immediately denied.
Profile IP restrictions serve as an absolute authorization boundary rather than an identity challenge trigger.
2
Evaluate the interaction between profile-level IP ranges and org-wide Network Access
Organization-wide Network Access trusted ranges determine whether users without profile IP restrictions need activation verification. They do not override or relax profile-level IP restrictions.
More restrictive profile-level security controls take precedence over organization-wide defaults.

Key Concept

Profile Login IP Ranges enforce hard access denial for unlisted IP addresses, whereas Organization Network Access Trusted IP Ranges only dictate whether identity verification is required.
Question 385Question

An organization plans to change its fiscal year structure from a Standard Fiscal Year to a 4-4-5 Custom Fiscal Year to align with its financial accounting period. Which two key considerations should the Salesforce administrator communicate to executive leadership before enabling this setting? (Choose 2 answers)

Select all that apply

Show answer & explanation

Answer: Enabling a Custom Fiscal Year is an irreversible setting that cannot be disabled once activated.; Standard forecasting and default calendar reporting features will be impacted and require custom fiscal year definitions.

Answer

Enabling a Custom Fiscal Year is irreversible once enabled, and standard forecasting and default reporting functionality will be impacted.
Enabling Custom Fiscal Years in Salesforce is an irreversible action that permanently changes how dates and periods are defined. Additionally, standard forecasting and default calendar reporting tools are impacted, requiring custom period definitions and forecasts.

Step-by-Step Solution

1
Analyze the request to transition from a Standard Fiscal Year to a 4-4-5 Custom Fiscal Year.
Identify key architectural and administrative impacts of custom fiscal year enablement in Salesforce.
Custom fiscal years alter how dates and periods are mapped to fiscal quarters across the organization.
2
Evaluate the permanency of the custom fiscal year configuration.
Confirm that once custom fiscal years are enabled, the organization cannot revert to standard fiscal years.
Salesforce enforces custom fiscal year settings permanently due to core calendar schema changes.
3
Assess the feature impacts on standard reporting and forecasting.
Determine that standard forecasts and default report dates will be affected.
Custom fiscal year structures require defining custom period definitions rather than relying on standard calendar rules.

Key Concept

Custom Fiscal Year Permanency and Feature Impact
Question 386Question

An administrator at a financial institution needs to restrict access to a new sensitive custom field, `Compliance_Audit_Status__c`, on the `Opportunity` object. A subset of users assigned to the standard Sales User profile requires Read and Edit access to this field, while users assigned to the Compliance Manager profile require Read-Only access. All other users must be completely restricted from accessing this field across all interfaces, including reports, list views, and the API. Furthermore, login attempts by Compliance Managers from outside specified corporate IP addresses must be strictly blocked rather than triggering identity verification.

Which TWO actions should the administrator take to fulfill these security requirements?

Select all that apply

Show answer & explanation

Answer: Set Field-Level Security (FLS) for `Compliance_Audit_Status__c` to Visible (Read-Only) on the Compliance Manager profile, set FLS to Hidden on the Sales User profile, and grant Read/Edit access to the designated subset of sales reps using a Permission Set.; Add the corporate IP address range to the Login IP Ranges section directly within the Compliance Manager Profile settings.

Answer

The administrator must set Field-Level Security on the profiles (restricting access on the standard Sales profile while granting Read-Only on the Compliance profile) and assign a Permission Set to the subset of sales reps requiring Read/Edit access. Additionally, the administrator must specify corporate IP addresses under Login IP Ranges on the Compliance Manager Profile.
To secure data effectively across all interfaces (including UI, reports, and API), Field-Level Security (FLS) must be configured on profiles and supplemented with Permission Sets for additive access. Restricting FLS on the standard Sales User profile while granting access to a specific subset of users via a Permission Set satisfies least-privilege access without profile duplication. Furthermore, placing IP restrictions within Profile Login IP Ranges strictly denies login attempts from outside those ranges, fulfilling the login restriction requirement.

Step-by-Step Solution

1
Analyze field access requirements across user groups
Identify that the standard Sales User profile must have the field hidden by default, while a subset requires Read/Edit access.
Salesforce security follows a principle of least privilege where base profiles define minimal access and permission sets grant additive permissions.
2
Configure Field-Level Security (FLS) and Permission Sets
Hide the field on the Sales User profile, set Read-Only on the Compliance Manager profile, and create a Permission Set with Read/Edit access for the specific sales subset.
FLS guarantees data restriction across all channels (UI, API, Reports), and permission sets prevent profile proliferation.
3
Evaluate login security requirements for Compliance Managers
Determine that login attempts outside corporate IPs must be denied rather than challenged.
Profile Login IP Ranges enforce strict login blocking outside defined ranges, whereas org-wide Network Access only bypasses multi-factor verification.

Key Concept

Field-Level Security (FLS) for data privacy across all API/UI boundaries, combined with Profile Login IP Ranges for strict login enforcement.
Question 387Question

An administrator at Northern Trail Outfitters needs to secure a sensitive custom field, Commission_Rate__c, on the Opportunity object. Standard Sales Users must not be able to view or edit this field in the user interface, reports, list views, or API integrations. However, two specific Sales Managers require edit access to Commission_Rate__c, while members of the Finance Audit team require read-only access. Which two configuration steps should the administrator perform to fulfill these security requirements?

Select all that apply

Show answer & explanation

Answer: Set Field-Level Security for Commission_Rate__c to hidden (uncheck both Visible and Read-Only) on the base Standard Sales User profile.; Create two distinct permission sets—one granting Edit access and one granting Read-Only access to Commission_Rate__c—and assign them to the appropriate users.

Answer

The administrator should set Field-Level Security (FLS) to hidden on the Standard Sales User profile and create two permission sets (one for Edit access, one for Read-Only access) to grant the required access to specific users.
To restrict field access universally, Field-Level Security (FLS) must be configured to remove both Read and Edit access on the base profile. To grant exceptional access to specific individuals or sub-teams, Permission Sets are used because Salesforce security uses an additive model where permission sets extend access beyond the profile base.

Step-by-Step Solution

1
Restrict baseline field access using Field-Level Security
Commission_Rate__c is hidden from all users assigned to the Standard Sales User profile across the UI, reports, search, and API.
Field-Level Security is the primary mechanism in Salesforce for controlling field visibility and access universally.
2
Create additive access permissions using Permission Sets
One permission set grants Read and Edit access on Commission_Rate__c; a second permission set grants Read-Only access on Commission_Rate__c.
Permission sets allow administrators to expand permissions for specific users on top of their baseline profile without modifying the baseline profile.
3
Assign permission sets to targeted users
The two Sales Managers receive the Edit permission set, and Finance Audit team members receive the Read-Only permission set.
This fulfills user-specific and role-specific requirements while maintaining a lean profile architecture.

Key Concept

Field-Level Security (FLS) restriction combined with Permission Set extension
Question 388Question

An administrator at Universal Containers is tasked with displaying the total calculated value of all associated custom Invoice records directly on the Account record page. When trying to create a new custom field on the Account object, the administrator notices that the Roll-Up Summary field type option is greyed out and unavailable. What is the reason for this limitation?

Show answer & explanation

Answer: The Invoice custom object is linked to the Account object using a Lookup relationship instead of a Master-Detail relationship.

Answer

The Invoice custom object is linked to the Account object using a Lookup relationship instead of a Master-Detail relationship.
Roll-Up Summary fields are exclusively available on the master object in a Master-Detail relationship. Because the relationship between Account and Invoice is configured as a Lookup relationship, the Roll-Up Summary field option is disabled.

Step-by-Step Solution

1
Identify the relationship requirements for Roll-Up Summary fields
Roll-Up Summary fields require a Master-Detail relationship where the target object (Account) acts as the Master object.
Salesforce native Roll-Up Summary functionality depends on the strict parent-child metadata binding inherent only to Master-Detail relationships.
2
Evaluate the current object model configuration
Since the field type is disabled, the Account and Invoice objects must be connected via a Lookup relationship or possess no direct relationship.
If the relationship type is Lookup, Salesforce automatically disables the Roll-Up Summary field type during field creation on the parent object.

Key Concept

Roll-Up Summary Field Relationship Requirements
Question 389Question

The leadership team at Orion Global Logistics decides to realign their corporate accounting calendar. The Salesforce administrator is instructed to change the organization's Standard Fiscal Year start month from January to May within Setup. Which outcome should the administrator expect after saving this change?

Show answer & explanation

Answer: Salesforce automatically recalculates report date ranges and opportunity forecasting quotas based on the newly selected start month.

Answer

Salesforce automatically recalculates report date ranges and opportunity forecasting quotas based on the newly selected start month.
When modifying the start month under Standard Fiscal Year settings, Salesforce updates relative date references across reporting and forecasting automatically. It remains a standard fiscal year without requiring complex migration steps.

Step-by-Step Solution

1
Identify the type of fiscal year being updated in Setup.
The scenario specifically states the administrator is updating a Standard Fiscal Year.
Standard Fiscal Years follow standard 12-month calendar structures starting on the first day of any selected month.
2
Analyze the impact of updating the Standard Fiscal Year start month.
Existing records, forecasting periods, and relative report date filters (such as 'Current FY') automatically shift to reflect the new start month.
Salesforce handles recalculations for Standard Fiscal Year shifts natively without requiring custom setup or account freezing.

Key Concept

Standard Fiscal Year Configuration Impacts
Estimated Time:1m 15s
Question 390Question

A Salesforce Administrator needs to create a Roll-Up Summary field on the Account object to calculate the total value of related custom Project records. However, while attempting to create the new custom field on Account, the Administrator notices that the Roll-Up Summary field type is unavailable and cannot be selected. Which relationship configuration requirement explains why the Roll-Up Summary field option is disabled?

Show answer & explanation

Answer: The Account and Project objects are connected through a Lookup relationship rather than a Master-Detail relationship.

Answer

The Account and Project objects are connected through a Lookup relationship rather than a Master-Detail relationship.
In Salesforce, native Roll-Up Summary fields can only be created on the master object in a Master-Detail relationship. If two objects are linked via a Lookup relationship, the Roll-Up Summary field type option will be disabled during field creation on the parent object.

Step-by-Step Solution

1
Identify the requirement for creating Roll-Up Summary fields in Salesforce.
Roll-Up Summary fields calculate values from related child records, but require a Master-Detail relationship defined on the child object pointing to the master object.
Salesforce restricts Roll-Up Summary field creation to the master object in a Master-Detail relationship.
2
Evaluate the current configuration issue.
Because the field type option is grayed out on the parent object, a Master-Detail relationship does not exist between Account and Project.
If objects are linked via a Lookup relationship, Roll-Up Summary fields cannot be created using standard declarative field setup.

Key Concept

Roll-Up Summary Field Relationship Requirements
Question 391Question

CloudMetrics is creating a Delegated Administration group named "Support Leads Delegation" to offload operational management for regional support teams and custom tracking tools. The primary administrator needs to configure the group to grant maximum allowable authority without granting full System Administrator permissions. Which two administrative tasks can be granted to members of this Delegated Administration group? (Select 2 options.)

Select all that apply

Show answer & explanation

Answer: Creating and editing user accounts within specified roles and subordinate role hierarchies.; Managing custom fields, page layouts, and picklists for explicitly specified custom objects.

Answer

Delegated administrators can be granted authority to manage users within specified role hierarchies and administer specified custom objects (including fields and layouts). They cannot modify profile definitions directly or bypass system limitations on user deactivation.
Delegated Administration in Salesforce provides scoped administrative rights. Delegated admins can create and manage users within defined role hierarchies and manage specified custom objects (including custom fields, page layouts, and picklists).

Step-by-Step Solution

1
Evaluate user management capabilities in Delegated Administration.
Delegated administrators can create and edit users within specified role groups and their subordinates.
User administration delegation is scoped by explicit roles and subordinate roles defined in the delegation group setup.
2
Evaluate object management capabilities in Delegated Administration.
Delegated administrators can manage custom object definitions, fields, page layouts, and validation rules for specified custom objects.
Custom object delegation allows non-admin leads to maintain schema elements for designated custom objects without access to standard objects or system settings.
3
Evaluate security configuration and deactivation boundaries.
Profile permissions cannot be altered by delegated admins, and user deactivation restrictions apply universally.
Profile modification requires full system administration capabilities, and workflow owner dependencies prevent account deactivation.

Key Concept

Delegated Administration Boundaries
Question 392Question

A Salesforce administrator at a renewable energy firm is configuring custom fields on the Lead object to support a new solar installation tracking initiative. The administrator must map custom Lead fields for conversion to target objects and modify existing custom field data types on the Lead object. Which two statements accurately describe the technical behavior and considerations for custom field mapping and data type changes in Salesforce? (Select 2)

Select all that apply

Show answer & explanation

Answer: Custom Lead fields can be mapped to custom fields on Account, Contact, or Opportunity records if both fields have matching data types or compatible conversion targets.; Changing a custom field data type from Text to Picklist may result in data loss if existing record values do not match defined picklist values or length constraints.

Answer

The correct statements are that custom Lead fields can be mapped to custom fields on Account, Contact, or Opportunity records with compatible data types, and changing a custom field data type from Text to Picklist can cause data loss if existing data does not align with the new picklist constraints.
Mapping custom Lead fields requires compatible target data types on Account, Contact, or Opportunity records. Furthermore, modifying a custom field's data type from Text to Picklist presents data loss risks if existing text data does not match the newly defined picklist values.

Step-by-Step Solution

1
Analyze Lead custom field mapping mechanics during lead conversion.
Lead conversion requires mapped fields on target objects (Account, Contact, Opportunity) to share compatible data types (e.g., Text to Text, Picklist to Picklist). Roll-Up Summary fields and unmapped fields cannot receive lead conversion data automatically.
Salesforce enforces field compatibility to maintain data integrity during record creation upon conversion.
2
Evaluate data type conversion risks when altering existing custom fields.
Converting a field from a flexible type (Text) to a structured type (Picklist) carries data loss risks if existing text values are not included in the picklist value set.
Salesforce warns administrators of potential data loss whenever changing data types to less permissive structures.
3
Identify correct operational statements matching Salesforce field rules.
Mapping compatible fields across objects and acknowledging data loss when modifying field data types are correct statements.
These rules reflect Salesforce core administration standards for field management and lead processing.

Key Concept

Custom Field Data Types and Lead Field Mapping Rules
Question 393Question

A company requires that customer support representatives be strictly denied access to Salesforce whenever they attempt to log in from outside the corporate office network. Which setting should the Salesforce Administrator configure to enforce this location-based login restriction?

Show answer & explanation

Answer: Login IP Ranges specified on the user Profile

Answer

Configuring Login IP Ranges on the Profile assigned to the representatives.
Specifying Login IP Ranges on a user's Profile enforces strict IP restriction. If a user attempts to authenticate from an IP address outside the defined ranges, Salesforce completely denies the login attempt.

Step-by-Step Solution

1
Identify the requirement
Logins from outside specified IP ranges must be completely denied.
Security policies demand strict access enforcement based on origin IP.
2
Evaluate Salesforce security features for IP restriction
Profile-level Login IP Ranges explicitly deny access for IP addresses outside the defined range.
Organization-wide Network Access only manages identity verification prompts, whereas Profile settings enforce hard login blocks.

Key Concept

Profile Login IP Ranges vs. Network Access Trusted IPs
Question 394Question

An administrator at a medical device company is tasked with enforcing data quality on the custom object Inspection_Log__c. The compliance team mandates the following requirements for record updates:

1. When an existing Inspection_Log__c record has its Inspection_Stage__c picklist value changed to "Failed", the Failure_Reason__c text field must not be left blank.
2. The validation rule must NOT execute when creating new records, as initial automated intake allows a temporary blank reason.
3. The rule must NOT execute during subsequent updates if the Inspection_Stage__c field was already set to "Failed" prior to the current edit.

Which validation rule formula correctly enforces these business requirements?

Show answer & explanation

Answer: AND( NOT(ISNEW()), ISCHANGED(Inspection_Stage__c), ISPICKVAL(Inspection_Stage__c, "Failed"), ISBLANK(Failure_Reason__c) )

Answer

The formula AND( NOT(ISNEW()), ISCHANGED(Inspection_Stage__c), ISPICKVAL(Inspection_Stage__c, "Failed"), ISBLANK(Failure_Reason__c) ) correctly satisfies all specified requirements.
The correct formula combines NOT(ISNEW()), ISCHANGED(Inspection_Stage__c), ISPICKVAL(Inspection_Stage__c, "Failed"), and ISBLANK(Failure_Reason__c) inside an AND statement. This ensures the rule only fires when an existing record is edited, the stage field itself is changed during the save, the new stage value is 'Failed', and the failure reason field has been left empty.

Step-by-Step Solution

1
Exclude new record creation
Use NOT(ISNEW()) to ensure the rule only evaluates existing record edits.
Requirement 2 states the rule must not execute upon record creation.
2
Isolate stage changes
Include ISCHANGED(Inspection_Stage__c) in the logical AND condition.
Requirement 3 specifies the rule should not re-trigger on subsequent edits if the stage was already 'Failed' prior to the current save.
3
Validate target picklist value
Use ISPICKVAL(Inspection_Stage__c, "Failed") to test the new picklist state.
Requirement 1 targets transitions specifically entering the 'Failed' stage.
4
Check required text field population
Use ISBLANK(Failure_Reason__c) to detect missing field values accurately.
ISBLANK is the Salesforce best-practice function for evaluating null or empty text values.

Key Concept

Validation Rule Logic & Transition Checking with ISCHANGED, ISNEW, and ISBLANK
Question 395Question

A renewable energy company has 40 field technicians who all share the 'Standard Field Tech' profile. The administrator needs to grant two lead technicians temporary Read and Edit access to a custom object named 'Substation Maintenance' for a 60-day project. The remaining 38 technicians should not be able to view or edit this object. Which administrative approach meets this requirement while adhering to Salesforce security best practices?

Show answer & explanation

Answer: Create a Permission Set with Read and Edit permissions on the 'Substation Maintenance' object, assign it to the two lead technicians, and configure a permission set assignment expiration date of 60 days.

Answer

Create a Permission Set with Read and Edit permissions on the 'Substation Maintenance' object, assign it to the two lead technicians, and configure a permission set assignment expiration date of 60 days.
The correct solution uses a Permission Set to grant object-level Read and Edit permissions specifically to the two lead technicians. By utilizing permission set assignment expiration, access automatically revokes after 60 days, satisfying least privilege and avoiding profile duplication.

Step-by-Step Solution

1
Identify the baseline profile vs. additive permission requirements.
Since 38 out of 40 users should retain standard access while only 2 require extra permissions, access must be granted additively rather than altering the baseline profile.
Profiles define base access for job functions, whereas permission sets grant incremental permissions to specific users.
2
Determine the optimal mechanism for temporary additive access.
Create a Permission Set granting Read and Edit access on the custom object.
Permission Sets allow clean management of object permissions without cloning or proliferating profiles.
3
Configure the assignment duration constraint.
Set an expiration date of 60 days on the Permission Set assignment for the two lead technicians.
Salesforce supports built-in permission set assignment expiration dates, eliminating manual overhead after the project ends.

Key Concept

Additive Permissions via Permission Sets with Expiration
Question 396Question

Universal Containers tracks field equipment maintenance using a custom object named `Equipment_Maintenance__c`. The Organization-Wide Default (OWD) for the object is set to Private, and Grant Access Using Hierarchies is enabled. The security team establishes the following access requirements:
1. Regional Service Managers must automatically inherit access to maintenance records owned by Field Technicians reporting below them in the role hierarchy.
2. The Safety Compliance Team (a public group) must have Read-Only access to all maintenance records where the `Safety_Hazard__c` checkbox is marked `True`, regardless of who owns the record.
3. The Operations Director role must have Read/Write access to all maintenance records owned by users in the Field Technician role.

Which TWO administrative configuration steps are required to fulfill these requirements?

Select all that apply

Show answer & explanation

Answer: Create a criteria-based sharing rule on `Equipment_Maintenance__c` to grant Read-Only access to the Safety Compliance Team public group when `Safety_Hazard__c` equals `True`.; Create an owner-based sharing rule on `Equipment_Maintenance__c` to grant Read/Write access to the Operations Director role for records owned by the Field Technician role.

Answer

The administrator must create a criteria-based sharing rule to grant Read-Only access to the Safety Compliance Team when Safety_Hazard__c equals True, and create an owner-based sharing rule to grant Read/Write access to the Operations Director role for records owned by the Field Technician role.
Creating a criteria-based sharing rule selectively shares only records matching Safety_Hazard__c = True with the Safety Compliance Team public group. Creating an owner-based sharing rule explicitly grants Read/Write access to the Operations Director role for records owned by the Field Technician role. Existing role hierarchy settings already fulfill manager access without modification.

Step-by-Step Solution

1
Evaluate role hierarchy inheritance
Since 'Grant Access Using Hierarchies' is enabled on Equipment_Maintenance__c, Regional Service Managers automatically inherit access to records owned by subordinate Field Technicians without needing additional sharing rules.
Standard role hierarchy behavior automatically grants record access upward when Grant Access Using Hierarchies is checked.
2
Configure conditional access for the Safety Compliance Team
Create a criteria-based sharing rule on Equipment_Maintenance__c with condition Safety_Hazard__c = True, sharing Read-Only access with the Safety Compliance Team public group.
Criteria-based sharing rules evaluate specific record field values to open up record access beyond OWD restrictions to designated groups.
3
Configure role-based record sharing for the Operations Director
Create an owner-based sharing rule on Equipment_Maintenance__c targeting records owned by the Field Technician role and sharing Read/Write access with the Operations Director role.
Owner-based sharing rules extend record access laterally or across specific roles based on ownership.

Key Concept

Combining Organization-Wide Defaults, Role Hierarchy inheritance, owner-based sharing rules, and criteria-based sharing rules to meet complex record access requirements while maintaining least privilege.
Question 397Question

An administrator is configuring access for a custom object named Equipment_Inspection__c with an Organization-Wide Default (OWD) set to Private. Which setting ensures that managers automatically gain access to records created by their direct reports in the role hierarchy?

Show answer & explanation

Answer: Enable the 'Grant Access Using Hierarchies' option for the custom object in Organization-Wide Defaults.

Answer

Enable the 'Grant Access Using Hierarchies' option for the custom object in Organization-Wide Defaults.
For custom objects in Salesforce, enabling 'Grant Access Using Hierarchies' in Organization-Wide Sharing Settings allows users in higher roles to automatically inherit the record permissions granted to users in roles below them in the hierarchy.

Step-by-Step Solution

1
Identify the requirement
Gaining record access for managers above record owners in the role hierarchy.
The scenario requires users higher in the role hierarchy to automatically inherit access to records owned by subordinates.
2
Evaluate Salesforce security mechanisms
Grant Access Using Hierarchies is the built-in mechanism for custom objects.
For custom objects, when OWD is Private, selecting 'Grant Access Using Hierarchies' ensures managers automatically inherit record access rights of lower roles.

Key Concept

Role Hierarchy Access Inheritance for Custom Objects
Question 398Question

A Salesforce administrator needs to create a Roll-Up Summary field on the Account object to calculate the sum of related custom record amounts. When attempting to create the field, the administrator notices that the Roll-Up Summary field type option is greyed out and unavailable. Upon reviewing the custom object schema, the administrator sees that the custom object is linked to Account using a Lookup relationship. Which action must the administrator take to enable the creation of a Roll-Up Summary field on the Account object?

Show answer & explanation

Answer: Convert the Lookup relationship field on the custom object to a Master-Detail relationship.

Answer

Convert the Lookup relationship field on the custom object to a Master-Detail relationship.
In Salesforce, standard Roll-Up Summary fields can only be created on the master object in a Master-Detail relationship. Converting an existing Lookup field to a Master-Detail relationship (ensuring all child records have a parent assigned first) makes the Roll-Up Summary field type available on the parent object.

Step-by-Step Solution

1
Identify the prerequisite for Roll-Up Summary fields in Salesforce.
Standard Roll-Up Summary fields are strictly supported on the master object of a Master-Detail relationship.
Lookup relationships do not natively support standard Roll-Up Summary fields because child records can exist independently without a parent.
2
Determine the necessary relationship modification.
Verify that all existing custom child records have a populated lookup value to Account, then change the field type from Lookup to Master-Detail.
Converting the relationship to Master-Detail establishes tight coupling, enabling the master object (Account) to aggregate child values via Roll-Up Summary fields.

Key Concept

Roll-Up Summary Prerequisite & Relationship Conversion
Question 399Question

A Salesforce Administrator at Beacon Renewable Energy is setting up a new Lightning Service Console application for support specialists. The business has specified two main operational requirements:
1. Support agents must have persistent access to productivity tools, such as Omni-Channel and History, anchored at the bottom of their workspace screen regardless of which record tab is currently selected.
2. When opening an Account record, any associated child records (such as Cases and Contacts) must automatically open as subtabs beneath the primary Account tab.

Which TWO configuration steps should the administrator perform in App Manager to meet these requirements?

Select all that apply

Show answer & explanation

Answer: Add the desired productivity components to the Utility Bar within the app configuration settings.; Set up Navigation Rules within the app settings to define child records as subtabs under the Account primary tab.

Answer

The administrator must add the productivity components to the Utility Bar in the app settings and configure Navigation Rules so child records open as subtabs under the Account primary tab.
To satisfy persistent footer tool requirements, administrators add items to the app's Utility Bar. To control whether related records open as primary tabs or subtabs, administrators configure Navigation Rules in the App Manager.

Step-by-Step Solution

1
Configure the console app's Utility Bar in App Manager.
Omni-Channel and History components become persistently available to agents in the app footer.
Utility Bar items are fixed components positioned at the bottom footer of a Lightning Service Console app.
2
Configure Navigation Rules for the app in App Manager.
Child objects like Cases and Contacts open as subtabs under the primary Account tab.
Navigation Rules govern whether workspace records open as primary tabs or subtabs relative to parent records.

Key Concept

Lightning Service Console App Configuration: Utility Bar and Navigation Rules
Estimated Time:1m 30s
Question 400Question

An administrator at a higher education institution is building a custom data model to manage campus facilities. The institution requires that when a Venue custom object record is deleted, all associated Event Reservation custom object records are automatically deleted from the system as well. Which field configuration should the administrator implement on the Event Reservation object to support this requirement?

Show answer & explanation

Answer: Create a Master-Detail relationship field referencing the Venue object.

Answer

The administrator should create a Master-Detail relationship field on the Event Reservation custom object that references the Venue custom object.
Creating a Master-Detail relationship field on the Event Reservation object pointing to the Venue object establishes Venue as the master and Event Reservation as the detail record. In a Master-Detail relationship, deleting the master record automatically cascades and deletes all related detail records, satisfying the requirement.

Step-by-Step Solution

1
Identify the parent and child objects based on business requirements.
Venue is the parent object, and Event Reservation is the child object.
The lifetime of an Event Reservation depends on the existence of the Venue.
2
Determine the necessary relationship behavior for deletion.
Cascading deletion is required so that removing a Venue automatically deletes all associated Event Reservations.
Master-Detail relationships strictly enforce cascade deletion of detail records when the master record is deleted.
3
Select the correct location for creating the relationship field.
The Master-Detail relationship field must be created on the detail object (Event Reservation).
In Salesforce, relationship custom fields are always defined on the child object pointing to the parent object.

Key Concept

Master-Detail Relationship Cascade Deletion
PreviousPage 20 / 90Next
All practice questions — Salesforce Certified Administrator | Examkin