All practice questions

1784 questions

Question 481Question

An organization's security policy mandates that standard users change their passwords every 90 days. However, to satisfy compliance requirements, users assigned to the Executive Operations team must change their passwords every 30 days. Which administrative action should a Salesforce administrator take to enforce this password expiration requirement specifically for the Executive Operations team?

Show answer & explanation

Answer: Edit the Password Policies settings on the Profile assigned to the Executive Operations team to expire passwords in 30 days.

Answer

The administrator should edit the Password Policies settings directly on the Profile assigned to the Executive Operations team to set password expiration to 30 days.
In Salesforce, Password Policies configured at the Profile level override the default Organization-Wide Password Policies. Setting the password expiration to 30 days on the specific Profile assigned to the Executive Operations team successfully enforces the requirement for those users without impacting standard users.

Step-by-Step Solution

1
Identify the administrative location where password policy overrides are configured for specific groups of users.
Determine that Profile-level password policies take precedence over Organization-Wide settings.
Organization-Wide policies establish defaults, but individual Profiles permit granular security control overrides.
2
Navigate to Setup -> Profiles and select the target profile assigned to the Executive Operations team.
Access the profile configuration interface.
Security controls such as password policies are maintained directly within the Profile configuration.
3
Edit the Password Policies section on the Profile to set password expiration to 30 Days.
Enforce the stricter 30-day password expiration requirement for all users assigned to that Profile.
This achieves the compliance requirement without altering password expiration timelines for standard users.

Key Concept

Profile-Level Password Policy Overrides
Question 482Question

An administrator at Cloud Kicks is configuring field requirements for a custom parent object, Equipment_Service_Plan__c, and a custom child object, Service_Log__c. The two objects are connected via a Lookup relationship so that service logs can be retained independently if a service plan is deactivated. The operations team requires a field on Equipment_Service_Plan__c that displays the total accumulated cost of all completed Service_Log__c records. Which configuration strategy should the administrator implement to fulfill this requirement while maintaining the existing relationship architecture?

Show answer & explanation

Answer: Create a declarative Record-Triggered Flow on Service_Log__c that executes upon creation or update to calculate and update a custom currency field on Equipment_Service_Plan__c.

Answer

The administrator should build a declarative Record-Triggered Flow on Service_Log__c that calculates the total cost of completed records and updates a custom currency field on Equipment_Service_Plan__c.
Because standard Roll-Up Summary fields are strictly limited to Master-Detail relationships, an administrator must use declarative automation such as Record-Triggered Flows (or Apex triggers) to aggregate child record data up to a parent record connected via a Lookup relationship. This preserves the independent lifecycle of the child records while meeting the reporting requirement.

Step-by-Step Solution

1
Analyze object relationship constraints
Equipment_Service_Plan__c and Service_Log__c are joined via a Lookup relationship to preserve child records independently upon parent deactivation/deletion.
Master-Detail relationships enforce cascading deletes, which violates the requirement to retain service logs.
2
Evaluate native Roll-Up Summary field availability
Native Roll-Up Summary fields are disabled for Lookup relationships in standard Salesforce functionality.
Roll-Up Summary fields strictly require a Master-Detail relationship between parent and child objects.
3
Evaluate alternative declarative automation tools
A Record-Triggered Flow can summarize child record values and update a parent custom field without altering relationship definitions.
Flow automation provides custom roll-up capabilities while keeping the underlying Lookup relationship architecture intact.

Key Concept

Roll-Up Summary Relationship Prerequisites and Declarative Workarounds
Estimated Time:2m 0s
Question 483Question

An administrator at a professional services firm needs to display the aggregate total of billable hours from child Time_Entry__c records on the parent Consulting_Engagement__c object. The two custom objects are currently connected via a Lookup relationship. When attempting to create a Roll-Up Summary field on Consulting_Engagement__c, the administrator notices that the Roll-Up Summary field type is disabled in the setup wizard. Upon investigating the data, several existing Time_Entry__c records have a blank Consulting_Engagement__c lookup field. What sequence of actions must the administrator take to successfully create the Roll-Up Summary field on Consulting_Engagement__c?

Show answer & explanation

Answer: Populate the Consulting_Engagement__c lookup field on all existing child Time_Entry__c records, convert the relationship field on Time_Entry__c from Lookup to Master-Detail, and then create the Roll-Up Summary field on Consulting_Engagement__c.

Answer

Populate the Consulting_Engagement__c lookup field on all existing child Time_Entry__c records, convert the relationship field on Time_Entry__c from Lookup to Master-Detail, and then create the Roll-Up Summary field on Consulting_Engagement__c.
The option stating that all existing child records must have their lookup field populated prior to converting the relationship from Lookup to Master-Detail correctly follows Salesforce architecture requirements. Roll-Up Summary fields are exclusively available on the master side of Master-Detail relationships. To convert an existing Lookup field to a Master-Detail field, every existing detail record must contain a populated reference to a master record.

Step-by-Step Solution

1
Identify why Roll-Up Summary field creation is disabled
Recognize that Roll-Up Summary fields can only be created on the master object in a Master-Detail relationship.
Lookup relationships do not natively support declarative Roll-Up Summary fields.
2
Prepare child records for relationship conversion
Ensure 100% of existing child Time_Entry__c records have a valid reference in the Consulting_Engagement__c lookup field.
Salesforce enforces data integrity by preventing conversion from Lookup to Master-Detail if orphan child records exist.
3
Convert relationship and build Roll-Up Summary
Convert the lookup field on Time_Entry__c to a Master-Detail relationship type, then create the Roll-Up Summary field on Consulting_Engagement__c using the SUM aggregate function.
Once converted, the parent object permits native declarative aggregation of child records.

Key Concept

Roll-Up Summary Relationship Requirements and Conversion Prerequisites
Question 484Question

An administrator at a healthcare logistics company needs to immediately block system access for an operations coordinator who has recently left the organization. The user is currently designated as a required approver in an active approval process. Which two statements describe the primary reasons for freezing the user account instead of deactivating it? (Select 2 answers)

Select all that apply

Show answer & explanation

Answer: Freezing prevents the user from logging into Salesforce immediately without breaking active system processes.; Freezing allows the administrator time to reassign pending approval requests and references before deactivating the account.

Answer

Freezing the account prevents user login while maintaining system dependencies, and it gives administrators time to reassign active processes before deactivation.
Freezing a user account immediately prevents login while keeping system references active, allowing administrators the necessary time to reassign pending approval requests before deactivating the user.

Step-by-Step Solution

1
Analyze the immediate operational requirements when revoking access for a user with system dependencies.
Determine that immediate deactivation might fail or disrupt active approval processes.
Users linked to ongoing automation or approval processes require temporary access restriction first.
2
Evaluate the functional behavior of freezing a user account.
Confirm that freezing prevents login and keeps dependencies intact while retaining the license.
Freezing allows administrators to perform necessary administrative cleanups prior to account deactivation.

Key Concept

User Freezing vs. Deactivation Rationale
Question 485Question

An administrator is configuring field calculations between related objects in Salesforce. Which two statements accurately describe the functional capabilities and constraints of Roll-Up Summary fields and Formula fields? (Select 2)

Select all that apply

Show answer & explanation

Answer: A Roll-Up Summary field can be created on the master object of a Master-Detail relationship to calculate SUM, MIN, MAX, or COUNT of child records.; Cross-object formula fields can reference fields from parent objects up to 10 relationships away.

Answer

Roll-Up Summary fields can calculate aggregate metrics (SUM, MIN, MAX, COUNT) on the master object in a Master-Detail relationship, and cross-object formulas can reference fields up to 10 parent relationships away.
The correct statements recognize that Roll-Up Summary fields require a Master-Detail relationship to aggregate child data using functions like SUM, MIN, MAX, and COUNT, and that cross-object formulas can span up to 10 parent relationships.

Step-by-Step Solution

1
Identify relationship requirements for Roll-Up Summary fields.
Roll-Up Summary fields require a Master-Detail relationship and cannot be created over Lookup relationships, even if the lookup field is marked as required.
Salesforce enforces master-detail relationships for roll-up fields to ensure tight data binding and automatic recalculation.
2
Evaluate cross-object formula field limitations.
Cross-object formulas can traverse up to 10 relationship levels to display or calculate values from parent objects.
This is a standard platform limit enforced by Salesforce for formula field compilation.
3
Determine deletion impact on roll-up calculations.
Deleted records residing in the Recycle Bin are automatically excluded from Roll-Up Summary metrics.
Only active child records associated with the master record are evaluated in roll-up calculations.

Key Concept

Roll-Up Summary fields require Master-Detail relationships and support aggregate functions, whereas cross-object formula fields enable spanning up to 10 parent relationships.
Question 486Question

A Salesforce administrator at a telecommunications service provider needs to ensure that when a Lead record is converted, the value stored in a custom date field named Initial_Site_Survey_Date__c on the Lead object is transferred to a custom date field on the resulting Opportunity record. The custom field on the Opportunity object has already been created with a matching data type. Which action must the administrator take to ensure this field value transfers during lead conversion?

Show answer & explanation

Answer: Navigate to Object Manager for the Lead object and configure custom field mapping under the Map Lead Fields interface.

Answer

Navigate to Object Manager for the Lead object and configure custom field mapping under the Map Lead Fields interface.
Mapping the custom lead field using the Map Lead Fields interface in the Lead object settings explicitly configures Salesforce to copy data from the Lead field to the designated target field on the Account, Contact, or Opportunity object upon lead conversion.

Step-by-Step Solution

1
Identify the object management tool required for Lead conversion mapping.
Lead custom field mapping is managed specifically under the Lead object settings.
Custom lead fields require explicit mapping rules to transfer data onto Account, Contact, or Opportunity custom fields during conversion.
2
Open Object Manager > Lead > Fields & Relationships and select Map Lead Fields.
The Lead conversion field mapping table is presented.
This interface allows selecting target custom fields on Account, Contact, and Opportunity that have compatible data types.
3
Map Initial_Site_Survey_Date__c under the Opportunity tab to the corresponding Opportunity date field.
The field value will now automatically populate on Opportunity creation during lead conversion.
Explicitly linking the fields establishes the data transfer definition used by the conversion process.

Key Concept

Custom Lead Field Mapping during Lead Conversion
Estimated Time:1m 30s
Question 487Question

An administrator at an enterprise firm needs to provision access for a newly hired Internal Auditor. The auditor requires baseline Read access to Accounts and Contacts, identical to 40 executive users currently assigned to the standard 'Executive User' profile. In addition, the auditor requires Read access to a custom 'Audit Logs' object. The security team also specifies that the auditor must be strictly restricted from logging into Salesforce outside the corporate office IP address range, whereas executive users assigned to the existing baseline profile must retain the ability to log in from any location. Which administrative solution fulfills these provisioning and security requirements while adhering to Salesforce best practices?

Show answer & explanation

Answer: Clone the 'Executive User' profile to create an 'Internal Auditor' profile, specify the corporate IP range under Login IP Ranges on the new profile, and assign a Permission Set to the auditor that grants Read access to the Audit Logs object.

Answer

Clone the baseline profile to create a dedicated profile where profile-level Login IP Ranges can be applied specifically to the auditor, and grant access to the custom object via a Permission Set.
The correct solution creates a distinct profile for the auditor so that Profile Login IP Ranges can strictly restrict logins to the corporate office IP range without affecting other users. It then uses a Permission Set to additively grant Read access to the Audit Logs object, adhering to Salesforce security best practices.

Step-by-Step Solution

1
Analyze security boundaries for profile vs permission set assignment.
Login IP Ranges are defined at the Profile level, not via Permission Sets. Because executive users must retain unrestricted location access while the auditor must be restricted, the auditor requires a separate profile.
Profile settings apply to all users assigned to that profile; modifying a shared profile's Login IP Ranges affects all existing users.
2
Determine object permission provisioning method.
Keep the cloned profile minimal and grant custom object ('Audit Logs') Read permissions using a Permission Set.
Salesforce security best practices mandate using Permission Sets for additive object and field permissions.
3
Evaluate network security mechanisms.
Use Profile Login IP Ranges to deny logins outside the corporate IP subnet.
Organization-wide Network Access entries only whitelist IP addresses to prevent activation challenges, whereas Profile Login IP Ranges strictly restrict access outside the specified ranges.

Key Concept

Profile IP Restrictions and Additive Permission Provisioning
Estimated Time:2m 0s
Question 488Question

An administrator at an automotive manufacturer is designing a security architecture to manage user permissions efficiently across sales, service, and external auditing teams. Match each administrative access requirement to the appropriate Salesforce permission management feature.

Click a left item, then click its matching right item

Items

Consolidate multiple permission sets granting order processing, discount approvals, and reporting capabilities into a single assignment unit for regional managers.
Explicitly remove the 'Delete' permission on Warranty Claims for contractor support agents who are assigned a broader service permission set group.
Grant elevated 'View All' object permissions on Inventory Records to three quality leads without modifying their baseline user profile.
Define an automated, scheduled end date for specialized analytics access granted to external compliance auditors.

Matches

Show answer & explanation

Answer

The administrative requirements match as follows: bundling multiple permission sets into one unit matches Permission Set Group; restricting specific permissions within a group matches Muting Permission Set; extending supplementary access to select users matches Standalone Permission Set; and configuring automatic access termination matches Permission Set Assignment Expiration.
Each security mechanism directly aligns with Salesforce administrative best practices: Permission Set Groups consolidate related permission sets into job-based roles; Muting Permission Sets grant targeted restriction within consolidated groups; Standalone Permission Sets provide additive permissions without profile alterations; and Assignment Expirations manage time-bound access automatically.

Step-by-Step Solution

1
Analyze requirement 1 (bundling permissions)
Identified Permission Set Group as the feature designed to package multiple permission sets together.
Permission Set Groups streamline administration by combining granular permission sets into job-function roles.
2
Analyze requirement 2 (restricting specific permissions within a group)
Identified Muting Permission Set as the mechanism to suppress permissions.
Muting permission sets override enabled permissions in a Permission Set Group for tailored access control.
3
Analyze requirement 3 (granting additive access without profile changes)
Identified Standalone Permission Set as the standard solution.
Profiles establish baseline access; permission sets grant additional permissions to specific users on top of profiles.
4
Analyze requirement 4 (setting automated access end dates)
Identified Permission Set Assignment Expiration.
Setting an expiration date during assignment ensures compliance and automatic revocation for temporary roles.

Key Concept

Salesforce Permission Sets, Permission Set Groups, Muting Permission Sets, and User Assignment Expiration
Question 489Question

A Salesforce administrator uses Lightning App Builder to migrate an Opportunity record page to Dynamic Forms. To protect sensitive financial information, the administrator sets a component visibility rule on the Annual Revenue field so that it only displays on the page when the viewing user has the Custom Finance profile. Which statement accurately describes the effect of this configuration on users with other profiles?

Show answer & explanation

Answer: Users without the Custom Finance profile can still view the field data in reports, list views, and API queries if Field-Level Security allows access.

Answer

Users without the Custom Finance profile can still view the field data in reports, list views, and API queries if Field-Level Security allows access.
Lightning App Builder component visibility filters control whether a component or field section is rendered visually on a specific Lightning Record Page. They do not alter object-level permissions or Field-Level Security (FLS). If FLS grants read access to a user, that user can still access the field's data through reports, list views, global search, and API integrations.

Step-by-Step Solution

1
Analyze the scope of Dynamic Forms component visibility filters.
Dynamic Forms component visibility rules are presentation-layer filters applied strictly to the user interface of the Lightning Record Page.
Understanding layer separation ensures administrators do not rely on layout rules for security enforcement.
2
Evaluate data access mechanisms outside the record page.
Reports, list views, global search, and API queries bypass page layout visibility and rely strictly on Field-Level Security (FLS) and Object-Level Permissions.
Field-Level Security is the authoritative control for field data visibility across the platform.

Key Concept

Dynamic Forms Component Visibility vs. Field-Level Security
Question 490Question

Match each Salesforce security requirement to the correct security feature or configuration setting used to implement it.

Click a left item, then click its matching right item

Items

Restricting access to a sensitive custom field across all page layouts and API calls for users assigned to a specific profile
Restricting the hours during which users assigned to a profile are allowed to log into the Salesforce organization
Defining baseline Create, Read, Edit, and Delete access to standard objects for a default group of users
Granting additional field visibility or object permissions to select individual users without changing their profile

Matches

Show answer & explanation

Answer

Field-Level Security matches field-level restrictions across layouts and API. Login Hours restrict time-based access on profiles. Object Permissions on profiles define baseline object CRUD access. Permission Sets grant additional access to specific users.
Each security requirement correctly aligns with its Salesforce administrative mechanism: Field-Level Security enforces field-level access universally; Profile Login Hours restrict login times per profile; Profile Object Permissions establish baseline object CRUD permissions; and Permission Sets provide additive permissions for specific users.

Step-by-Step Solution

1
Identify field access controls
Field-Level Security (FLS) enforces field visibility universally, ensuring fields remain hidden regardless of page layout assignment.
FLS is the authoritative mechanism for field visibility across the entire org, including API and reports.
2
Identify user session and login controls
Profile Login Hours enforce time window restrictions on login attempts for users assigned to that profile.
Login hours are configured directly at the profile level.
3
Differentiate object permissions from additive permission assignment
Profiles set baseline Object Permissions (Create, Read, Edit, Delete), whereas Permission Sets addively grant extra permissions to targeted individuals.
Salesforce security principles mandate restrictive baseline profiles supplemented by additive permission sets.

Key Concept

Profiles and Object/Field-Level Security Controls
Question 491Question

An organization is setting up a new customer support desk in Frankfurt operating on Central European Time (CET). The administrator has defined a custom Business Hours record named 'Frankfurt Support Hours' and created a Holiday record named 'German Unity Day'. Which two configuration steps must the administrator complete to ensure that Case Escalation Rules correctly pause elapsed time calculations during company holidays for cases handled by this desk? (Select 2 options)

Select all that apply

Show answer & explanation

Answer: Associate the 'German Unity Day' holiday record with the 'Frankfurt Support Hours' business hours schedule.; Specify 'Frankfurt Support Hours' on the Case Escalation Rule entries or configure cases to inherit business hours from the case record.

Answer

The administrator must associate the holiday record directly with the custom Business Hours schedule and configure Case Escalation Rule entries to specify or inherit those Business Hours.
To ensure holiday suspensions apply to SLA escalation timers, the holiday record must be linked to the relevant Business Hours schedule, and the Case Escalation Rule entry must reference those Business Hours (or inherit them from the Case).

Step-by-Step Solution

1
Associate the Holiday with Business Hours
The holiday schedule is tied directly to the operational hours of the Frankfurt support team.
Creating a Holiday record alone does not pause SLA timers; it must be explicitly linked to one or more Business Hours definitions.
2
Assign Business Hours to Case Escalation Rule Entries
Escalation rule calculations evaluate elapsed time strictly against the specified Business Hours and associated holidays.
Escalation rules rely on the designated Business Hours setting on the rule entry or case record to determine operational vs non-operational time.

Key Concept

Business Hours and Holiday association in Case Escalation Rules
Estimated Time:1m 30s
Question 492Question

BioHealth Labs utilizes a custom object named Product_Batch__c to track pharmaceutical production data. Most Quality Assurance inspectors assigned to the custom profile 'QA Inspector' must not be able to view or edit the sensitive Formulation_Secret__c field on this object. However, three Lead QA Inspectors who share the same 'QA Inspector' profile require Read and Edit access to Formulation_Secret__c across all interfaces, including reports, list views, and the API. Which configuration should the administrator implement to satisfy these security requirements while minimizing administrative overhead?

Show answer & explanation

Answer: Set Field-Level Security (FLS) for Formulation_Secret__c to deselect Visible on the 'QA Inspector' profile, create a Permission Set granting Read and Edit access to Formulation_Secret__c, and assign the Permission Set to the three Lead QA Inspectors.

Answer

Set Field-Level Security (FLS) on Formulation_Secret__c to deselect Visible for the 'QA Inspector' profile, create a Permission Set granting Read and Edit access to Formulation_Secret__c, and assign the Permission Set to the three Lead QA Inspectors.
The option advocating setting Field-Level Security to hidden on the profile and granting access via a Permission Set correctly follows Salesforce security architecture. Profile FLS acts as the restrictive base, ensuring the field is protected across all interfaces (reports, API, list views, record pages), while the Permission Set seamlessly extends Read and Edit access to specific users without profile duplication.

Step-by-Step Solution

1
Identify the base security level needed for the majority of users assigned to the profile.
Since most 'QA Inspector' profile users should not see Formulation_Secret__c, deselecting 'Visible' on the 'QA Inspector' profile establishes a secure default across all UI and API channels.
Profiles set the baseline permissions for users sharing that profile role.
2
Determine the optimal mechanism to grant elevated access to a subset of users.
Permission Sets grant additive permissions to individual users without requiring dedicated custom profiles.
Salesforce best practice dictates keeping profile counts low and using Permission Sets for specialized user access.
3
Assign the new Permission Set containing Read and Edit FLS for Formulation_Secret__c to the three Lead QA Inspectors.
The three Lead QA Inspectors gain full Read and Edit access to the field across reports, list views, and API, while other inspectors remain restricted.
Combining restrictive baseline FLS with additive Permission Sets satisfies the principle of least privilege efficiently.

Key Concept

Field-Level Security (FLS) Baseline & Permission Set Extension
Question 493Question

A customer support manager at a medical technology firm requires newly created high-priority cases to be routed immediately to a specialized Tier 2 Support Queue upon record creation. During implementation, an administrator creates an Escalation Rule entry configured to reassign the case to the Tier 2 Support Queue instead of using a Case Assignment Rule. Which outcome will occur as a result of this setup?

Show answer & explanation

Answer: The case will initially be assigned to the default case owner and will only be reassigned to the Tier 2 Support Queue after the escalation rule's time-based age criteria are met.

Answer

The case will initially be assigned to the default case owner and will only be reassigned to the Tier 2 Support Queue after the escalation rule's time-based age criteria are met.
Case Assignment Rules are designed to define initial case ownership (users or queues) automatically when cases are created. Escalation Rules are designed to locate unaddressed cases that meet specific criteria and reassign or notify individuals after a predefined time limit has elapsed. Attempting to use an Escalation Rule for immediate routing results in the case initially falling to the default case owner until the escalation time criteria trigger.

Step-by-Step Solution

1
Differentiate between the primary functions of Case Assignment Rules and Escalation Rules.
Case Assignment Rules determine initial case ownership upon record creation, whereas Escalation Rules perform actions after a case has remained open for a specified period.
Correct rule selection depends on whether action is needed immediately on creation or after a elapsed duration.
2
Analyze the effect of substituting an Escalation Rule for initial routing.
Because no Case Assignment Rule routed the record immediately, ownership defaults to the running user or default case owner. The Escalation Rule will only evaluate time criteria later.
Escalation rules require time thresholds to elapse before performing escalation actions.

Key Concept

Case Assignment Rules vs. Escalation Rules
Question 494Question

A wealth management firm tracks sensitive private market deals using a custom object named Private_Investment__c. Executive management mandates that standard advisors should only access investment records they own. Furthermore, due to strict regulatory compliance, managers higher in the role hierarchy must NOT automatically inherit record access to investments owned by their direct reports. Which TWO configuration settings must the administrator implement to fulfill these security requirements? (Select TWO answers.)

Select all that apply

Show answer & explanation

Answer: Set the Organization-Wide Default (OWD) internal access for Private_Investment__c to Private.; Deselect the 'Grant Access Using Hierarchies' checkbox for the Private_Investment__c custom object in Organization-Wide Sharing Settings.

Answer

To meet the compliance requirements, the administrator must set the Organization-Wide Default (OWD) for the Private_Investment__c custom object to Private and uncheck the 'Grant Access Using Hierarchies' setting on the object's organization-wide sharing default configuration.
Setting the OWD internal access to Private ensures that users have no access to records owned by others by default. For custom objects, deselecting the 'Grant Access Using Hierarchies' setting prevents higher-level roles in the hierarchy from gaining automatic record access to records owned by subordinates.

Step-by-Step Solution

1
Determine baseline record visibility
Setting the Organization-Wide Default (OWD) to Private ensures that standard users cannot see records owned by other users.
OWD defines the most restrictive baseline level of data access across the entire organization.
2
Evaluate role hierarchy propagation for custom objects
Deselecting 'Grant Access Using Hierarchies' disables automatic access propagation up the role hierarchy.
By default, Salesforce enables hierarchy access for custom objects. Explicitly unchecking this setting prevents managers from automatically seeing records owned by lower roles.

Key Concept

Organization-Wide Defaults and Hierarchy Access for Custom Objects
Question 495Question

A Salesforce administrator needs to display the total sum of all related child record amounts on a custom parent object. However, when creating a new field on the parent object, the Roll-Up Summary field type option is greyed out and cannot be selected. What is the primary reason the administrator is unable to create a Roll-Up Summary field?

Show answer & explanation

Answer: The relationship between the parent object and the child object is a Lookup relationship rather than a Master-Detail relationship.

Answer

The relationship between the parent object and the child object is a Lookup relationship rather than a Master-Detail relationship.
Declarative Roll-Up Summary fields are only available on the master object in a Master-Detail relationship. When objects are connected via a Lookup relationship, Salesforce disables the Roll-Up Summary field option during custom field creation.

Step-by-Step Solution

1
Identify the field requirement
The administrator needs to summarize data from child records onto a parent record using standard Salesforce field configuration.
Roll-Up Summary fields perform aggregate functions (SUM, COUNT, MIN, MAX) on child records.
2
Evaluate relationship type prerequisite
Native Roll-Up Summary fields require a Master-Detail relationship.
If objects are connected via a standard Lookup relationship, Salesforce disables the Roll-Up Summary field type during field creation.

Key Concept

Roll-Up Summary fields require a Master-Detail relationship between parent and child objects.
Question 496Question

An administrator at Global Renewables sets the Organization-Wide Default (OWD) for a custom object named Facility_Inspection__c to Private and deselects the 'Grant Access Using Hierarchies' option on the object definition to prevent automatic manager access. Executive leadership now requires that users assigned to the 'Safety Director' role receive Read-Only access to all Facility_Inspection__c records owned by users in the 'Inspector' role. Which configuration should the administrator implement to fulfill this requirement without re-enabling automatic role hierarchy access for all other roles?

Show answer & explanation

Answer: Create an owner-based sharing rule on Facility_Inspection__c that shares records owned by members of the 'Inspector' role with members of the 'Safety Director' role.

Answer

The administrator should create an owner-based sharing rule on Facility_Inspection__c that shares records owned by members of the 'Inspector' role with members of the 'Safety Director' role.
Creating an owner-based sharing rule allows the administrator to share records owned by users in the 'Inspector' role with users in the 'Safety Director' role with Read-Only access. This approach works when OWD is Private and operates independently of the 'Grant Access Using Hierarchies' setting on the custom object.

Step-by-Step Solution

1
Analyze the existing Organization-Wide Default (OWD) and hierarchy access settings.
Facility_Inspection__c has a Private OWD, and automatic access roll-up via the role hierarchy is disabled.
Deselecting 'Grant Access Using Hierarchies' on custom objects stops automatic access propagation to higher roles.
2
Identify the target access requirement.
The 'Safety Director' role requires access specifically to records owned by the 'Inspector' role.
Access must be granted selectively based on record ownership without turning hierarchy access back on globally for the object.
3
Select the appropriate sharing mechanism.
Configure an owner-based sharing rule specifying the 'Inspector' role as the source owner group and the 'Safety Director' role as the target recipient group.
Owner-based sharing rules provide targeted cross-role visibility without changing overall object-level hierarchy settings.

Key Concept

Owner-Based Sharing Rules vs. Custom Object Role Hierarchy Settings
Question 497Question

A Salesforce Administrator is configuring security controls for an enterprise organization. Match each security requirement scenario to the correct administrative configuration location in Salesforce Setup where it must be configured.

Click a left item, then click its matching right item

Items

Enforce a 15-minute session inactivity timeout exclusively for users assigned to the Customer Support Representative profile.
Define the default organization-wide password complexity requirement to include alpha, numeric, and special characters.
Terminate active sessions and force re-authentication when a user's session expires due to inactivity across all profiles by default.
Set maximum invalid login attempts to 3 before locking out users specifically assigned to the System Administrator profile.

Matches

Show answer & explanation

Answer

1. Enforce a 15-minute session timeout for a specific profile maps to Profile Session Settings. 2. Define default org-wide password complexity maps to Organization-Wide Password Policies. 3. Force logout on session timeout across all profiles maps to Organization-Wide Session Settings. 4. Set maximum invalid login attempts for a specific profile maps to Profile Password Policies.
Each scenario correctly differentiates between session settings (timeout/logout behavior) and password policies (lockout/complexity), as well as between organization-wide baseline defaults and profile-level override configurations.

Step-by-Step Solution

1
Analyze whether each requirement applies globally to the entire organization or is specific to a target profile.
Requirements targeting specific user profiles must be configured at the Profile level, whereas baseline defaults for the entire org belong at the Organization-Wide level.
Salesforce allows profile-level security policies to override default organization-wide settings for session timeout and password restrictions.
2
Distinguish between Session Settings and Password Policies for each scenario.
Timeouts and force logout behaviors are Session Settings; password complexity and lockout thresholds are Password Policies.
Session settings govern active user connections and session lifecycles, while password policies govern credential creation and login attempt constraints.
3
Map each scenario to its correct setup interface.
The profile session timeout maps to Profile Session Settings, org-wide complexity maps to Organization-Wide Password Policies, global forced logout maps to Organization-Wide Session Settings, and profile-specific lockout attempts map to Profile Password Policies.
This satisfies both the functional scope (Session vs Password) and administrative hierarchy (Org-wide default vs Profile override).

Key Concept

Salesforce Session Settings vs. Password Policies Hierarchy (Organization-Wide Defaults vs. Profile Overrides)
Estimated Time:1m 30s
Question 498Question

CloudScale Technologies uses a custom object named Software_License_Request__c to manage internal software requests. The Organization-Wide Default (OWD) sharing setting for this object is set to Private. The administrator needs to guarantee that managers automatically inherit access to software request records owned by their direct reports without setting up manual sharing or individual sharing rules. Which configuration on the custom object achieves this requirement?

Show answer & explanation

Answer: Ensure the 'Grant Access Using Hierarchies' checkbox is selected in the custom object sharing settings.

Answer

Select the 'Grant Access Using Hierarchies' checkbox on the custom object sharing settings.
Selecting the 'Grant Access Using Hierarchies' checkbox ensures that users in roles above the record owner in the role hierarchy automatically inherit the record access granted to the owner. For custom objects with a Private OWD, this is the standard and most efficient way to grant managers access to their subordinates' records.

Step-by-Step Solution

1
Analyze the access requirement between subordinates and managers.
Direct reports own records that their managers in the role hierarchy need to view and edit automatically.
Salesforce uses the role hierarchy to grant record access vertically to users positioned above record owners.
2
Evaluate how custom objects handle role hierarchy access when OWD is Private.
For custom objects, the 'Grant Access Using Hierarchies' option determines whether access rolls up to superior roles.
By default, 'Grant Access Using Hierarchies' is enabled for custom objects, but ensuring it remains checked allows managers to automatically access subordinates' records without extra sharing rules.

Key Concept

Role Hierarchy and Custom Object Sharing Controls
Question 499Question

A System Administrator needs to temporarily block a sales manager from logging into Salesforce while they are on leave. When attempting to deactivate the record, Salesforce displays an error because the manager is currently configured as a default running user in a scheduled Apex job. What should the administrator do to immediately prevent the manager from logging in?

Show answer & explanation

Answer: Freeze the user account to prevent login access without affecting scheduled system processes.

Answer

Freeze the user account to prevent login access without affecting scheduled system processes.
Freezing a user account is the recommended solution when an administrator must immediately restrict login access for a user who cannot be deactivated right away due to dependencies like scheduled jobs, workflow ownership, or custom hierarchy fields. Freezing does not free up the user license, but it prevents login without breaking system automations.

Step-by-Step Solution

1
Identify the operational constraint preventing user deactivation.
The user cannot be deactivated because they are assigned as the running user in a scheduled Apex job.
Salesforce blocks deactivation when user records are tied to active automated operations or hierarchy configurations.
2
Select the appropriate administrative action to restrict access immediately.
Freeze the user account.
Freezing stops the user from logging in immediately without unassigning their license or breaking active background automation.

Key Concept

Distinction between freezing a user account and deactivating a user account in Salesforce.
Estimated Time:1m 0s
Question 500Question

Universal Containers tracks customer site deployments using a custom parent object named Installation_Site__c and individual maintenance events using a custom child object named Maintenance_Log__c. Currently, Maintenance_Log__c has a Lookup relationship to Installation_Site__c. The administration team needs to display the total aggregate cost of all completed maintenance logs directly on the parent Installation_Site__c record. Additionally, users need to view the email address of the Installation Site's Primary Contact directly on each Maintenance_Log__c record. Which TWO configurations or requirements must the administrator evaluate to successfully implement this solution?

Select all that apply

Show answer & explanation

Answer: The relationship on Maintenance_Log__c must be converted to a Master-Detail relationship before a Roll-Up Summary field using a SUM aggregate function can be created on Installation_Site__c.; A cross-object formula field can be created on Maintenance_Log__c to retrieve the contact email address using the formula syntax Installation_Site__r.Primary_Contact__r.Email.

Answer

The administrator must convert the existing Lookup relationship to a Master-Detail relationship to enable Roll-Up Summary capabilities on the parent object, and create a cross-object formula field on the child object to reference the Primary Contact's email address.
Native Roll-up summary fields are strictly supported on the master object of a Master-Detail relationship, so converting the Lookup relationship to Master-Detail is a mandatory prerequisite to aggregate values on the parent object. In addition, cross-object formula fields allow referencing parent and grand-parent fields using relationship syntax across up to 10 relationship levels.

Step-by-Step Solution

1
Evaluate relationship requirements for Roll-Up Summary fields.
Determine that native Roll-Up Summary fields require a Master-Detail relationship between parent and child objects.
Salesforce natively restricts roll-up summary fields to master objects within master-detail relationships.
2
Evaluate cross-object data visibility requirements on the child record.
Determine that a cross-object formula field on Maintenance_Log__c can reference Installation_Site__r.Primary_Contact__r.Email.
Cross-object formula fields support spanning relationship paths across parent objects up to 10 levels deep.
3
Analyze deletion behavior implications of object relationship conversion.
Recognize that converting to Master-Detail introduces cascading deletion behavior.
Detail records in a master-detail relationship cannot exist as orphan records and are automatically deleted when the master record is deleted.

Key Concept

Roll-Up Summary and Cross-Object Formula Capabilities and Relationship Constraints
Estimated Time:3m 0s
PreviousPage 25 / 90Next
All practice questions — Salesforce Certified Administrator | Examkin