All practice questions

1784 questions

Question 761Question

BrightHorizon Media utilizes a custom object named Security_Incident__c to log internal IT security events. The Organization-Wide Default (OWD) for Security_Incident__c is set to Private. Management requires that upper-level managers in the role hierarchy should NOT automatically inherit access to security incident records owned by their subordinates. However, the Compliance Director role must be granted Read access to any Security_Incident__c record where the Severity field is set to 'Critical'. Which configuration should a System Administrator implement to satisfy these access requirements?

Show answer & explanation

Answer: Deselect 'Grant Access Using Hierarchies' on the custom object definition, and create a criteria-based sharing rule to share records where Severity equals 'Critical' with the Compliance Director role.

Answer

Deselect 'Grant Access Using Hierarchies' on the custom object definition, and create a criteria-based sharing rule to share records where Severity equals 'Critical' with the Compliance Director role.
For custom objects, administrators can deselect the 'Grant Access Using Hierarchies' checkbox in Organization-Wide Defaults / Sharing Settings. This prevents users higher in the role hierarchy from automatically receiving access to records owned by or shared with their subordinates. To grant conditional access to a specific role based on field values (Severity = 'Critical'), a criteria-based sharing rule is the correct and supported mechanism.

Step-by-Step Solution

1
Analyze hierarchy access requirements for the custom object
By default, custom objects have 'Grant Access Using Hierarchies' selected, allowing record access to propagate up the role hierarchy. Unchecking this setting disables automatic access propagation.
Prevents managers higher in the role hierarchy from automatically viewing records owned by subordinates.
2
Determine the record sharing mechanism for selective record access
Since access depends on field values (Severity = 'Critical') rather than record ownership, a criteria-based sharing rule is required.
Criteria-based sharing rules grant access to specified roles or groups when field criteria are met, regardless of record owner.

Key Concept

Disabling Grant Access Using Hierarchies on custom objects combined with criteria-based sharing rules.
Estimated Time:1m 30s
Question 762Question

A Salesforce administrator needs to configure a custom case lifecycle for a newly established tier of technical support. The team requires a specific sequence of Case Status picklist values that differs from the default support process. Which feature must the administrator create first so that these custom status values can be assigned to a new Case Record Type?

Show answer & explanation

Answer: Support Process

Answer

The administrator must create a Support Process first.
On the Case object, the Case Status field is controlled by Support Processes. Administrators must create a Support Process to select which status values are active before creating a Case Record Type that links to that process.

Step-by-Step Solution

1
Identify the relationship between Case Status picklist values and Case Record Types.
Recognize that Case Status is controlled specifically by a Support Process.
On the Case object, Case Status values cannot be assigned directly to Record Types without an intermediate Support Process.
2
Determine the required administrative setup order.
Create the Support Process with the necessary status values before creating the Record Type.
When creating a Case Record Type, selecting an existing Support Process is a mandatory prerequisite.

Key Concept

Support Process prerequisite for Case Record Types
Question 763Question

A Salesforce administrator at a commercial solar equipment manufacturer is updating the Lead conversion workflow for sales operations. The team needs to ensure lead data transfers accurately to new records while maintaining proper record creation controls. Which two statements accurately describe administrative configurations or standard platform behaviors during Lead conversion?

Select all that apply

Show answer & explanation

Answer: Custom fields created on the Lead object can only be mapped to custom fields on the Account, Contact, or Opportunity objects.; Administrators can configure Lead Settings to hide the option to create an Opportunity during the conversion process.

Answer

Custom Lead fields can only be mapped to custom fields on target records (Account, Contact, Opportunity), and administrators can optionally hide the Opportunity creation section in Lead Settings.
Custom Lead fields must always map to custom fields on target Account, Contact, or Opportunity records. Additionally, Lead Settings allows administrators to hide the Opportunity column in the lead conversion window to prevent unnecessary opportunity creation.

Step-by-Step Solution

1
Evaluate field mapping capabilities for custom Lead fields.
Confirm that custom Lead fields map exclusively to custom fields on Account, Contact, or Opportunity records of compatible data types.
Salesforce custom field mapping tool does not allow mapping custom Lead fields to standard fields on converted records.
2
Evaluate Opportunity creation configuration options in Lead Settings.
Confirm that administrators can suppress Opportunity creation via Lead Settings.
Checking 'Hide Opportunity column in Convert Lead window' removes the option to create Opportunities for converted leads.

Key Concept

Lead Custom Field Mapping and Lead Conversion Settings
Question 764Question

A Salesforce Administrator at Veritas Cyber Solutions is configuring a custom price book named 'Federal Enterprise' for a newly launched endpoint protection service. When attempting to add the new product to the 'Federal Enterprise' custom price book, the administrator finds that the custom price book cannot be selected. What is the mandatory prerequisite that must be completed before a product can be added to any custom price book?

Show answer & explanation

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

Answer

The product must have an active price entry in the Standard Price Book.
In Salesforce Core Administration, a product must have an active standard price entry in the Standard Price Book before it can be added to any custom price book. This ensures that a foundational price exists for the product across the organization.

Step-by-Step Solution

1
Identify the standard architecture requirements for Salesforce Products and Price Books.
Salesforce mandates that every product must first have an active standard price defined in the Standard Price Book before it can be assigned to custom price books.
The standard price serves as the baseline price entry for the product catalog.
2
Evaluate the prerequisite setup for the 'Federal Enterprise' custom price book.
Ensure an active Standard Price Book entry exists for the endpoint protection service product.
Without an active standard price, the system prevents adding the product to any custom price book entries.

Key Concept

Standard Price Book entry requirement before custom price book assignment
Question 765Question

A Salesforce administrator is configuring Lightning App Builder activations and component visibility for a custom object named Asset_Service__c. The business requires that specific user profiles see a tailored Lightning Record Page when accessing records in the Service Console app. Additionally, an executive summary component on the page must only display when the service status field is marked as 'Completed'. Which two administrative actions should the administrator take to meet these requirements? (Select 2 choices)

Select all that apply

Show answer & explanation

Answer: Activate the Lightning Record Page as the App, Record Type, and Profile default for the Service Console app and target user profiles.; Set a component visibility filter on the executive summary component using the Record Field criteria where Status equals 'Completed'.

Answer

The administrator must activate the page at the App, Record Type, and Profile level for specific user access, and configure a component visibility filter based on the Status field value.
To grant specific user profiles a unique page layout within a particular Lightning app, the administrator must activate the record page at the App, Record Type, and Profile level. Furthermore, to dynamically display a component based on a record's field values (such as Status = 'Completed'), a component visibility filter must be configured in Lightning App Builder.

Step-by-Step Solution

1
Determine the required page activation level
Identify that different profiles needing distinct views within a specific app requires App, Record Type, and Profile activation.
Org Default and App Default do not provide granular control down to specific user profiles and record types.
2
Configure component visibility criteria
Add a visibility filter on the target component where the field criteria is Status equals 'Completed'.
Dynamic component visibility evaluates record field values to control component rendering on Lightning Record Pages.

Key Concept

Lightning Record Page Activation and Dynamic Component Visibility
Question 766Question

An administrator at a healthcare non-profit needs to track patient satisfaction surveys using a new custom object named Patient_Feedback__c. The business team requires that aggregate score totals from all feedback records display directly on the parent Account record using a declarative roll-up summary field. Additionally, if an Account is deleted, all associated Patient_Feedback__c records must automatically be removed. Which relationship configuration on the custom object satisfies these requirements?

Show answer & explanation

Answer: Create a Master-Detail relationship field on the Patient_Feedback__c custom object referencing the Account standard object.

Answer

Create a Master-Detail relationship field on the Patient_Feedback__c custom object referencing the Account standard object.
Creating a Master-Detail relationship field on Patient_Feedback__c referencing Account satisfies both business requirements. In a Master-Detail relationship, the master record (Account) controls detail record behavior, enabling automatic cascade deletion of child records when the master is deleted, and allowing standard Roll-Up Summary fields to be created on Account.

Step-by-Step Solution

1
Identify the relationship requirements between Account and Patient_Feedback__c.
The requirements demand declarative roll-up summary fields on the parent and automatic cascade deletion when a parent record is deleted.
Master-Detail relationships natively support cascade deletion and permit roll-up summary fields on the master object.
2
Determine the child object and relationship placement.
Patient_Feedback__c must be the child/detail object containing the Master-Detail field pointing to the parent Account object.
Relationship custom fields are always created on the child object pointing toward the parent.

Key Concept

Master-Detail Relationship Capabilities and Setup
Question 767Question

A System Administrator at Cloud Kicks needs to set up a new sales pipeline for a specialized business division. Arrange the administrative steps in the correct chronological order required to successfully deploy this pipeline and make it available to sales representatives.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence of administrative steps is: 1) Add new stage values to the Opportunity Stage picklist field; 2) Create a new Sales Process selecting the appropriate stages; 3) Create an Opportunity Record Type linked to the Sales Process; 4) Assign the Record Type and Page Layout to the user profiles.
In Salesforce Opportunity administration, strict object dependencies govern setup: 1) Stage picklist values must be created first on the Opportunity object. 2) A Sales Process must be created next to curate which stage values belong to a specific lifecycle. 3) An Opportunity Record Type must then be created and linked to the Sales Process (since Opportunity record types derive stage picklist availability from Sales Processes rather than direct picklist mapping). 4) Finally, the Record Type and associated Page Layout must be assigned to user profiles so sales representatives can utilize the new pipeline.

Step-by-Step Solution

1
Define Stage Master Picklist Values
Opportunity Stage picklist contains all required pipeline stages, each mapped with probability percentages and forecast categories.
Stage picklist values serve as the foundational master list for all sales processes.
2
Create Sales Process
A named Sales Process entity exists containing only the active stages relevant to this specific sales cycle.
Sales Processes dictate which stage picklist values are exposed for opportunities governed by that process.
3
Create Opportunity Record Type
An Opportunity Record Type is linked to the newly created Sales Process.
Sales Processes cannot be assigned directly to profiles; they must be mapped through an Opportunity Record Type.
4
Assign Record Type and Page Layout to Profiles
Target sales users gain access to select the new Record Type when creating or editing Opportunity records.
Security and profile permissions dictate visibility and access to record types and page layouts in Salesforce.

Key Concept

Salesforce Sales Process and Opportunity Record Type Setup Dependency Chain
Question 768Question

To streamline record creation, an organization requires a mechanism on the Account record page that allows users to create a related Opportunity record while automatically setting the Stage field to 'Prospecting' and linking it to the source Account. Which tool should be configured on the Account object?

Show answer & explanation

Answer: An Object-Specific Quick Action with predefined field values

Answer

An Object-Specific Quick Action with predefined field values is the correct tool to create related records directly from a record page while setting default field values.
Object-Specific Quick Actions are designed to perform actions within the context of a specific record page, such as creating related records. Administrators can set predefined field values on the action to automatically populate fields like Stage with specific defaults.

Step-by-Step Solution

1
Identify the functional requirement
The requirement involves creating a child record (Opportunity) directly from a parent record (Account) and setting default field values ('Prospecting').
This requires record context and field pre-population capabilities.
2
Evaluate available Lightning actions
Object-Specific Quick Actions support creating related records within the context of the current object and allow setting Predefined Field Values.
Global actions lack record context, whereas custom visibility rules and permission sets do not create records.

Key Concept

Object-Specific Quick Actions and Predefined Field Values
Estimated Time:1m 0s
Question 769Question

Match each Salesforce Opportunity Team configuration or sharing scenario on the left with its corresponding access behavior and system capability on the right.

Click a left item, then click its matching right item

Items

User configures a Default Opportunity Team with specific team roles and access levels in their personal settings.
An Opportunity Owner adds a user to an Opportunity Team with Read/Write access on a Private record where OWD is Private.
An Administrator configures Account Team Sharing and sets Opportunity Access for an Account Team member to Private.
An Opportunity Owner transfers record ownership to a new owner while selecting the option to retain the Opportunity Team.

Matches

Show answer & explanation

Answer

1. Default Opportunity Team setup in personal settings automatically populates team members on newly created opportunities. 2. Adding an Opportunity Team member with Read/Write access grants explicit row-level sharing to the record while honoring field-level security. 3. Setting Opportunity Access to Private on Account Teams restricts access to related account opportunities. 4. Retaining Opportunity Teams during ownership transfer keeps directly assigned members while re-evaluating implicit/hierarchical access.
Each Opportunity Team feature serves a specific administrative function: Default Opportunity Teams automate team assignment upon record creation; Opportunity Team members receive explicit row-level sharing without overriding FLS; Account Team settings dictate child Opportunity access; and retaining team members during ownership transfer preserves manual team assignments.

Step-by-Step Solution

1
Analyze Default Opportunity Team behavior.
Default Opportunity Teams allow users to define standard sales team members in personal settings to automatically populate on new opportunities.
Reduces administrative overhead for sales reps working with fixed teams.
2
Evaluate manual Opportunity Team member addition permissions.
Granting Read/Write access via Opportunity Team adds a sharing entry to the Opportunity Share object, granting record access without bypassing field-level security.
Salesforce object-level and field-level security always override record-level sharing permissions.
3
Examine Account Team to Opportunity record access propagation.
Account Team settings allow specifying opportunity access (Private, Read Only, Read/Write). Setting it to Private prevents access propagation to account opportunities.
Account Team access settings override standard Organization-Wide Defaults for associated child records when configured.
4
Verify ownership transfer impact on Opportunity Teams.
Selecting the option to retain team members during transfer preserves explicit Opportunity Team members while updating owner-based implicit sharing.
Explicit team assignments are maintained on the record unless manually removed or wiped during transfer.

Key Concept

Opportunity Team member sharing permissions and Default Opportunity Team automation
Question 770Question

An administrator at a healthcare organization needs to design a data model connecting Patient (`Patient__c`) records with Medical Specialist (`Specialist__c`) records. A patient can consult with multiple specialists, and a specialist can treat multiple patients. The business requires that deleting a Patient or Specialist record automatically removes the related consultation record, and that aggregate metrics from consultation records are calculated directly on the Specialist record. Which TWO configuration steps should the administrator implement to fulfill these requirements? (Choose 2 answers)

Select all that apply

Show answer & explanation

Answer: Create a custom junction object that contains Master-Detail relationship fields referencing both Patient and Specialist objects.; Create Roll-Up Summary fields on the Specialist object that aggregate calculation data from the child junction object records.

Answer

The administrator must create a custom junction object with Master-Detail relationships to both the Patient and Specialist objects, and then create Roll-Up Summary fields on the Specialist object to calculate aggregate values from the junction object records.
To connect two objects in a many-to-many relationship, a custom junction object with two Master-Detail relationships is required. Master-Detail relationships natively enforce cascading record deletion when a parent record is deleted and enable the creation of Roll-Up Summary fields on the master object to calculate aggregate data from child records.

Step-by-Step Solution

1
Analyze data model requirements for many-to-many structure and deletion behavior.
Determined that a junction object with two Master-Detail relationship fields is required to connect Patient and Specialist objects and enforce automatic deletion of junction records.
Master-Detail relationships enable cascading deletion, ensuring child records are automatically removed when either parent record is deleted.
2
Evaluate field capability for aggregate calculations on the master object.
Confirmed that Roll-Up Summary fields can be created on the master object (Specialist) referencing the child junction object.
Roll-Up Summary fields require a Master-Detail relationship and cannot be constructed over standard Lookup relationships.

Key Concept

Many-to-Many Relationships and Roll-Up Summary Capabilities
Question 771Question

A system administrator at a software enterprise needs to temporarily block system access for a technical lead who is taking a four-month leave of absence. The user is currently assigned as the default case owner in active automated assignment rules and owns pending scheduled workflows. The company security policy mandates an immediate block of login capabilities without disrupting background operations or reassigning rule dependencies. Which administrative action should the administrator perform to satisfy these requirements?

Show answer & explanation

Answer: Freeze the user account from the user detail page to prevent login while preserving account references in background operations.

Answer

Freezing the user account from the user detail page prevents login access immediately without affecting automated processes or assignment rules where the user is listed as an owner.
Freezing a user account immediately blocks the user from logging in to Salesforce while keeping the user record active in the system. This prevents disruption to automated processes, workflow rules, or assignment rules where the user is designated as the default owner.

Step-by-Step Solution

1
Identify system dependencies and background process ownership.
Recognize that the user is configured as a default owner in active assignment rules and scheduled workflows.
Deactivating a user assigned to active automated processes causes system validation issues or workflow failures.
2
Evaluate the difference between user freezing and user deactivation.
Determine that freezing stops user authentication immediately without releasing licenses or unlinking ownership references.
Freezing is designed specifically for temporary login prevention when account dependencies exist.
3
Select the appropriate user management action.
Choose to freeze the user account.
This satisfies security requirements while preserving background operational integrity.

Key Concept

User Freezing vs. User Deactivation
Question 772Question

Universal Containers uses a custom object to track executive compliance reviews. To streamline the user experience, a conditional visibility filter was configured on a Dynamic Forms field section containing executive compensation details so that the section is hidden when a review status is set to 'Draft'. Despite this filter working as intended on the record page, compliance assistants report that they can still view the compensation values when running custom reports on these records. Which explanation accounts for why these users can see the field data in reports?

Show answer & explanation

Answer: Dynamic Forms visibility rules only affect the display of fields on the Lightning record page and do not restrict data visibility in reports or through API access.

Answer

Dynamic Forms component visibility rules control UI rendering on Lightning record pages only; they do not alter Field-Level Security or prevent users with field read access from viewing field data in reports, list views, or API calls.
Dynamic Forms component visibility rules are presentation-layer filters configured in Lightning App Builder. They dictate whether fields, field sections, or components display on the record detail page. However, they do not restrict data access outside of the record page layout. If users have Field-Level Security (FLS) Read access to a field, that field remains accessible in custom reports, dashboards, list views, global search, and API queries regardless of page-level visibility filters.

Step-by-Step Solution

1
Analyze the scope of Dynamic Forms visibility filters.
Dynamic Forms visibility filters determine whether components, sections, or fields are rendered on a Lightning record page layout based on defined filter criteria.
Understanding the boundary between UI display rules and data security layers is essential.
2
Compare Dynamic Forms visibility against data access mechanisms like Field-Level Security (FLS) and Reporting.
Hiding a field using Dynamic Forms does not remove Field-Level Security (FLS) read permissions. If a user has read access via FLS, the field remains accessible in reports, list views, exports, and APIs.
True data protection requires configuring FLS or restriction rules, not relying on page layout component visibility.
3
Evaluate the reported scenario where users see field data in custom reports.
The users retain FLS read access, which allows custom reports to query and display the field values despite the field being hidden on the record detail page.
Reports bypass Lightning App Builder page layout rules and query object data directly based on object permissions and FLS.

Key Concept

Decoupling of Dynamic Forms UI Component Visibility from Field-Level Security (FLS) and Data Access
Estimated Time:2m 0s
Question 773Question

BrightSky Utilities needs to set up tailored case management workflows for Billing Inquiries, Technical Escalations, and Field Service Requests. Match each Salesforce administrative component on the left to its corresponding configuration role on the right.

Click a left item, then click its matching right item

Items

Support Process
Case Record Type
Page Layout
Master Case Status Field

Matches

Show answer & explanation

Answer

Support Process matches the subset of Case Status picklist values. Case Record Type links the Support Process to a Page Layout and Profile. Page Layout organizes fields and sections on the detail page. Master Case Status Field stores the complete list of all status values defined across the organization.
Each component serves a specific dependency layer in Salesforce Case management. The Master Case Status field holds all status values org-wide. A Support Process filters these values down to a specific lifecycle. The Case Record Type then pairs that Support Process with a Page Layout and assigns it to user profiles, while the Page Layout governs UI structure.

Step-by-Step Solution

1
Identify the function of a Support Process
Recognize that a Support Process filters the Master Case Status picklist into a customized lifecycle stage subset.
Support Processes must be created first to define case lifecycle stages before associating them with Record Types.
2
Identify the function of a Case Record Type
Connect the Record Type to its role of tying together a Support Process, a Page Layout, and user profiles.
Record types require an existing Support Process when created on the Case object.
3
Identify the function of Page Layouts and the Master Case Status Field
Map Page Layouts to visual field arrangements and Master Case Status to the organization-wide list of status values.
Page layouts handle UI arrangement, while master picklist fields store all potential values.

Key Concept

Prerequisite order and operational relationships between Support Processes, Case Record Types, Page Layouts, and Case Status picklist values.
Estimated Time:1m 30s
Question 774Question

When an opportunity owner adds a team member to an Opportunity Team in Salesforce, which access levels can be directly assigned to that team member for the opportunity record?

Show answer & explanation

Answer: Read Only or Read/Write

Answer

Read Only or Read/Write access can be directly assigned to an Opportunity Team member for the opportunity record.
When adding members to an Opportunity Team, Salesforce allows the user to specify record-level access to the opportunity as either Read Only or Read/Write.

Step-by-Step Solution

1
Identify the purpose of Opportunity Teams
Opportunity Teams facilitate team selling by granting extra visibility and collaboration rights to team members.
Team members require record-level sharing access specified by the record owner or admin.
2
Determine the available access levels on Opportunity Team Member records
The available opportunity access settings for team members are Read Only and Read/Write.
Salesforce allows record owners to choose between view-only access or edit access for each team member added.

Key Concept

Opportunity Team Record Sharing Access
Question 775Question

An organization is deploying distinct business processes for service agreement management on the Contract object across different regional groups. All users belong to a single shared user profile. The administrator has created two Record Types: 'NA Service Contract' and 'EMEA Service Contract'. Which two actions must the administrator perform to ensure users see only the relevant picklist options for Contract Status and the correct field layout when working with records? (Choose 2 answers.)

Select all that apply

Show answer & explanation

Answer: Configure Page Layout Assignment to map the appropriate page layout to each Record Type for the users' profile.; Edit the 'Picklists Available for Editing' settings on each Record Type to specify the allowed values for the Contract Status field.

Answer

The administrator must configure Page Layout Assignment for the profile and record type combinations, and edit the Picklists Available for Editing section on each Record Type to define the valid status values.
To display customized field layouts and specific picklist options based on business processes, administrators must map the page layouts for each Record Type and Profile combination in Page Layout Assignment, and edit the 'Picklists Available for Editing' section on each Record Type to filter available values for picklist fields.

Step-by-Step Solution

1
Assign Page Layouts to Profiles and Record Types
Each Record Type is paired with its specific Page Layout for the shared user profile in the Page Layout Assignment matrix.
Salesforce uses Profile + Record Type mapping to determine which page layout a user sees.
2
Configure Available Picklist Values per Record Type
The Contract Status picklist is edited on each Record Type detail page to include only valid regional status options.
Record Types allow admins to filter picklist values independently without requiring multiple profiles or custom code.

Key Concept

Page Layout and Record Type Assignment
Question 776Question

A Salesforce Administrator at a media publishing company needs to calculate and display the total number of physical copies printed across all production batches on the parent custom object record, Book_Title__c. The production batches are stored in a child custom object named Print_Run__c, which currently links to Book_Title__c using a Lookup relationship. Which two configuration steps must the administrator perform to achieve this requirement declaratively using a Roll-Up Summary field?

Select all that apply

Show answer & explanation

Answer: Convert the existing Lookup relationship field on Print_Run__c to a Master-Detail relationship.; Create a custom Roll-Up Summary field on Book_Title__c that uses the SUM aggregate function on the Quantity__c field of Print_Run__c.

Answer

The administrator must convert the existing Lookup relationship on Print_Run__c to a Master-Detail relationship and then create a Roll-Up Summary field on Book_Title__c using the SUM aggregate function on the child Quantity__c field.
Native Roll-Up Summary fields are only available on the parent (master) object in a Master-Detail relationship. Converting the existing Lookup relationship field on the child object (Print_Run__c) to a Master-Detail relationship enables the creation of a Roll-Up Summary field on the parent object (Book_Title__c). Once converted, creating a Roll-Up Summary field that uses the SUM aggregate function on the child object's Quantity__c field will automatically calculate the total.

Step-by-Step Solution

1
Evaluate relationship requirements for Roll-Up Summary fields
Identify that Roll-Up Summary fields are exclusively available on the master object of a Master-Detail relationship.
Lookup relationships do not support native roll-up summary field functionality.
2
Convert the relationship type
Change the lookup field on Print_Run__c to a Master-Detail relationship after ensuring all child records have a populated parent lookup value.
Master-Detail relationship is required to unlock roll-up capabilities on the parent object.
3
Create the Roll-Up Summary field
Add a new Roll-Up Summary field on Book_Title__c, select Print_Run__c as the summarized object, choose SUM as the aggregate operation, and select Quantity__c as the field to aggregate.
This declaratively calculates and displays the sum of printed quantities across all child records on the parent record.

Key Concept

Roll-Up Summary Field Relationship Requirements and Operations
Question 777Question

Solaris Energy tracks vendor performance using a custom object named Vendor_Evaluation__c. The Organization-Wide Default (OWD) for Vendor_Evaluation__c is set to Private. The VP of Procurement requires that all evaluations owned by members of the Procurement Team role be shared with Read access to users in the Compliance Audit role, which sits in a separate hierarchy branch. Additionally, Procurement Officers must automatically receive Read access to evaluations where the evaluation's Region field matches their designated geographical territory, regardless of record ownership. Which TWO administrative actions should be configured to fulfill these requirements? (Select 2)

Select all that apply

Show answer & explanation

Answer: Create an owner-based sharing rule on Vendor_Evaluation__c sharing records owned by the Procurement Team role with the Compliance Audit role.; Create a criteria-based sharing rule on Vendor_Evaluation__c evaluating the Region field to share records with the corresponding regional roles.

Answer

To meet both access requirements, the administrator must create an owner-based sharing rule to share records owned by the Procurement Team role with the Compliance Audit role, and a criteria-based sharing rule based on the Region field to share records with regional roles.
The solution requires extending read access beyond Private Organization-Wide Defaults (OWD) for two separate scenarios. First, an owner-based sharing rule selectively shares records owned by members of the Procurement Team role with users assigned to the Compliance Audit role across hierarchy branches. Second, a criteria-based sharing rule uses the evaluation's Region field to grant targeted Read access to regional roles regardless of owner.

Step-by-Step Solution

1
Analyze the baseline access setting and the first sharing requirement.
The Private OWD restricts access so only owners and users above them in the hierarchy can view records. Sharing records between separate hierarchy branches (Procurement Team to Compliance Audit) based on record ownership requires an owner-based sharing rule.
Owner-based sharing rules grant record access across non-linear role hierarchy structures based on who owns the records.
2
Analyze the second sharing requirement regarding geographical territories.
Sharing evaluations based on the Region field value regardless of owner requires a criteria-based sharing rule.
Criteria-based sharing rules evaluate field criteria rather than record ownership to grant Read or Read/Write permissions to designated roles or public groups.

Key Concept

Role Hierarchy and Sharing Rules
Question 778Question

An administrator is setting up a dedicated internal IT help desk team alongside the existing customer support department. The IT team requires a tailored case lifecycle with specific status values such as 'Triage' and 'Pending Vendor'. Which two configuration steps must the administrator complete to implement this requirement? (Select 2 answers)

Select all that apply

Show answer & explanation

Answer: Create a new Support Process that includes the specific Case Status picklist values needed for IT cases.; Create a new Case Record Type and associate it with the custom IT Support Process.

Answer

To establish a distinct case lifecycle with custom status values, the administrator must create a Support Process containing the required Case Status values and then link that Support Process to a newly created Case Record Type.
On the Case object, status picklist options are managed through Support Processes. To present a customized list of status values for IT cases, an administrator must first build a Support Process containing those values and then assign that Support Process when creating the Case Record Type.

Step-by-Step Solution

1
Create the Support Process
A designated Support Process is defined selecting the specific status picklist values for IT cases.
On the Case object, status field picklists are governed specifically by Support Processes.
2
Create and link the Case Record Type
A Case Record Type is configured and assigned the newly created Support Process.
Record types require an assigned Support Process to enforce the custom status lifecycle.

Key Concept

Prerequisite relationship between Support Processes and Case Record Types
Question 779Question

A Salesforce Administrator at Crestline Industrial Equipment is setting up a newly created product, 'Titan Heavy Drill', to be sold to enterprise clients using a custom price book named 'Enterprise Machinery Pricing'. Which TWO configuration steps must the administrator perform before sales representatives can select and add the 'Titan Heavy Drill' to an Opportunity using the 'Enterprise Machinery Pricing' custom price book? (Select 2 options)

Select all that apply

Show answer & explanation

Answer: Create an active entry for the Titan Heavy Drill in the Standard Price Book with a standard price.; Add the Titan Heavy Drill as an active line item entry in the 'Enterprise Machinery Pricing' custom price book.

Answer

The administrator must create an active entry for the product in the Standard Price Book and add the product as an active price entry in the target custom price book.
To make a product selectable on an opportunity using a custom price book, two essential requirements must be fulfilled: 1) The product must have an active price entry in the Standard Price Book, and 2) The product must be added to the desired custom price book with an active price book entry. Once both entries exist and are marked active, sales reps can add the product to opportunities associated with that price book.

Step-by-Step Solution

1
Create standard price entry
The product receives an active standard price entry in the Standard Price Book.
Salesforce mandates that a product must exist with an active standard price in the Standard Price Book before it can be included in any custom price books.
2
Add product entry to custom price book
The product becomes available with a list price under the custom price book.
Sales reps select products based on the Opportunity's assigned price book, which requires an active entry in that specific custom price book.

Key Concept

Standard and Custom Price Book Entry Prerequisites
Question 780Question

Match each Salesforce Opportunity Team or Account Team sharing scenario on the left with its correct record access behavior or system capability on the right.

Click a left item, then click its matching right item

Items

Adding a user to an Opportunity Team with 'Read/Write' access on an opportunity record when Organization-Wide Defaults for Opportunities are 'Private'.
Configuring a user's 'Default Opportunity Team' in personal settings and enabling automatic addition.
Adding an Account Team member with 'Opportunity Access' specified as 'Read-Only'.
Updating an existing Opportunity Team member's role access level directly on a specific opportunity record.

Matches

Show answer & explanation

Answer

1. Adding a user to an Opportunity Team with 'Read/Write' access on a Private OWD opportunity corresponds to granting record-level sharing access to that specific opportunity without changing global OWD or object permissions.
2. Configuring a Default Opportunity Team with automatic addition corresponds to automatically adding pre-configured team members when creating or receiving opportunity records.
3. Adding an Account Team member with 'Read-Only' Opportunity Access corresponds to provisioning Read-Only access across all opportunities associated with that account.
4. Updating a team member's access on a specific opportunity corresponds to modifying the underlying record sharing table entry for that single record.
Each match correctly aligns the Salesforce team sharing feature with its underlying mechanism:
- Opportunity Team membership grants explicit record-level access without changing object permissions or OWD.
- Default Opportunity Teams automate team assignment upon record creation.
- Account Team opportunity sharing settings propagate access to all child opportunities of the account.
- Direct edits to an Opportunity Team member's access alter the share row for that individual opportunity.

Step-by-Step Solution

1
Analyze Opportunity Team record sharing behavior under Private OWD.
Confirm that Opportunity Team membership creates a sharing record that opens up record access on the specific opportunity.
Opportunity Teams operate on the record-sharing layer to grant access to users who need to collaborate on a deal.
2
Evaluate the function of Default Opportunity Teams in User Settings.
Identify that default teams automatically append members to newly created or assigned opportunities.
Default Opportunity Teams streamline administration by removing the need to manually add frequent collaborators to every new deal.
3
Determine how Account Team member settings propagate to related opportunities.
Confirm that specifying Opportunity Access on an Account Team member grants that level of access to all opportunities under the parent Account.
Account Teams allow centralized sharing management across related child records like opportunities and cases.
4
Examine the scope of modifying access levels on an individual opportunity team record.
Recognize that editing member access directly on an opportunity record updates only that individual record's share entry.
Record-level team edits do not affect other records or default settings.

Key Concept

Opportunity Teams and Team Selling Access
Estimated Time:2m 0s
PreviousPage 39 / 90Next
All practice questions — Salesforce Certified Administrator | Examkin