All practice questions

1784 questions

Question 581Question

A System Administrator at a wealth management firm needs to immediately revoke login access for a departing Senior Portfolio Manager. Upon attempting to deactivate the user record, the administrator receives an error stating the operation cannot be completed because the user is designated as the Default Workflow User in Process Automation Settings and serves as the default owner for incoming lead ingestion queues.

Which two statements accurately describe how the administrator should manage this situation to satisfy both security and system administration requirements? (Choose 2 answers)

Select all that apply

Show answer & explanation

Answer: Freeze the user account immediately to block login access without requiring immediate reassignment of the system administration dependencies.; Reassign the Default Workflow User setting and default lead queue ownership to an active user prior to deactivating the user record.

Answer

The administrator should freeze the user account immediately to block login access without requiring system dependency updates, and reassign the Default Workflow User setting and default lead queue ownership to an active user prior to deactivating the user record.
Freezing a user account immediately revokes login access without breaking or requiring the immediate reconfiguration of system-level dependencies such as the Default Workflow User or default queue ownership. However, freezing does not release the user license. To permanently deactivate the account and free up the user license, the administrator must first reassign those system dependencies to another active user.

Step-by-Step Solution

1
Evaluate the immediate security mandate vs system limitations
Login access must be blocked immediately, but direct deactivation is blocked due to active system dependencies (Default Workflow User and default queue owner).
Freezing a user account prevents login immediately without requiring changes to underlying processes or system defaults.
2
Plan the license reclamation and permanent deactivation workflow
System settings (Default Workflow User in Process Automation Settings and queue default ownership) must be manually updated to another active user.
Salesforce blocks user deactivation until all critical system-level dependencies are transferred.
3
Complete the deactivation after dependency reassignment
The user account can now be deactivated, successfully releasing the user license back to the organization pool.
Deactivating a user releases the license, whereas freezing keeps the license consumed.

Key Concept

User Activation, Deactivation, and Freezing
Question 582Question

An administrator at a medical device company needs to display the total monetary value of all approved maintenance service records on the parent Asset object. Upon inspecting the schema, the administrator discovers that the Service_Contract__c custom object is connected to the Asset object via a lookup relationship. Which configuration change will allow the administrator to summarize the total monetary value directly on the Asset record?

Show answer & explanation

Answer: Convert the existing lookup relationship between Asset and Service_Contract__c into a master-detail relationship, then create a Roll-Up Summary field using the SUM function on the Asset object.

Answer

Convert the existing lookup relationship between Asset and Service_Contract__c into a master-detail relationship, then create a Roll-Up Summary field using the SUM function on the Asset object.
Declarative roll-up summary fields in Salesforce require a master-detail relationship between the master (parent) and detail (child) objects. By converting the lookup relationship on the child object to a master-detail relationship, the administrator enables the ability to build a Roll-Up Summary field on the parent Asset object using the SUM aggregate function.

Step-by-Step Solution

1
Identify relationship constraints for Roll-Up Summary fields
Recognize that native Roll-Up Summary fields are only available on the master side of a Master-Detail relationship.
Salesforce platform limits declarative roll-up summaries to Master-Detail object relationships.
2
Determine the required architectural change
Convert the lookup relationship on Service_Contract__c to a master-detail relationship targeting Asset.
Ensuring all child records have a populated master lookup value allows relationship conversion.
3
Create the Roll-Up Summary field
Define a new Roll-Up Summary field on Asset using the SUM aggregate function filtered for approved records.
This natively calculates and displays the aggregate monetary value on the parent Asset object.

Key Concept

Roll-up summary fields require a Master-Detail relationship between the parent and child objects.
Question 583Question

An administrator needs to deploy a custom Lightning Record Page for the Case object. The business requires that this specific page layout is displayed only when users assigned to the Tier 2 Support profile view Cases with the Escalated Record Type while working inside the Service Console application.

Which two actions must the administrator perform during page activation to meet this requirement? (Select 2 choices)

Select all that apply

Show answer & explanation

Answer: Select the 'App, Record Type, and Profile' activation level in the Activation wizard.; Select the Service Console app, assign the Escalated Record Type, and select the Tier 2 Support profile.

Answer

The administrator must select the 'App, Record Type, and Profile' activation level in Lightning App Builder, and then select the Service Console app, Escalated Record Type, and Tier 2 Support profile during activation.
Lightning App Builder provides three levels of page activation for record pages: Org Default, App Default, and App, Record Type, and Profile. When a business requirement mandates a unique record page layout for a specific profile viewing a specific record type within a specific Lightning App, the administrator must choose the 'App, Record Type, and Profile' assignment level and configure the exact app, record type, and profile values.

Step-by-Step Solution

1
Identify the activation scope requirement
Recognize that the requirement involves a specific app (Service Console), record type (Escalated), and profile (Tier 2 Support).
Lightning Record Pages support three activation scopes: Org Default, App Default, and App + Record Type + Profile.
2
Select the appropriate activation level
Choose 'App, Record Type, and Profile' in the Activation wizard.
This is the only activation scope that allows assigning distinct Lightning Record Pages to specific profile and record type combinations within a specific app.
3
Map the specific assignment criteria
Select Service Console as the app, Escalated as the Record Type, and Tier 2 Support as the Profile.
This ensures the page layout is served only to target users in the intended context.

Key Concept

Lightning Record Page Activation Precedence and Scope
Question 584Question

A Salesforce administrator is ready to deploy a newly created Lightning Home Page using the Lightning App Builder. Which two activation assignments can the administrator configure for a Home Page? (Select two choices.)

Select all that apply

Show answer & explanation

Answer: Assign the page as the Org Default for all users.; Assign the page as the App Default for specific Lightning apps.

Answer

Lightning Home Pages can be activated as either the global Org Default or assigned as an App Default (including App and Profile combinations). They cannot be assigned by Record Type or assigned directly to individual users.
Lightning Home Pages support three activation options: Org Default, App Default, and App & Profile assignment. Therefore, designating the page as the global Org Default or assigning it as the App Default for specific Lightning applications are both valid activation choices.

Step-by-Step Solution

1
Identify the target page type being activated.
The target page is a Lightning Home Page.
Home Pages differ from Record Pages because they do not display object records.
2
Evaluate available activation levels for Home Pages in Lightning App Builder.
Home Page activation options include Org Default, App Default, and App & Profile assignment.
These levels allow administrators to customize the home experience globally or per Lightning app and user profile.
3
Eliminate invalid activation scope options.
Record Type assignments and direct user assignments are excluded.
Record Types apply strictly to Record Pages, and page activation does not assign directly to specific individual user accounts.

Key Concept

Lightning Home Page Activation Options
Question 585Question

Match each Salesforce business requirement related to object configuration with the correct administration setup action for Page Layouts and Record Types.

Click a left item, then click its matching right item

Items

Display a subset of Case Stage picklist values specifically tailored for a specialized Tier 3 Support team.
Control which fields and related lists are visible and editable for a specific profile when viewing a specific record type.
Ensure a specific Record Type is pre-selected by default whenever a user with a given Profile creates a new record.
Remove an obsolete picklist value so that it is unavailable across all existing and future Record Types on an object.

Matches

Show answer & explanation

Answer

Each business requirement correctly pairs with its underlying Salesforce administration setting: filtering picklist options per business process requires Record Type Picklists Available for Editing; controlling field arrangement per profile/record type relies on Page Layout Assignment; pre-selecting a record type uses Profile Default Record Type settings; and globally eliminating a picklist choice requires updating the Master Picklist values.
The pairings accurately reflect standard Salesforce architecture: Picklists Available for Editing controls picklist choices per Record Type; Page Layout Assignment links Profile + Record Type to a layout; Profile Record Type Settings govern defaults upon record creation; and Master Picklist defines global value availability.

Step-by-Step Solution

1
Analyze picklist filtering requirements
Identify that restricting available picklist options for specific business processes without creating separate fields is managed on the Record Type detail page under Picklists Available for Editing.
Record Types allow admins to offer different picklist values for the same field.
2
Analyze layout assignment rules
Identify that assigning page layouts requires navigating to Object Manager > [Object] > Page Layouts > Page Layout Assignment and setting the matrix for Profile x Record Type.
Page Layout assignment is determined by both the user's profile and the record's record type.
3
Analyze profile record type defaults
Identify that setting default record types during creation is configured within the Profile's Record Type Settings.
Default record types are assigned at the Profile level, not on individual user records or permission sets.
4
Analyze master picklist management
Identify that removing a picklist value globally requires updating the Master Picklist on the field definition itself.
The Master Picklist contains the master list of all values that can be assigned across record types.

Key Concept

Page Layouts and Record Types Assignment Matrix
Question 586Question

Cloud Kicks uses a custom object named Audit_Log__c to store compliance reviews. Management requires that users only have access to records they explicitly own. However, upper management must automatically inherit full read and write access to records owned by their direct and indirect subordinates. Which configuration should the administrator implement to meet these security requirements?

Show answer & explanation

Answer: Set the Organization-Wide Default (OWD) for Audit_Log__c to Private and ensure Grant Access Using Hierarchies is enabled.

Answer

Set the Organization-Wide Default (OWD) for Audit_Log__c to Private and ensure Grant Access Using Hierarchies is enabled.
Setting the Organization-Wide Default (OWD) to Private restricts record access to the record owner. Enabling Grant Access Using Hierarchies ensures that users positioned higher in the role hierarchy automatically receive the same access to records owned by users below them.

Step-by-Step Solution

1
Determine the baseline record access requirement.
The requirement states that users should only see records they own, which calls for the most restrictive baseline setting: Private.
Organization-Wide Defaults set the base level of access across all records for non-owners.
2
Determine how managers in the role hierarchy should gain access.
Enabling 'Grant Access Using Hierarchies' automatically grants access to users higher in the role hierarchy.
For custom objects, Grant Access Using Hierarchies can be toggled; enabling it ensures superior roles inherit the record access level of their subordinates.

Key Concept

Organization-Wide Defaults establish the baseline record access for an object, and Grant Access Using Hierarchies allows record access to roll up through the role hierarchy automatically.
Question 587Question

When introducing a novel Record Type on a custom object named Project, which two administrative tasks are required to ensure users view the correct layout and valid field choices? (Select 2 answers)

Select all that apply

Show answer & explanation

Answer: Specify the page layout assignment for each user profile under the object's Record Type settings.; Edit the picklist values assigned specifically to the new Record Type.

Answer

The necessary administrative tasks are assigning the page layout to user profiles for the record type and editing the available picklist values for that record type.
When configuring a new Record Type, the administrator must map the Record Type to the appropriate Page Layout for each user Profile and customize which picklist values are available for that specific Record Type.

Step-by-Step Solution

1
Assign Page Layouts to Profiles
Defines which page layout each profile uses when viewing or editing records of the new record type.
Record types map specific page layouts to user profiles.
2
Configure Record Type Picklist Values
Restricts selectable values for picklist fields based on the business requirements of the new record type.
Each record type can display a customized subset of master picklist values.

Key Concept

Page Layouts and Record Types Assignment
Question 588Question

An administrator at Cloud Kicks is notified that a operations lead is going on an extended sabbatical. The operations lead is currently designated as the default lead owner in active Lead Assignment Rules and is an assigned approver in several active Approval Processes. The administrator needs to prevent this user from logging into Salesforce immediately without disrupting existing automated processes or causing errors in pending workflow submissions. Which action should the administrator take to meet these requirements?

Show answer & explanation

Answer: Freeze the user account from the User setup page.

Answer

Freezing the user account prevents login access while keeping the user record active as a reference in existing automated workflows and approval processes.
Freezing a user account immediately blocks authentication into Salesforce while keeping the record intact for running process references, such as default assignment rule targets or pending approval steps.

Step-by-Step Solution

1
Analyze the operational requirements and process dependencies.
Identified that the user is linked to active Lead Assignment Rules and Approval Processes, meaning complete deactivation would break automated executions.
Salesforce prevents or errors out on deactivation when a user is tied to specific automated system roles unless references are reassigned first.
2
Evaluate the administrative capabilities of Freezing versus Deactivating a user.
Freezing temporarily revokes login privileges without altering underlying assignments or user license availability.
Freezing is designed specifically for scenarios where immediate login block is required but workflow dependencies prevent immediate account deactivation.
3
Select the appropriate administrative action in Setup.
Navigate to Setup > Users and click Freeze on the target user record.
This achieves the dual goal of security enforcement and maintaining continuous system automation without runtime failures.

Key Concept

User Freezing vs. Deactivation
Question 589Question

Universal Containers has configured Lead field mapping so that a custom Lead picklist field, 'Industry Segment', maps to a custom Account picklist field of the same name upon Lead conversion. During testing, users report that when converting a Lead, the value selected in 'Industry Segment' does not appear on the newly created Account record, even though the custom field mapping in Lead Settings was saved successfully. What should the system administrator do to resolve this issue?

Show answer & explanation

Answer: Ensure that the corresponding picklist values are added to the available picklist values for the target Account record type.

Answer

Ensure that the corresponding picklist values are added to the available picklist values for the target Account record type.
When converting a Lead into an Account, Contact, or Opportunity with specific Record Types enabled, mapped custom picklist field values must be valid and enabled for the target record type. If the picklist value is missing from the assigned Account Record Type's picklist edit list, the field will fail to populate on the newly created Account record.

Step-by-Step Solution

1
Analyze the lead conversion behavior for custom picklist field mapping.
Lead custom field mapping requires that source and target custom fields have compatible data types.
Mapping custom picklists between Lead and Account is supported, but record-level restrictions on the target object apply.
2
Evaluate record type picklist value assignments on the target Account object.
If the default record type assigned upon conversion does not explicitly include the mapped picklist values, Salesforce silently drops or clears the value during record creation.
Record type picklist assignments enforce data integrity on the target record.
3
Identify the required administrative resolution.
Updating the Account record type configuration to include the required picklist values allows the mapped value to populate correctly.
This resolves the issue without altering the correct Lead field mapping.

Key Concept

Lead Custom Field Mapping and Record Type Picklist Enforcement
Estimated Time:2m 0s
Question 590Question

A sales administrator is documenting the standard Salesforce lead conversion process for new sales representatives. What is the correct sequence of events when converting a qualified lead into standard Salesforce records?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence of lead conversion is: 1) Update Lead Status to 'Qualified', 2) Click the 'Convert' button, 3) Select or create target Account, Contact, and Opportunity records, 4) Salesforce copies mapped Lead field data to the target records, and 5) Salesforce sets IsConverted to true on the original Lead record.
The standard lead lifecycle begins when a lead reaches a qualified status. The user triggers conversion using the Convert button, configures destination Account, Contact, and Opportunity options, after which Salesforce creates or updates the target records, applies custom field mappings, and updates the original lead status to Converted.

Step-by-Step Solution

1
Identify the initial qualification status update.
The Lead Status is updated to 'Qualified'.
Conversion begins after a lead has satisfied qualification criteria within the sales lifecycle.
2
Initiate the conversion process in the Salesforce user interface.
Click the 'Convert' button on the Lead detail page.
This action opens the standard lead conversion modal.
3
Specify target destination records.
Choose or create the target Account, Contact, and optional Opportunity.
The user configures whether to create new records or attach to existing Account and Contact records.
4
Execute system data mapping and record creation.
Mapped lead fields populate target record fields.
Salesforce transfers standard and configured custom Lead fields to destination fields on the Account, Contact, or Opportunity.
5
Finalize original lead record state.
The Lead record is flagged with IsConverted = true.
The converted lead becomes read-only for standard users and is hidden from standard active lead views.

Key Concept

Salesforce Lead Lifecycle and Lead Conversion Process Sequence
Question 591Question

A sales representative at a financial services company is guiding a prospect through the standard Salesforce lead lifecycle and conversion process. Place the following operational and system steps in the correct chronological order from lead intake to final conversion.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct chronological sequence is: 1. A new Lead record is created via Web-to-Lead with an initial status of Open - Not Contacted, 2. The lead owner updates the status to Working - Contacted while evaluating business fit and qualification criteria, 3. The user clicks the Convert button and specifies target Account, Contact, and optional Opportunity parameters, 4. Salesforce executes custom validation rules on the Lead and target objects, 5. Target Account, Contact, and Opportunity records are created or updated, mapped custom fields populate, and the Lead status changes to Converted.
The correct order follows the standard Salesforce lead lifecycle and conversion order of operations: initial lead capture (Open - Not Contacted), active qualification (Working - Contacted), user conversion invocation, platform validation enforcement, and final target record creation accompanied by setting Lead Status to Converted.

Step-by-Step Solution

1
Identify the lead generation step
Web-to-Lead submission creates the record in an initial open state.
The lifecycle begins when prospect data is captured in Salesforce.
2
Determine the qualification activity step
The lead status advances to Working - Contacted during prospect qualification.
The lead lifecycle tracks status progression as sales reps interact with the prospect.
3
Identify the user-initiated conversion action
The user clicks Convert and chooses destination objects.
Conversion requires explicit user interaction to define target Account, Contact, and Opportunity details.
4
Trace the system validation order of execution
Salesforce evaluates validation rules before record creation.
System data quality checks must pass before records are committed to the database.
5
Establish the completion state
Records are generated/updated, mapped fields transfer, and Lead status becomes Converted.
The lead lifecycle terminates by marking the lead record as read-only Converted and creating corresponding core CRM records.

Key Concept

Salesforce Lead Conversion Lifecycle and Order of Operations
Question 592Question

A marine shipping company uses Salesforce to manage container freight bookings. Eighty Operations Specialists are assigned to a baseline profile named 'Standard Cargo Operations'. The system administrator needs to bundle individual permission sets granting access to 'Customs Clearance', 'Hazardous Material Handling', and 'Port Inspection Log Access' into a single re-usable permission structure. Additionally, the administrator must selectively suppress the 'Delete Port Logs' permission for a subset of users assigned to this bundled access. Which two administrative actions should the administrator perform to achieve this requirement?

Select all that apply

Show answer & explanation

Answer: Combine the 'Customs Clearance', 'Hazardous Material Handling', and 'Port Inspection Log Access' permission sets into a Permission Set Group.; Add a Muting Permission Set to the Permission Set Group that explicitly mutes the 'Delete Port Logs' permission.

Answer

The administrator should bundle the individual permission sets into a Permission Set Group and configure a Muting Permission Set within that group to disable the 'Delete Port Logs' permission.
Bundling the individual permission sets into a Permission Set Group streamlines user assignment. Adding a Muting Permission Set directly to the group selectively revokes specific permissions, such as 'Delete Port Logs', without requiring changes to the original permission sets.

Step-by-Step Solution

1
Bundle the required functional permission sets.
Create a Permission Set Group containing the 'Customs Clearance', 'Hazardous Material Handling', and 'Port Inspection Log Access' permission sets.
Permission Set Groups consolidate multiple permission sets so they can be assigned efficiently as a single unit.
2
Configure permission suppression for specific users.
Add a Muting Permission Set inside the newly created Permission Set Group and set the 'Delete Port Logs' permission to Muted.
Muting Permission Sets allow administrators to restrict permissions granted by other permission sets within that specific group without modifying the source permission sets.

Key Concept

Permission Set Groups and Muting Permission Sets
Question 593Question

A B2B financial services enterprise requires capturing a lead's investment category using a custom picklist field, Investment_Tier__c, on the Lead object. Upon lead conversion, management requires this value to automatically populate the standard Industry field on the Account record and a custom picklist field, Opportunity_Tier__c, on the Opportunity record. When attempting to configure Lead Custom Field Mapping, the administrator finds that the standard Account Industry field does not appear in the target mapping dropdown list. Which explanation accounts for this limitation, and how should the administrator resolve it?

Show answer & explanation

Answer: Custom lead fields can only be mapped to custom fields on target objects; the administrator must create a custom picklist on Account to map the field, or use automation to populate the standard Industry field.

Answer

Custom lead fields can only be mapped to custom fields on target objects; the administrator must create a custom picklist on Account to map the field, or use automation to populate the standard Industry field.
In Salesforce Lead Conversion configuration, custom lead fields can only be mapped to custom fields created on the Account, Contact, or Opportunity objects. Standard fields, such as standard Account Industry, are not available in the dropdown selection for Lead Custom Field Mapping. To fulfill the requirement, the administrator must either map the Lead field to a custom Account picklist field or use Flow automation triggered upon conversion to update the standard Industry field.

Step-by-Step Solution

1
Analyze Salesforce Lead Conversion custom field mapping rules.
Salesforce Lead Custom Field Mapping strictly enforces that custom fields on the Lead object can only map to custom fields on Account, Contact, or Opportunity.
Standard fields like Account Industry are system-defined and cannot be selected as custom field mapping targets.
2
Identify the cause of the missing mapping target in the setup UI.
Because standard Account Industry is a standard field, it is unavailable in the Lead Custom Field Mapping UI drop-down menu.
Salesforce limits custom lead field mapping targets exclusively to custom fields.
3
Determine the appropriate administrative solution.
Create a custom picklist on the Account object to hold the mapped value, or implement post-conversion record-triggered automation (such as Flow) to copy the converted value into the standard Account Industry field.
This complies with platform constraints while fulfilling the business requirement.

Key Concept

Salesforce Lead Custom Field Mapping Constraints
Question 594Question

Universal Containers has launched a new software subscription product for its international accounts. The system administrator is attempting to add this product to a newly configured custom price book named 'EMEA Regional Price Book'. However, Salesforce prevents the administrator from creating the price book entry. Which condition must be met before this product can be added to any custom price book?

Show answer & explanation

Answer: The product must have an active standard price entry created in the Standard Price Book.

Answer

The product must have an active standard price entry created in the Standard Price Book.
In Salesforce, the Standard Price Book serves as the master pricing foundation. A product cannot be assigned to any custom price book until an active price entry is created for it within the Standard Price Book.

Step-by-Step Solution

1
Analyze the prerequisite relationship between Products and Price Books in Salesforce.
Salesforce enforces a strict dependency where the Standard Price Book acts as the master repository for all product pricing.
Every product requires a baseline standard price entry before regional or specialized pricing can be established.
2
Verify standard price record status.
Ensure that a Standard Price Book entry exists and that its active checkbox is marked.
Without an active standard price entry, custom price book entries cannot be saved.

Key Concept

Standard Price Book Prerequisite for Custom Price Books
Question 595Question

A Salesforce administrator is tasked with deploying a customized Opportunity Lightning Record Page designed specifically for executive leadership. The business requirement states that users with the Executive profile must see this customized layout when viewing any Opportunity record within the Sales Application. All other staff using the Sales Application should retain the existing layout. What activation assignment option should the administrator select in Lightning App Builder?

Show answer & explanation

Answer: Assign the page as App, Record Type, and Profile default for the Sales App, all Opportunity record types, and the Executive profile.

Answer

Assigning the custom page as the App, Record Type, and Profile default specifically targeted to the Sales App, Opportunity record types, and Executive profile satisfies the business requirement.
In Lightning App Builder, assigning a page as the App, Record Type, and Profile default provides the exact level of targeting needed when a specific subset of users (by profile) within a specific application (Sales App) requires a custom Record Page layout.

Step-by-Step Solution

1
Analyze the activation requirements
The requirement specifies a page override limited to a specific combination of Application (Sales App) and User Profile (Executive).
Lightning App Builder supports three levels of page activation: Org Default, App Default, and App, Record Type, and Profile.
2
Select the correct activation granularity
The App, Record Type, and Profile assignment level is required.
Org Default applies to all users across all apps, and App Default applies to all users within a given app regardless of profile.
3
Configure activation in Lightning App Builder
Assign the page to the Sales App, select the appropriate Opportunity Record Types, and select the Executive profile.
This ensures only users with the Executive profile in the Sales App view the customized record page.

Key Concept

Lightning Record Page Activation Levels and Precedence
Question 596Question

An administrator is designing a custom data structure to track consulting engagements and specialized team skill certifications. Each consulting engagement can require multiple skill certifications, and each skill certification can be associated with multiple consulting engagements. If a skill certification is deleted, the association to the engagement must be removed automatically without deleting the engagement itself. Additionally, managers need to calculate aggregate metrics on the engagement record, such as the total certification level count. Which two design choices should the administrator implement to meet these business requirements?

Select all that apply

Show answer & explanation

Answer: Create a custom junction object that links Consulting Engagement and Skill Certification using two Master-Detail relationships.; Define Consulting Engagement as a Master object in a Master-Detail relationship on the junction object to enable roll-up summary fields.

Answer

The administrator must create a custom junction object with two Master-Detail relationships to establish a many-to-many model, and define Consulting Engagement as a Master object on that junction object to enable roll-up summary calculations.
To model a many-to-many relationship between Consulting Engagement and Skill Certification, a custom junction object with Master-Detail relationships to both objects must be created. Building a Master-Detail relationship where Consulting Engagement is the Master permits the creation of native Roll-Up Summary fields on Consulting Engagement to aggregate child records, while ensuring junction records are deleted if a Skill Certification is removed.

Step-by-Step Solution

1
Analyze relationship cardinality requirements
Since one engagement can have multiple certifications and one certification can apply to multiple engagements, a Many-to-Many relationship model using a junction object is required.
Direct single lookup fields cannot model many-to-many business relationships in Salesforce.
2
Determine relationship types for deletion cascade and roll-up capabilities
Master-Detail relationships must be used from the junction object to both parent objects.
Master-Detail relationships enforce cascading deletion of junction records when a parent record is deleted and enable Roll-Up Summary fields on the Master object.
3
Verify roll-up summary requirement on the parent object
Consulting Engagement acts as the Master object, allowing Roll-Up Summary fields to summarize child junction records.
Salesforce only allows Roll-Up Summary fields on the Master side of a Master-Detail relationship.

Key Concept

Many-to-Many Relationships and Roll-Up Summary Requirements
Estimated Time:2m 0s
Question 597Question

ApexCare Health configures a Delegated Administration group to grant a Regional Support Manager administrative privileges over users in the 'US Field Support' role. The setup includes user management rights, password resets, and permission set assignment capabilities. The Regional Support Manager needs to grant extra object permissions to a single user in their delegated role without affecting other team members who share the same profile. Which administrative approach should the Regional Support Manager take within their delegated authority?

Show answer & explanation

Answer: Assign an authorized permission set containing the required object permissions directly to the user.

Answer

Assign an authorized permission set containing the required object permissions directly to the user.
Delegated administrators are empowered to assign designated permission sets to users within their assigned role hierarchy. Utilizing a permission set grants the necessary object access to the specific user while maintaining the security baseline for all other users assigned to the profile.

Step-by-Step Solution

1
Identify the requirement to grant additive permissions to a specific user without altering permissions for other users sharing the same profile.
Recognize that permission sets must be used for user-specific additive permissions.
Profiles grant baseline permissions to groups of users, whereas permission sets extend access on an individual basis.
2
Evaluate Delegated Administration capabilities regarding user permission management.
Confirm that delegated administrators can assign explicitly specified permission sets to users within their assigned roles.
Delegated group settings define specific permission sets that delegated admins are permitted to assign.
3
Eliminate options requiring profile creation or modification.
Determine that creating or editing profiles is beyond delegated administration scope and impacts broader user groups.
Profile administrative changes require full system administration privileges ('Manage Profiles and Permission Sets').

Key Concept

Delegated Administration Permission Set Assignment and Profile Boundaries
Question 598Question

A System Administrator at a corporate training firm needs to track aggregate metrics on the custom parent object Training_Course__c based on related child Course_Registration__c records. Currently, Course_Registration__c is linked to Training_Course__c via a standard Lookup relationship. The administrator wants to display the total number of enrolled participants and the maximum fee paid directly on the Training_Course__c record using standard platform declarative tools.

Which two considerations or constraints must the administrator keep in mind when designing this solution?

Select all that apply

Show answer & explanation

Answer: Standard Roll-Up Summary fields cannot be created on Training_Course__c while the objects are linked via a Lookup relationship.; Converting the Lookup relationship to a Master-Detail relationship requires that all existing Course_Registration__c records have a populated Training_Course__c lookup field.

Answer

Standard Roll-Up Summary fields require a Master-Detail relationship structure and cannot be created over a Lookup relationship. Additionally, converting a Lookup relationship to a Master-Detail relationship requires that all existing child records have a populated lookup field value.
Standard Roll-Up Summary fields require a Master-Detail relationship. Converting an existing Lookup relationship to a Master-Detail relationship mandates that every existing child record has a populated value in the lookup field.

Step-by-Step Solution

1
Evaluate relationship requirements for Roll-Up Summary fields
Declarative Roll-Up Summary fields are supported exclusively on the master object of a Master-Detail relationship.
Lookup relationships do not support native Roll-Up Summary calculation fields.
2
Identify relationship conversion requirements from Lookup to Master-Detail
All existing child records must have a non-null parent lookup reference prior to relationship type conversion.
Master-Detail relationships strictly enforce child record dependency on parent records.

Key Concept

Roll-up summary relationship prerequisites and conversion considerations
Question 599Question

Apex Global Logistics has a sensitive custom field, Contract_Renewal_Value__cContract\_Renewal\_Value\_\_c, on the Vendor Account record. The Procurement Operations team requires view and edit access to this field, whereas warehouse staff—who share the same base Operations profile—must not have access. Additionally, system compliance mandates that Procurement Operations users be prohibited from logging into Salesforce when outside the corporate network IP range of 192.168.10.0192.168.10.0 to 192.168.10.255192.168.10.255. Which two configuration steps should the Salesforce Administrator take to meet these security requirements? (Select 2 answers)

Select all that apply

Show answer & explanation

Answer: Create a Permission Set granting Read and Edit access to Contract_Renewal_Value__c and assign it to the Procurement Operations users.; Create a custom Procurement profile assigned to Procurement Operations users and configure the Login IP Ranges on that profile.

Answer

The administrator must create a Permission Set granting Read and Edit access on Contract_Renewal_Value__c for the Procurement team, and create a custom Procurement profile to enforce Profile Login IP Ranges.
The correct solution uses a Permission Set to grant Read and Edit access on the sensitive field specifically to Procurement Operations users without affecting warehouse staff. Additionally, because Login IP Ranges restrict login access exclusively when configured on a Profile (and cannot be set via Permission Sets), creating a distinct custom profile for Procurement users allows setting the required Login IP Ranges without impacting warehouse staff.

Step-by-Step Solution

1
Evaluate field access requirements across user groups
Since warehouse staff and Procurement users share a profile, baseline Field-Level Security (FLS) for Contract_Renewal_Value__c should remain restricted on the base profile. Access is granted additively to Procurement users via a Permission Set.
Using Permission Sets for incremental field access avoids profile proliferation.
2
Evaluate login restriction requirements
Login IP Ranges enforce strict login blocking outside designated ranges and must be defined on a Profile. Because warehouse staff should not be restricted by these IP ranges, Procurement users must be assigned a distinct custom profile.
Permission Sets cannot enforce Login IP Ranges; login hours and IP restrictions are exclusively managed at the Profile level.

Key Concept

Combining Permission Sets for additive Field-Level Security (FLS) with Profile-level Login IP Restrictions
Estimated Time:1m 30s
Question 600Question

A Salesforce Administrator at a renewable energy firm is tasked with displaying the total cost of completed inspections on the parent custom object `Solar_Project__c`. The inspection details are stored on a child custom object `Site_Inspection__c`, which is currently connected to `Solar_Project__c` via a Lookup relationship. When navigating to Object Manager to create a new field on `Solar_Project__c`, the administrator finds that the Roll-Up Summary field type option is grayed out and unavailable. Which statement correctly explains why the Roll-Up Summary field type is disabled and describes the appropriate administrative resolution?

Show answer & explanation

Answer: Roll-up summary fields are only supported on the parent object of a Master-Detail relationship. To enable this field type, the administrator must convert the existing Lookup relationship on Site_Inspection__c to a Master-Detail relationship, ensuring all existing child records contain a parent lookup value first.

Answer

Roll-up summary fields are only supported on the parent object of a Master-Detail relationship. To enable this field type, the administrator must convert the existing Lookup relationship on Site_Inspection__c to a Master-Detail relationship, ensuring all existing child records contain a parent lookup value first.
In Salesforce Core Administration, native Roll-Up Summary fields are exclusively available on the master object in a Master-Detail relationship. Because Site_Inspection__c is linked to Solar_Project__c via a Lookup relationship, the Roll-Up Summary option is disabled. To resolve this, the administrator must convert the Lookup relationship to a Master-Detail relationship, which requires verifying that every child Site_Inspection__c record has a non-null parent project reference.

Step-by-Step Solution

1
Identify relationship type requirement for native Roll-Up Summary fields.
Native Salesforce Roll-Up Summary fields can only be created on the master object in a Master-Detail relationship.
Lookup relationships do not enforce strict parent-child data dependency or tight coupling required by native declarative roll-up engine calculations.
2
Determine conversion prerequisites from Lookup to Master-Detail.
Ensure all Site_Inspection__c records have a valid Solar_Project__c populated in the lookup field.
Converting a lookup relationship to master-detail will fail if any orphan child records exist without a parent value.
3
Convert relationship type and create Roll-Up Summary field.
Change field type of the relationship field to Master-Detail, then create the SUM Roll-Up Summary field on Solar_Project__c.
Once the Master-Detail relationship is established, the Roll-Up Summary field type becomes available on the parent object setup wizard.

Key Concept

Roll-Up Summary Field Relationship Requirements
Estimated Time:1m 30s
PreviousPage 30 / 90Next
All practice questions — Salesforce Certified Administrator | Examkin