All practice questions

1784 questions

Question 501Question

A Salesforce Administrator is attempting to create a Roll-Up Summary field on a parent object to calculate the sum of related child record amounts. However, the child object is linked to the parent object through a Lookup relationship, and the Roll-Up Summary field type is unavailable during field creation. What is the primary reason the administrator cannot create a Roll-Up Summary field in this scenario?

Show answer & explanation

Answer: Roll-Up Summary fields are only supported on the master object of a Master-Detail relationship.

Answer

Roll-Up Summary fields are only supported on the master object of a Master-Detail relationship.
In Salesforce, native declarative Roll-Up Summary fields can only be created on the master object in a Master-Detail relationship. Because the objects are connected via a Lookup relationship, the Roll-Up Summary field type is disabled in the schema builder.

Step-by-Step Solution

1
Identify the relationship type between the parent and child objects.
The objects are currently linked via a standard Lookup relationship.
Salesforce declarative features differ based on whether the relationship is a Lookup or Master-Detail.
2
Determine the platform requirements for declarative Roll-Up Summary fields.
Declarative Roll-Up Summary fields are natively available only on the parent (master) side of a Master-Detail relationship.
Lookup relationships do not enforce the strict parent-child data dependency required by declarative roll-ups.
3
Select the correct explanation for why the field type is disabled.
The option stating that Roll-Up Summary fields are only supported on Master-Detail relationships explains the system behavior.
Converting the relationship to Master-Detail (or using custom code/automation) would be necessary to summarize the values.

Key Concept

Roll-Up Summary Field Capabilities and Relationship Dependencies
Estimated Time:45s
Question 502Question

An administrator at a global logistics firm is designing custom data tracking between a parent custom object named Project__c and a child custom object named Project_Task__c. Currently, Project_Task__c is linked to Project__c via a standard Lookup relationship. The business requires calculating the total estimated hours from all related tasks on the Project record, as well as displaying the Project's priority level on each child task record. Which two statements accurately describe the capabilities and configuration requirements for this scenario?

Select all that apply

Show answer & explanation

Answer: Native roll-up summary fields on Project__c require converting the relationship field on Project_Task__c from a Lookup to a Master-Detail relationship.; Cross-object formula fields on Project_Task__c can reference fields from the parent Project__c record using the existing Lookup relationship.

Answer

To aggregate child task hours onto the Project object using native roll-up summary fields, the relationship must be converted from a Lookup to a Master-Detail relationship. Furthermore, cross-object formulas on child records can access parent fields regardless of whether the relationship is Lookup or Master-Detail.
Native roll-up summary fields in Salesforce strictly require a Master-Detail relationship between the parent (master) and child (detail) objects. Therefore, converting the existing Lookup relationship to a Master-Detail relationship is necessary to summarize child task hours on the Project object natively. Additionally, cross-object formula fields on child records are capable of referencing fields from parent records across both Lookup and Master-Detail relationships.

Step-by-Step Solution

1
Analyze relationship requirements for native roll-up summary fields
Native Salesforce roll-up summary fields can only be created on the master object of a Master-Detail relationship.
Lookup relationships do not support native roll-up summary fields, even if the lookup field is marked as required.
2
Evaluate cross-object formula capabilities across lookup relationships
Cross-object formulas on a child object can reference field values on its parent object via Lookup or Master-Detail relationships.
Formulas can traverse lookup paths upward to retrieve values from referenced parent records.
3
Distinguish deletion behaviors between Lookup and Master-Detail relationships
Deleting a parent record in a Lookup relationship clears or restricts the lookup field based on configuration, but does not perform a cascade delete of child records.
Cascading deletes automatically occur only in Master-Detail relationships.

Key Concept

Roll-Up Summary and Cross-Object Formula Relationship Constraints
Question 503Question

A Salesforce administrator at a commercial real estate company needs to configure custom fields to support lead management and account tracking. The administrator must map a custom Lead picklist field, Property_Preference__c, to a custom Account field upon lead conversion. Additionally, the administrator must change an existing custom Text field on Account, Account_Tier_Notes__c, to a Picklist field while minimizing data issues for existing records. Which two actions must the administrator perform to fulfill these requirements? (Choose 2)

Select all that apply

Show answer & explanation

Answer: Map the custom Lead picklist field to a custom Account picklist field in the Map Lead Fields setup interface.; Ensure all existing string values in the text field correspond to active picklist API values prior to converting the data type.

Answer

The administrator must map the custom Lead picklist field to a custom Account picklist field using the Map Lead Fields interface, and ensure that all existing text values in the Account text field correspond to active picklist API values prior to converting the field type.
Mapping custom lead fields requires creating a corresponding custom field on the destination object and configuring the field mapping in Object Manager. Furthermore, converting a field from Text to Picklist requires ensuring that legacy text values align with defined picklist API values to preserve data integrity across existing records.

Step-by-Step Solution

1
Evaluate Lead conversion mapping capabilities for custom fields.
Confirm that custom fields on the Lead object must map to corresponding custom fields on destination objects (Account, Contact, or Opportunity).
Salesforce lead conversion routing prohibits mapping custom Lead fields directly into standard destination fields.
2
Assess data integrity requirements for converting a Text field to a Picklist field.
Verify existing record values against planned picklist API values before performing the type conversion.
Converting field data types can result in lost data or unassigned picklist values if legacy values do not match configured picklist entries.

Key Concept

Custom Fields and Data Types
Estimated Time:1m 30s
Question 504Question

An administrator at an IT services firm is instructed to create a field on the custom parent object, Project__c, that calculates the total number of related completed child Project_Milestone__c records using native platform capabilities without code or automation flows. When attempting to create a Roll-Up Summary field on Project__c, the administrator notices that the Roll-Up Summary field type option is disabled. The current relationship between Project__c and Project_Milestone__c is a Lookup relationship. Which administrative action is required to enable the creation of the Roll-Up Summary field?

Show answer & explanation

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

Answer

Convert the existing Lookup relationship field on Project_Milestone__c to a Master-Detail relationship after ensuring all child records have a populated parent lookup value.
Native Salesforce Roll-Up Summary fields are strictly supported on the master object of a Master-Detail relationship. To enable this field type when objects are linked via a Lookup relationship, the administrator must convert the lookup field on the child object to a Master-Detail relationship. Before converting, every existing child record must have a populated value in the lookup field.

Step-by-Step Solution

1
Identify the relationship requirement for native Salesforce Roll-Up Summary fields.
Recognize that Roll-Up Summary fields are only available on the master object in a Master-Detail relationship.
Salesforce schema constraints prevent Roll-Up Summary fields on parent objects linked via standard Lookup relationships.
2
Determine the prerequisites for converting a Lookup relationship field to a Master-Detail relationship.
Ensure all existing child Project_Milestone__c records contain a valid parent Project__c record reference.
A Lookup field can only be converted to a Master-Detail field if every existing child record has a populated value in that lookup field.
3
Perform the field type conversion on the child object.
The relationship type becomes Master-Detail, enabling the Roll-Up Summary field type on the parent Project__c object.
Once the Master-Detail relationship is established, native roll-up calculations (SUM, MIN, MAX, COUNT) become active on the parent object.

Key Concept

Roll-Up Summary Field Relationship Requirements and Field Conversion
Question 505Question

A biopharmaceutical company has 150 Clinical Research Associates assigned to a single baseline profile named 'Clinical CRA'. Due to new compliance requirements, a subset of 12 Clinical Research Associates requires temporary Edit access to a custom object named 'Audit Log' for 90 days, while the remaining 138 users must maintain their existing access level. Which solution should the administrator implement to grant this access while maintaining security best practices?

Show answer & explanation

Answer: Create a permission set granting Read and Edit access on the Audit Log object, configure an assignment expiration date of 90 days, and assign it to the 12 Clinical Research Associates.

Answer

Create a permission set granting Read and Edit access on the Audit Log object, configure an assignment expiration date of 90 days, and assign it to the 12 Clinical Research Associates.
Permission sets are designed to extend functional access to specific users without modifying baseline profile settings. Using User Assignment Expiration allows administrators to specify an expiration period (such as 90 days), after which access automatically expires.

Step-by-Step Solution

1
Analyze the access requirement
Identified that 12 users out of 150 require additive, temporary (90-day) object access beyond the baseline profile.
Salesforce security model recommends keeping profiles lean for baseline access and using permission sets for additive access.
2
Determine permission set functionality required
A permission set with object-level Read and Edit access for 'Audit Log' combined with User Assignment Expiration.
Permission Set User Assignment Expiration automatically revokes user access after the specified period (90 days) without manual intervention.
3
Evaluate alternative options against security best practices
Rejected profile cloning and modifying baseline profile due to administrative overhead and improper access expansion.
Profile changes impact baseline permissions unnecessarily, whereas muting permission sets only function inside Permission Set Groups.

Key Concept

Additive permissions via Permission Sets and temporary access using User Assignment Expiration
Question 506Question

A Senior Supply Chain Manager at an e-commerce enterprise is taking an extended leave of absence. The Salesforce Administrator needs to immediately prevent this user from logging into the Salesforce org. However, during an administrative audit, the administrator notes that this user is currently designated as the Default Workflow User in Process Automation Settings and is the scheduled running user for multiple active nightly inventory reporting jobs.

Which two statements explain why the administrator should freeze the user account instead of attempting to deactivate it? (Choose 2 answers)

Select all that apply

Show answer & explanation

Answer: Deactivating a user who is designated as the Default Workflow User is prevented by Salesforce until that background assignment is updated to another active user.; Freezing the user account immediately blocks login access while preserving the user's setup references and preventing background job failures.

Answer

The administrator should freeze the user because Salesforce prevents deactivating users assigned as the Default Workflow User, and freezing immediately blocks user access without disrupting background processing or requiring immediate dependency cleanup.
Freezing a user is the appropriate action when login access must be suspended immediately, but the user cannot be deactivated due to active dependencies such as being the Default Workflow User or running user for scheduled processes. Freezing prevents user login without releasing the user license or breaking background automated processes.

Step-by-Step Solution

1
Analyze the operational constraints preventing immediate deactivation
Identified that the user is configured as the Default Workflow User and is the execution context for active scheduled Apex jobs.
Deactivating a user with active system process dependencies can cause administrative errors or break background automations.
2
Evaluate the technical distinction between freezing and deactivating a user account
Freezing stops user login immediately while maintaining license usage and system references; deactivation releases the license but requires resolving system dependencies first.
Freezing is designed specifically for scenarios where access must be blocked immediately but deactivation is blocked or requires additional setup migration.
3
Select the correct administrative actions matching the scenario goals
Chosen options accurately state that Default Workflow User assignment prevents direct deactivation and that freezing temporarily blocks access without causing job failures.
This meets both the security requirement (preventing login) and the operational requirement (system stability).

Key Concept

User Freezing vs. Deactivation with System Automation Dependencies
Question 507Question

A System Administrator is managing a custom object named Project_Task__c that has a Master-Detail relationship with a parent custom object named Project__c. What happens to the associated child Project_Task__c records when a parent Project__c record is deleted?

Show answer & explanation

Answer: The associated Project_Task__c records are automatically deleted and moved to the Recycle Bin.

Answer

The associated child records are automatically deleted and moved to the Recycle Bin along with the master record.
In Salesforce, Master-Detail relationships strictly enforce cascade deletion. When a parent master record is deleted, all of its associated child detail records are automatically deleted and moved to the Recycle Bin.

Step-by-Step Solution

1
Identify the relationship type between the parent object and the child object.
The objects are linked via a Master-Detail relationship.
Master-Detail relationships enforce tight coupling between master and detail records.
2
Evaluate the deletion behavior enforced by Salesforce for Master-Detail relationships.
Deleting a master record automatically triggers a cascading deletion of all related child records.
Child records in a Master-Detail relationship cannot exist independently without their master record.

Key Concept

Master-Detail Relationship Cascade Deletion
Question 508Question

A logistics company tracks equipment servicing using a custom object named Maintenance_Log__c. An administrator is tasked with summarizing total maintenance counts on the standard Asset object and ensuring that deleting an Asset automatically removes all associated Maintenance_Log__c records. However, several Maintenance_Log__c records currently exist in the org without an assigned Asset. Which TWO steps must the administrator take to successfully implement this requirement?

Select all that apply

Show answer & explanation

Answer: Populate the Asset lookup field on all existing Maintenance_Log__c records prior to converting the relationship to a Master-Detail relationship.; Create Roll-Up Summary fields on the standard Asset object after establishing the Master-Detail relationship.

Answer

The administrator must populate the Asset reference on all existing Maintenance_Log__c records before converting the Lookup relationship to a Master-Detail relationship, and then create Roll-Up Summary fields on the Asset object.
To achieve automatic cascading deletion and native roll-up summary capabilities on the parent Asset object, a Master-Detail relationship is required. Converting an existing Lookup field to a Master-Detail field requires that every existing child record has a parent value populated. Once converted, Roll-Up Summary fields can be configured on the Asset object.

Step-by-Step Solution

1
Evaluate relationship requirements for cascading deletion and roll-up summaries
Determined that a Master-Detail relationship is required between Asset (master) and Maintenance_Log__c (detail).
Standard Lookup relationships do not support native Roll-Up Summary fields or automatic cascading deletion upon parent deletion.
2
Prepare existing data for relationship conversion
Populate the Asset lookup field across all existing Maintenance_Log__c records in the org.
Salesforce enforces that a Lookup relationship can only be converted to Master-Detail if every child record has a populated lookup field.
3
Convert relationship and build summary fields
Change the relationship field type to Master-Detail and define Roll-Up Summary fields on Asset.
Master-Detail relationships enable automatic cascade deletion of child records and allow native Roll-Up Summary fields on the parent object.

Key Concept

Master-Detail Relationship Conversion Rules & Roll-Up Summary Requirements
Estimated Time:2m 0s
Question 509Question

A Salesforce administrator creates a new holiday entry for 'Independence Day' in Organization Settings. However, support cases assigned to the custom 'APAC Tier 2 Support' Business Hours schedule continue to evaluate and trigger Case Escalation Rules during the observed holiday. Which administrative action is required to ensure escalations pause on this holiday for the APAC team?

Show answer & explanation

Answer: Associate the 'Independence Day' holiday specifically with the 'APAC Tier 2 Support' Business Hours schedule.

Answer

The administrator must associate the holiday with the specific 'APAC Tier 2 Support' Business Hours schedule.
In Salesforce, creating a holiday only defines the holiday date centrally. To halt case escalation clocks for a particular support schedule, the holiday must be explicitly added to the relevant Business Hours record.

Step-by-Step Solution

1
Identify why escalations fire on holidays
Creating a holiday record in Salesforce makes the holiday definition available in the org, but does not automatically apply it to any custom Business Hours schedule.
Business hours operating schedules must be explicitly linked to holiday records so the system knows which schedules should suspend escalation timers.
2
Navigate to the Business Hours configuration page and edit the target schedule
In Setup, locate 'APAC Tier 2 Support' under Business Hours and add 'Independence Day' to its Holidays list.
Once linked, Salesforce automatically subtracts holiday hours from escalation clock calculations for cases using that Business Hours schedule.

Key Concept

Holiday Association with Business Hours Schedules
Question 510Question

A system administrator is designing a custom standalone Lightning App Page to display team resources and tools. Which two actions can the administrator perform within Lightning App Builder when configuring an App Page? (Select 2 choices)

Select all that apply

Show answer & explanation

Answer: Adding standard Lightning components, such as Flow and Report Chart, to page regions.; Selecting a layout template to structure the page regions, such as a Two Regions template.

Answer

The correct options are adding standard Lightning components (like Flow and Report Chart) to page regions and selecting a layout template (such as a Two Regions template) to structure page regions.
Lightning App Pages allow administrators to select layout templates (such as header with two regions) and populate those regions with standard components like Flow, Report Chart, or Rich Text. Because App Pages are standalone landing pages, they do not require an underlying record context.

Step-by-Step Solution

1
Identify the Lightning page type being built
The scenario specifies a standalone App Page.
App Pages serve as custom landing tabs in Lightning Experience or the mobile app and do not bind to a single record context.
2
Evaluate features supported on App Pages
App Pages support region layout templates and standard/custom components like Flows, Report Charts, and Chatter feeds.
These components provide general interactivity without requiring an underlying record ID.
3
Filter out Record Page specific features
Record Types and Record Detail components require record context and cannot be assigned or placed on an App Page.
Record context features only function on Lightning Record Pages.

Key Concept

Lightning App Page Capabilities and Layout Templates
Estimated Time:1m 0s
Question 511Question

Northern Trail Outfitters wants to restrict access to a custom currency field, Bonus_Amount__c, on the Employee Review object so that general sales managers cannot view, search for, or report on this field anywhere within Salesforce. Which configuration setting should the administrator modify to restrict field access across the entire platform?

Show answer & explanation

Answer: Field-Level Security (FLS) settings for the Bonus_Amount__c field on the profiles assigned to sales managers.

Answer

Field-Level Security (FLS) settings for the Bonus_Amount__c field on the profiles assigned to sales managers.
Configuring Field-Level Security (FLS) ensures that specified profiles cannot view or edit the target field anywhere in Salesforce, including page layouts, standard and custom reports, list views, global search, and API queries.

Step-by-Step Solution

1
Identify the security scope required
Access must be restricted comprehensively across reports, list views, search results, and API access.
UI-only restrictions are insufficient for complete data security.
2
Evaluate Salesforce security mechanisms
Field-Level Security (FLS) directly enforces field visibility and edit permissions at the platform data layer.
FLS overrides page layouts and UI visibility to secure data everywhere in Salesforce.

Key Concept

Field-Level Security (FLS)
Question 512Question

An administrator is designing a custom data model in Salesforce to manage corporate sponsorship agreements. The organization needs to connect a custom object named Sponsorship_Campaign__c with a custom object named Corporate_Sponsor__c in a many-to-many relationship. The finance team requires a Roll-Up Summary field on Sponsorship_Campaign__c to calculate the total pledged contribution across all connected sponsors. Additionally, administrators must be able to move existing sponsorship records to a different campaign if an agreement is modified.

Which two configuration steps or relationship characteristics must the administrator implement to satisfy these requirements? (Select 2 answers.)

Select all that apply

Show answer & explanation

Answer: Create a custom junction object containing Master-Detail relationship fields to both Sponsorship_Campaign__c and Corporate_Sponsor__c.; Enable the 'Allow reparenting' option on the Master-Detail relationship field pointing to Sponsorship_Campaign__c.

Answer

To implement a many-to-many relationship with roll-up summaries and reassignable records, the administrator must create a custom junction object with Master-Detail relationships to both parent objects and select the 'Allow reparenting' setting on the Master-Detail relationship field.
Creating a custom junction object with two Master-Detail relationships models a many-to-many relationship and unlocks the ability to create Roll-Up Summary fields on the master object. Enabling 'Allow reparenting' on the Master-Detail field allows administrators to reassign child junction records to a different master campaign record when business needs change.

Step-by-Step Solution

1
Evaluate the relationship type needed for many-to-many modeling and aggregate calculations.
A custom junction object with two Master-Detail relationships is required to establish the many-to-many model and allow Roll-Up Summary fields on the master objects.
Lookup relationships do not support Roll-Up Summary fields or model native many-to-many relationships with master security inheritance.
2
Address the requirement to move records between campaigns.
Check the 'Allow reparenting' setting on the Master-Detail field pointing to Sponsorship_Campaign__c.
Detail records in Master-Detail relationships are locked to their master record upon creation unless reparenting is explicitly enabled in the field definition.

Key Concept

Many-to-Many Relationships and Master-Detail Field Capabilities
Question 513Question

A global logistics provider uses a custom object named Vendor_Dispute__c to track contract disputes with carrier partners. Security policy mandates that standard employees should only have access to vendor dispute records they own. However, managers must automatically inherit read and edit access to all vendor dispute records owned by their direct and indirect reports in the role hierarchy. Which configuration of Organization-Wide Defaults (OWD) and sharing behavior satisfies these requirements?

Show answer & explanation

Answer: Set the Organization-Wide Default for Vendor_Dispute__c to Private, and ensure Grant Access Using Hierarchies remains checked.

Answer

Set the Organization-Wide Default for the custom object to Private and keep 'Grant Access Using Hierarchies' enabled.
Setting the Organization-Wide Default (OWD) for the custom object to Private restricts baseline record access so that users can only view records they own. Keeping 'Grant Access Using Hierarchies' checked ensures that users higher in the role hierarchy automatically inherit full access to records owned by their subordinates.

Step-by-Step Solution

1
Determine the baseline record access requirement for standard non-owner users.
Standard users must only access records they own, requiring the most restrictive baseline OWD setting of Private.
Organization-Wide Defaults establish the baseline access level for records users do not own.
2
Determine how access should propagate to management via the role hierarchy.
Enabling 'Grant Access Using Hierarchies' grants managers higher in the role hierarchy the same level of access as record owners.
For custom objects, 'Grant Access Using Hierarchies' is enabled by default, but can be toggled. Keeping it checked ensures automatic upward access propagation.
3
Evaluate whether profile or permission set controls can further restrict access.
Profiles and permission sets grant object and administrative permissions but cannot override OWD to make record-level access more restrictive.
Salesforce security enforces OWD as the absolute base layer of record-level security; sharing tools can only grant additional access, never restrict it.

Key Concept

Organization-Wide Defaults (OWD) and Role Hierarchy Access
Question 514Question

An administrator is configuring custom calculation fields for a custom object called Project_Milestone__c, which has a Master-Detail relationship with Project__c and a Lookup relationship with Department__c. Which two statements accurately describe supported field configurations on these objects? (Select 2)

Select all that apply

Show answer & explanation

Answer: A Roll-Up Summary field can be created on Project__c to aggregate values from related Project_Milestone__c records.; A cross-object formula field on Project_Milestone__c can reference and display fields from the parent Department__c record.

Answer

Roll-Up Summary fields can be created on the master object (Project__c) to aggregate detail records, and cross-object formula fields on the child object (Project_Milestone__c) can reference fields from parent records across lookup relationships.
Roll-Up Summary fields can only be created on the master object in a Master-Detail relationship (Project__c to Project_Milestone__c). Additionally, cross-object formula fields on child records can reference parent values through both Lookup and Master-Detail relationships.

Step-by-Step Solution

1
Evaluate relationship requirements for Roll-Up Summary fields
Roll-Up Summary fields require a Master-Detail relationship and can only be defined on the master object. Therefore, aggregating Project_Milestone__c on Project__c is valid, but aggregating on Department__c (lookup) is invalid.
Lookup relationships do not support native Roll-Up Summary fields in Salesforce.
2
Evaluate cross-object formula field capabilities
Cross-object formula fields can reference fields up to 10 relationships away on parent objects, including both lookup and master-detail parent objects.
Formula fields support cross-object referencing regardless of relationship type.
3
Evaluate Master-Detail deletion behavior
Deleting a master record automatically deletes related detail records.
Cascading deletion is a foundational behavior of Master-Detail relationships that cannot be overridden by Roll-Up Summary fields.

Key Concept

Roll-Up Summary fields require a Master-Detail relationship on the master object, whereas cross-object formulas can reference parent fields across both Lookup and Master-Detail relationships.
Question 515Question

A security audit reveals that remote employees can initiate a Salesforce session while connected to an authorized corporate network and continue using the active session token after switching to an untrusted network. Which setting in Session Settings should the administrator configure to prevent a session from remaining valid when a user's IP address changes?

Show answer & explanation

Answer: Lock sessions to the IP address from which they originated

Answer

The administrator should enable 'Lock sessions to the IP address from which they originated' in Session Settings.
Enabling 'Lock sessions to the IP address from which they originated' in Setup > Session Settings forces Salesforce to verify that every HTTP request originates from the IP address associated with the initial login. If the IP address changes, the session is invalidated immediately.

Step-by-Step Solution

1
Identify the security requirement.
The requirement is to invalidate active session tokens if a user shifts from one network IP to another.
Preventing session reuse across different IP addresses mitigates session hijacking risks.
2
Evaluate Salesforce Session Settings options.
The setting 'Lock sessions to the IP address from which they originated' explicitly forces session termination when the client IP changes.
This setting directly evaluates the origin IP of incoming requests against the initial login IP.

Key Concept

Session IP Locking in Salesforce Session Settings
Question 516Question

A System Administrator at AeroPulse Avionics is configuring record-level security for a custom object named Supplier_Audit__c. The Organization-Wide Default (OWD) for Supplier_Audit__c is set to Private. Executive management specifies two key security requirements:
1. Record access must NOT automatically propagate up the role hierarchy to managers of record owners.
2. Members of the 'Compliance Quality Group' public group must be granted Read/Write access to all Supplier_Audit__c records where the Audit_Status__c field is set to 'Completed'.

Which TWO configuration steps should the administrator perform to satisfy these security requirements? (Select 2 answers)

Select all that apply

Show answer & explanation

Answer: Deselect the 'Grant Access Using Hierarchies' checkbox on the Supplier_Audit__c custom object definition.; Create a criteria-based sharing rule on Supplier_Audit__c that shares records matching Audit_Status__c = 'Completed' with the 'Compliance Quality Group' public group, granting Read/Write access.

Answer

The administrator must deselect the 'Grant Access Using Hierarchies' setting on the Supplier_Audit__c object definition and create a criteria-based sharing rule targeting records with Audit_Status__c = 'Completed' to share with the Compliance Quality Group.
To satisfy both requirements: (1) Unchecking 'Grant Access Using Hierarchies' on the custom object definition stops records from automatically rolling up access to managers higher in the role hierarchy when OWD is Private. (2) Creating a criteria-based sharing rule evaluates the record's Audit_Status__c field value ('Completed') and grants Read/Write access specifically to the 'Compliance Quality Group' public group.

Step-by-Step Solution

1
Evaluate the requirement to block automatic record access rollup in the role hierarchy.
Identify that 'Grant Access Using Hierarchies' is enabled by default on custom objects and must be manually deselected.
Deselecting this checkbox on a custom object ensures users higher in the role hierarchy do not receive automatic access to records owned by subordinates.
2
Evaluate the requirement to grant access based on a specific field value (Audit_Status__c = 'Completed').
Select a criteria-based sharing rule as the appropriate sharing mechanism.
Criteria-based sharing rules evaluate record field values (such as picklist status) to automatically grant access to specific public groups or roles regardless of record ownership.

Key Concept

Disabling Role Hierarchy Record Rollup & Implementing Criteria-Based Sharing Rules
Question 517Question

An administrator is establishing a relationship between a parent custom object, Project_Plan__c, and a child custom object, Project_Task__c. The business requires that deleting a project plan automatically deletes all related project tasks, and management wants to calculate the total estimated task hours on the project plan record.

Which two statements describe the capabilities and behaviors of implementing a Master-Detail relationship for this requirement? (Choose 2 answers)

Select all that apply

Show answer & explanation

Answer: A Roll-Up Summary field can be created on Project_Plan__c to calculate aggregate values from related Project_Task__c records.; Deleting a Project_Plan__c record automatically deletes all associated Project_Task__c records.

Answer

The correct statements are that a Roll-Up Summary field can be created on the parent object to aggregate child record values, and deleting a parent record automatically deletes all associated child records.
In Salesforce, Master-Detail relationships provide tight coupling between master and detail records. This enables native Roll-Up Summary fields on the master object to aggregate child values (such as total hours) and enforces cascading deletion, which automatically deletes detail records when their parent master record is deleted.

Step-by-Step Solution

1
Analyze the business requirements for record deletion behavior and data aggregation.
Requirements specify cascade deletion of child records and roll-up calculations on the parent record.
Master-Detail relationships enforce cascading deletion and natively enable Roll-Up Summary fields on the master object.
2
Evaluate relationship capabilities between Lookup and Master-Detail types.
Lookup relationships do not natively support Roll-Up Summary fields and do not automatically cascade delete records by default.
Master-Detail is the correct architecture to meet both requirements natively.

Key Concept

Master-Detail Relationship Capabilities and Lifecycle Inheritance
Estimated Time:1m 0s
Question 518Question

A System Administrator at a renewable energy company must immediately block login access for a customer support representative who is currently selected as the default record owner in an active Lead Assignment Rule. Which two statements describe the correct administrative approach for handling this user account? (Select 2 answers)

Select all that apply

Show answer & explanation

Answer: Freeze the user account immediately to block login access without altering active system process references.; Reassign or replace the user reference in the Lead Assignment Rule before attempting account deactivation.

Answer

Freezing the user account allows an administrator to immediately prevent login without disrupting system automation, while replacing the user reference in the Lead Assignment Rule is required before deactivating the user to release the license.
Freezing a user account immediately blocks access while allowing administrators time to update active system references. Removing or updating the user's reference in the Lead Assignment Rule allows the user to be safely deactivated afterward to release the user license.

Step-by-Step Solution

1
Evaluate immediate access restriction requirements
Freezing the account immediately prevents login access while keeping current record ownership settings intact.
Freezing is used when a user cannot be deactivated right away due to references in active automation or hierarchy fields.
2
Resolve process dependencies prior to deactivation
Update the Lead Assignment Rule to reference a different active user as the default owner.
Deactivating a user directly referenced in active automated processes causes execution errors.
3
Deactivate the account to reclaim the license
Once all dependencies are reassigned, deactivating the account safely frees up the user license.
Deactivation frees the user license for reassignment, whereas freezing retains the license.

Key Concept

User Freezing vs. User Deactivation in Salesforce Administration
Estimated Time:1m 0s
Question 519Question

An administrator at a clean energy firm manages a standard Account object and a custom Solar_Site__c object connected by a lookup relationship. The operations team requires a field on the Account record that dynamically displays the total combined capacity (in megawatts) of all active related Solar_Site__c records. When attempting to create a custom field on Account, the administrator notices that the Roll-Up Summary field type is disabled. Why is the Roll-Up Summary field unavailable, and what is the appropriate declarative approach to satisfy this requirement?

Show answer & explanation

Answer: Roll-Up Summary fields can only be created on the master object of a master-detail relationship; the administrator should convert the lookup to a master-detail relationship (if data model constraints allow) or use Salesforce Flow to update a custom field on Account.

Answer

Roll-Up Summary fields are strictly available on parent objects that are part of a Master-Detail relationship. Because Account and Solar_Site__c are connected via a Lookup relationship, native roll-up fields are disabled. The administrator can convert the relationship to Master-Detail (if all child records have parent values assigned) or implement a Record-Triggered Flow to calculate and store the aggregate total on a custom number field on the Account.
Native Roll-Up Summary fields require a Master-Detail relationship where the parent object serves as the master. Because the Account and Solar_Site__c objects are linked via a Lookup relationship, the Roll-Up Summary option is unavailable. To meet the requirement declaratively, the administrator must either convert the Lookup relationship to a Master-Detail relationship or use a Record-Triggered Flow to aggregate child values into a standard custom number field on the Account.

Step-by-Step Solution

1
Analyze relationship requirements for Roll-Up Summary fields
Identify that standard Roll-Up Summary fields require a Master-Detail relationship between parent and child objects.
Salesforce native roll-up capabilities enforce strict data integrity rules provided only by Master-Detail relationships.
2
Evaluate relationship type between Account and Solar_Site__c
Confirm the objects are linked via a Lookup relationship, explaining why the Roll-Up Summary options are grayed out.
Lookup relationships do not support native declarative roll-up summaries.
3
Determine declarative alternatives for aggregate calculations over lookup relationships
Select converting to Master-Detail or building a Record-Triggered Flow (or Apex/custom solution) to maintain the aggregate field.
Cross-object formulas cannot evaluate lists of child records, so automation or relationship conversion is necessary.

Key Concept

Roll-up summary fields require a Master-Detail relationship. To aggregate child records over a Lookup relationship, administrators must convert the relationship or use automation like Salesforce Flow.
Estimated Time:2m 0s
Question 520Question

A Salesforce administrator at an architectural design firm needs to display the total monetary value of all completed project tasks on the parent custom object named Project__c. Currently, the child custom object named Project_Task__c is connected to Project__c through a Lookup relationship. When attempting to create a new Roll-Up Summary field on Project__c, the administrator discovers that the Roll-Up Summary field type is unavailable in the field creation wizard. Which action should the administrator take to enable the creation of a Roll-Up Summary field on Project__c?

Show answer & explanation

Answer: Convert the Lookup relationship on Project_Task__c to a Master-Detail relationship after verifying all Project_Task__c records have a populated Project__c field.

Answer

Convert the Lookup relationship on Project_Task__c to a Master-Detail relationship after verifying all Project_Task__c records have a populated Project__c field.
In Salesforce, Roll-Up Summary fields are only available on the master object in a Master-Detail relationship. To convert a Lookup relationship to a Master-Detail relationship, all child records must have a value in the lookup field because Master-Detail relationship fields are mandatory on detail records.

Step-by-Step Solution

1
Identify the relationship type between the parent and child objects
Determined that Project__c and Project_Task__c are currently linked via a Lookup relationship.
Roll-Up Summary fields are strictly supported on the parent object of a Master-Detail relationship, not a Lookup relationship.
2
Ensure data integrity on existing child records
Verify that every existing Project_Task__c record contains a valid reference to a parent Project__c record.
Salesforce prevents converting a Lookup relationship to a Master-Detail relationship if any child record has a blank parent lookup field.
3
Change the relationship field type
Change the field type of the Lookup relationship field on Project_Task__c to Master-Detail.
This relationship shift enables the Roll-Up Summary field type when creating new fields on the parent Project__c object.

Key Concept

Roll-Up Summary fields require a Master-Detail relationship between the parent and child objects.
PreviousPage 26 / 90Next
All practice questions — Salesforce Certified Administrator | Examkin