Tüm alıştırma soruları

1784 soru

Soru 421Soru

Ursa Major Solar tracks custom Service_Contract__c records that serve as parent records to custom Equipment_Maintenance__c records using a Master-Detail relationship. The administrator also maintains a standard Lookup relationship between Service_Contract__c and the AssetAsset object. The business requires reporting aggregated maintenance costs on the service contract as well as displaying asset warranty dates dynamically. Which two field configuration rules and system behaviors must the administrator take into account when setting up Roll-Up Summary and Cross-Object Formula fields?

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

Cevabı ve açıklamayı göster

Cevap: Roll-Up Summary fields can only aggregate data from records linked via a Master-Detail relationship and cannot summarize fields on objects connected solely through a Lookup relationship.; A Roll-Up Summary field cannot summarize a custom formula field on a child object if that formula field references values from another related object.

Cevap

Roll-Up Summary fields require a Master-Detail relationship and cannot summarize child formula fields that contain cross-object references.
Native Roll-Up Summary fields in Salesforce strictly require a Master-Detail relationship between parent and child objects. Furthermore, Salesforce imposes limits on summarizing formula fields on child objects: if a child field relies on a cross-object formula spanning another relationship, it cannot be referenced as the target of a Roll-Up Summary field.

Adım Adım Çözüm

1
Evaluate relationship requirements for Roll-Up Summary fields
Confirm that native Roll-Up Summary fields are strictly supported only on the parent side of Master-Detail relationships.
Lookup relationships do not support native Roll-Up Summary fields regardless of whether the lookup field is marked as required.
2
Analyze field limitations regarding formula fields in Roll-Up Summaries
Identify that child formula fields referencing fields on another object (cross-object formulas) cannot be aggregated by a Roll-Up Summary field.
Dynamic updates on cross-object values do not automatically fire recalculations on the child record required by the roll-up engine.
3
Verify deletion impact on Roll-Up Summary values
Recognize that sending a detail record to the Recycle Bin immediately recalculates the summary value on the parent master record.
Master-Detail rollup engine updates synchronously upon record deletion and restoration.

Anahtar Kavram

Roll-Up Summary Field Capabilities and Formula Restrictions
Soru 422Soru

Match each Salesforce security or UI control feature on the left with its correct administrative function on the right.

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

Öğeler

Object Permissions (CRUD)
Field-Level Security (FLS)
Profile Login IP Ranges
Dynamic Forms Component Visibility

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Object Permissions define baseline CRUD operations for an object; Field-Level Security restricts field access universally across all entry points; Profile Login IP Ranges enforce network login locations; Dynamic Forms Component Visibility controls page layout rendering without enforcing data security.
Each feature is correctly matched to its security scope: Object Permissions control object-wide CRUD capabilities, Field-Level Security controls field access universally at the data level, Profile Login IP Ranges govern network location access, and Dynamic Forms component visibility rules handle UI display on record pages.

Adım Adım Çözüm

1
Identify Object Permissions function
Matched Object Permissions to baseline Create, Read, Edit, and Delete permissions.
Profiles manage baseline record operation capabilities per object.
2
Identify Field-Level Security function
Matched Field-Level Security to field access control across all interfaces and reports.
FLS operates at the data layer, ensuring field restrictions apply everywhere in the org.
3
Identify Profile Login IP Ranges function
Matched Profile Login IP Ranges to network login restrictions.
IP ranges defined on profiles dictate allowed network login locations.
4
Identify Dynamic Forms Component Visibility function
Matched Dynamic Forms Component Visibility to UI component display rules.
Visibility rules only modify page presentation and do not secure field data at the API or reporting levels.

Anahtar Kavram

Profiles and Object/Field-Level Security
Tahmini Süre:1m 0s
Soru 423Soru

A healthcare company uses Salesforce to manage patient care. The administrator is designing a custom data model to link a custom object named Medical_Procedure__c to both Patient__c and Doctor__c. The architecture must satisfy two specific constraints:
1. The Patient__c record must display a native Roll-Up Summary field calculating the sum of procedure costs from all related Medical_Procedure__c records.
2. If a Doctor__c record is deleted from the system, any associated Medical_Procedure__c records must remain active, and the reference to the deleted doctor must simply be cleared.

Which relationship configuration must the administrator implement on the Medical_Procedure__c object to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Create a Master-Detail relationship pointing to Patient__c, and create a Lookup relationship pointing to Doctor__c configured to clear the value of the field if deleted.

Cevap

Create a Master-Detail relationship from Medical_Procedure__c to Patient__c, and a Lookup relationship from Medical_Procedure__c to Doctor__c configured to clear the field value upon record deletion.
To calculate roll-up summary values natively on Patient__c, Patient__c must be the master object in a Master-Detail relationship with Medical_Procedure__c. To prevent Medical_Procedure__c records from being deleted when a Doctor__c record is removed, the link to Doctor__c must be a Lookup relationship set to clear the field value upon deletion.

Adım Adım Çözüm

1
Analyze the Roll-Up Summary requirement on Patient__c
Native Roll-Up Summary fields are strictly supported on the master side of a Master-Detail relationship. Therefore, Medical_Procedure__c must be the detail object in a Master-Detail relationship with Patient__c.
Lookup relationships do not support native declarative Roll-Up Summary fields.
2
Analyze the deletion requirement for Doctor__c
Medical_Procedure__c must have a Lookup relationship to Doctor__c configured with the 'Clear the value of this field' deletion option.
If Doctor__c were established as a Master in a Master-Detail relationship, deleting a Doctor__c record would trigger a cascade deletion of all related Medical_Procedure__c records, violating the requirement.
3
Combine relationship definitions on the custom object
Medical_Procedure__c functions as a hybrid junction object (Master-Detail to Patient__c and Lookup to Doctor__c), satisfying both calculation and record persistence requirements.
Custom objects support up to two Master-Detail relationships alongside multiple Lookup relationships.

Anahtar Kavram

Object Relationship Design (Master-Detail vs. Lookup Behavior)
Tahmini Süre:2m 0s
Soru 424Soru

An IT consulting firm tracks sensitive client risk assessments using a custom object named Security_Audit__c. Management requires that standard users can only view and edit records that they own. However, managers must automatically retain full access to records owned by their direct and indirect subordinates in the role hierarchy. Which two configuration steps must the Salesforce administrator take to enforce these security requirements?

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

Cevabı ve açıklamayı göster

Cevap: Set the Organization-Wide Default (OWD) for the Security_Audit__c object to Private.; Keep the Grant Access Using Hierarchies option selected for the Security_Audit__c object.

Cevap

Set the Organization-Wide Default (OWD) for the Security_Audit__c object to Private and keep the Grant Access Using Hierarchies option selected for the object.
Setting the Organization-Wide Default (OWD) to Private sets the baseline security so users can only access records they own. Keeping Grant Access Using Hierarchies enabled ensures that managerial users automatically receive access to records owned by their subordinates in the role hierarchy.

Adım Adım Çözüm

1
Determine the baseline access requirement for standard users.
Since standard users should only view and edit their own records, the Organization-Wide Default (OWD) for Security_Audit__c must be set to Private.
Organization-Wide Defaults define the most restrictive baseline access level for records an employee does not own.
2
Determine how managers should access subordinates' records.
Ensure that the Grant Access Using Hierarchies setting remains checked on the custom object.
When enabled, Grant Access Using Hierarchies automatically grants record access to users positioned above the record owner in the role hierarchy.

Anahtar Kavram

Organization-Wide Defaults (OWD) and Role Hierarchy Access Propagation
Soru 425Soru

An administrator at Global Logistics Inc. is configuring support management settings for a regional team in São Paulo. The team manages high-priority customer cases that rely on specific Case Escalation Rules during working hours. The administrator has already defined a custom Business Hours record named "LATAM Support Hours". To ensure that Brazilian national holidays pause escalation actions exclusively for LATAM cases without disrupting escalation schedules for North American cases, which two configuration steps must the administrator perform? (Select 2 options)

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

Cevabı ve açıklamayı göster

Cevap: Create the holiday records in Setup and associate them directly with the LATAM Support Hours schedule.; Specify LATAM Support Hours in the business hours criteria for the relevant Case Escalation Rule entries.

Cevap

The administrator must create holiday records in Setup and associate them directly with LATAM Support Hours, and specify LATAM Support Hours on the relevant Case Escalation Rule entries.
To pause case escalation rule timers for a specific region on holidays without affecting other regions, the administrator must create Holiday records and attach them to the regional Business Hours schedule (LATAM Support Hours), then configure the specific Case Escalation Rule entries to evaluate against that LATAM Support Hours schedule.

Adım Adım Çözüm

1
Define Holiday records and link them to Business Hours
Holidays are linked to the LATAM Support Hours schedule so time on those dates is excluded from SLA elapsed time.
Salesforce requires Holiday records to be explicitly assigned to specific Business Hours schedules to pause time calculations for that specific regional team.
2
Assign Business Hours to Case Escalation Rule Entries
The escalation rule entry evaluates case elapsed time using LATAM Support Hours and its linked holidays.
Escalation rules determine when to trigger escalation actions based on the Business Hours specified on the case, entitlement, or escalation rule entry.

Anahtar Kavram

Business Hours and Holiday Association with Case Escalation Rules
Tahmini Süre:2m 0s
Soru 426Soru

A System Administrator creates a custom object named Internal_Feedback__c with an Organization-Wide Default (OWD) set to Private. Executive leadership requires that record access for this object must NOT automatically roll up to superior roles in the role hierarchy. Which setting on the Sharing Settings page should the administrator modify to meet this requirement?

Cevabı ve açıklamayı göster

Cevap: Deselect the "Grant Access Using Hierarchies" checkbox for the Internal_Feedback__c object.

Cevap

Deselect the "Grant Access Using Hierarchies" checkbox for the Internal_Feedback__c object.
Deselecting the 'Grant Access Using Hierarchies' checkbox on the Sharing Settings page for a custom object prevents users above the record owner in the role hierarchy from automatically gaining access to those records. Standard objects always have this setting enabled and grayed out, but custom objects allow administrators to toggle it off.

Adım Adım Çözüm

1
Identify the mechanism controlling automatic vertical access inheritance for custom objects.
By default, Salesforce enables 'Grant Access Using Hierarchies' for custom objects, causing users in higher roles to automatically inherit record access granted to subordinate roles.
Understanding default hierarchy behavior helps locate the setting that disables automatic access rollout.
2
Determine how to disable vertical access propagation for custom objects on the Sharing Settings page.
Deselecting the 'Grant Access Using Hierarchies' checkbox for the specific custom object disables automatic record sharing up the role hierarchy.
This setting is configurable on custom objects, allowing administrators to restrict record visibility strictly to owners and explicitly shared users.

Anahtar Kavram

Grant Access Using Hierarchies for Custom Objects
Soru 427Soru

A Salesforce administrator at a biomedical equipment manufacturer is updating field configurations on a custom object named Medical_Device__c. The administrator needs to convert an existing custom field, Calibration_Interval_Days__c, from a Number data type to a Picklist data type to enforce standardized values. Furthermore, the administrator needs to calculate the total repair expenditure by summarizing maintenance costs from a related custom object, Maintenance_Log__c, which is currently connected to Medical_Device__c through a Lookup relationship.

Which two statements accurately describe the system impacts and requirements of implementing these changes? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Converting the custom field from Number to Picklist can result in data loss if existing numerical values do not correspond to the newly defined picklist values.; Roll-up summary fields cannot be created on Medical_Device__c to aggregate repair costs because Maintenance_Log__c is connected using a Lookup relationship.

Cevap

Converting a Number field to a Picklist field can cause data loss if existing numerical data does not match newly defined picklist entries, and Roll-up Summary fields cannot be created over Lookup relationships because they strictly require a Master-Detail relationship.
Data type conversion from Number to Picklist can cause data loss if values do not match defined picklist entries. Additionally, roll-up summary fields require a Master-Detail relationship and cannot be created on parent objects linked via Lookup relationships.

Adım Adım Çözüm

1
Analyze the implications of data type conversion from Number to Picklist.
Identified that converting data types from numeric formats to picklists poses a risk of data loss for any existing field values that do not align with the new picklist entries.
Salesforce warns of data loss when changing custom field types to Picklist from numeric or text data types.
2
Evaluate the relationship requirement for Roll-up Summary fields.
Determined that roll-up summary capability is unavailable on parent objects connected via a Lookup relationship.
Roll-up summary fields require a Master-Detail relationship between parent and child objects to aggregate values automatically.

Anahtar Kavram

Custom Field Data Type Conversion Risks and Roll-up Summary Relationship Requirements
Soru 428Soru

A Salesforce Administrator at AeroPulse Technologies is evaluating login access controls for users assigned to the Field Representative profile. The administrator needs to differentiate between Profile-level login security restrictions and Organization-wide Network Access settings. Which two statements accurately describe how Salesforce enforces these IP security controls?

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

Cevabı ve açıklamayı göster

Cevap: Defining IP ranges on the Profile restricts login completely for users outside the specified range.; Configuring IP ranges under Organization Network Access allows users outside the range to log in if they complete identity verification.

Cevap

Defining IP ranges on the Profile restricts login completely for users outside the specified range, and configuring IP ranges under Organization Network Access allows users outside the range to log in if they complete identity verification.
Profile-level IP ranges establish strict login boundaries, causing any login attempt outside the defined IP range to be denied immediately. In contrast, Organization-wide Network Access IP ranges define trusted locations where identity verification (such as SMS or email codes) is skipped; users logging in from outside org network ranges can still log in after successfully completing identity verification.

Adım Adım Çözüm

1
Analyze Profile-level Login IP Range behavior.
Profile-level Login IP Ranges enforce hard access limits. Access outside the range is blocked immediately without a verification prompt.
Profile security settings dictate exact login boundaries for users assigned to that profile.
2
Analyze Organization-level Network Access behavior.
Organization Network Access defines trusted networks. Logins from within the range bypass verification, while logins from outside require identity verification.
Org-wide network access controls verification prompts rather than hard blocking access.
3
Select the correct combination of statements.
The correct options state that Profile IP ranges hard-block access and Org Network Access controls identity verification requirements.
This correctly distinguishes between profile-level access denial and org-level trust boundaries.

Anahtar Kavram

Profile Login IP Ranges vs. Organization Network Access IP Ranges
Soru 429Soru

An administrator needs to track aggregate data on a custom parent object, Project_Tracker__cProject\_Tracker\_\_c, by showing the total estimated hours from all associated child Project_Task__cProject\_Task\_\_c records. However, when navigating to create a new custom field on Project_Tracker__cProject\_Tracker\_\_c, the Roll-Up Summary field type option is disabled. What is the primary reason for this field type being unavailable?

Cevabı ve açıklamayı göster

Cevap: The relationship between Project_Tracker__cProject\_Tracker\_\_c and Project_Task__cProject\_Task\_\_c is defined as a Lookup relationship instead of a Master-Detail relationship.

Cevap

The relationship between Project_Tracker__cProject\_Tracker\_\_c and Project_Task__cProject\_Task\_\_c is defined as a Lookup relationship instead of a Master-Detail relationship.
Salesforce natively restricts Roll-Up Summary fields to the master object in a Master-Detail relationship. When two custom objects are linked via a standard Lookup relationship, the Roll-Up Summary option is greyed out and cannot be selected until the relationship is converted to Master-Detail.

Adım Adım Çözüm

1
Identify the field requirement
The requirement calls for calculating an aggregate total (sum of hours) from child records on a parent record.
Roll-Up Summary fields perform aggregate operations (SUM, MIN, MAX, COUNT) on child records.
2
Evaluate object relationship prerequisites for Roll-Up Summary fields
Roll-Up Summary fields strictly require a Master-Detail relationship where the target parent object acts as the Master.
If objects are linked via a Lookup relationship, Salesforce disables the Roll-Up Summary field type.

Anahtar Kavram

Roll-Up Summary Field Relationship Requirements
Tahmini Süre:1m 15s
Soru 430Soru

An administrator is configuring custom functionality for an organization that tracks equipment maintenance. The Equipment_Maintenance__c custom object is currently linked to the standard Asset object via a Lookup relationship. The business requires displaying the total aggregated maintenance cost directly on the Asset record, as well as showing the parent Asset region name on the Equipment_Maintenance__c record layout.

Which two statements accurately describe the technical considerations and limitations for implementing these fields? (Select 2)

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

Cevabı ve açıklamayı göster

Cevap: Creating a standard Roll-Up Summary field on Asset to calculate total maintenance costs requires converting the Lookup relationship to a Master-Detail relationship.; A Cross-Object Formula field can be created on Equipment_Maintenance__c to display the region name from the parent Asset record.

Cevap

Standard Roll-Up Summary fields require a Master-Detail relationship on the parent object, while Cross-Object Formula fields on child records can reference fields on parent objects over Lookup relationships.
The correct options accurately reflect Salesforce object relationship behaviors: standard Roll-Up Summary fields strictly require a Master-Detail relationship (requiring conversion from Lookup), whereas Cross-Object Formula fields can easily look up values from parent records over standard Lookup relationships.

Adım Adım Çözüm

1
Evaluate the requirement for summarizing child records on the parent object.
Native Salesforce Roll-Up Summary fields can only be created on the master object in a Master-Detail relationship. Because Equipment_Maintenance__c is currently linked to Asset via a Lookup relationship, a standard Roll-Up Summary field cannot be created without converting the relationship to Master-Detail (or using custom code/flow automation).
Salesforce platform capabilities enforce Master-Detail relationships as a prerequisite for native declarative Roll-Up Summary fields.
2
Evaluate the requirement for pulling parent field values down to the child record layout.
A Cross-Object Formula field defined on Equipment_Maintenance__c can reference fields on the parent Asset object (e.g., Asset.Region__c) across lookup relationships.
Formula fields support cross-object field references pointing upward from child to parent across both Lookup and Master-Detail relationships.

Anahtar Kavram

Relationship types determine summary capabilities (Master-Detail for standard Roll-Up Summaries), whereas Cross-Object Formulas can navigate upward across Lookup relationships.
Tahmini Süre:3m 0s
Soru 431Soru

A Salesforce Administrator needs to manage the complete lifecycle of a specialized sales representative—from initial provisioning with custom permissions to executing an urgent security block and completing formal offboarding. In what order should the Administrator perform the following user management steps in Salesforce Setup?

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

Cevabı ve açıklamayı göster

Cevap

The correct sequence for managing the user lifecycle is: 1) Create the custom Permission Set, 2) Create the User record with baseline User License and Profile, 3) Assign the custom Permission Set to the User record, 4) Freeze the User account to immediately halt login access during an active security concern, and 5) Deactivate the User account to finalize offboarding and reclaim the user license.
The correct order respects standard administrative sequence and security governance: permission set metadata must be created before assignment, user records require a base profile upon creation, additive access is granted via permission set assignment, security incidents are immediately mitigated by freezing the account, and permanent offboarding concludes with deactivation to recover licenses.

Adım Adım Çözüm

1
Build the custom Permission Set in Setup with the required extra privileges.
The permission set container is created and ready for assignment.
Permission sets must exist as organizational metadata before they can be granted to user records.
2
Create the new User record, specifying required fields, User License, and base Profile.
The core user identity is established in the Salesforce instance.
A valid user record with a baseline profile is required before any additional security components can be attached.
3
Assign the custom Permission Set to the user record.
The user gains targeted permissions beyond their default profile capabilities.
Salesforce security best practices advocate for restrictive baseline profiles supplemented by permission sets for specific user role requirements.
4
Freeze the user account when a security alert occurs.
The user is immediately prevented from logging into Salesforce while keeping background user references intact.
Freezing provides an immediate stop-gap for login access during investigations without altering license counts or process dependencies.
5
Deactivate the user account after HR confirms offboarding.
Login capability is permanently disabled and the user license is returned to the active pool.
Deactivation is the standard administrative procedure for completing user offboarding.

Anahtar Kavram

Salesforce User Provisioning and Lifecycle Management (Profiles, Permission Sets, Freezing, and Deactivation)
Tahmini Süre:2m 0s
Soru 432Soru

An administrator at a medical technology company is configuring a custom data model for tracking equipment maintenance. The business requires that every maintenance log record must be linked to a master diagnostic equipment record, and deleting a diagnostic equipment record must automatically remove all associated maintenance log records. Additionally, management needs to view the total cost of all maintenance performed directly on the master diagnostic equipment record. Which two configuration steps should the administrator take to meet these requirements?

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

Cevabı ve açıklamayı göster

Cevap: Create a Master-Detail relationship field on the Equipment Maintenance object referencing the Diagnostic Machine object.; Create a Roll-Up Summary field on the Diagnostic Machine object to aggregate total costs from related Equipment Maintenance records.

Cevap

The administrator must create a Master-Detail relationship field on the Equipment Maintenance object referencing the Diagnostic Machine object, and create a Roll-Up Summary field on the Diagnostic Machine object to aggregate cost values.
Establishing a Master-Detail relationship on the child object (Equipment Maintenance) ensures that child records inherit ownership and are automatically deleted if the parent Diagnostic Machine record is deleted. Furthermore, Master-Detail relationships enable the creation of standard Roll-Up Summary fields on the parent master object to aggregate numeric values such as total maintenance costs.

Adım Adım Çözüm

1
Analyze record dependency and cascading deletion requirements.
Automatic cascading deletion requires a Master-Detail relationship rather than a Lookup relationship.
Master-Detail relationships strictly enforce parent record presence and automatically delete child records when the master record is deleted.
2
Analyze total cost aggregation requirement on the parent object.
A Roll-Up Summary field must be created on the parent Diagnostic Machine object.
Roll-Up Summary fields allow declarative SUM aggregation of child record numeric fields directly on the master object in a Master-Detail relationship.

Anahtar Kavram

Standard and Custom Object Relationships and Aggregations
Soru 433Soru

A Salesforce Administrator must temporarily prevent an employee on extended medical leave from logging into the organization. However, the user is currently configured as a default workflow user and an active record owner in multiple automated processes. Which administrative action should the administrator perform to achieve this requirement?

Cevabı ve açıklamayı göster

Cevap: Freeze the user account from the user detail page.

Cevap

Freezing the user account from the user detail page prevents the user from logging into Salesforce without disrupting existing automated workflows, scheduled jobs, or record ownership references.
Freezing a user account blocks authentication while keeping the user record, license allocation, and system process dependencies intact. This is ideal when a user is temporarily away and is referenced in active automated processes.

Adım Adım Çözüm

1
Identify the primary requirement and system constraint.
The administrator must prevent user login immediately without removing the user from active automated workflow roles.
Deactivating users who are referenced in active processes can break system automation or require transferring dependencies.
2
Evaluate the difference between freezing and deactivating a user.
Freezing blocks login access immediately while maintaining license consumption and process references. Deactivation revokes the license and requires clearing process references.
Freezing is designed specifically for temporary login restriction when deactivation is hindered by active dependencies.
3
Select the appropriate administrative step.
Navigate to the user detail page and click Freeze.
This accomplishes the requirement cleanly with a single administrative action.

Anahtar Kavram

User Freezing vs. User Deactivation
Soru 434Soru

A Salesforce Administrator needs to configure appropriate security controls to satisfy four distinct security and access requirements. Match each business requirement to the most appropriate Salesforce profile or field/object-level security mechanism.

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

Öğeler

Completely hide the Social_Security_Number__c field on the Patient object across all page layouts, reports, list views, and API queries for Intake Specialists.
Restrict the specific hours of the day during which Call Center Support Specialists assigned to a custom profile are allowed to authenticate into the org.
Grant Read and Create access on the Patient_Notes__c object to only three specific Care Coordinators who share a baseline profile with non-clinical staff.
Allow Field Technicians assigned to a custom profile to create and edit Equipment__c records, while preventing them from ever deleting any Equipment__c records regardless of ownership.

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Hiding a field globally across layouts, reports, and APIs requires Field-Level Security. Restricting login times for users on a profile requires Profile Login Hours. Selectively granting object access to a subset of users on a shared profile requires a Permission Set. Enforcing a prohibition on deleting records profile-wide requires configuring Profile Object Permissions.
Each requirement maps to its exact Salesforce security setting: Field-Level Security enforces field privacy everywhere including APIs and reports; Profile Login Hours restricts user authentication windows; Permission Sets grant additive object permissions to specific users without altering profiles; and Profile Object Permissions dictate baseline CRUD access including Delete restrictions.

Adım Adım Çözüm

1
Analyze global field visibility across reporting and API layers.
Determine that Page Layouts only control visibility on the user interface, whereas Field-Level Security enforces field privacy universally across reports, list views, and APIs.
FLS is the standard security control for field data protection.
2
Evaluate login authentication time constraints.
Identify that Profile settings include Login Hours to control authentication windows per profile.
Profile-level Login Hours enforce strict login access windows.
3
Address selective privilege expansion for a subset of users on a shared profile.
Assign a Permission Set containing Read and Create object permissions to the targeted users.
Permission Sets provide additive permissions selectively without causing profile duplication.
4
Evaluate record deletion restriction at the profile level.
Edit object permissions on the custom profile to disable the Delete permission.
Object permissions override record-level sharing for CRUD operations; disabling Delete ensures records cannot be removed.

Anahtar Kavram

Profiles and Object/Field-Level Security Controls
Soru 435Soru

A global telecommunications company uses a single baseline profile named 'Telecom Rep' for its 200 account representatives. A specialized group of 15 representatives requires access to a custom field named 'International Tax ID' on the Account object and access to the 'International Accounts' custom tab. The administrator must grant these additional permissions to only these 15 reps without affecting the baseline profile or creating redundant profiles. Which action should the administrator take to fulfill this requirement following Salesforce security best practices?

Cevabı ve açıklamayı göster

Cevap: Create a Permission Set that grants Read and Edit access to the 'International Tax ID' field and access to the 'International Accounts' tab, then assign it to the 15 representatives.

Cevap

Create a Permission Set that grants Read and Edit access to the 'International Tax ID' field and access to the 'International Accounts' tab, then assign it to the 15 representatives.
The correct approach is to create a Permission Set granting Read and Edit access to the custom field and access to the custom tab, and assign it to the 15 representatives. Permission sets are designed specifically to extend user permissions additively beyond what their baseline profile allows, keeping profile administration simple and maintainable.

Adım Adım Çözüm

1
Analyze the access requirement
Identify that 15 out of 200 users sharing a baseline profile require selective, additive field and object/tab permissions.
Salesforce security architecture relies on profiles for minimum baseline access and permission sets for additive access privileges.
2
Evaluate permission assignment mechanism
Determine that creating a dedicated Permission Set allows the administrator to grant the exact required field-level security and custom tab access to only the target 15 users.
Using permission sets avoids profile proliferation and maintains a clean, scalable security setup.
3
Assign the Permission Set
Assign the new Permission Set to the 15 enterprise representatives while leaving the baseline profile untouched for all 200 reps.
User-level permission set assignment dynamically expands capability without altering profile-wide settings.

Anahtar Kavram

Additive Permissions using Permission Sets
Soru 436Soru

A digital media agency has 80 content creators assigned to a single baseline profile named 'Content Creator'. The company recently introduced a custom object named 'Sponsor Contracts'. The system administrator needs to grant Read and Edit access for 'Sponsor Contracts' to a subset of 15 creators who manage corporate sponsorships, while keeping their base profile unchanged. Additionally, the administrator wants to simplify ongoing management by grouping these sponsorship permissions with existing specialized media permissions. Which two administrative configuration steps should the 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 a Permission Set granting Read and Edit permissions on the Sponsor Contracts object.; Add the newly created Permission Set into a Permission Set Group that consolidates relevant specialized permissions and assign the group to the 15 sponsorship creators.

Cevap

The administrator should create a Permission Set granting Read and Edit permissions on Sponsor Contracts and include it in a Permission Set Group assigned to the 15 users.
Creating a focused Permission Set grants additive Read and Edit access on the Sponsor Contracts custom object without affecting other users on the baseline profile. Including this Permission Set in a Permission Set Group consolidates permissions for cleaner, scalable user assignment.

Adım Adım Çözüm

1
Determine the strategy for additive permissions.
Identify that a Permission Set should be created for object-level access on Sponsor Contracts to avoid modifying baseline profile settings.
Profiles provide baseline access, whereas Permission Sets grant additive permissions to specific user subsets according to least privilege.
2
Consolidate permissions into a Permission Set Group.
Combine the new Sponsor Contracts Permission Set with existing specialized Permission Sets into a single Permission Set Group.
Permission Set Groups enable scalable management by bundling related permission sets into a single assignment for users.
3
Assign the Permission Set Group to the targeted users.
Assign the consolidated group to the 15 creators who handle corporate sponsorships.
This grants all required permissions in a structured manner while leaving the 65 other creators with only baseline access.

Anahtar Kavram

Additive permissions via Permission Sets and scalable management using Permission Set Groups
Soru 437Soru

Northern Trail Outfitters tracks joint vendor agreements using a custom object named Partner_Deal__c. The Organization-Wide Default (OWD) for Partner_Deal__c is set to Private. To prevent executive leadership from automatically viewing sensitive early-stage deal drafts created by junior staff, the administrator deselected the 'Grant Access Using Hierarchies' option on the custom object definition.

Management now requires Regional Sales Managers to view and edit all Partner_Deal__c records created by Sales Representatives in their respective territories, while continuing to restrict automatic access for executive roles above the Regional Managers in the hierarchy.

Which two configurations should the administrator implement to grant the necessary access without exposing records to upper executive roles? (Select 2)

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

Cevabı ve açıklamayı göster

Cevap: Create owner-based sharing rules on Partner_Deal__c to share records owned by Sales Representatives with the Regional Sales Managers role with Read/Write access.; Keep the 'Grant Access Using Hierarchies' setting deselected on the Partner_Deal__c custom object definition.

Cevap

The administrator must create owner-based sharing rules targeting the Regional Sales Managers role and maintain 'Grant Access Using Hierarchies' as deselected on the custom object definition.
When 'Grant Access Using Hierarchies' is deselected for a custom object, record access does not automatically roll up to managers or upper executive roles. To grant Regional Sales Managers access to Sales Representatives' records without exposing them to higher executive roles, an administrator must create an owner-based sharing rule targeting the Regional Sales Managers while keeping hierarchy access disabled on the object.

Adım Adım Çözüm

1
Evaluate default hierarchy access behavior for custom objects
Disabling 'Grant Access Using Hierarchies' on a custom object stops automatic record access inheritance by superior roles in the role hierarchy.
This guarantees that executive roles above Regional Sales Managers will not inherit access automatically through the role hierarchy.
2
Establish explicit lateral/vertical sharing using sharing rules
An owner-based sharing rule grants record access from records owned by Sales Representatives directly to the Regional Sales Managers role.
Sharing rules extend access beyond OWD to specific groups or roles without enabling global hierarchy inheritance.

Anahtar Kavram

Role Hierarchy and Sharing Rules with Custom Object Access Controls
Soru 438Soru

An administrator at a telecommunications company wants to create a Roll-Up Summary field on a custom object named Account_Plan__c to calculate the total amount of related custom Subscription__c records. Which object relationship configuration is required to allow the Roll-Up Summary field creation on Account_Plan__c?

Cevabı ve açıklamayı göster

Cevap: A Master-Detail relationship must be created where Account_Plan__c is the master object and Subscription__c is the detail object.

Cevap

A Master-Detail relationship must be created where Account_Plan__c is the master object and Subscription__c is the detail object.
Native Salesforce Roll-Up Summary fields can only be created on the parent object when a Master-Detail relationship links the master object to the detail object.

Adım Adım Çözüm

1
Identify the required declarative calculation feature
The requirement specifies creating a native Roll-Up Summary field on the parent custom object (Account_Plan__c).
Roll-Up Summary fields aggregate data automatically from child records.
2
Determine relationship requirements for declarative roll-up summary fields
Standard Roll-Up Summary fields can only be created on the master object of a Master-Detail relationship.
Salesforce native roll-up functionality relies strictly on the tight data binding provided by Master-Detail relationships.

Anahtar Kavram

Roll-Up Summary Relationship Requirements
Soru 439Soru

An administrator is designing a custom compliance tracking application. The requirement states that each Audit Finding record must strictly belong to a parent Vendor Audit record. If a Vendor Audit is deleted, all related Audit Findings must be automatically deleted. Additionally, executive managers require a real-time count of high-priority Audit Findings directly on the Vendor Audit record, and administrators must retain the ability to move an Audit Finding to a different Vendor Audit if it was created under the wrong audit.

Which two relationship configurations and behaviors must the administrator implement to meet these requirements? (Choose 2 answers)

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

Cevabı ve açıklamayı göster

Cevap: Create a Master-Detail relationship on the Audit Finding object pointing to Vendor Audit to enable Roll-Up Summary fields on Vendor Audit.; Enable the 'Allow reparenting' setting on the Master-Detail relationship field definition to permit reassignment of Audit Findings to another Vendor Audit.

Cevap

The administrator must create a Master-Detail relationship on the Audit Finding object referencing Vendor Audit to support Roll-Up Summary fields and cascade deletion, and explicitly enable the 'Allow reparenting' checkbox on the relationship field definition.
A Master-Detail relationship defined on the Audit Finding child object fulfills the automatic deletion requirement when a parent Vendor Audit is deleted, and enables Roll-Up Summary fields on Vendor Audit to calculate finding counts. Enabling the 'Allow reparenting' checkbox on the Master-Detail relationship field grants administrators permission to reassign an Audit Finding record to a different Vendor Audit.

Adım Adım Çözüm

1
Analyze relationship requirements for record deletion and rollup capabilities.
Determine that a Master-Detail relationship is required on Audit Finding.
Cascading deletion of child records and standard Roll-Up Summary fields are only available on Master-Detail relationships, not Lookup relationships.
2
Evaluate requirement for reassigning child records to a different parent record.
Enable 'Allow reparenting' on the Master-Detail field setup.
In Master-Detail relationships, child records are locked to their initial parent record by default unless reparenting is explicitly enabled.

Anahtar Kavram

Master-Detail Relationship Capabilities and Reparenting Configuration
Tahmini Süre:2m 0s
Soru 440Soru

An organization tracks safety compliance using custom objects. An administrator is tasked with connecting the Inspection_Audit__c object and the Compliance_Regulation__c object using a custom linking structure. The design must meet the following requirements:
1. Deleting an Inspection_Audit__c record must automatically delete all associated link records.
2. Deleting a Compliance_Regulation__c record must NOT delete associated link records, but instead clear the reference field value.
3. Executive managers must be able to view a real-time aggregate count of all linked audit regulations directly on each Inspection_Audit__c record.

Which two configuration actions should the administrator take to fulfill these requirements? Choose 2 answers.

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

Cevabı ve açıklamayı göster

Cevap: Create a Master-Detail relationship field on the link object referencing Inspection_Audit__c as the primary master.; Create a Lookup relationship field on the link object referencing Compliance_Regulation__c.

Cevap

The administrator must create a Master-Detail relationship field on the link object pointing to Inspection_Audit__c, and a Lookup relationship field on the link object pointing to Compliance_Regulation__c.
To satisfy the scenario requirements, a Master-Detail relationship must be defined on the link object pointing to Inspection_Audit__c so that child records are deleted when the audit is deleted and so that a Roll-Up Summary field can be created on Inspection_Audit__c. Concurrently, a Lookup relationship must be created on the link object pointing to Compliance_Regulation__c so that deleting a regulation does not cascade deletion to the link record.

Adım Adım Çözüm

1
Analyze cascading deletion requirements for the parent objects.
Inspection_Audit__c requires cascading deletion (Master-Detail), whereas Compliance_Regulation__c requires record preservation (Lookup).
Master-Detail relationships enforce cascading deletes from parent to child, while Lookup relationships allow child records to remain intact.
2
Determine where Roll-Up Summary fields can be created.
A Roll-Up Summary field can be placed on Inspection_Audit__c to calculate the aggregate count of child link records.
Roll-Up Summary fields require a Master-Detail relationship to summarize child records.
3
Select the correct combination of relationship fields on the junction object.
A Master-Detail field referencing Inspection_Audit__c and a Lookup field referencing Compliance_Regulation__c fulfill all business constraints.
This hybrid design allows counting child records on the audit parent while preventing unintended data loss when regulations are removed.

Anahtar Kavram

Object Relationships & Roll-Up Summary Eligibility
ÖncekiSayfa 22 / 90Sonraki
Tüm alıştırma soruları — Salesforce Certified Administrator | Examkin