All practice questions

1784 questions

Question 441Question

An administrator needs to completely hide a custom field named Hourly_Rate__c on the Consultant__c object for all users assigned to the Standard Support Profile, while preserving existing access for all other profiles. Which configuration change should the administrator make?

Show answer & explanation

Answer: Set Field-Level Security for the Hourly_Rate__c field to hidden on the Standard Support Profile.

Answer

Set Field-Level Security for the Hourly_Rate__c field to hidden on the Standard Support Profile.
Field-Level Security (FLS) on the profile directly controls field visibility and editability across the entire Salesforce platform, including record pages, reports, search, and API calls.

Step-by-Step Solution

1
Identify the security requirement.
Access to the Hourly_Rate__c field needs to be restricted at the data level for users assigned to the Standard Support Profile.
Security requirements regarding field data visibility require field-level authorization controls rather than UI-only restrictions.
2
Evaluate the appropriate security mechanism.
Field-Level Security (FLS) on the profile restricts access to the field across all interfaces, including reports, list views, and API calls.
FLS is the standard setting in Salesforce for enforcing field privacy per profile or permission set.

Key Concept

Field-Level Security (FLS) enforcement on profiles
Question 442Question

An administrator is configuring a support process for a company with headquarters in New York (EST) and a new branch in Sydney (AEST). Users in Sydney report that date/time stamps on newly created Case records appear several hours behind their local wall-clock time when viewed in reports. The organization's Default Time Zone is set to America/New_York. What should the administrator do to ensure Sydney agents see record date/time values in their local time?

Show answer & explanation

Answer: Instruct each Sydney user to update the Time Zone field in their personal User Settings.

Answer

Instruct each Sydney user to update the Time Zone field in their personal User Settings.
Salesforce converts UTC-stored date/time fields into the user's specific locale/time zone based on their personal User Settings. Setting the user's personal Time Zone to Australia/Sydney resolves the display issue without altering organization-wide defaults.

Step-by-Step Solution

1
Analyze how Salesforce stores and presents Date/Time values.
Salesforce stores all Date/Time field values internally in UTC.
Internal UTC storage allows multi-region organizations to maintain consistent audit logs.
2
Determine how user-facing time formatting is calculated.
Salesforce converts UTC values to the logged-in user's personal Time Zone setting when rendered on record detail pages and reports.
Personal user locale settings override the Organization Default Time Zone for UI display.
3
Identify the required administrative configuration.
Sydney users must set their individual user record Time Zone setting to Australia/Sydney under Personal Settings.
Updating individual user settings displays accurate local wall-clock times without altering global organization settings.

Key Concept

Personal Time Zone Display vs Organization Default Time Zone
Question 443Question

Zephyr Freight tracks custom Shipment records related to parent Delivery Manifest records using a Master-Detail relationship. The Salesforce administrator needs to configure Roll-Up Summary fields on Delivery Manifest to aggregate shipment data. Which two operations can a Roll-Up Summary field perform on the related child records? (Select 2)

Select all that apply

Show answer & explanation

Answer: Calculate the total SUM of a numeric field across all child records.; Find the MIN or MAX value of a date or date/time field among the child records.

Answer

Roll-Up Summary fields can calculate the total SUM of numeric fields and determine the MIN or MAX value of date or date/time fields on related detail records in a Master-Detail relationship.
Roll-Up Summary fields allow administrators to calculate aggregate values—specifically COUNT, SUM, MIN, and MAX—from detail records in a Master-Detail relationship. Calculating a SUM of numeric fields and finding MIN/MAX dates are both core supported operations.

Step-by-Step Solution

1
Identify relationship requirements for Roll-Up Summary fields.
Confirm that Roll-Up Summary fields are only allowed on the master object of a Master-Detail relationship.
Salesforce standard functionality restricts declarative roll-up summaries strictly to Master-Detail parent objects.
2
Evaluate allowed aggregate functions.
Identify COUNT, SUM, MIN, and MAX as valid calculations.
SUM applies to numbers, currency, and percentages, while MIN and MAX work with numbers, currency, percentages, dates, and date/time fields.

Key Concept

Roll-Up Summary Fields Capabilities and Master-Detail Dependencies
Question 444Question

An organization tracks custom Payment_Transaction__c records linked to a parent custom Invoice__c object using a Lookup relationship. The finance team needs a field on the Invoice__c object that automatically calculates the total settled amount from all related Payment_Transaction__c records in real time. However, when trying to create a standard Roll-Up Summary field on the Invoice__c object, the administrator finds that the Roll-Up Summary field type option is disabled. What configuration change must the administrator make to enable the creation of the Roll-Up Summary field on Invoice__c?

Show answer & explanation

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

Answer

Convert the existing Lookup relationship field on Payment_Transaction__c to a Master-Detail relationship field after ensuring all child records have a populated parent.
Declarative Roll-Up Summary fields are strictly supported on the master object of a Master-Detail relationship. Converting the lookup field on the child object (Payment_Transaction__c) to a Master-Detail field (after verifying that all child records have parent values populated) allows the administrator to create a Roll-Up Summary field on the parent Invoice__c object.

Step-by-Step Solution

1
Identify relationship requirements for declarative Roll-Up Summary fields.
Standard declarative Roll-Up Summary fields are only available on the master object in a Master-Detail relationship.
Lookup relationships do not support native roll-up summary fields without custom automation or Apex triggers.
2
Determine where the relationship field resides.
The relationship field resides on the child object (Payment_Transaction__c) pointing to the parent object (Invoice__c).
Child records contain the foreign key (relationship field) referencing the parent record.
3
Evaluate prerequisites for converting Lookup to Master-Detail.
Ensure every existing Payment_Transaction__c record has a valid parent Invoice__c reference populated.
Salesforce prevents converting a Lookup to a Master-Detail relationship if any child record contains a null value in the relationship field.

Key Concept

Roll-Up Summary Field Relationship Requirements
Estimated Time:1m 30s
Question 445Question

A Salesforce administrator at an insurance brokerage firm is configuring custom fields on a parent custom object named Insurance_Policy__c and a child custom object named Policy_Claim__c. The two objects are currently connected by a Lookup relationship. The management team requires a field on the Insurance_Policy__c record that dynamically displays the total count of related Policy_Claim__c records. However, when attempting to create a new field on Insurance_Policy__c, the administrator notices that the Roll-Up Summary field type is unavailable. Which action should the administrator take to enable the required field capability?

Show answer & explanation

Answer: Convert the Lookup relationship on Policy_Claim__c to a Master-Detail relationship, then create a Roll-Up Summary field on Insurance_Policy__c.

Answer

Convert the Lookup relationship on Policy_Claim__c to a Master-Detail relationship, then create a Roll-Up Summary field on Insurance_Policy__c.
In Salesforce, native Roll-Up Summary fields can only be created on the master object in a Master-Detail relationship. Because Insurance_Policy__c and Policy_Claim__c are currently linked by a Lookup relationship, the Roll-Up Summary data type is disabled. Converting the lookup field on Policy_Claim__c to a Master-Detail relationship enables the Roll-Up Summary field type on Insurance_Policy__c to summarize child claims.

Step-by-Step Solution

1
Identify relationship limitations for field creation
Recognize that Roll-Up Summary fields are only available on parent objects in a Master-Detail relationship, not a Lookup relationship.
Salesforce architecture restricts native Roll-Up Summary functionality strictly to master objects in Master-Detail relationships.
2
Ensure data integrity before relationship conversion
Verify that all existing Policy_Claim__c records have a value populated in the Insurance_Policy__c lookup field.
Converting a Lookup field to a Master-Detail field requires every child record to have a parent record assigned.
3
Change field type and create roll-up field
Change the data type of the relationship field on Policy_Claim__c to Master-Detail, then create the Roll-Up Summary field on Insurance_Policy__c using COUNT aggregation.
This unlocks the Roll-Up Summary field type on the parent object to fulfill the requirement.

Key Concept

Roll-Up Summary Field Eligibility and Master-Detail Relationships
Estimated Time:1m 30s
Question 446Question

An administrator at Ursa Major Solar is creating a Roll-Up Summary field on the standard Account object to calculate the total amount of related closed-won Opportunities. The business requirement specifies that the roll-up calculation should only include child Opportunity records where a custom formula field, Region_Code__c (which references the related Owner's Region), equals 'US-WEST'. However, while configuring the filter criteria for the Roll-Up Summary field, the administrator notices that Region_Code__c is not available for selection in the Field picklist. What is the reason the formula field cannot be selected in the Roll-Up Summary filter criteria?

Show answer & explanation

Answer: Roll-Up Summary filter criteria cannot reference formula fields that contain cross-object field references.

Answer

Roll-Up Summary filter criteria cannot reference formula fields that contain cross-object field references.
Roll-Up Summary filter criteria cannot reference cross-object formula fields (formula fields containing fields derived from another object, such as the Owner object). Because changes to cross-object records do not execute triggers or system recalculations on the detail record, Salesforce restricts them from roll-up filter logic to prevent stale data.

Step-by-Step Solution

1
Analyze the Roll-Up Summary field filter requirements.
The requirement requests filtering child Opportunity records using the custom formula field Region_Code__c.
Roll-Up Summary fields allow filtering child records using direct field attributes.
2
Identify the composition of the formula field Region_Code__c.
Region_Code__c relies on a cross-object reference (Owner.Region__c).
Formula fields referencing fields on other related objects are considered cross-object formulas.
3
Evaluate Salesforce platform limitations regarding Roll-Up Summary filter criteria.
Salesforce prevents cross-object formula fields from being used in Roll-Up Summary filter criteria because dynamic changes on the referenced record (e.g., User/Owner) do not trigger automatic recalculation of the child record's parent roll-up.
Understanding platform filter limitations prevents configuration errors during object design.

Key Concept

Roll-Up Summary Filter Criteria Limitations
Question 447Question

Universal Containers enforces a standard 2-hour session inactivity timeout across the organization. To comply with internal security policies, users in the Finance department must have a stricter 15-minute inactivity session timeout applied to their logins. Which administrative configuration should be used to enforce this requirement exclusively for the Finance team?

Show answer & explanation

Answer: Edit the Profile assigned to Finance users and configure the Session Timeout setting to 15 minutes.

Answer

Edit the Profile assigned to Finance users and configure the Session Timeout setting to 15 minutes.
In Salesforce, session inactivity timeouts are established globally under Session Settings, but administrators can override session timeouts for specific user groups by modifying the Session Timeout setting directly on their assigned Profile.

Step-by-Step Solution

1
Identify where session inactivity policies are evaluated in Salesforce.
Salesforce evaluates Organization-Wide Session Settings first, but allows Profile-level settings to override the organization default for users assigned to that Profile.
Profile-level session settings take precedence over Organization-Wide Session Settings.
2
Evaluate whether Permission Sets can configure session timeout policies.
Permission Sets grant functional permissions and object access, but do not contain session timeout policies.
Session security policies (timeout, password policy overrides) are maintained on Profiles.
3
Select the correct administrative action.
Configuring the 15-minute session timeout directly on the Finance Profile achieves targeted security compliance without affecting other users.
It fulfills the requirement cleanly using native Salesforce security architecture.

Key Concept

Profile-Level Session Setting Overrides
Question 448Question

An administrator is configuring record access for a custom object named Vendor_Contract__c. The Organization-Wide Default (OWD) for the object is set to Private. The administrator needs to ensure that managers automatically gain access to vendor contract records owned by their subordinates in the role hierarchy, and that members of the Procurement Team public group gain Read/Write access whenever a contract's status is set to 'Approved'. Which two configuration steps should the administrator take to fulfill these access requirements?

Select all that apply

Show answer & explanation

Answer: Ensure the Grant Access Using Hierarchies checkbox remains selected on the custom object definition.; Create a criteria-based sharing rule on Vendor_Contract__c that shares records with the Procurement Team public group when Status equals 'Approved'.

Answer

The administrator must keep the 'Grant Access Using Hierarchies' checkbox selected on the custom object and create a criteria-based sharing rule targeting the Procurement Team public group when the Status field equals 'Approved'.
Keeping 'Grant Access Using Hierarchies' enabled ensures users above the record owner in the role hierarchy automatically receive access to records owned by subordinates. Creating a criteria-based sharing rule allows granting Read/Write access to a specified public group whenever field conditions (Status = 'Approved') are met.

Step-by-Step Solution

1
Review how role hierarchy access works for custom objects when OWD is Private.
By default, 'Grant Access Using Hierarchies' is selected for custom objects, ensuring users above the owner in the role hierarchy inherit access.
Maintaining this setting fulfills the requirement for managers to access subordinate records.
2
Evaluate record sharing requirements based on field criteria.
Create a criteria-based sharing rule on Vendor_Contract__c where Status equals 'Approved', sharing Read/Write access with the Procurement Team public group.
Criteria-based sharing rules extend access based on field values rather than record ownership.

Key Concept

Role Hierarchy and Sharing Rules
Estimated Time:1m 0s
Question 449Question

An administrator at an industrial equipment supplier manages a custom object named Equipment_Inspection__c that is linked to the standard Asset object through a Master-Detail relationship. The business operations team requests changing this Master-Detail relationship into a Lookup relationship so that inspection records can have independent record ownership and security control. However, when the administrator attempts to modify the relationship field type in Object Manager, Salesforce displays an error preventing the change. Which situation is preventing the administrator from converting the Master-Detail relationship to a Lookup relationship?

Show answer & explanation

Answer: The standard Asset object has a Roll-Up Summary field that calculates aggregate metrics from related Equipment_Inspection__c records.

Answer

The conversion from a Master-Detail relationship to a Lookup relationship is blocked because the master Asset object contains a Roll-Up Summary field that references the child Equipment_Inspection__c object.
Salesforce prevents converting a Master-Detail relationship to a Lookup relationship if any Roll-Up Summary fields exist on the master object that aggregate data from the detail object. Because Roll-Up Summary fields are exclusively supported on Master-Detail relationships, those fields must be removed before the relationship type can be changed to Lookup.

Step-by-Step Solution

1
Analyze relationship conversion rules in Salesforce Object Manager.
Converting a Master-Detail relationship to a Lookup relationship is permitted only if the parent object does not reference the child object in any Roll-Up Summary fields.
Lookup relationships do not support Roll-Up Summary fields. Therefore, any existing Roll-Up Summary fields on the master object must be deleted prior to converting the field type.
2
Evaluate the requirement for converting in the reverse direction (Lookup to Master-Detail).
Converting Lookup to Master-Detail requires every existing child record to have a populated parent lookup reference.
Master-Detail relationships require every detail record to be linked to a master record, whereas Master-Detail to Lookup conversions do not have this requirement.

Key Concept

Relationship Field Type Conversions and Roll-Up Summary Dependencies
Question 450Question

A Salesforce administrator is designing a custom data model to link a parent object, Event_Project__c, to a child object, Deliverable__c. The business requires that deleting an Event_Project__c record automatically deletes all associated Deliverable__c records. Which two statements correctly describe the capabilities and behavior of configuring a Master-Detail relationship for this requirement? (Choose 2 answers)

Select all that apply

Show answer & explanation

Answer: Deleting an Event_Project__c record automatically deletes all related Deliverable__c records.; Roll-up summary fields can be created on Event_Project__c to aggregate data from Deliverable__c records.

Answer

The correct statements are that deleting an Event_Project__c record automatically deletes all related Deliverable__c records, and roll-up summary fields can be created on Event_Project__c to aggregate data from Deliverable__c records.
In a Master-Detail relationship, the detail record's lifecycle is tied to the master record, so deleting the master automatically deletes all detail records. Furthermore, Master-Detail relationships enable roll-up summary fields on the master object to aggregate child values.

Step-by-Step Solution

1
Identify the relationship type that supports cascading deletes.
Master-Detail relationships inherently perform cascading deletes of child records when the master record is deleted.
This directly fulfills the business requirement of deleting associated deliverable records automatically.
2
Identify additional features unlocked by a Master-Detail relationship.
Master-Detail relationships allow roll-up summary fields on the master object.
The master record can summarize values such as record counts, totals, or minimum/maximum values from detail records.

Key Concept

Master-Detail Relationship Behavior and Roll-Up Summary Capabilities
Question 451Question

A Salesforce Administrator needs to provision access for a new sales representative who requires standard Salesforce access along with permissions to manage specialized custom fields. Which TWO administrative actions should the administrator take to fulfill this requirement following Salesforce best practices? (Select TWO)

Select all that apply

Show answer & explanation

Answer: Assign a standard User Profile that matches the user's core job function.; Create and assign a Permission Set to grant the specific custom field access.

Answer

Assign a baseline profile matching the job function and use a permission set to grant the extra custom field access.
According to Salesforce user management best practices, baseline access is established via a profile, while extra access—such as specific field-level security—is granted additively using a permission set.

Step-by-Step Solution

1
Assign the appropriate baseline user profile.
The user receives the appropriate license and core functional access.
Profiles control baseline permissions and license assignment for users.
2
Create and assign a Permission Set for the custom field permissions.
The user receives targeted access to the required custom fields.
Permission sets allow flexible, additive granting of permissions to individual users.

Key Concept

User Provisioning with Profiles and Permission Sets
Question 452Question

A Salesforce Administrator is configuring tracking for a custom parent object, Vendor_Contract__c, and a custom child object, Deliverable__c, which are currently connected by a Lookup relationship. The business management team requires displaying two metrics on each vendor contract record: the combined total financial value of all related deliverables, and the calculated average value per deliverable. Which two configuration steps should the administrator perform to fulfill these requirements? (Select 2)

Select all that apply

Show answer & explanation

Answer: Convert the existing Lookup relationship field on Deliverable__c to a Master-Detail relationship field.; Create a Roll-Up Summary field on Vendor_Contract__c using the SUM aggregate function, and a Formula field on Vendor_Contract__c to calculate the average value.

Answer

The administrator must convert the Lookup relationship on Deliverable__c to a Master-Detail relationship, then create a Roll-Up Summary field (SUM) on Vendor_Contract__c along with a Formula field to calculate the average value.
To create standard Roll-Up Summary fields, the underlying object relationship must be a Master-Detail relationship. Converting the lookup field on the child object to a master-detail field enables roll-up capabilities. Once converted, a Roll-Up Summary field using the SUM operation calculates the total deliverable value, and a formula field can calculate the average by dividing total value by total deliverable count.

Step-by-Step Solution

1
Verify relationship requirements for declarative aggregation
Standard declarative Roll-Up Summary fields require a Master-Detail relationship between parent and child objects.
Salesforce does not support standard Roll-Up Summary fields over Lookup relationships.
2
Convert the relationship type
The Lookup field on Deliverable__c is converted to a Master-Detail relationship.
Converting the relationship unlocks Roll-Up Summary field creation on Vendor_Contract__c.
3
Build summary and formula calculations on the parent object
Create a SUM Roll-Up Summary field for total value and a COUNT Roll-Up Summary field (or direct formula calculation) to calculate average value via a Formula field.
Formula fields on the parent object can reference Roll-Up Summary fields to execute mathematical calculations like averages.

Key Concept

Roll-Up Summary Field Relationship Requirements and Aggregate Formula Calculations
Question 453Question

An administrator at Cloud Kicks needs to grant a temporary auditor group access to a sensitive custom field, Tax_ID__c, on the Account object. The auditors currently share the 'Custom: Support User' profile with standard support agents who do not have access to this field. The requirements specify that only the auditors should have Read access to Tax_ID__c, and they must be strictly denied login access when attempting to log in from outside the corporate network IP address range. Standard support agents must retain their existing field visibility and maintain remote login access. Which administrative configuration best meets these requirements?

Show answer & explanation

Answer: Create a new custom profile for the auditor group with Login IP Ranges restricted to the corporate network, and assign the auditors a permission set that grants Read access to the Tax_ID__c field.

Answer

Create a new custom profile for the auditor group with Login IP Ranges restricted to the corporate network, and assign the auditors a permission set that grants Read access to the Tax_ID__c field.
Profile Login IP Ranges explicitly prevent users assigned to that profile from logging in outside the designated IP addresses. Because standard support users must maintain remote access, the auditor group requires a separate profile with the corporate Login IP Range configured. Field-Level Security for Tax_ID__c is then cleanly granted using a permission set assigned to the auditors.

Step-by-Step Solution

1
Evaluate the IP restriction requirement.
Identify that restricting login access exclusively to specific IP ranges (denying access outside the range) must be configured via Profile Login IP Ranges, as Organization-Wide Network Access only controls identity verification requirements.
Login IP Ranges are configured on Profiles, not Permission Sets or Network Access settings.
2
Evaluate user separation for IP restrictions.
Create a distinct profile for the auditor group so that standard support users retain their ability to log in remotely outside the corporate network.
Profile settings apply to all users assigned to that profile; shared profiles cannot enforce different IP rules for a sub-group.
3
Evaluate the Field-Level Security requirement.
Grant Read access to Tax_ID__c using a Permission Set assigned specifically to the auditors, preserving the principle of least privilege.
Permission Sets allow additive field permissions without modifying base profiles.

Key Concept

Profile Login IP Ranges vs. Permission Sets & Org-Wide Network Access
Estimated Time:2m 0s
Question 454Question

An administrator creates a custom Lightning Record Page for the Opportunity object. Which activation level must the administrator select to display this page specifically to users accessing the Sales App with the System Administrator profile?

Show answer & explanation

Answer: App, Record Type, and Profile

Answer

The App, Record Type, and Profile activation level allows administrators to assign a custom Lightning Record Page to specific combinations of Lightning Apps, Record Types, and User Profiles.
Activating a record page at the App, Record Type, and Profile level allows administrators to target specific user profiles within a designated application context, fulfilling the requirement.

Step-by-Step Solution

1
Open Lightning App Builder and click Activation for the custom Opportunity record page.
The Activation dialog opens displaying the activation options.
Page activation settings determine where and to whom the customized layout is displayed.
2
Select the 'App, Record Type, and Profile' tab and click 'Assign to Apps, Record Types, and Profiles'.
The activation assignment wizard starts.
This activation level provides granular targeting by application context and user role profile.
3
Select the Sales App, choose the relevant record types, and assign the System Administrator profile.
The custom page is activated specifically for System Administrators viewing opportunities within the Sales App.
This fulfills the exact requirement without affecting other applications or user profiles.

Key Concept

Lightning Record Page Activation Levels
Question 455Question

Cloud Matrix Systems tracks enterprise compliance using a custom object named Regional_Audit__c. The Organization-Wide Default (OWD) for Regional_Audit__c is set to Private. An administrator manually deselected the 'Grant Access Using Hierarchies' option on the Regional_Audit__c object definition. Later, an owner-based sharing rule is configured to share Regional_Audit__c records owned by Field Auditors with the Regional Compliance Manager role. The Compliance Director, who is positioned directly above the Regional Compliance Manager in the role hierarchy, reports being unable to view these shared records. Which configuration change should the administrator make to allow the Compliance Director to view the records while adhering to the principle of least privilege?

Show answer & explanation

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

Answer

Select the 'Grant Access Using Hierarchies' checkbox on the Regional_Audit__c custom object definition.
Selecting the 'Grant Access Using Hierarchies' checkbox on the custom object definition allows record access—whether derived from record ownership or sharing rules—to propagate up the role hierarchy to superior roles. This directly grants the Compliance Director access to records shared with the Regional Compliance Manager while preserving Private OWD for the rest of the organization.

Step-by-Step Solution

1
Analyze the Organization-Wide Default and object configuration
Regional_Audit__c has Private OWD and 'Grant Access Using Hierarchies' is deselected.
For standard objects, hierarchy access is mandatory, but for custom objects, it can be disabled. Disabling it prevents users higher in the role hierarchy from inheriting access granted to lower roles.
2
Evaluate the sharing mechanism and role positioning
Records are shared with Regional Compliance Managers via a sharing rule, but the Compliance Director (higher in the hierarchy) cannot view them.
Because hierarchy access is disabled on the object, access granted to the Regional Compliance Manager role does not roll up to the Compliance Director.
3
Identify the minimal configuration change required
Re-enabling 'Grant Access Using Hierarchies' on the custom object restores automatic access roll-up up the hierarchy.
This grants the Compliance Director access to records owned by or shared with subordinate roles without altering org-wide access levels or assigning administrative permissions.

Key Concept

Custom Object Role Hierarchy Access Roll-up
Estimated Time:2m 0s
Question 456Question

A Salesforce administrator attempts to create a Roll-Up Summary field on a custom parent object called Course__c to count related student registration records. However, during field creation, the Roll-Up Summary field type option is greyed out and disabled. What is the most likely reason for this restriction?

Show answer & explanation

Answer: The relationship between Course__c and the student registration object is a Lookup relationship rather than a Master-Detail relationship.

Answer

The relationship between Course__c and the student registration object is a Lookup relationship rather than a Master-Detail relationship.
In Salesforce, native Roll-Up Summary fields can only be created on the master object of a Master-Detail relationship. If two objects are joined using a Lookup relationship, the Roll-Up Summary field type remains disabled during field setup on the parent object.

Step-by-Step Solution

1
Identify the object relationship prerequisite for Roll-Up Summary fields.
Salesforce requires a Master-Detail relationship on the parent object to enable native Roll-Up Summary functionality.
Lookup relationships do not natively support built-in roll-up summary fields.
2
Evaluate the field creation behavior on the parent object.
Because the relationship is a Lookup relationship, the Roll-Up Summary radio button is greyed out during field creation.
Converting or re-creating the relationship as a Master-Detail relationship is required to enable roll-up summaries.

Key Concept

Roll-Up Summary Field Relationship Prerequisites
Question 457Question

An administrator is designing field calculations for a custom architecture where `Partner_Tier__c` acts as a parent object to `Deal_Registration__c`. Currently, `Deal_Registration__c` references `Partner_Tier__c` through a Lookup relationship. The business requires `Partner_Tier__c` to display the total aggregate revenue from all related deal registrations and also requires each `Deal_Registration__c` record to display the tier threshold value defined on its parent `Partner_Tier__c` record.

Which TWO statements accurately describe the field configuration requirements and capabilities to meet these business needs?

Select all that apply

Show answer & explanation

Answer: The Lookup relationship field on `Deal_Registration__c` must be converted to a Master-Detail relationship before a Roll-Up Summary field can be created on `Partner_Tier__c`.; A Cross-Object Formula field can be created on `Deal_Registration__c` to reference and display field values from the parent `Partner_Tier__c` record.

Answer

Converting the Lookup relationship to a Master-Detail relationship is required to build a Roll-Up Summary field on the parent object, and creating a Cross-Object Formula field on the child object allows referencing parent field values.
Roll-Up Summary fields calculate values from related detail records and are strictly limited to the master object in a Master-Detail relationship. Therefore, converting the existing lookup to a master-detail relationship is mandatory for native roll-up functionality. Furthermore, formula fields on child objects can span upward across relationships (up to 10 relationships away) to reference fields on parent records.

Step-by-Step Solution

1
Analyze the requirement to aggregate child data onto the parent object (`Partner_Tier__c`).
Native Roll-Up Summary fields require a Master-Detail relationship; therefore, the existing Lookup relationship on `Deal_Registration__c` must be converted to Master-Detail.
Salesforce standard Roll-Up Summary fields are unsupported on Lookup relationships.
2
Analyze the requirement to display parent tier threshold data on the child object (`Deal_Registration__c`).
A Cross-Object Formula field can be created on `Deal_Registration__c` referencing `Partner_Tier__r.Threshold__c`.
Formula fields support spanning upward across lookup or master-detail relationships to access fields on parent objects.

Key Concept

Roll-Up Summary Relationship Prerequisites and Cross-Object Formula Capabilities
Question 458Question

An administrator at a corporate catering enterprise is setting up a new custom object named Event_Booking__c in Salesforce to manage client events. Which two options represent standard capabilities available when defining optional features and properties during custom object creation? (Select 2)

Select all that apply

Show answer & explanation

Answer: Enabling Allow Reports to permit users to report on records of this custom object using standard report types; Setting the Record Name data type to Auto-Number with a custom display format

Answer

The correct options are enabling Allow Reports to permit reporting via standard report types and setting the Record Name data type to Auto-Number with a custom display format.
When configuring a custom object, enabling 'Allow Reports' allows standard report types to include the object. Additionally, administrators can choose between Text and Auto-Number for the object's Record Name field, configuring display formats as needed.

Step-by-Step Solution

1
Identify the standard settings available during custom object setup in Salesforce.
Salesforce allows enabling reporting via the 'Allow Reports' setting and defining the Record Name field as either Text or Auto-Number.
These are built-in features when defining object properties in Object Manager.
2
Evaluate relationship limitations for Roll-up Summary fields and Master-Detail deletion behavior.
Roll-up Summary fields require a Master-Detail relationship, not a Lookup relationship. Master-Detail relationships automatically delete detail records when master records are deleted.
This rules out the incorrect options regarding Lookup roll-ups and detail record survival.

Key Concept

Custom Object Creation and Optional Features
Question 459Question

Universal Containers uses a custom object named Project__c to track consulting engagements and a custom object named Consultant__c to manage staff availability. A Salesforce Administrator must establish a relationship structure using a custom object named Assignment__c to link consultants to projects. The business requirements state that:
1. Deleting a Project__c record must automatically delete all related Assignment__c records.
2. Deleting a Consultant__c record must leave the related Assignment__c records intact while clearing the consultant reference.
3. Administrators must be able to create Roll-Up Summary fields on the Project__c object to calculate total billable hours from related Assignment__c records.

Which relationship configuration on the Assignment__c object satisfies all of these requirements?

Show answer & explanation

Answer: Create a Master-Detail relationship pointing to Project__c and a Lookup relationship pointing to Consultant__c.

Answer

Create a Master-Detail relationship pointing to Project__c and a Lookup relationship pointing to Consultant__c.
Establishing a Master-Detail relationship from Assignment__c to Project__c fulfills two requirements: deleting a Project__c record cascades deletion to related Assignment__c records, and it allows Roll-Up Summary fields to be created on Project__c. Establishing a Lookup relationship from Assignment__c to Consultant__c ensures that deleting a Consultant__c record will not delete the Assignment__c record.

Step-by-Step Solution

1
Analyze the requirement for cascading record deletion and Roll-Up Summary capability on Project__c.
Project__c must be the Master object in a Master-Detail relationship with Assignment__c.
Master-Detail relationships enforce cascade deletion from master to detail and enable Roll-Up Summary fields on the master object.
2
Analyze the requirement for record preservation upon deletion of Consultant__c.
Consultant__c must be linked to Assignment__c via a Lookup relationship.
Lookup relationships allow child records to remain intact when the parent record is deleted, clearing the lookup field value.
3
Combine the relationship definitions on the Assignment__c object.
Assignment__c requires one Master-Detail field referencing Project__c and one Lookup field referencing Consultant__c.
This hybrid structure satisfies all cascading delete, roll-up summary, and record preservation requirements.

Key Concept

Master-Detail vs. Lookup Relationship Behaviors and Limitations
Estimated Time:2m 0s
Question 460Question

An administrator needs to grant Read and Edit access for a sensitive custom field, Salary_Tier__c, on the Employee object to a specific subset of users assigned to the Standard User profile. All other users with the Standard User profile must not be able to view or edit this field. Which TWO configurations should the administrator implement?

Select all that apply

Show answer & explanation

Answer: Set Field-Level Security on the Salary_Tier__c field to restricted (not visible) for the Standard User profile.; Create a permission set that grants Read and Edit access to Salary_Tier__c and assign it to the specific subset of users.

Answer

The administrator should restrict Field-Level Security on the base Standard User profile so the field is hidden by default, and create a permission set granting Read and Edit access to Salary_Tier__c and assign it to the users who require access.
To grant selective access while maintaining default restriction, Field-Level Security must be un-checked (hidden) on the base profile, and a Permission Set granting Read and Edit access must be assigned to the designated users. Salesforce security follows a model where profiles establish baseline restrictions and permission sets grant additive access.

Step-by-Step Solution

1
Restrict base access using Field-Level Security
Users with the Standard User profile cannot view or edit Salary_Tier__c by default.
Security permissions in Salesforce are restrictive at the profile level before additive access is layered on.
2
Create and assign a Permission Set
Only the assigned subset of users receives Read and Edit access to Salary_Tier__c.
Permission sets allow administrators to grant additional field permissions to specific users without creating unnecessary profiles.

Key Concept

Field-Level Security and Permission Sets
Estimated Time:1m 0s
PreviousPage 23 / 90Next
All practice questions — Salesforce Certified Administrator | Examkin