Tüm alıştırma soruları

1784 soru

Soru 461Soru

An organization operates a support desk in Chicago with custom Business Hours configured from 08:00 to 17:00 CST, Monday through Friday. The administrator defined a recurring Holiday record for Independence Day. However, support managers noticed that Case Escalation Rule timers continued to advance and escalate cases on July 4th. Which TWO administrative actions are required to ensure escalation timers halt on specified holidays? (Choose 2 answers)

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

Cevabı ve açıklamayı göster

Cevap: Add the Independence Day holiday record to the Chicago Business Hours schedule.; Configure the Case Escalation Rule entries to determine how escalation times are set using Business Hours.

Cevap

To pause case escalation rule timers on holidays, the administrator must associate the Holiday record with the designated Business Hours schedule and ensure that the Case Escalation Rule entries are configured to calculate escalation times using Business Hours.
For Salesforce Case Escalation Rules to pause during holidays, the holiday record must be associated with the specific Business Hours schedule assigned to the case, and the Escalation Rule Entry must be configured to calculate escalation actions using those Business Hours.

Adım Adım Çözüm

1
Identify the relationship between Holidays and Business Hours in Salesforce.
Creating a Holiday record alone does not pause automated processes. It must be added to the relevant Business Hours record.
Business Hours define operating schedules, and Holidays linked to those Business Hours subtract non-working hours/days from escalation timer calculations.
2
Verify Escalation Rule Entry settings.
Ensure Escalation Rule Entries explicitly reference Business Hours (e.g., from Case record, specified on rule, or default).
If an Escalation Rule Entry ignores Business Hours, escalation clocks run continuously (24/7), overriding holiday configurations.

Anahtar Kavram

Business Hours and Holiday Association for Case Escalation Rules
Soru 462Soru

A Salesforce administrator is instructed to enforce strict security controls specifically for users assigned to the Call Center Representative profile. Internal compliance requires that call center representatives experience an inactivity timeout after 30 minutes of idle time and be required to change their passwords every 60 days. These requirements must override the default organization-wide settings without impacting other profiles. Which TWO actions must the administrator take to fulfill these requirements?

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

Cevabı ve açıklamayı göster

Cevap: Adjust the Session Settings section directly on the Call Center Representative profile to set the session timeout to 30 minutes.; Modify the Password Policies settings directly on the Call Center Representative profile to enforce password expiration every 60 days.

Cevap

To enforce specific session inactivity limits and password expiration rules for a targeted set of users without affecting the rest of the organization, the administrator must configure both the Session Settings and Password Policies sections directly on the relevant profile.
In Salesforce, organization-wide Session Settings and Password Policies serve as defaults for the entire organization. However, administrators can override these defaults for specific user groups by editing the Session Settings and Password Policies directly on individual Profiles.

Adım Adım Çözüm

1
Navigate to Setup and open the target Profile.
Locate the Call Center Representative profile configuration page.
Profile-level security settings allow specific user groups to have custom security policies that supersede organization-wide defaults.
2
Edit the Profile Session Settings.
Set the session timeout duration specifically to 30 minutes for this profile.
Session timeout overrides are maintained within the Profile Session Settings section.
3
Edit the Profile Password Policies.
Set the password expiration timeline specifically to 60 days for this profile.
Password expiration policies configured on a profile override the default organization password policy.

Anahtar Kavram

Profile-Level Security Overrides for Session Settings and Password Policies
Soru 463Soru

Cloud Kicks tracks recurring customer orders using a custom parent object named Subscription__c and a custom child object named Subscription_Line_Item__c, which are linked by a Master-Detail relationship. Each Subscription__c record also maintains a Lookup relationship to a standard Account record. The Salesforce Administrator needs to configure automated field calculations and data roll-ups to display total charges and cross-object metrics on the Subscription__c record.

Which TWO statements accurately describe the capabilities, limitations, and re-evaluation behaviors of Roll-Up Summary fields and Formula fields in this architectural setup? (Select 2 answers)

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

Cevabı ve açıklamayı göster

Cevap: A Roll-Up Summary field cannot be created on Subscription_Line_Item__c to summarize fields from the related Account record because Roll-Up Summary fields are only supported on the master object in a Master-Detail relationship.; A Roll-Up Summary field on Subscription__c cannot calculate a SUM using a custom formula field on Subscription_Line_Item__c if that formula field references fields on another object across a relationship.

Cevap

The two correct statements are: 1) A Roll-Up Summary field cannot be created on Subscription_Line_Item__c to summarize fields from the related Account record because Roll-Up Summary fields are only supported on the master object in a Master-Detail relationship, and 2) A Roll-Up Summary field on Subscription__c cannot calculate a SUM using a custom formula field on Subscription_Line_Item__c if that formula field references fields on another object across a relationship.
The statement explaining that roll-up summary fields cannot be created on the child object to aggregate data from the parent Account is correct because roll-up summary fields can only be created on the master object in a Master-Detail relationship. Furthermore, the statement explaining that a roll-up summary field cannot summarize a formula field containing cross-object references is correct because Salesforce explicitly blocks roll-up summaries from aggregating formula fields that pull values from span relationships across objects.

Adım Adım Çözüm

1
Analyze relationship requirements for Roll-Up Summary fields.
Roll-up summary fields can only be placed on the master object of a Master-Detail relationship. They cannot be created on detail records or on objects linked only via Lookup relationships.
Salesforce enforces master-detail relationships as a strict prerequisite for roll-up summary field creation.
2
Evaluate cross-object formula field restrictions in Roll-Up Summary calculations.
Salesforce prevents Roll-Up Summary fields from aggregating detail formula fields that contain cross-object references (e.g., formula fields referencing Account fields from Subscription_Line_Item__c).
Cross-object formula values are calculated dynamically at runtime and do not trigger database write events, preventing synchronous roll-up recalculation.
3
Evaluate relationship conversion and deletion impacts.
Converting a Master-Detail relationship to Lookup requires deleting all roll-up summary fields, and deleting a master record cascades deletion to all detail records.
Master-detail relationships control record lifecycle and cascading actions in Salesforce architecture.

Anahtar Kavram

Roll-Up Summary Fields vs Lookup Relationships and Cross-Object Formula Limitations
Soru 464Soru

A Salesforce Administrator needs to restrict access so that sales agents can log into Salesforce only when they are physically present at the corporate office. If an agent attempts to log in from an IP address outside the corporate network, the login attempt must be denied. Where should the administrator configure these IP restrictions to meet this requirement?

Cevabı ve açıklamayı göster

Cevap: Login IP Ranges on the sales agents' assigned Profile

Cevap

Login IP Ranges on the sales agents' assigned Profile
Configuring Login IP Ranges on the user Profile strictly restricts login access. Any login request originating outside the specified ranges on the profile is automatically blocked.

Adım Adım Çözüm

1
Identify the security requirement.
Logins from outside the designated corporate network must be explicitly denied.
Determines whether to use organization-wide trusted IPs or profile-based login restrictions.
2
Evaluate the behavior of Profile Login IP Ranges vs. Org Network Access.
Profile Login IP Ranges enforce login restrictions by blocking unlisted IPs, whereas Network Access only controls identity verification prompts.
Selects the feature that matches the strict denial requirement.

Anahtar Kavram

Profile Login IP Ranges vs. Network Access (Trusted IPs)
Tahmini Süre:45s
Soru 465Soru

Universal Containers is updating its user governance procedures. An administrator must fulfill two specific operational requirements:

1. A senior operations manager who is currently designated as the default user in active lead assignment rules and referenced in custom user hierarchy fields is taking a 6-month sabbatical.
2. A group of external auditors requires temporary access to confidential risk assessment records for a strict 30-day timeframe.

Which TWO administrative actions should the Salesforce Administrator take to address these requirements without disrupting system processes or compromising security? (Select TWO)

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

Cevabı ve açıklamayı göster

Cevap: Freeze the senior operations manager's user account to prevent logins during the sabbatical.; Assign the external auditors a standard profile with base permissions and grant temporary access to risk assessment records via a permission set with an expiration date.

Cevap

The administrator should freeze the manager's user account to block access while preserving automated system references, and provision the external auditors using a standard profile combined with a permission set that has a defined expiration date.
Freezing the account of the manager on sabbatical immediately blocks authentication without breaking active lead assignment rules or hierarchy references that would prevent deactivation. Using permission sets with expiration dates for the external auditors enables time-bound temporary access to specialized objects without modifying base profile assignments or requiring manual revocation.

Adım Adım Çözüm

1
Analyze the account status requirement for the manager on sabbatical.
Identified that deactivation will fail or break automated lead assignment rules and hierarchy fields because the user is actively referenced across automation settings.
Freezing blocks authentication immediately without removing license allocations or invalidating automated background process dependencies.
2
Evaluate access provisioning for the short-term risk assessment auditors.
Determined that assigning a permission set with an expiration date on top of a minimal base profile satisfies temporary privilege elevation.
Permission set expiration feature automatically revokes access after 30 days without requiring custom profile creation or manual administrative cleanup.
3
Evaluate wrong options regarding deactivation and network security.
Confirmed that deactivation disrupts process dependencies, and Network Access trusted IP ranges do not restrict login capability outside specified ranges.
Profile IP ranges restrict access strictly, whereas Network Access settings only control multi-factor/identity verification challenges.

Anahtar Kavram

User Lifecycle Management and Temporary Access Provisioning
Soru 466Soru

A Salesforce administrator at a SaaS enterprise management company is reviewing field configurations for lead conversion and custom field modifications on custom objects. Which TWO statements accurately describe the behavior and limitations of custom fields and data types in Salesforce? (Select 2)

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

Cevabı ve açıklamayı göster

Cevap: Custom Lead fields can be mapped to custom fields on the Account, Contact, or Opportunity objects during lead conversion, provided the target fields share compatible data types.; Converting a custom field type from Text to Picklist can cause data loss if existing text values exceed character limits or conflict with picklist configurations.

Cevap

Custom Lead fields must be explicitly mapped to compatible custom fields on Account, Contact, or Opportunity objects during lead conversion, and converting field data types (such as Text to Picklist) carries potential data loss risks if existing data does not comply with the new data type requirements.
Custom Lead fields require explicit mapping to compatible custom fields on Account, Contact, or Opportunity objects. Furthermore, altering a custom field's data type, such as converting from Text to Picklist, presents data loss risks if existing records contain values that exceed length parameters or fail to match picklist entries.

Adım Adım Çözüm

1
Analyze Lead field mapping rules during conversion
Confirm that custom Lead fields map to custom target fields of matching or compatible data types on Account, Contact, or Opportunity.
Salesforce Lead conversion field mapping enforces compatible data types between custom source and custom target fields.
2
Evaluate custom field data type conversion implications
Identify that converting data types (e.g., Text to Picklist) risks data loss when existing data exceeds limits or violates new validation requirements.
Salesforce alerts administrators that modifying custom field data types can result in data truncation or loss.
3
Evaluate incorrect options against Salesforce platform rules
Disqualify options suggesting direct mapping to Roll-Up Summary fields, automatic assignment of picklist values to all Record Types, or auto-mapping of custom Lead fields to standard fields.
Roll-Up Summary fields are read-only calculated fields, picklist values require explicit Record Type assignment, and custom Lead fields require manual mapping to custom target fields.

Anahtar Kavram

Custom Field Data Type Behavior and Lead Conversion Field Mapping Rules
Soru 467Soru

An organization sets the Organization-Wide Default (OWD) sharing setting for a custom object named Event_Sponsorship__c to Private, and the 'Grant Access Using Hierarchies' setting remains selected. User A is assigned to the Regional Sales Director role, which is positioned directly above User B's role of Sales Representative in the role hierarchy. If User B creates and owns a new Event_Sponsorship__c record, which users automatically gain access to this record?

Cevabı ve açıklamayı göster

Cevap: User A automatically gains access to the record because access is inherited upward through the role hierarchy.

Cevap

User A automatically gains access to the record because access is inherited upward through the role hierarchy.
In Salesforce data security, enabling 'Grant Access Using Hierarchies' on a custom object allows users situated higher in the role hierarchy to inherit the record access permissions of users beneath them. Since User A holds a role higher than User B, User A automatically receives access to records owned by User B.

Adım Adım Çözüm

1
Evaluate the Organization-Wide Default (OWD) setting and hierarchy settings for the custom object.
The OWD is set to Private and 'Grant Access Using Hierarchies' is selected for Event_Sponsorship__c.
This establishes that record access is restricted by default, but higher positions in the role hierarchy inherit access from lower positions.
2
Analyze the relative role hierarchy positions of User B (the record owner) and User A.
User A's role (Regional Sales Director) sits above User B's role (Sales Representative).
Access propagates upward along the role hierarchy chain, giving User A automatic visibility into User B's owned records.

Anahtar Kavram

Role Hierarchy Record Access Propagation
Soru 468Soru

An administrator at Universal Containers needs to display the total monetary value of all related child Service_Ticket__c records on a custom parent object named Asset_Tracker__c. The two objects are currently linked using a custom Lookup relationship. While attempting to set up the field on Asset_Tracker__c, the administrator notices that the Roll-Up Summary field type is greyed out and cannot be selected. Which statement correctly explains why the Roll-Up Summary field type is disabled in this scenario?

Cevabı ve açıklamayı göster

Cevap: Roll-Up Summary fields can only be created on the parent object in a Master-Detail relationship, not a Lookup relationship.

Cevap

Roll-Up Summary fields require a Master-Detail relationship between the parent and child objects.
In Salesforce, native Roll-Up Summary fields can only be created on the master object of a Master-Detail relationship. Because Asset_Tracker__c and Service_Ticket__c are linked via a Lookup relationship, the Roll-Up Summary field type is disabled. To resolve this, the administrator would need to convert the Lookup relationship to a Master-Detail relationship or use an automated flow/Apex solution to calculate the sum.

Adım Adım Çözüm

1
Analyze the relationship type between Asset_Tracker__c and Service_Ticket__c
The objects are connected using a Lookup relationship.
Salesforce declarative Roll-Up Summary fields are only allowed when the parent object is the master in a Master-Detail relationship.
2
Determine why the Roll-Up Summary option is unavailable in Schema Builder / Field Creation wizard
The option is disabled because no Master-Detail relationship exists with the child object.
Salesforce disables the creation of Roll-Up Summary fields on parent objects when related child records are connected only via Lookup relationships.

Anahtar Kavram

Roll-Up Summary Field Relationship Requirements
Soru 469Soru

An administrator at a financial services firm needs to grant Read and Edit access on a custom object named 'Investment Audit' to 5 wealth managers for a temporary compliance project. These 5 wealth managers share the baseline 'Wealth Advisor' profile with 50 other advisors who must not receive access to this object. Which administrative approach best fulfills this requirement while adhering to security best practices?

Cevabı ve açıklamayı göster

Cevap: Create a Permission Set that grants Read and Edit access on the Investment Audit object and assign it to the 5 wealth managers.

Cevap

Create a Permission Set that grants Read and Edit access on the Investment Audit object and assign it to the 5 wealth managers.
Permission Sets are used to grant additional permissions to specific users on top of their baseline profile. By creating a permission set with Read and Edit access on the Investment Audit object and assigning it to the 5 wealth managers, the administrator satisfies the business requirement without granting unnecessary access to the other 45 wealth advisors who share the baseline profile.

Adım Adım Çözüm

1
Analyze the access requirement and target user group
Identified that only a subset (5 out of 50 users) on the same profile requires extra permissions.
Profiles determine baseline permissions for all assigned users, so altering the profile impacts everyone.
2
Evaluate permission assignment mechanisms in Salesforce
Determined that Permission Sets are designed to grant flexible, additive permissions to individual users.
Permission sets allow administrators to extend functionality to specific users without splitting baseline profiles.
3
Select the optimal access control method
Create a dedicated Permission Set for 'Investment Audit' access and assign it to the 5 wealth managers.
This maintains a clean security model, prevents profile sprawl, and enforces the principle of least privilege.

Anahtar Kavram

Additive Access with Permission Sets
Soru 470Soru

An administrator at a commercial real estate management firm is configuring a custom object named Lease_Agreement__c to track tenant contracts linked to the standard Account object. Before finalizing the data model, the leadership team requests clarification on Salesforce system behaviors regarding object customization, standard fields, and deletion management. Which two statements correctly describe standard and custom object capabilities in this scenario? (Select 2)

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

Cevabı ve açıklamayı göster

Cevap: Standard system fields automatically created on Lease_Agreement__c, such as Created By and Last Modified By, cannot be deleted from the object, though their display labels can be customized.; Deleting the Lease_Agreement__c custom object places it and its data in the Deleted Objects list for 15 days, allowing full restoration within that timeframe, whereas standard objects cannot be deleted.

Cevap

The two correct capabilities are that standard system fields on custom objects cannot be deleted (although their labels can be renamed), and deleting a custom object places it in the Deleted Objects list for 15 days for potential restoration while standard objects cannot be deleted.
When creating custom objects in Salesforce, standard system fields such as Created By, Last Modified By, and Created Date are automatically assigned. These standard fields cannot be deleted, but administrators can rename their display labels using Rename Labels and Language Settings. Furthermore, custom objects can be deleted by an administrator, which moves the object, its metadata, and data into a soft-deleted state under Deleted Objects for 15 days before hard deletion occurs. In contrast, standard objects like Account cannot be deleted.

Adım Adım Çözüm

1
Analyze standard field behavior on custom objects
Confirm that system-generated standard fields (ID, CreatedBy, LastModifiedBy, Owner) are mandatory components of all custom objects and cannot be deleted, though their labels can be renamed via administrative tools.
Salesforce architecture enforces essential auditing and metadata fields across every object structure.
2
Evaluate object lifecycle and deletion rules for standard vs. custom objects
Confirm that custom objects support deletion with a 15-day soft-delete grace period in Deleted Objects, whereas standard objects (such as Account or Contact) cannot be deleted.
Standard objects form the core framework of the Salesforce platform and cannot be deleted.
3
Evaluate distractor capabilities regarding relationship roll-ups and standard object deletion
Identify that Roll-Up Summary fields are invalid over Lookup relationships, and standard Account objects cannot be deleted even if child records are removed.
Native Roll-Up Summary functionality strictly requires a Master-Detail relationship parent-child structure.

Anahtar Kavram

Standard vs. Custom Object Architectural Rules and Capabilities
Soru 471Soru

A Salesforce administrator is building and deploying custom Home pages in Lightning App Builder to customize the experience for different business units. Which two statements accurately describe the capabilities and activation options available for custom Home pages? (Select 2 choices)

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

Cevabı ve açıklamayı göster

Cevap: A custom Home page can be set as the Org Default for all users in the organization.; A custom Home page can be assigned as the default page for a specific Lightning App and specific User Profiles.

Cevap

Custom Home pages in Salesforce can be activated as the Org Default or assigned at the App and Profile level.
The correct answers highlight valid Home page deployment options in Salesforce. Lightning App Builder allows administrators to activate a Home page as the Org Default or target specific user roles by assigning the page to a combination of a Lightning App and specific User Profiles.

Adım Adım Çözüm

1
Review Lightning Home page activation options.
Salesforce supports three activation assignments for Home pages: Org Default, App Default, and App + Profile combination.
Home pages provide landing page experiences for apps and orgs, but do not interact with record-level constructs like Record Types.
2
Evaluate component visibility and security boundary capabilities.
Dynamic component visibility controls UI component display based on record fields or user attributes, but it is purely a display setting.
UI visibility rules do not override or modify data security mechanisms such as Field-Level Security (FLS).

Anahtar Kavram

Lightning Home Page Activation Assignments and Component Visibility Scope
Soru 472Soru

A Salesforce Administrator is designing a custom data model to manage resource allocations. A custom object named Resource_Assignment__c serves as a junction object connecting the Project__c object and the Consultant__c object. The business requirement dictates that summary reporting of total allocated hours must be displayed directly on the Project__c record, and managers must be able to move an existing assignment record from one project to another when staffing shifts occur. Which two configuration choices or system behaviors must the administrator take into account for this data model? (Select 2 answers)

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

Cevabı ve açıklamayı göster

Cevap: The relationship between Resource_Assignment__c and Project__c must be a Master-Detail relationship to support Roll-Up Summary fields on Project__c.; The Master-Detail relationship field referencing Project__c must have the 'Allow reparenting' setting enabled to permit reassigning records to a different project.

Cevap

The data model requires establishing a Master-Detail relationship to support Roll-Up Summary fields on the parent object, and the 'Allow reparenting' checkbox must be explicitly selected on the relationship field definition to allow shifting assignments between parent records.
Native Roll-Up Summary fields on custom parent objects require a Master-Detail relationship with the child object. Furthermore, because Master-Detail child records cannot be reparented by default, enabling the 'Allow reparenting' setting on the custom field definition is necessary to fulfill the requirement of moving assignment records between projects.

Adım Adım Çözüm

1
Evaluate field type requirements for summary calculations.
Determined that native Roll-Up Summary fields on parent custom objects (Project__c) are strictly limited to Master-Detail relationships.
Lookup relationships do not support native Roll-Up Summary fields on custom objects.
2
Evaluate record re-assignment requirements.
Identified that child records in a Master-Detail relationship are locked to their master record upon creation by default.
To allow moving a child assignment record to another parent project, the 'Allow reparenting' setting on the Master-Detail field must be enabled.
3
Analyze deletion and structural implications.
Confirmed that deleting a parent master record cascades deletion to all child detail records, contradicting the misconception that child records persist unlinked.
Cascading deletion is inherent to Master-Detail relationships in Salesforce.

Anahtar Kavram

Master-Detail Relationship Capabilities and Reparenting Rules
Soru 473Soru

A non-profit organization tracks community outreach using a custom object named Volunteer Assignment, which has a Master-Detail relationship with a parent custom object named Community Event. What happens to the related Volunteer Assignment records when a Community Event record is deleted?

Cevabı ve açıklamayı göster

Cevap: The related Volunteer Assignment records are automatically deleted along with the parent record.

Cevap

When a parent master record in a Master-Detail relationship is deleted, Salesforce automatically deletes all associated child detail records.
In Salesforce custom object administration, a Master-Detail relationship tightly couples the detail object to the master object. A core feature of this architecture is cascading deletion: deleting the master record automatically deletes all linked detail records.

Adım Adım Çözüm

1
Identify the relationship type between the two objects.
The relationship is defined as Master-Detail between Community Event (Master) and Volunteer Assignment (Detail).
Relationship type dictates record lifecycle, security inheritance, and deletion behavior.
2
Determine cascading deletion rules for Master-Detail relationships.
Deleting a master record automatically cascades deletion to all child detail records.
Child detail records depend entirely on the parent master record for their existence and security access.

Anahtar Kavram

Master-Detail Cascading Deletion
Soru 474Soru

An industrial manufacturing company uses a custom object named Equipment_Inspection__c to record machinery safety audits. Management mandates that plant technicians must only be able to view and edit inspection records that they personally own. However, plant managers require full read and edit access to all inspection records created by the technicians who report directly or indirectly to them. Which Organization-Wide Default (OWD) setting and configuration for Equipment_Inspection__c fulfills these requirements with the least administrative effort?

Cevabı ve açıklamayı göster

Cevap: Set Default Internal Access to Private and keep 'Grant Access Using Hierarchies' selected.

Cevap

Set Default Internal Access to Private and keep 'Grant Access Using Hierarchies' selected.
Setting the Organization-Wide Default to Private ensures that plant technicians can only view and edit records they own. Leaving 'Grant Access Using Hierarchies' selected ensures that managers higher in the role hierarchy automatically inherit read and edit access to records owned by their subordinates.

Adım Adım Çözüm

1
Determine the baseline access requirement for the most restricted users (plant technicians).
Since technicians should only see records they own, the baseline Organization-Wide Default (OWD) must be set to Private.
OWD defines the most restrictive baseline access for records an individual user does not own.
2
Evaluate how managerial access up the role hierarchy should be granted.
By keeping 'Grant Access Using Hierarchies' enabled, users above the record owner in the role hierarchy inherit the owner's access automatically.
Role hierarchy access grants managers read and edit capabilities for subordinate records without needing extra sharing rules.

Anahtar Kavram

Organization-Wide Defaults (OWD) and Role Hierarchy Access
Tahmini Süre:1m 30s
Soru 475Soru

A Salesforce administrator needs to ensure that users assigned to the Support Specialist profile can view the Social_Security_Number__c field on the Contact object, but are strictly prevented from editing it across all user interfaces, reports, and API integrations. Which security mechanism should the administrator configure to satisfy this requirement?

Cevabı ve açıklamayı göster

Cevap: Configure Field-Level Security (FLS) on the Social_Security_Number__c field to Read-Only for the Support Specialist profile.

Cevap

Configure Field-Level Security (FLS) on the Social_Security_Number__c field to Read-Only for the Support Specialist profile.
Field-Level Security (FLS) is the authoritative standard in Salesforce for restricting access to individual fields. Setting a field to Read-Only for a profile ensures users assigned to that profile can view the field value but cannot create or update values in that field regardless of where they interact with Salesforce (UI, API, reports, or tools).

Adım Adım Çözüm

1
Identify the level of security required.
The requirement specifies preventing edits across all interfaces, reports, and API integrations.
UI-only settings like page layouts or Dynamic Forms do not secure data at the API or report level.
2
Select the appropriate security control feature.
Field-Level Security (FLS) overrides page layout settings and enforces field access across the entire platform.
Setting FLS to Read-Only on the target profile guarantees users can read the field data but cannot modify it anywhere in Salesforce.

Anahtar Kavram

Field-Level Security (FLS) vs. UI Layout Controls
Soru 476Soru

A Salesforce Administrator is reviewing custom field capabilities to fulfill data reporting requirements on related objects. Which two statements accurately describe the behavior and requirements of Roll-Up Summary fields and Formula fields? (Select 2)

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

Cevabı ve açıklamayı göster

Cevap: Roll-Up Summary fields can only be defined on the master object of a Master-Detail relationship to calculate values from child records.; Cross-object formula fields can reference data from parent records connected through either a Lookup or a Master-Detail relationship.

Cevap

Roll-Up Summary fields require a Master-Detail relationship on the master object, and cross-object formula fields can reference parent fields across both Lookup and Master-Detail relationships.
The correct statements recognize that Roll-Up Summary fields strictly require a Master-Detail relationship on custom objects and must reside on the master object, whereas cross-object formula fields can access parent data regardless of whether the underlying relationship is a Lookup or Master-Detail.

Adım Adım Çözüm

1
Evaluate relationship requirements for Roll-Up Summary fields
Confirm that native Roll-Up Summary fields require a Master-Detail relationship and must reside on the master side.
Lookup relationships do not support native roll-up functionality without custom development or automation tools.
2
Evaluate capabilities of cross-object Formula fields
Confirm that cross-object formulas can span parent records over both Lookup and Master-Detail links.
Salesforce formula syntax allows traversing child-to-parent relationship fields regardless of whether the link is a Lookup or Master-Detail.

Anahtar Kavram

Roll-Up Summary vs Cross-Object Formula Relationship Dependencies
Soru 477Soru

Apex Global Logistics tracks cargo shipments using a custom object named `Shipment_Manifest__c`. The Organization-Wide Default (OWD) for `Shipment_Manifest__c` is set to Private, and the Grant Access Using Hierarchies setting has been explicitly deselected on the object for strict security compliance.

The system administrator is tasked with meeting two new record access requirements:
1. The VP of Operations must be able to view all `Shipment_Manifest__c` records created by users assigned to the Dispatch Manager role.
2. A cross-departmental Compliance Audit Team must have Read/Write access to any `Shipment_Manifest__c` record where the `Hazardous_Material__c` checkbox field is set to True.

Which two administrative configurations should be implemented to meet these requirements while maintaining the principle of least privilege? (Select 2 options)

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

Cevabı ve açıklamayı göster

Cevap: Create an owner-based sharing rule on `Shipment_Manifest__c` that shares records owned by members of the Dispatch Manager role with the VP of Operations role.; Create a criteria-based sharing rule on `Shipment_Manifest__c` where `Hazardous_Material__c = True` that grants Read/Write access to a Public Group containing the Compliance Audit Team.

Cevap

The administrator must create an owner-based sharing rule to share records owned by the Dispatch Manager role with the VP of Operations role, and create a criteria-based sharing rule for Hazardous_Material__c = True granting Read/Write access to a Public Group containing the Compliance Audit Team.
The correct solution involves two distinct sharing rule configurations. First, because 'Grant Access Using Hierarchies' has been unchecked on the custom object's Organization-Wide Defaults, managers do not automatically gain access to subordinate records; thus, an owner-based sharing rule must be created to share records owned by the Dispatch Manager role with the VP of Operations role. Second, access based on field values (such as Hazardous_Material__c = True) requires a criteria-based sharing rule targeting a Public Group that contains the Compliance Audit Team members.

Adım Adım Çözüm

1
Analyze the impact of deselecting 'Grant Access Using Hierarchies' on a custom object.
When 'Grant Access Using Hierarchies' is deselected on a custom object in OWD, users higher in the role hierarchy no longer automatically inherit access to records owned by or shared with their subordinates.
To grant the VP of Operations access to records owned by Dispatch Managers without altering the object-level OWD hierarchy setting, an owner-based sharing rule target vector must be established.
2
Determine the optimal mechanism for sharing records based on record field values across departments.
Criteria-based sharing rules allow sharing records meeting specific field criteria (e.g., Hazardous_Material__c = True) with specific Public Groups, Roles, or Territories.
Creating a Public Group for the Compliance Audit Team and linking it to a criteria-based sharing rule fulfills the cross-departmental access requirement adhering to least privilege.
3
Evaluate distractors against least privilege and system architecture boundaries.
'View All' permission grants global record visibility ignoring sharing rules, which violates least privilege. 'Grant Access Using Hierarchies' is an object-level setting, not a role-level property.
Eliminates incorrect configuration choices.

Anahtar Kavram

Interaction between Custom Object OWD Hierarchy Toggles, Owner-Based Sharing Rules, and Criteria-Based Sharing Rules
Soru 478Soru

Apex Language Services utilizes a custom object named Translation_Project__c with an Organization-Wide Default (OWD) setting set to Private. The administrator needs to fulfill two record access requirements: managers must automatically view records owned by their direct subordinates in the role hierarchy, and members of the Quality Assurance team must be able to view all records owned by the Sales team. Which TWO configuration actions should the administrator take to meet these requirements?

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

Cevabı ve açıklamayı göster

Cevap: Verify that the Grant Access Using Hierarchies checkbox is selected for the Translation_Project__c object.; Create an owner-based sharing rule that grants Read access on Translation_Project__c to the Quality Assurance role or group for records owned by the Sales role.

Cevap

The administrator should verify that Grant Access Using Hierarchies is enabled for Translation_Project__c and create an owner-based sharing rule to share records owned by the Sales role with the Quality Assurance team.
The requirement has two parts: managerial access and cross-functional team access. Keeping 'Grant Access Using Hierarchies' enabled satisfies the requirement for managers to view subordinate records automatically. Creating an owner-based sharing rule selectively extends access from records owned by the Sales role to members of the Quality Assurance team without opening up access to the entire organization.

Adım Adım Çözüm

1
Analyze managerial access requirement within the role hierarchy
Enabling 'Grant Access Using Hierarchies' on custom objects automatically allows users higher in the role hierarchy to access records owned by subordinates.
This provides standard upward access without needing additional sharing rules.
2
Analyze lateral team access requirement between Sales and Quality Assurance
An owner-based sharing rule defined from the Sales role/hierarchy to the Quality Assurance role/group opens access specifically for those teams.
When OWD is Private, sharing rules extend access to specified groups of users based on record ownership.

Anahtar Kavram

Role Hierarchy and Owner-Based Sharing Rules
Soru 479Soru

An administrator is building a grant management application and needs to link a parent object, Funding_Program__c, to a child object, Grant_Application__c. The administrator establishes a Master-Detail relationship on Grant_Application__c pointing to Funding_Program__c.

Which two technical capabilities or behaviors are characteristic of this Master-Detail relationship? (Choose 2 answers)

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

Cevabı ve açıklamayı göster

Cevap: Detail records automatically inherit the security and sharing settings of the parent master record.; The administrator can create Roll-Up Summary fields on the Funding_Program__c object to aggregate data from child records.

Cevap

Detail records inherit the security and sharing settings of the parent master record, and Roll-Up Summary fields can be created on the master object to aggregate child record data.
Establishing a Master-Detail relationship ensures that detail records derive their security, visibility, and access directly from the master record. Additionally, it enables administrators to configure native Roll-Up Summary fields on the master object to summarize child record values such as count or total amounts.

Adım Adım Çözüm

1
Analyze the security model of Master-Detail relationships.
Confirm that child records inherit visibility, sharing rules, and ownership from the master record.
Master-Detail relationships do not have independent Owner fields on child records; access is entirely driven by master record access.
2
Evaluate data aggregation capabilities.
Confirm that Roll-Up Summary fields are supported on the parent master object.
Roll-Up Summary fields require a Master-Detail relationship to calculate SUM, COUNT, MIN, or MAX operations on detail records.
3
Evaluate cascading behavior and lookup limitations to eliminate incorrect choices.
Identify that master deletion cascades to detail records and that lookups do not support native roll-up summaries.
Deleting a master record removes all detail records automatically, and lookup relationships lack native roll-up summary functionality.

Anahtar Kavram

Master-Detail Relationship Capabilities and Behaviors
Soru 480Soru

An organization headquartered in San Francisco (PST) expands customer support operations with a dedicated team in London (GMT). The administrator creates a custom Business Hours record for the London team (09:00 to 17:00 GMT, Monday through Friday) and sets up a Case Escalation Rule to escalate unresolved high-priority cases after 4 hours. However, cases assigned to the London team are escalating based on the organization's default PST schedule instead of London business hours. Which configuration change must the administrator make to resolve this issue?

Cevabı ve açıklamayı göster

Cevap: Specify the London custom Business Hours schedule directly on the Case Escalation Rule Entry.

Cevap

Specify the London custom Business Hours schedule directly on the Case Escalation Rule Entry.
Escalation rules calculate time thresholds using business hours. To enforce a specific regional schedule, the administrator must configure the rule entry to explicitly specify the custom Business Hours record created for that region.

Adım Adım Çözüm

1
Analyze the escalation issue
Escalation rules default to using the organization's Default Business Hours unless a specific Business Hours criteria is explicitly designated on the rule entry or case record.
By default, Salesforce uses the org-wide default business hours for escalation calculations.
2
Identify the proper administrative solution
Edit the Case Escalation Rule Entry and select the custom London Business Hours record.
Explicitly linking the regional business hours to the escalation rule entry ensures the escalation clock runs only during London operating hours.

Anahtar Kavram

Case Escalation Rule Business Hours Assignment
Tahmini Süre:1m 30s
ÖncekiSayfa 24 / 90Sonraki
Tüm alıştırma soruları — Salesforce Certified Administrator | Examkin