Examkin

Tüm alıştırma soruları

1784 soru

Tüm türler1,784Çoktan seçmeli918Çoklu seçim587Eşleştirme142Sıralama137
Soru 681Soru →

A System Administrator at Horizon Healthcare is configuring access control for a custom object named Clinical_Trial__c. The Organization-Wide Default (OWD) for Clinical_Trial__c is set to Private.

Management has established the following requirements:
1. Managers and executives positioned above record owners in the role hierarchy must automatically inherit Read and Edit permissions for records owned by their subordinates.
2. Members of the Regulatory Compliance team, who are assigned to the 'Compliance Analyst' role, must be granted Read-Only access to any Clinical_Trial__c record where the Risk_Level__c field is set to 'High', regardless of who owns the record.

Which combination of Salesforce security configurations will meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Ensure 'Grant Access Using Hierarchies' remains enabled for Clinical_Trial__c, and create a criteria-based sharing rule sharing records where Risk_Level__c equals 'High' with the 'Compliance Analyst' role.

Cevap

Enable 'Grant Access Using Hierarchies' for Clinical_Trial__c and create a criteria-based sharing rule that shares records where Risk_Level__c equals 'High' with the 'Compliance Analyst' role.
The correct option combines Salesforce's native role hierarchy behavior with targeted criteria-based sharing. Enabling 'Grant Access Using Hierarchies' on the custom object automatically extends record access upward to managers and executives. A criteria-based sharing rule evaluates the field condition (Risk_Level__c = 'High') and grants access to the designated role without granting access to low or medium risk records.

Adım Adım Çözüm

1
Evaluate role hierarchy access inheritance requirement
Confirming 'Grant Access Using Hierarchies' is enabled on the custom object ensures users higher in the role hierarchy inherit the record permissions of their subordinates automatically.
For standard objects, hierarchy access is mandatory, but for custom objects, it can be toggled. Keeping it checked satisfies requirement 1.
2
Evaluate conditional access requirement based on record field criteria
Create a criteria-based sharing rule targeting Clinical_Trial__c records where Risk_Level__c = 'High' and share Read-Only access with the 'Compliance Analyst' role.
Criteria-based sharing rules allow access to be granted to specified user groups based on field values without depending on record ownership.

Anahtar Kavram

Role Hierarchy Access and Criteria-Based Sharing Rules
Soru 682Soru →

A Salesforce administrator at a digital publishing company needs to create a field on the Account object that displays the total calculated value of all related subscription records. The Subscription custom object is currently connected to the Account object through a Lookup relationship. However, when trying to create a new custom field on Account, the Roll-Up Summary field type is grayed out and unavailable. What is the cause of this limitation, and how can the administrator fulfill the business requirement?

Cevabı ve açıklamayı göster

Cevap: Roll-Up Summary fields are only natively supported on the master object in a Master-Detail relationship, so the relationship must be converted to Master-Detail or automated using Flow.

Cevap

Roll-Up Summary fields are only natively supported on the master object in a Master-Detail relationship, so the relationship must be converted to Master-Detail or automated using Flow.
In Salesforce, native Roll-Up Summary fields are only supported on parent objects involved in a Master-Detail relationship. Because Account and Subscription are linked via a Lookup relationship, the option to create a Roll-Up Summary field is disabled. To resolve this, an administrator must either convert the Lookup relationship to a Master-Detail relationship or use an automated solution such as Flow or Apex to calculate and update the value on the Account record.

Adım Adım Çözüm

1
Identify the relationship type between Account and Subscription
The objects are connected via a standard Lookup relationship.
Salesforce declarative capabilities differ significantly between Lookup and Master-Detail relationships.
2
Evaluate standard Roll-Up Summary field requirements
Roll-Up Summary fields require the parent object to be the Master in a Master-Detail relationship.
Lookup relationships do not enforce strict parent-child data dependency required for standard declarative roll-ups.
3
Determine appropriate administrative resolution
Convert the Lookup relationship to Master-Detail (ensuring all child records have parent values) or create a record-triggered Flow to aggregate values.
Either approach enables the parent Account object to reflect cumulative metrics from child Subscription records.

Anahtar Kavram

Roll-Up Summary Field Restrictions and Relationship Data Types
Soru 683Soru →

A system administrator is onboarding new sales representatives who require specialized access to specific records based on their sub-team functions. Simultaneously, an existing account executive has unexpectedly left the company while assigned as the default workflow user and an active approver on several high-value pending quotes. Which TWO actions should the administrator take to address user provisioning and account maintenance in this scenario?

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Freeze the departed account executive's user account immediately to block system access without disrupting existing automated processes.; Assign a standard base profile to all new sales representatives and use permission sets to grant additional specialized record access.

Cevap

The administrator should freeze the departed account executive's account immediately to temporarily block login access while maintaining workflow integrity, and assign a standard base profile to new representatives while granting specialized access using permission sets.
Freezing a user account temporarily blocks login access immediately without causing runtime failures in automated workflows or active approval hierarchies where the user is assigned. Additionally, pairing a baseline profile with targeted permission sets follows Salesforce security best practices for provisioning additive user permissions.

Adım Adım Çözüm

1
Evaluate access blocking for a user tied to automated system dependencies.
Identify that freezing the account immediately prevents login without causing errors in processes where the user is referenced as a workflow user or approver.
Deactivating a user who is currently configured as a default workflow user or active approver can break active workflows or prevent deactivation altogether until references are cleared.
2
Determine the optimal permission assignment strategy for onboarding users requiring specialized functional access.
Assign a core profile for baseline permissions and leverage permission sets for role-specific additive access.
Profiles should define baseline access, while permission sets and permission set groups should handle flexible, additive permissions across subsets of users.

Anahtar Kavram

User Provisioning and Freezing vs Deactivating Users
Soru 684Soru →

A Salesforce Administrator wants to migrate an existing custom object record page to Dynamic Forms using Lightning App Builder. What is the correct chronological sequence of steps to complete this migration?

Öğeleri doğru sıraya koymak için sürükleyin

Cevabı ve açıklamayı göster

Cevap

The correct sequence to upgrade a record page to Dynamic Forms is: 1) Open the record page in Lightning App Builder, 2) Select the Record Detail component, 3) Click Upgrade Now in the properties panel, 4) Select the source page layout, and 5) Save and activate the page.
To migrate an existing record page to Dynamic Forms, an administrator opens the page in Lightning App Builder, selects the Record Detail component, clicks Upgrade Now in the component properties panel, selects the desired source page layout to extract fields, and finally saves and activates the page.

Adım Adım Çözüm

1
Open the record page in Lightning App Builder.
The Lightning App Builder canvas and component tree load.
Page customization and Dynamic Forms migration are performed inside Lightning App Builder.
2
Select the Record Detail component on the canvas.
The Record Detail properties panel opens on the right side.
The migration feature is embedded within the properties panel of the Record Detail component.
3
Click the Upgrade Now button.
The Dynamic Forms migration wizard opens.
This initiates the wizard to convert monolithic page layouts into individual Field and Field Section components.
4
Select the source page layout.
Fields and sections from the chosen page layout are extracted directly onto the App Builder canvas.
The wizard uses the selected layout as the starting template for placing fields.
5
Save and activate the record page.
The Dynamic Forms page layout is saved and deployed to users according to assigned profiles or org defaults.
App Builder modifications are draft state until saved and activated.

Anahtar Kavram

Migrating standard page layouts to Dynamic Forms in Lightning App Builder using the Upgrade Now wizard.
Soru 685Soru →

A Salesforce Administrator at Zenith Telecom is setting up a new enterprise internet subscription offering. The administrator needs to make this new product available for sales representatives to add to opportunities using a specialized custom price book. Arrange the steps in the correct order to complete this configuration.

Öğeleri doğru sıraya koymak için sürükleyin

Cevabı ve açıklamayı göster

Cevap

The correct order of steps is: 1) Create the new Product record for the enterprise internet subscription, 2) Create a Standard Price Book entry by assigning a standard price to the product, 3) Add the product to the specialized Custom Price Book with a custom list price, and 4) Add the enterprise internet subscription as an Opportunity Line Item on a customer opportunity.
In Salesforce, configuring product pricing follows a mandatory sequence: first, create the Product record; second, establish a Standard Price Book entry (which acts as a prerequisite); third, associate the product with custom price books; fourth, select the product on opportunities via Opportunity Line Items.

Adım Adım Çözüm

1
Create the Product record
Product is created in the system catalog.
You must create the parent Product record before establishing any price book entries.
2
Create a Standard Price Book entry
Standard price is established for the product.
Salesforce architecture mandates that a product must have an active entry in the Standard Price Book before it can be added to custom price books.
3
Add the product to the Custom Price Book
Product is available in the Custom Price Book with specified custom pricing.
Custom price books allow negotiated or tier-specific pricing built on top of existing standard price definitions.
4
Add the product as an Opportunity Line Item
Opportunity displays the line item with custom pricing.
Products in an active custom price book can be selected when building opportunities.

Anahtar Kavram

Price Book Entry Dependency and Order of Operations
Soru 686Soru →

Match each Salesforce administrative action regarding Page Layouts and Record Types with its correct configuration purpose.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

Setting default Record Types for a user group
Modifying available values in a custom picklist field per Record Type
Organizing fields, sections, and related lists on a record detail page

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Setting default Record Types maps to Profile Record Type Settings; Modifying available values in a custom picklist field per Record Type maps to Record Type Picklists for Editing section; Organizing fields, sections, and related lists maps to Page Layout Editor.
Each administrative task corresponds directly to its specific setup area in Salesforce: default record type selection is assigned in Profile settings, picklist value filtering per record type is configured in the Record Type setup, and page content arrangement (fields and related lists) is managed via the Page Layout Editor.

Adım Adım Çözüm

1
Identify the setup area responsible for user default record type assignments.
Default record types are designated at the Profile level in Record Type Settings.
Profiles determine which record types are visible and selected by default when a user creates a new record.
2
Identify where picklist values are restricted based on record classification.
Picklist values are customized per Record Type within Object Manager.
Each record type allows administrators to specify a subset of active picklist values for custom or standard picklist fields.
3
Identify the tool used to design record structure and field placement.
Page Layout Editor controls the visual structure of detail pages.
Page Layouts define the organization of fields, sections, custom links, and related lists on record pages.

Anahtar Kavram

Page Layouts and Record Types Assignment
Soru 687Soru →

A System Administrator at Universal Containers needs to enable Sales Operations representatives working on Account records in Lightning Experience to complete two distinct tasks without navigating away from the page:
1. Rapidly create a child Case record pre-populated with specific parent Account field values (such as Account Owner and Account Type) and a default Priority set to 'High'.
2. Launch an interactive Screen Flow that calculates customer credit risk scores using the current Account record context.

Which TWO configuration steps should the System Administrator take to fulfill these requirements? Select 2 answers.

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Create an Object-Specific Create Record Quick Action on the Account object targeting the Case object, configure Predefined Field Values for the target fields, and add the action to the Account page layout or Dynamic Actions.; Create an Object-Specific Flow Quick Action on the Account object referencing the credit score Screen Flow, and add the action to the Account Lightning page action bar.

Cevap

The correct configuration requires creating an Object-Specific Create Record Quick Action on Account with Predefined Field Values for Case creation, and creating an Object-Specific Flow Quick Action on Account to launch the Screen Flow while passing record context.
To create a child record pre-populated with parent record data, an Object-Specific Create Record Quick Action must be created on the parent object (Account) targeting the child object (Case). This allows administrators to set Predefined Field Values using formulas (such as Account.OwnerId). To execute a Screen Flow while maintaining record context, an Object-Specific Quick Action calling the Flow must be configured and placed on the action bar.

Adım Adım Çözüm

1
Evaluate record creation requirements with field defaults from the parent record.
Identify that Object-Specific Quick Actions on Account targeting Case support Predefined Field Values derived from the source Account record.
Global Quick Actions do not have access to the underlying parent record context, whereas Object-Specific Quick Actions retain relationship context.
2
Evaluate Screen Flow invocation requirements from a Lightning record page.
Identify that an Object-Specific Quick Action of action type 'Flow' on Account can launch a Screen Flow directly.
Object-Specific Flow actions seamlessly pass the record's ID into the flow's recordId variable without requiring page redirects.
3
Verify Lightning Experience compatibility and component placement.
Confirm that Object-Specific Quick Actions are fully supported in Lightning Experience dynamic actions and publisher layouts, while JavaScript buttons are unsupported.
JavaScript custom buttons are legacy features restricted to Salesforce Classic.

Anahtar Kavram

Object-Specific Quick Actions vs Global Quick Actions and Custom Buttons in Lightning Experience
Tahmini Süre:2m 0s
Soru 688Soru →

An administrator at Vertex Heavy Machinery creates a new active Product record for an industrial equipment component named 'TitanDrill X1'. The administrator also creates an active custom price book titled 'EMEA Enterprise Price Book'. When sales representatives in the EMEA region attempt to add 'TitanDrill X1' to an opportunity using the 'EMEA Enterprise Price Book', the product does not appear in the search results. Which action must the administrator take to make the product available on opportunities?

Cevabı ve açıklamayı göster

Cevap: Create and activate a standard price entry for the product in the Standard Price Book.

Cevap

The administrator must create and activate a standard price entry for the product in the Standard Price Book.
In Salesforce Core Administration, a product cannot be added to any custom price book—nor can it be selected on opportunity line items—until an active price entry exists for that product in the Standard Price Book. Creating and activating the standard price entry satisfies this architecture prerequisite.

Adım Adım Çözüm

1
Identify the prerequisite for custom price book entries in Salesforce product management.
Recognize that Salesforce requires every active product to have an active entry in the Standard Price Book before custom price book entries can be created or utilized.
Standard price entries establish the base currency pricing foundation across the organization.
2
Evaluate the current configuration state of 'TitanDrill X1'.
The product record and custom price book are both active, but no standard price entry was created for the product.
Without a standard price entry, the product cannot be associated with or selected from any custom price book on opportunity line items.
3
Determine the necessary administrative resolution.
Add a standard price entry to 'TitanDrill X1' within the Standard Price Book and mark the entry active.
Creating this entry satisfies the prerequisite, enabling the product to be selected in the custom price book and added to opportunities.

Anahtar Kavram

Standard Price Book Entry Prerequisite for Custom Price Books
Soru 689Soru →

A Salesforce administrator at a maritime freight logistics provider is configuring lead conversion settings. A custom picklist field on the Lead object, Shipping_Preference__c, is mapped to a custom picklist field on the Account object, Preferred_Service__c, using Lead Custom Field Mapping. During testing, sales representatives convert qualified leads, but the selected value in Shipping_Preference__c is consistently blank on the newly created Account record. Further investigation shows that the target field exists on the Account page layout, but the values are not visible under the Account record type assigned to the converting sales representative. Which administrative action will resolve this issue and ensure the picklist value populates correctly upon conversion?

Cevabı ve açıklamayı göster

Cevap: Edit the selected Account record type configuration to include the missing picklist values for the Preferred_Service__c field.

Cevap

Edit the selected Account record type configuration to include the missing picklist values for the target picklist field.
The correct action is to update the target Account record type settings to ensure the required picklist values are enabled for the custom field. During lead conversion, mapped picklist values will only populate on the destination record if those values are allowed by the record type assigned to the newly created record.

Adım Adım Çözüm

1
Identify the root cause of missing picklist data during lead conversion.
Lead custom field mapping requires both valid field-level mapping and active picklist value availability on the target record type.
If a mapped picklist value is restricted or disabled on the record type assigned to the newly created Account, Salesforce suppresses the value.
2
Navigate to Object Manager > Account > Record Types and select the record type assigned during conversion.
The picklist configuration for Preferred_Service__c is opened.
Record type settings govern which picklist values are available for selection and population on records using that record type.
3
Add the required values to the Selected Values list for the picklist field and save.
The target field now accepts and displays the mapped values upon lead conversion.
Enabling the picklist values at the record type level allows Salesforce to write the converted lead picklist data onto the target Account record.

Anahtar Kavram

Lead Conversion Field Mapping and Record Type Picklist Value Availability
Soru 690Soru →

Vanguard Global Tech needs to grant regional helpdesk supervisors administrative permissions over user accounts strictly within the 'APAC Support' role hierarchy without providing full System Administrator access. The Salesforce administrator creates a Delegated Administration group for these supervisors.

Which two administrative capabilities can be granted to the helpdesk supervisors through this Delegated Administration group? (Select 2 options)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Unlocking user accounts and resetting passwords for users within the specified role hierarchy; Assigning specified permission sets to users within the delegated user scope

Cevap

Delegated administrators can unlock accounts, reset passwords, and assign pre-approved permission sets to users within their assigned roles and subordinate roles.
Delegated Administration allows administrators to grant specific management rights over users in assigned roles. Valid delegated tasks include unlocking accounts, resetting passwords, editing specified user fields, assigning specified profiles, and assigning pre-approved permission sets.

Adım Adım Çözüm

1
Analyze the capabilities permitted within Salesforce Delegated Administration groups.
Delegated administration allows specific non-admin users to manage users in specified roles (unlocking, resetting passwords, editing fields) and assign specified permission sets.
Delegated administration provides targeted user management scope without exposing full system administrator rights.
2
Evaluate limitations of delegated administration regarding profiles and user status operations.
Delegated admins cannot edit or create profile definitions, nor can they bypass standard deactivation constraints for users tied to default system references.
Profile modification rights are restricted to prevent unauthorized privilege escalation, and deactivation constraints protect system automation integrity.

Anahtar Kavram

Delegated Administration Scope and Privileges
Soru 691Soru →

A Salesforce Administrator at a commercial catering company needs to calculate the total weight of ingredients directly on the custom parent object, Catering_Order__c. The individual ingredient quantities are stored in records of a custom child object, Order_Component__c. Currently, Order_Component__c is linked to Catering_Order__c through a Lookup relationship. When attempting to create a new field on Catering_Order__c to sum the component weights, the Roll-Up Summary field type is disabled. What action should the administrator take to allow the creation of the roll-up summary field on Catering_Order__c?

Cevabı ve açıklamayı göster

Cevap: Convert the Lookup relationship on Order_Component__c to a Master-Detail relationship after ensuring all child records have a populated lookup value.

Cevap

Convert the Lookup relationship on Order_Component__c to a Master-Detail relationship after ensuring all child records have a populated lookup value.
The correct action is to convert the Lookup relationship to a Master-Detail relationship. Roll-up summary fields can only be created on the master object in a Master-Detail relationship. Before converting an existing lookup field to a master-detail field, every existing detail record must have a populated value in that lookup field.

Adım Adım Çözüm

1
Identify the relationship requirement for Roll-Up Summary fields.
Determine that Roll-Up Summary fields are supported exclusively on the master object of a Master-Detail relationship.
Lookup relationships do not support native declarative roll-up summary fields on the parent object.
2
Evaluate prerequisite steps for converting a Lookup relationship to a Master-Detail relationship.
Ensure that every existing child record (Order_Component__c) has a value in the parent lookup field.
Master-Detail relationships enforce data integrity by requiring all detail records to have a valid reference to a master record.
3
Change the field type of the lookup field to Master-Detail and create the Roll-Up Summary field.
The Roll-Up Summary field type becomes selectable on Catering_Order__c to perform SUM operations on child records.
Converting the field establishes the required master-detail relationship structure.

Anahtar Kavram

Roll-Up Summary Field Relationship Requirements
Soru 692Soru →

A healthcare company needs to restrict visibility of a sensitive custom field, Patient_Social_Security_Number__c, on the Contact object. Currently, all internal staff share a single Custom Standard Staff profile that grants Read and Edit access to this field. Management requires that only two Compliance Officers retain access to view and edit this field, while all other staff lose access. What is the recommended, scalable security solution an administrator should implement to fulfill this requirement?

Cevabı ve açıklamayı göster

Cevap: Remove Read and Edit access for the field on the Custom Standard Staff profile, create a Permission Set granting Read and Edit access to the field, and assign the Permission Set to the two Compliance Officers.

Cevap

Remove Read and Edit access for the custom field on the profile level, create a Permission Set granting access to the field, and assign that Permission Set to the two compliance users.
In Salesforce security architecture, Field-Level Security (FLS) set at the profile level defines the baseline access for all users assigned to that profile. When only a small subset of users requires elevated access to a sensitive field, standard best practice dictates removing FLS access from the base profile and assigning a Permission Set with FLS access to the specific users.

Adım Adım Çözüm

1
Modify Field-Level Security (FLS) on the base profile
Uncheck Read Access and Edit Access for Patient_Social_Security_Number__c on the Custom Standard Staff profile so no users inherit access by default.
Security best practice requires setting the baseline access to the most restrictive level needed across the user population.
2
Create a new Permission Set
Define a Permission Set specifically for sensitive compliance field access and grant Read and Edit FLS permissions for Patient_Social_Security_Number__c on the Contact object.
Permission Sets provide additive permissions for specific user requirements without requiring dedicated profiles.
3
Assign the Permission Set to target users
Assign the created Permission Set to the two designated Compliance Officers.
This grants access selectively to only those users who require it while maintaining a clean, scalable profile architecture.

Anahtar Kavram

Profiles establish baseline access (most restrictive), while Permission Sets grant additive access to specific users.
Soru 693Soru →

A Salesforce administrator at a global logistics company is reviewing the standard lead conversion process with new sales operations team members. When a sales representative converts a qualified Lead record in Salesforce, which two standard records are created or populated by default? (Select two answers.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Account; Contact

Cevap

During lead conversion, Salesforce automatically creates or relates the converted lead to an Account record and a Contact record. Opportunity creation is optional.
In standard Salesforce lead conversion, information from the Lead record is split and mapped into an Account record (representing the organization) and a Contact record (representing the individual). An Opportunity record can also optionally be created.

Adım Adım Çözüm

1
Identify the standard target records generated during lead conversion in Salesforce.
Lead conversion maps single lead data into separate core CRM entities.
Standard lead conversion separates company demographic data into Account records and individual contact information into Contact records.
2
Evaluate the choices to distinguish standard data records from setup configuration objects.
Account and Contact records are created/matched by default. Price Books and Sales Processes are setup objects.
Price Books and Sales Processes are administrative structures and are not instantiated when converting individual leads.

Anahtar Kavram

Lead Conversion Data Model Mapping
Tahmini Süre:45s
Soru 694Soru →

Apex Global Energy is launching a new commercial solar battery system called 'VoltGrid X' for regional enterprise customers. The Salesforce Administrator must establish the complete product catalog hierarchy so sales representatives can add VoltGrid X to opportunities using a dedicated regional custom price book. What is the correct sequence of administrative steps required to achieve this configuration in Salesforce?

Öğeleri doğru sıraya koymak için sürükleyin

Cevabı ve açıklamayı göster

Cevap

The correct sequence begins with creating and activating the Product record, followed by establishing an active Standard Price Book Entry. Next, the administrator creates and activates the Custom Price Book, creates the Custom Price Book Entry linking the product to the custom price book with a list price, and finally adds the product as an Opportunity Line Item under that custom price book.
In Salesforce Core Administration, setting up products for custom price books follows a strict dependency chain. First, the Product record must be created and activated. Second, an active Standard Price Book Entry must be defined for each currency used, as Salesforce requires a standard price as a prerequisite for any custom pricing. Third, the Custom Price Book must be created and set to active. Fourth, the Custom Price Book Entry is created to assign a list price to the product within that specific custom price book. Finally, the price book can be selected on an Opportunity to add the product as an Opportunity Line Item.

Adım Adım Çözüm

1
Create and activate the Product record
The base Product object for 'VoltGrid X' exists in the catalog.
All price book entries and opportunity line items depend on an active base Product record.
2
Create an active Standard Price Book Entry
A standard price entry in the target currency is associated with the product.
Salesforce architecture mandates an active Standard Price Book entry before any custom price book entries can be created for a product.
3
Create and activate the Custom Price Book
The 'Enterprise Regional Solar' custom price book is created and enabled.
A custom price book must exist and be active to hold customized list prices for specific customer segments.
4
Create the Custom Price Book Entry
The product is assigned a custom list price within the new price book.
With both the prerequisite standard price entry and active custom price book present, the custom price book entry can be successfully saved.
5
Add the product as an Opportunity Line Item
Sales reps can quote and sell 'VoltGrid X' using the custom price book on opportunities.
Once the custom price book entry is active, the product can be selected on opportunities that use that price book.

Anahtar Kavram

Salesforce Product and Price Book setup dependency sequence
Tahmini Süre:3m 0s
Soru 695Soru →

Universal Containers is running a targeted multi-touch marketing campaign. The marketing director requires that prospect interactions are accurately tracked in campaign ROI metrics and performance reports after leads undergo conversion. Which two configurations or standard system behaviors must an administrator utilize to fulfill these requirements? (Choose two.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Define custom Campaign Member Status values and designate statuses that indicate engagement by selecting the Responded checkbox.; Rely on standard lead conversion behavior, which automatically transfers existing Campaign Member records from the Lead to the newly created Contact.

Cevap

The administrator must define custom Campaign Member Statuses with the 'Responded' checkbox selected for engagement values, and rely on standard lead conversion behavior where Campaign Member records automatically transfer from the Lead to the Contact.
Campaign metrics rely on Campaign Member Status settings having the 'Responded' checkbox selected to count interactions toward ROI. Additionally, Salesforce standard lead conversion logic automatically moves existing Campaign Member records attached to the Lead over to the newly generated Contact record, ensuring historical engagement is maintained.

Adım Adım Çözüm

1
Analyze Campaign Member Status requirements for response reporting.
Realize that campaign metrics like 'Value Responses' and 'Total Responses' rely specifically on Member Statuses marked with the 'Responded' flag.
Unflagged member statuses (e.g., 'Sent') do not count toward response metrics.
2
Evaluate Lead conversion behavior for campaign tracking.
Confirm that existing campaign memberships on a Lead automatically relocate to the resulting Contact record upon conversion.
Salesforce natively preserves campaign history during conversion without requiring custom field mapping setups.
3
Evaluate distractor options regarding field mapping and roll-up summaries.
Reject mapping Campaign Member fields in Lead Conversion mapping and reject roll-ups between Account and Lead.
Lead Conversion Field Mapping applies only to Lead object fields, and Roll-Up Summary fields require Master-Detail relationships.

Anahtar Kavram

Campaign Member Status response tracking and Campaign Member relocation during Lead conversion
Soru 696Soru →

Universal Containers uses a custom object named Equipment Maintenance to track service requests. The administrator has created two record types: Preventive and Breakdown. The administrator now needs to ensure that users with the Facilities Technician profile see only relevant picklist options on the Maintenance Priority field for Preventive records, and that the Preventive Maintenance Layout is displayed when these records are accessed.

Which two administrative actions must be completed to satisfy these requirements? (Choose 2 answers)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Edit the picklist values available for the Maintenance Priority field within the Preventive Record Type detail page.; Update the Page Layout Assignment matrix on the Equipment Maintenance object to map the Facilities Technician profile and Preventive Record Type to the Preventive Maintenance Layout.

Cevap

The correct actions are to edit the picklist values available for the Maintenance Priority field directly within the Preventive Record Type detail page, and to update the Page Layout Assignment matrix on the Equipment Maintenance object to map the Facilities Technician profile and Preventive Record Type to the Preventive Maintenance Layout.
To restrict picklist values for a specific record type, an administrator must edit the picklist options under that record type's detail page in Object Manager. Additionally, assigning page layouts requires modifying the Page Layout Assignment matrix, which pairs a user's Profile with a Record Type to determine the assigned layout.

Adım Adım Çözüm

1
Navigate to the Equipment Maintenance object in Object Manager and locate the Record Types section.
Access the setup interface for record-type-specific configurations.
Record types control picklist availability and page layout assignments.
2
Select the Preventive Record Type and edit the Maintenance Priority picklist to select allowed values.
Only selected picklist values are visible when users create or edit Preventive records.
Modifying picklist values per record type restricts field selection options.
3
Click Page Layout Assignment on the Equipment Maintenance object and edit the assignment grid.
The Facilities Technician profile combined with the Preventive Record Type is assigned to the Preventive Maintenance Layout.
Page layout assignment is determined by the matrix combination of user Profile and record Record Type.

Anahtar Kavram

Page Layouts and Record Types Assignment
Soru 697Soru →

A Salesforce Administrator at Horizon Fleet Solutions creates a custom price book named 'Government & Defense' to accommodate negotiated rates for fleet tracking hardware. While attempting to add the new 'GPS Tracker HD' product to this custom price book, the system throws an error and prevents the creation of the price entry. What is the most likely cause of this issue?

Cevabı ve açıklamayı göster

Cevap: The product does not have an active price entry in the Standard Price Book.

Cevap

The product must have an active price entry in the Standard Price Book before it can be added to any custom 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. If a standard price entry does not exist or is inactive, Salesforce will prevent adding the product to custom price books.

Adım Adım Çözüm

1
Identify the relationship requirements between Products, Standard Price Books, and Custom Price Books.
Recognize that Salesforce enforces a prerequisite standard price entry requirement for all custom price books.
The Standard Price Book serves as the master price repository for products.
2
Verify if the product has an active standard price entry created.
Determined that 'GPS Tracker HD' lacks an active standard price entry in the Standard Price Book.
Without an active standard price, Salesforce blocks adding the product to custom price books.
3
Create and activate the standard price entry for the product in the Standard Price Book.
The product can now successfully be added to the 'Government & Defense' custom price book.
The system prerequisite for custom price book entries is now satisfied.

Anahtar Kavram

Standard Price Book Entry Prerequisite
Tahmini Süre:1m 0s
Soru 698Soru →

An administrator is configuring a Lightning Record Page for a custom object named Vendor_Contract__c. The business requires a specialized executive summary component on the page to be visible only to users with the 'Procurement Manager' job role. Additionally, the administrator must ensure that sensitive financial fields on the page are completely inaccessible via API and reports to users without proper data access. Which set of actions meets these requirements while following Salesforce security best practices?

Cevabı ve açıklamayı göster

Cevap: Configure component visibility rules on the Lightning Record Page using the User > Role field for the executive summary component, and enforce Field-Level Security (FLS) settings on the profile or permission set for the financial fields.

Cevap

Configure component visibility rules on the Lightning Record Page using the User > Role field for the executive summary component, and enforce Field-Level Security (FLS) settings on the profile or permission set for the financial fields.
The correct response properly distinguishes between UI display logic and underlying data security. Component visibility rules in Lightning App Builder allow administrators to dynamically filter which components appear based on user record attributes (such as User > Role). Meanwhile, Field-Level Security (FLS) is mandatory for securing sensitive fields against unauthorized access across all access points, including reports, SOQL queries, and API endpoints.

Adım Adım Çözüm

1
Analyze UI component restriction requirements
Dynamic component visibility filter criteria on the Lightning App Builder page can conditionally show/hide components based on user attributes such as User > Role.
This selectively displays UI elements without creating redundant record pages.
2
Analyze data access and security requirements for sensitive fields
Field-Level Security (FLS) must be configured at the profile or permission set level to restrict Read/Edit access.
FLS ensures comprehensive data protection across the UI, reports, dashboards, search, and API integrations.
3
Evaluate combined architecture for compliance
Combining Lightning App Builder component visibility with Field-Level Security satisfies both UI customization and data privacy standards.
UI component visibility is for user experience control, while FLS is for true security enforcement.

Anahtar Kavram

Lightning App Builder Component Visibility vs Field-Level Security (FLS)
Tahmini Süre:2m 0s
Soru 699Soru →

An administrator at a logistics enterprise needs to temporarily block login access for an operations manager who is taking a three-month sabbatical. The user account is currently designated as the Default Web-to-Case Owner and is referenced in active lead assignment rules. Attempting to deactivate the user immediately triggers administrative errors due to these system dependencies. Which course of action should the administrator take to resolve this issue while maintaining system automation?

Cevabı ve açıklamayı göster

Cevap: Freeze the user account from the User detail page to prevent login access without affecting automated processes or record assignments.

Cevap

Freeze the user account from the User detail page to prevent login access without affecting automated processes or record assignments.
Freezing a user account prevents login access instantly while retaining the user ID in active automated workflows, default case ownership configurations, and assignment rules. This provides an immediate solution when deactivation is blocked by system dependencies.

Adım Adım Çözüm

1
Identify system constraints
Recognize that the user is configured as a Default Web-to-Case Owner and referenced in active assignment rules, preventing standard user deactivation.
Salesforce blocks user deactivation when the account is tied to critical default system processes or active workflow dependencies.
2
Evaluate available administrative operations
Select the Freeze action on the user's detail record.
Freezing stops user authentication immediately without unlinking the user from existing default configuration roles or triggering validation errors.

Anahtar Kavram

User Account Freezing vs. Deactivation
Soru 700Soru →

Nexus Logistics utilizes a custom object named Shipment_Audit__c with an Organization-Wide Default (OWD) set to Private. The 'Grant Access Using Hierarchies' setting is currently deselected for this object.

The Salesforce Administrator needs to meet the following record access requirements:
1. Regional Operations Managers must have Read access to Shipment Audit records owned by Logistics Coordinators below them in the role hierarchy, but ONLY when the Audit_Status__c field is set to 'Action Required'.
2. The Corporate Compliance team, located in a completely separate branch of the role hierarchy, must have Read/Write access to ALL Shipment Audit records, regardless of record owner or status.

Which TWO configuration steps must the administrator execute to fulfill these requirements? (Select 2 options.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Create a criteria-based sharing rule on Shipment_Audit__c sharing records where Audit_Status__c equals 'Action Required' with the Regional Operations Manager role.; Create an owner-based sharing rule on Shipment_Audit__c sharing records owned by All Internal Users with the Corporate Compliance role with Read/Write access.

Cevap

The administrator must create a criteria-based sharing rule on Shipment_Audit__c sharing records where Audit_Status__c equals 'Action Required' with the Regional Operations Manager role, and create an owner-based sharing rule sharing records owned by All Internal Users with the Corporate Compliance role with Read/Write access.
The criteria-based sharing rule correctly grants access only to records meeting the specific criteria ('Action Required') to the Regional Operations Manager role. The owner-based sharing rule shares all records owned by internal users with the Corporate Compliance role across hierarchy branches with Read/Write access.

Adım Adım Çözüm

1
Analyze the conditional access requirement for Regional Operations Managers.
Since access depends on a specific field value ('Action Required') rather than unconditional role-hierarchy inheritance, a criteria-based sharing rule targeting the Regional Operations Manager role is required.
Grant Access Using Hierarchies cannot filter records by field criteria.
2
Analyze the broad access requirement for the Corporate Compliance team.
Since Corporate Compliance sits in a separate role hierarchy branch and requires Read/Write access to all records, an owner-based sharing rule sharing records owned by 'All Internal Users' with the Corporate Compliance role must be created.
Role hierarchy alone does not open cross-branch access when OWD is Private.

Anahtar Kavram

Combining criteria-based and owner-based sharing rules to extend access beyond OWD when role hierarchy inheritance is insufficient or conditional.
Tahmini Süre:1m 30s
ÖncekiSayfa 35 / 90Sonraki
Tüm alıştırma soruları — Salesforce Certified Administrator | Examkin