Tüm alıştırma soruları

1784 soru

Soru 561Soru

Vanguard Asset Operations utilizes a custom object named `Equipment_Audit__c` to log site safety reviews. The Organization-Wide Default (OWD) for `Equipment_Audit__c` is configured as Private, and the Grant Access Using Hierarchies setting for this custom object was previously deselected by an administrator.

The administrator must now meet two new security requirements:
1. Regional Operations Managers must automatically gain Read/Write access to all `Equipment_Audit__c` records owned by Field Inspectors who report below them in the role hierarchy.
2. Members of the internal Compliance department (organized into the Public Group "Compliance Auditors") must be granted Read-Only access to any `Equipment_Audit__c` record where `Audit_Status__c` equals "Non-Compliant", regardless of record ownership.

Which TWO configuration actions should the administrator take to fulfill these requirements? (Select 2)

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

Cevabı ve açıklamayı göster

Cevap: Select the 'Grant Access Using Hierarchies' checkbox in Organization-Wide Defaults for the Equipment_Audit__c object.; Create a criteria-based sharing rule on Equipment_Audit__c to grant Read-Only access to the 'Compliance Auditors' Public Group when Audit_Status__c equals 'Non-Compliant'.

Cevap

The administrator must select the 'Grant Access Using Hierarchies' checkbox for the Equipment_Audit__c object and create a criteria-based sharing rule targeting records with Audit_Status__c equal to 'Non-Compliant' shared with the 'Compliance Auditors' Public Group.
Selecting the 'Grant Access Using Hierarchies' option for the custom object ensures that users higher in the role hierarchy automatically inherit the access rights of their subordinates. Creating a criteria-based sharing rule allows sharing records based on field values (Audit_Status__c = 'Non-Compliant') with the specified Public Group ('Compliance Auditors'). Together, these two steps address both business requirements securely and efficiently.

Adım Adım Çözüm

1
Analyze requirement 1: Regional Operations Managers must access records owned by Field Inspectors below them in the hierarchy.
Recognize that custom objects allow toggling 'Grant Access Using Hierarchies'. When unchecked, managers do not inherit subordinate record access. Checking this setting restores native upward access inheritance.
Grant Access Using Hierarchies is enabled by default for custom objects but can be deselected. Re-enabling it satisfies role hierarchy access propagation cleanly without custom rules.
2
Analyze requirement 2: Compliance department members must access records meeting specific field criteria (Audit_Status__c = 'Non-Compliant').
Determine that access based on record field values requires a criteria-based sharing rule.
Criteria-based sharing rules evaluate record field values (not ownership) to share records matching defined criteria with designated users, roles, or public groups.

Anahtar Kavram

Role Hierarchy Access Inheritance and Criteria-Based Sharing Rules
Tahmini Süre:2m 0s
Soru 562Soru

A Salesforce administrator is explaining the standard lead conversion process to a new sales team at a logistics management company. Which two records are automatically generated when a sales representative converts a Lead in Salesforce?

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

Cevabı ve açıklamayı göster

Cevap: Account; Contact

Cevap

During the standard lead conversion process, Salesforce automatically generates (or maps to existing) Account and Contact records. An Opportunity record can also be created optionally.
When a Lead is converted in Salesforce, the platform converts the lead record into an Account (representing the organization) and a Contact (representing the individual). An Opportunity can also be created, though users can check a box to suppress Opportunity creation if desired.

Adım Adım Çözüm

1
Identify the standard target objects generated upon Lead conversion in Salesforce.
Lead conversion maps lead fields to Account, Contact, and optionally Opportunity objects.
Salesforce architecture converts prospect data into core sales records (Account for company information, Contact for individual person information).
2
Evaluate the choices to select the two standard objects created by default.
Account and Contact are selected.
Case and Product objects are unrelated to the lead conversion target record creation flow.

Anahtar Kavram

Standard Lead Conversion Output Objects
Soru 563Soru

A Salesforce administrator at a logistics management firm is working with two custom objects: Warehouse__c and Inventory_Item__c, which are currently connected by a Lookup relationship. The operations manager requests two key metrics on record pages:
1. A calculated field on Warehouse__c displaying the sum total monetary value of all associated inventory items.
2. A dynamic field on Inventory_Item__c displaying the number of elapsed days since the item was created.

Which TWO statements accurately describe the configuration requirements or system behaviors for fulfilling these requests?

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

Cevabı ve açıklamayı göster

Cevap: The existing Lookup relationship must be converted to a Master-Detail relationship before a native Roll-Up Summary field can be created on the Warehouse__c object.; A custom Formula field with a Number return type can be created on Inventory_Item__c using a date difference formula to calculate the elapsed days dynamically.

Cevap

The correct requirements are converting the Lookup relationship to a Master-Detail relationship prior to creating the Roll-Up Summary field on Warehouse__c, and creating a custom Formula field with a Number return type on Inventory_Item__c to compute elapsed days.
Native Roll-Up Summary fields require a Master-Detail relationship structure between parent and child objects; converting an existing Lookup relationship to Master-Detail satisfies this requirement. Additionally, dynamic day calculations on child records are efficiently handled using a custom Formula field with a Number return type that calculates the difference between current date functions and the record creation date.

Adım Adım Çözüm

1
Analyze relationship requirements for Roll-Up Summary fields.
Native Salesforce Roll-Up Summary fields require a Master-Detail relationship and cannot be created on parent objects linked strictly via Lookup relationships.
Master-Detail relationships enforce tight coupling between parent and child records, allowing the system to maintain synchronized aggregate data.
2
Analyze field options for calculating elapsed days on individual records.
A Formula field returning a Number can perform dynamic date arithmetic using functions like TODAY() - DATEVALUE(CreatedDate).
Formula fields compute values dynamically on record read without requiring underlying database updates.

Anahtar Kavram

Roll-Up Summary Field Relationship Requirements and Formula Date Calculations
Tahmini Süre:1m 30s
Soru 564Soru

A Salesforce Administrator creates a new Record Type named 'Partner Referral' on the Lead object and assigns the 'Partner Lead Layout' to users with the 'Channel Sales User' profile for this record type. However, when users with the 'Channel Sales User' profile create a new 'Partner Referral' lead record, they observe two issues: first, the 'Industry' picklist field displays values meant only for internal leads; second, the default record type selected automatically upon lead creation remains set to 'Standard Lead'. Which pair of configuration actions must the administrator perform to resolve both issues?

Cevabı ve açıklamayı göster

Cevap: Edit the 'Partner Referral' Record Type detail page to select the appropriate available picklist values for the 'Industry' field, and update the Record Type Settings on the 'Channel Sales User' profile to set 'Partner Referral' as the default Record Type.

Cevap

The administrator must edit the 'Partner Referral' Record Type setup page to select the available picklist values for the 'Industry' field, and edit the Record Type Settings on the 'Channel Sales User' profile to assign 'Partner Referral' as the default Record Type.
Configuring available picklist values on the Record Type detail page ensures that only relevant picklist options are shown to users selecting that record type. Setting the default Record Type within the user's Profile Record Type Settings ensures that 'Partner Referral' is automatically pre-selected when users create new leads.

Adım Adım Çözüm

1
Identify the mechanism for restricting picklist choices per Record Type.
Recognize that creating a Record Type requires explicitly configuring which picklist values are active and visible for that specific Record Type under Object Manager.
By default, new Record Types may inherit all global picklist values unless customized on the Record Type detail page.
2
Identify the location of default Record Type settings for users.
Navigate to the Profile settings for 'Channel Sales User' under Record Type Settings for the Lead object.
Default record type selection during record creation is driven by the user's Profile configuration, not Page Layout Assignment or OWD.
3
Combine both corrective actions.
Select the option that configures picklist value assignments on the Record Type and modifies the default Record Type on the Profile.
This fully addresses both observed functional issues in accordance with Salesforce administration best practices.

Anahtar Kavram

Record Type Picklist Value Assignment and Profile Default Record Type Configuration
Tahmini Süre:2m 0s
Soru 565Soru

A Salesforce administrator at a commercial vehicle leasing company needs to capture a custom 'Contract Duration' value on Lead records and ensure that this data transfers automatically to a custom field on the Opportunity record whenever a Lead is converted. Which administrative action is required to meet this requirement?

Cevabı ve açıklamayı göster

Cevap: Navigate to Fields & Relationships on the Lead object and configure the custom field mapping to link the Lead field to the corresponding custom Opportunity field.

Cevap

Configure custom lead field mapping under the Lead object's Fields & Relationships settings to link the custom Lead field to the custom Opportunity field.
To preserve custom lead field values when converting a lead into an account, contact, or opportunity, an administrator must navigate to Object Manager > Lead > Fields & Relationships and click 'Map Lead Fields' to explicitly pair the source custom lead field with an appropriately typed target custom field.

Adım Adım Çözüm

1
Identify the data transfer requirement during lead conversion.
Recognize that custom lead fields do not automatically populate target object fields upon conversion unless mapped.
Salesforce requires explicit mapping between custom fields on the Lead object and matching custom fields on Account, Contact, or Opportunity.
2
Navigate to Object Manager > Lead > Fields & Relationships > Map Lead Fields.
Access the lead conversion field mapping interface.
This interface allows administrators to pair custom Lead fields with custom destination fields of compatible data types.
3
Map the custom Lead field to the target custom field on the Opportunity object.
Ensure seamless data flow from Lead to Opportunity during conversion.
This completes the setup required for automated data preservation upon lead conversion.

Anahtar Kavram

Lead Custom Field Mapping
Soru 566Soru

A Salesforce administrator is configuring a custom Lightning Record Page for the Case object. The business requires Tier 2 Support Representatives using the Service Console application to view a specialized layout tailored to their workflow. Additionally, a sensitive financial component on the page must be conditionally hidden from standard users, while maintaining secure data access controls across the platform.

Which TWO statements accurately describe the required configuration steps or platform behaviors for this deployment?

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

Cevabı ve açıklamayı göster

Cevap: Activating the custom record page as the App Default for the Service Console app ensures all users accessing Cases within that app see the customized layout unless overridden by profile assignments.; Component visibility filters in Lightning App Builder control interface rendering only; Field-Level Security (FLS) must still be configured to prevent unauthorized data access via reports or APIs.

Cevap

The correct statements state that activating the page as an App Default assigns the customized layout to users within the Service Console app, and that component visibility rules only control UI visibility while Field-Level Security (FLS) must be used to enforce true data access control.
Activating a Lightning Record Page as an App Default assigns the page layout specifically to users working within that Lightning App (such as Service Console), taking precedence over the Org Default. Additionally, component visibility rules on Lightning Record Pages strictly govern whether an element renders on screen; Field-Level Security remains mandatory for controlling underlying data access across the platform.

Adım Adım Çözüm

1
Evaluate activation scope requirement
To target users inside the Service Console application, activate the custom Lightning Record Page at the App Default level or the App, Record Type, and Profile level.
App Default overrides the Org Default specifically for users navigating within the Service Console app.
2
Evaluate security vs UI visibility requirements
Use Lightning App Builder component visibility filters to dynamically show/hide components on the record page layout, and configure Field-Level Security (FLS) on the profile/permission set level to restrict API, report, and export access.
Component visibility only affects UI rendering on Lightning pages and does not secure data across rest of the platform.

Anahtar Kavram

Lightning App Builder Page Activation Levels and Component Visibility vs Field-Level Security
Tahmini Süre:2m 0s
Soru 567Soru

A System Administrator is creating a new field on a custom object called Project__c. The administrator intends to aggregate total cost values from related Project_Task__c records using a Roll-Up Summary field. However, when choosing the field type for Project__c, the Roll-Up Summary option is greyed out. Which relationship configuration explains why the Roll-Up Summary field type is unavailable?

Cevabı ve açıklamayı göster

Cevap: The relationship field linking Project_Task__c to Project__c is a Lookup relationship rather than a Master-Detail relationship.

Cevap

The relationship field linking Project_Task__c to Project__c is a Lookup relationship rather than a Master-Detail relationship.
Roll-Up Summary fields can only be created on the master object of a Master-Detail relationship. Because the two objects are connected via a Lookup relationship, Salesforce disables the Roll-Up Summary field data type option.

Adım Adım Çözüm

1
Identify the relationship type between the parent object (Project__c) and child object (Project_Task__c).
Determined that the relationship is currently configured as a Lookup relationship.
Roll-Up Summary fields in Salesforce require a Master-Detail relationship.
2
Verify Salesforce platform capabilities for Roll-Up Summary field creation.
Confirmed that Roll-Up Summary field types are disabled when objects are connected via Lookup relationships.
Salesforce only allows Roll-Up Summary fields on the master side of a Master-Detail relationship.

Anahtar Kavram

Roll-Up Summary Relationship Requirements
Soru 568Soru

An administrator is configuring a customized Case Lightning Record Page in Lightning App Builder for a service department. The organization requires a specialized record layout for support agents using the Support Console desktop app when handling cases assigned to the Tier 3 Escalation record type. However, when support agents view the same cases on the Salesforce Mobile App, they must continue to view the org default page layout rather than the specialized layout. Which two configuration steps or activation behaviors must the administrator consider to meet these requirements? (Select 2 choices)

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

Cevabı ve açıklamayı göster

Cevap: The custom Lightning Record Page must be activated using the App, Record Type, and Profile assignment combination, selecting Desktop as the supported form factor during activation.; App, Record Type, and Profile page activation takes precedence over Org Default and App Default activations when a user meets all assigned criteria on a supported form factor.

Cevap

To meet the requirements, the administrator must activate the record page at the App, Record Type, and Profile level while selecting Desktop as the supported form factor, relying on the fact that App/Record Type/Profile activations take precedence over Org Default activations for supported devices.
Activating a Lightning Record Page using the App, Record Type, and Profile combination provides the narrowest and highest precedence assignment rule in Salesforce. Because form factors can be filtered to Desktop during the activation wizard, mobile users will bypass this assignment and fall back to the Org Default record page.

Adım Adım Çözüm

1
Analyze activation precedence hierarchy in Lightning App Builder.
App + Record Type + Profile activation provides the highest level of specificity, overriding Org Default and App Default settings for matching users.
Specific assignments take priority over generic defaults in Salesforce activation logic.
2
Configure form factor filtering during page activation.
Selecting Desktop-only form factor ensures mobile users fall back to the broader Org Default assignment.
Form factor selections limit which device types render the custom Lightning Record Page.

Anahtar Kavram

Lightning Record Page Activation Hierarchy and Form Factor Targeting
Tahmini Süre:2m 0s
Soru 569Soru

A financial compliance software company has 40 customer support representatives assigned to a baseline profile named 'Standard Support Specialist'. During an upcoming 30-day compliance review, 8 tier-2 representatives require temporary Read and Edit access to a custom object named Compliance Audit. The remaining support representatives must not have access to this object. What is the recommended administrative solution to satisfy this requirement while preserving a clean security model?

Cevabı ve açıklamayı göster

Cevap: Create a Permission Set granting Read and Edit access to the Compliance Audit object, assign it to the 8 tier-2 representatives with an assignment expiration date, and keep the baseline profile unchanged.

Cevap

Create a Permission Set granting Read and Edit access on the Compliance Audit object, assign it to the 8 tier-2 representatives with a specified assignment expiration date, and leave the baseline profile unchanged.
The correct approach is to keep the baseline profile intact and assign a custom Permission Set containing Read and Edit access on the Compliance Audit object to the 8 tier-2 representatives. Using assignment expiration allows the temporary access to automatically revoke after 30 days without manual intervention or profile maintenance.

Adım Adım Çözüm

1
Identify the base security architecture and requirements
All 40 representatives share a baseline profile ('Standard Support Specialist'), but only 8 require extra object permissions for a temporary 30-day period.
Profiles establish baseline access for job functions, whereas permission sets extend access for specific sub-teams or tasks.
2
Determine the appropriate tool for additive, temporary access
Create a dedicated Permission Set granting Read and Edit permissions to the Compliance Audit object.
Permission Sets provide additive permissions without requiring profile duplication or modifying broad user access.
3
Configure assignment expiration
Assign the permission set to the 8 tier-2 representatives and set an expiration date of 30 days.
Permission Set assignment expiration automatically revokes access after the audit concludes, removing the need for manual administrative cleanup.

Anahtar Kavram

Additive permissions via Permission Sets and Permission Set Expiration
Soru 570Soru

Universal Containers uses a custom object named Contract_Review__c to manage sensitive legal evaluations of enterprise customer agreements. Company policy requires that, by default, contract review records must be restricted so that only the record owner and users higher in the role hierarchy can access them. Additionally, the administrator must grant Read access to regional compliance officers who are outside the record owner's direct management chain. Which TWO configuration actions should the administrator take to satisfy these security requirements?

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

Cevabı ve açıklamayı göster

Cevap: Set the Organization-Wide Default (OWD) internal access for Contract_Review__c to Private.; Create criteria-based or owner-based sharing rules to extend Read access to regional compliance officers.

Cevap

The administrator must set the Organization-Wide Default internal access for the custom object to Private and create sharing rules to grant Read access to regional compliance officers.
The correct configuration strategy requires establishing a Private Organization-Wide Default for the custom object to secure records at the baseline level, while relying on default role hierarchy propagation and sharing rules to open up Read access for specific cross-functional teams.

Adım Adım Çözüm

1
Determine the baseline security requirement.
Since record access must be restricted to record owners and their management chain by default, the Organization-Wide Default (OWD) must be set to Private.
Organization-Wide Defaults define the most restrictive baseline access level for all users in the organization.
2
Evaluate role hierarchy behavior.
Ensure Grant Access Using Hierarchies remains enabled for the custom object.
By keeping hierarchy access enabled, users positioned above the owner in the role hierarchy automatically inherit access to owned records.
3
Extend access to lateral or cross-functional teams.
Define criteria-based or owner-based sharing rules targeting regional compliance officers.
Salesforce security principles mandate starting with a restrictive OWD baseline and using sharing rules to open up access to additional roles or public groups.

Anahtar Kavram

Salesforce Sharing Architecture and OWD Baseline Configuration
Soru 571Soru

An administrator at a global telecommunications company needs to track service warranties using a custom object named Equipment_Warranty__c. The object currently has an existing Lookup relationship to the standard Asset object. The business requires calculating the sum of claim amounts directly on the Asset record using a Roll-Up Summary field and ensuring that deleting an Asset automatically deletes all associated Equipment_Warranty__c records. However, several existing Equipment_Warranty__c records currently have null values in their Asset lookup field. Which sequence of actions must the administrator perform to satisfy these business requirements?

Cevabı ve açıklamayı göster

Cevap: Populate the Asset field on all existing Equipment_Warranty__c records, convert the relationship to Master-Detail, and then create the Roll-Up Summary field on the Asset object.

Cevap

Populate the Asset field on all existing Equipment_Warranty__c records, convert the relationship to Master-Detail, and then create the Roll-Up Summary field on the Asset object.
The requirement to calculate aggregated child values via native Roll-Up Summary fields and enforce automatic cascading deletion necessitates a Master-Detail relationship. Converting a Lookup field to a Master-Detail field requires that every existing record has a populated parent lookup value. Therefore, populating all null values, converting the relationship, and creating the Roll-Up Summary field is the correct sequence.

Adım Adım Çözüm

1
Analyze requirement dependencies
Roll-Up Summary fields and cascading record deletion both require a Master-Detail relationship between the parent (Asset) and child (Equipment_Warranty__c) objects.
Standard lookup relationships do not support native roll-up summary functionality or automatic deletion of child records.
2
Evaluate data prerequisites for relationship conversion
Identify that existing child records with null lookup values will prevent changing the relationship type to Master-Detail.
Master-Detail fields are mandatory on child records; Salesforce enforces that every existing record must have a parent populated before conversion.
3
Execute conversion and configuration sequence
Populate all blank Asset values, convert the field to Master-Detail, and construct the Roll-Up Summary field on the Asset object.
Once all records have valid parent pointers and the field is converted to Master-Detail, Roll-Up Summary fields can be successfully created on the parent.

Anahtar Kavram

Converting Lookup Relationships to Master-Detail and Roll-Up Summary Field Eligibility
Tahmini Süre:2m 0s
Soru 572Soru

A Salesforce Administrator needs to manually provision a new sales representative who requires standard Salesforce license access, reporting visibility based on management hierarchy, and specialized permissions to delete lead records. What is the correct sequence of administrative steps to provision this user while maintaining the principle of least privilege?

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

Cevabı ve açıklamayı göster

Cevap

The correct order of steps to provision the user is: 1) Create the user record with the Salesforce User License and baseline Profile, 2) Assign the appropriate Role in the Role Hierarchy on the user creation screen, 3) Save the user record to commit account creation, and 4) Assign the specialized Lead Delete Permission Set from the User Detail page.
Provisioning a user in Salesforce follows a logical sequence: first, initialize the user record with mandatory fields including User License and a minimal baseline Profile; second, set the Role to establish hierarchy-based sharing; third, save the record to generate the account; fourth, navigate to the newly created User Detail page to assign supplemental Permission Sets for specialized capabilities like deleting leads.

Adım Adım Çözüm

1
Define baseline identity and minimum access
User record initialized with correct User License and minimal baseline Profile
Salesforce user creation requires license and profile selection to establish base system availability and minimum permissions.
2
Configure hierarchy-based record access
User record assigned to correct Role
Setting the Role on the user record defines record sharing and management visibility parameters.
3
Commit record creation in Salesforce Setup
User record created in database and activation email dispatched
Saving the record creates a valid User ID in the org, enabling related list items like Permission Set assignments.
4
Grant supplemental functional permissions
Lead Delete Permission Set linked to the user account
Following least privilege, specialized permissions (like record deletion) are layer-assigned via Permission Sets after user creation.

Anahtar Kavram

User Provisioning Workflow and Least Privilege Access Assignment
Soru 573Soru

An administrator at Universal Containers needs to ensure that data captured in a custom field on the Lead object is automatically transferred to a custom field on the Contact object whenever a lead is converted. Which Salesforce configuration tool should the administrator use to fulfill this requirement?

Cevabı ve açıklamayı göster

Cevap: Map Lead Fields under Lead Object Manager settings

Cevap

Map Lead Fields under Lead Object Manager settings.
Using the 'Map Lead Fields' feature in the Lead Object Manager settings allows administrators to map custom Lead fields to custom Account, Contact, or Opportunity fields of compatible data types. This ensures data is retained and transferred during conversion.

Adım Adım Çözüm

1
Navigate to Setup > Object Manager > Lead.
Access the admin settings for the Lead object.
Lead field mapping is configured from within the Lead object settings.
2
Select Fields & Relationships and click the 'Map Lead Fields' button.
Open the lead conversion field mapping interface.
This tool defines how custom Lead fields relate to target object fields.
3
Select the Contact tab and pair the source Lead custom field with the target Contact custom field of matching data type.
The custom field mapping for lead conversion is established.
Salesforce copies values from mapped Lead custom fields into their paired Contact fields upon lead conversion.

Anahtar Kavram

Lead Custom Field Mapping during Lead Conversion
Soru 574Soru

An organization manages internal projects using a parent custom object, Internal_Project__c, and child records using Project_Milestone__c. The administrator needs to create a standard Roll-Up Summary field on Internal_Project__c to calculate the total count of related milestones. Which relationship configuration must exist between these two objects to allow the Roll-Up Summary field?

Cevabı ve açıklamayı göster

Cevap: A Master-Detail relationship created on the Project_Milestone__c object referencing Internal_Project__c as the master

Cevap

A Master-Detail relationship created on the Project_Milestone__c object referencing Internal_Project__c as the master.
Standard Roll-Up Summary fields can only be created on the master object of a Master-Detail relationship. To establish this relationship, the Master-Detail relationship field must be created on the child object (Project_Milestone__c), referencing the parent object (Internal_Project__c) as the master.

Adım Adım Çözüm

1
Identify the field requirement on the parent object
The requirement calls for a standard Roll-Up Summary field on Internal_Project__c.
Standard Roll-Up Summary fields require a Master-Detail relationship to function.
2
Determine where the relationship custom field must be created
The relationship custom field must be defined on the detail (child) object, which is Project_Milestone__c.
In Salesforce data modeling, child objects store the custom relationship field that links back to the parent master object.

Anahtar Kavram

Roll-Up Summary Field Eligibility
Soru 575Soru

A Salesforce Administrator at Quantum Energy must configure security controls for five HR Compliance Officers who currently share the standard Operations profile with thirty other employees. The business requirements state:
1. The five HR Compliance Officers require Read access to the sensitive `National_ID__c` field on the Contact object, but all other Operations users must be prevented from accessing or viewing this field across all interfaces, reports, and API calls.
2. The five HR Compliance Officers must be strictly blocked from logging into Salesforce when working outside the corporate network IP range of 198.51.100.0/24198.51.100.0/24, while other Operations users may continue logging in from any location.

Which configuration strategy should the administrator implement to satisfy these security requirements with minimal impact on other users?

Cevabı ve açıklamayı göster

Cevap: Clone the Operations profile to create a custom HR Compliance profile, configure the Login IP Ranges on the new profile, and assign a Permission Set with Read access for National_ID__c via Field-Level Security to the five officers.

Cevap

Create a custom profile for the HR Compliance Officers with Login IP Ranges configured to enforce the IP restriction, and assign a Permission Set granting Field-Level Security Read access for the field.
Configuring a custom profile for the HR Compliance Officers allows the administrator to define strict Profile Login IP Ranges that block login attempts outside the designated IP network without impacting non-HR Operations users. Combining this with a Permission Set that grants Read access to the sensitive field via Field-Level Security (FLS) ensures secure, complete protection across all access channels (UI, API, and reporting) in alignment with Salesforce security best practices.

Adım Adım Çözüm

1
Analyze login IP restrictions requirement
Login IP Ranges must be configured at the Profile level because Login IP Ranges cannot be set in Permission Sets or Network Access settings.
Profile Login IP Ranges actively deny login outside specified ranges, whereas Network Access only waives multi-factor/activation challenges.
2
Evaluate user separation for profile settings
Create a dedicated custom profile for the five HR Compliance Officers cloned from the Operations profile.
Modifying IP ranges on the shared Operations profile would inadvertently restrict the remaining thirty employees.
3
Configure Field-Level Security (FLS) access
Keep the field hidden on the profile and grant Read access to the field using a Permission Set assigned to the five officers.
Field-Level Security (FLS) ensures total field privacy across UI, API, and reports, and using a Permission Set follows Salesforce best practices for additive field permissions.

Anahtar Kavram

Profiles control restrictive security boundary settings like Login IP Ranges, whereas Permission Sets grant additive data and field access like Field-Level Security (FLS).
Tahmini Süre:2m 0s
Soru 576Soru

An administrator at Universal Containers is configuring lead conversion settings. The business requirement states that a custom picklist field on the Lead object named 'Product Interest' must populate a custom field on the Contact object when a lead is converted. However, during custom lead field mapping setup in Salesforce, the administrator cannot find or select the desired custom Contact field in the mapping dropdown menu. What is the most likely cause of this issue?

Cevabı ve açıklamayı göster

Cevap: The custom field on the Contact object has an incompatible data type for mapping from the custom picklist Lead field.

Cevap

The custom field on the Contact object has an incompatible data type for mapping from the custom picklist Lead field.
When configuring custom field mapping for lead conversion ('Map Lead Fields' in Setup), Salesforce filters the available destination fields based on strict data type compatibility. A custom picklist field on the Lead object can only be mapped to a custom picklist or custom text field on the destination Account, Contact, or Opportunity object. If a field does not appear in the dropdown menu, its data type is incompatible with the source Lead field.

Adım Adım Çözüm

1
Analyze Lead conversion custom field mapping requirements in Salesforce.
Lead custom field mapping requires custom Lead fields to map exclusively to custom fields on Account, Contact, or Opportunity.
Salesforce schema restrictions do not allow mapping custom Lead fields to standard destination fields.
2
Evaluate data type compatibility rules.
Target destination fields must match or be compatible with the source Lead field data type (e.g., Picklist to Picklist or Picklist to Text).
If the target custom Contact field is of an incompatible type (such as Date, Number, or Checkbox), it will not appear in the mapping dropdown list.

Anahtar Kavram

Lead Custom Field Mapping Data Type Compatibility
Tahmini Süre:1m 15s
Soru 577Soru

A Salesforce Administrator needs to enforce tailored security controls for different user roles while maintaining organizational baselines. Match each security administration scenario to the correct location in Setup where the policy must be configured.

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

Öğeler

Set a custom 15-minute session inactivity timeout exclusively for users assigned to the Customer Support profile.
Ensure that any user whose session expires across the organization is immediately logged out without receiving a session renewal prompt.
Configure a maximum limit of 3 invalid login attempts before lockout specifically for users assigned to the System Administrator profile.
Establish a baseline requirement for passwords to expire every 90 days for all users in the organization who do not have a profile override.

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

1. Custom 15-minute timeout for a specific profile matches Profile-Level Session Settings. 2. Immediate logout upon session expiration org-wide matches Organization-Wide Session Settings. 3. Custom lockout threshold for a specific profile matches Profile-Level Password Policies. 4. Baseline password expiration for all users matches Organization-Wide Password Policies.
Custom session timeout durations tailored to specific user roles belong in Profile-Level Session Settings. Global session behavior, such as forcing logout upon session timeout, is configured under Organization-Wide Session Settings. Custom password lockout thresholds for dedicated user roles are defined in Profile-Level Password Policies, whereas default password expiration timelines for the entire tenant are established in Organization-Wide Password Policies.

Adım Adım Çözüm

1
Categorize each scenario into Session Settings vs Password Policies.
Scenarios concerning inactivity timeout durations and forced logouts fall under Session Settings. Scenarios concerning invalid login lockouts and password expiration periods fall under Password Policies.
Isolating session behavior from authentication rules identifies the proper administration category in Setup.
2
Determine whether each requirement applies to the entire organization or to a specific subset of users defined by a Profile.
Scenarios targeting the Customer Support profile and System Administrator profile require Profile-level overrides. Scenarios specifying default behavior for all users or tenant-wide forced logout require Organization-Wide configurations.
Salesforce allows admins to define org-wide defaults while overriding session timeouts and password policies at the individual profile level.
3
Pair each scenario with its designated administrative interface in Salesforce.
Specific profile timeout -> Profile-Level Session Settings; Org-wide forced logout -> Organization-Wide Session Settings; Specific profile lockout -> Profile-Level Password Policies; Default org password expiration -> Organization-Wide Password Policies.
This satisfies security requirements by applying overrides where specific control is required and global settings where universal enforcement is needed.

Anahtar Kavram

Distinction between Organization-Wide and Profile-Level enforcement for Session Settings and Password Policies in Salesforce.
Soru 578Soru

A Salesforce Administrator is designing a customized tracking system for a real estate firm. The schema includes a parent object, Property_Listing__c, and a child object, Open_House_Feedback__c, connected via a Master-Detail relationship. Additionally, Property_Listing__c is related to a standard Account record via a Lookup relationship. The administrator needs to display aggregated metrics on parent records and reference parent fields on child records. Which TWO considerations and capabilities must the administrator keep in mind when configuring Formula and Roll-Up Summary fields? (Select 2)

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

Cevabı ve açıklamayı göster

Cevap: Roll-Up Summary fields can be created on Property_Listing__c to aggregate metrics from Open_House_Feedback__c because they share a Master-Detail relationship.; A cross-object formula field on Open_House_Feedback__c can reference fields from Property_Listing__c and its related Account record.

Cevap

The correct statements are that Roll-Up Summary fields can be created on Property_Listing__c to calculate values from Open_House_Feedback__c due to their Master-Detail relationship, and cross-object formula fields on Open_House_Feedback__c can reference merge fields from parent records up to 10 relationships away.
Roll-Up Summary fields are natively supported on parent records in a Master-Detail relationship, allowing calculations like SUM, COUNT, MIN, and MAX on detail records. Additionally, cross-object formulas on child records can reference field values across both Lookup and Master-Detail relationships up to 10 levels deep.

Adım Adım Çözüm

1
Evaluate Roll-Up Summary requirements between Property_Listing__c and Open_House_Feedback__c.
Since Property_Listing__c and Open_House_Feedback__c are in a Master-Detail relationship, Roll-Up Summary fields are fully supported on the master object.
Salesforce natively restricts standard Roll-Up Summary fields to the master side of Master-Detail relationships.
2
Evaluate Roll-Up Summary capabilities between Account and Property_Listing__c.
Creating a native Roll-Up Summary field on Account for Property_Listing__c is invalid because they are connected via a Lookup relationship.
Lookup relationships do not support native Roll-Up Summary fields.
3
Analyze cross-object formula capabilities on child records.
Formula fields on Open_House_Feedback__c can navigate relationship paths to pull data from Property_Listing__c and Account.
Cross-object formulas can span up to 10 relationship hops across both lookup and master-detail paths.
4
Analyze schema conversion constraints regarding Roll-Up Summary fields.
Converting Master-Detail to Lookup is blocked while Roll-Up Summary fields exist.
Salesforce requires deleting all Roll-Up Summary fields prior to changing a Master-Detail field type to Lookup.

Anahtar Kavram

Roll-Up Summary fields require a Master-Detail relationship on the parent master object and block relationship type conversion until removed, whereas cross-object formulas can span across both Lookup and Master-Detail relationships.
Soru 579Soru

An administrator at Universal Containers needs to track compliance audits. The company uses a custom object named Inspection_Site__c and a custom object named Audit_Report__c, which are currently connected by a Lookup relationship. Management introduces two new requirements:
1. Deleting an Inspection_Site__c record must automatically delete all associated Audit_Report__c records.
2. A field on Inspection_Site__c must continuously display the aggregate count of all related Audit_Report__c records.

When attempting to create a Roll-Up Summary field on Inspection_Site__c, the administrator discovers that the option is unavailable. Which sequence of actions should the administrator perform to satisfy these requirements?

Cevabı ve açıklamayı göster

Cevap: Populate the Inspection_Site__c lookup field on all existing Audit_Report__c records, convert the Lookup relationship to a Master-Detail relationship, and create the Roll-Up Summary field on Inspection_Site__c.

Cevap

Ensure all existing Audit_Report__c records have a value in the Inspection_Site__c lookup field, convert the existing Lookup relationship field to a Master-Detail relationship, and then create the Roll-Up Summary field on Inspection_Site__c.
To fulfill the requirements, the relationship must be converted to Master-Detail because Master-Detail relationships automatically delete detail records when the master record is deleted and enable the creation of Roll-Up Summary fields on the master object. A Lookup relationship can only be converted to a Master-Detail relationship if all existing child records have a value in the lookup field.

Adım Adım Çözüm

1
Audit existing records and populate parent values.
Every Audit_Report__c record contains a non-null reference to an Inspection_Site__c record.
Salesforce enforces that a Master-Detail relationship cannot be created or converted if child records exist without a parent assigned.
2
Convert the custom Lookup relationship field on Audit_Report__c to a Master-Detail relationship.
The relationship type changes to Master-Detail, enabling automatic cascade deletion of child records when a master record is deleted.
Master-Detail relationships inherently control deletion cascade behavior and security inheritance from master to detail.
3
Create the Roll-Up Summary field on Inspection_Site__c.
The Roll-Up Summary field option becomes available and active on Inspection_Site__c to count related Audit_Report__c records.
Roll-Up Summary fields are exclusively allowed on master objects targetting detail records in a Master-Detail relationship.

Anahtar Kavram

Converting Lookup Relationships to Master-Detail Relationships and Roll-Up Summary Requirements
Soru 580Soru

An organization configures three distinct custom Lightning Record Pages for the Account object within Lightning App Builder:

- Account_Page_Global is assigned as the Org Default across all desktop and mobile views.
- Account_Page_Sales is assigned as the App Default for the 'Sales Hub' Lightning App.
- Account_Page_Enterprise is assigned to the 'Sales Hub' Lightning App, paired specifically with the 'Enterprise' Record Type and the 'Custom: Sales Manager' Profile.

A sales representative who is assigned the 'Custom: Sales Representative' Profile opens an Account record with the 'Enterprise' Record Type while navigating inside the 'Sales Hub' Lightning App. Which Lightning Record Page will be displayed to the user?

Cevabı ve açıklamayı göster

Cevap: Account_Page_Sales

Cevap

Account_Page_Sales will be displayed because the user's profile does not match the profile criteria of the triple-combination assignment, causing activation precedence to fall back to the App Default.
Salesforce evaluates Lightning Record Page activation assignments using a clear three-tiered hierarchy: 1) App, Record Type, and Profile combination, 2) App Default, and 3) Org Default. In this scenario, the combination assignment is specified for the 'Custom: Sales Manager' profile. Because the viewing user possesses the 'Custom: Sales Representative' profile, the combination assignment fails to match. Salesforce then evaluates the next priority tier, which is the App Default for the 'Sales Hub' app, correctly rendering Account_Page_Sales.

Adım Adım Çözüm

1
Evaluate the most specific activation assignment tier (App + Record Type + Profile).
The triple assignment requires the 'Sales Hub' App, 'Enterprise' Record Type, and 'Custom: Sales Manager' Profile. The active user has the 'Custom: Sales Representative' Profile, so this tier does not match.
Granular record page activations only take effect if all three criteria (App, Record Type, Profile) match the context of the user and record.
2
Evaluate the second activation assignment tier (App Default).
Account_Page_Sales is explicitly configured as the App Default for the 'Sales Hub' Lightning App.
When no matching App + Record Type + Profile combination is found for the user's profile, Salesforce checks for an active App Default assignment for the current application.
3
Determine the final page rendered.
Account_Page_Sales is rendered.
Since a valid App Default match exists, evaluation stops and Org Default fallback is not evaluated.

Anahtar Kavram

Lightning Record Page Activation Precedence
ÖncekiSayfa 29 / 90Sonraki
Tüm alıştırma soruları — Salesforce Certified Administrator | Examkin