Tüm alıştırma soruları

1784 soru

Soru 981Soru

An administrator converts a custom Vendor Application object page to Dynamic Forms and sets a component visibility filter to hide the sensitive 'Tax Identification Number' field unless the status is set to 'Approved'. However, a user without authorization to view tax details reports being able to view and export the 'Tax Identification Number' field using a standard Salesforce report. Which statement explains why the field remains visible in reports, and what should the administrator do to secure the field across the entire org?

Cevabı ve açıklamayı göster

Cevap: Dynamic Forms component visibility rules control UI layout presentation on Lightning pages only; Field-Level Security (FLS) must be restricted on the user profile or permission set to block access in reports and APIs.

Cevap

Dynamic Forms component visibility rules control UI presentation on Lightning Record Pages only. To restrict field data access in reports, list views, and APIs, Field-Level Security (FLS) must be configured on the user profile or assigned via permission sets.
Dynamic Forms visibility rules govern UI component rendering on Lightning Record Pages. They do not restrict backend data access. Field-Level Security (FLS) settings on profiles and permission sets control data visibility globally across reports, list views, and API calls.

Adım Adım Çözüm

1
Analyze the difference between presentation layer controls and data security controls.
Dynamic Forms visibility rules only determine whether a field component renders on a specific Lightning Record Page layout.
UI visibility filters do not alter underlying object security or data access permissions.
2
Identify why the field is visible in reports.
Standard and custom reports query the database directly subject to object permissions and Field-Level Security (FLS), bypassing Lightning page layout rules.
Since FLS was not restricted for the user, the field remains accessible in reporting features.
3
Determine the correct administrative remediation.
Update Field-Level Security on the user's profile or permission set to hide or restrict read access to the 'Tax Identification Number' field.
Field-Level Security is the primary mechanism in Salesforce for enforcing field confidentiality across all interfaces, including reports, list views, and APIs.

Anahtar Kavram

UI Presentation (Dynamic Forms Visibility) vs. Platform Data Security (Field-Level Security)
Tahmini Süre:1m 30s
Soru 982Soru

An administrator at a telecommunications enterprise is configuring Salesforce Knowledge for both internal service desk agents and external customers using an Experience Cloud site. Internal agents can view and attach articles tagged under the 'Billing & Payments' Data Category to cases. However, external customers logged into the Experience Cloud site cannot view any articles under this category, even though the 'Billing & Payments' Data Category Group visibility is set to 'All Categories' for the site member profiles and all relevant articles are published. Which configuration setting is preventing the external customers from viewing these published articles?

Cevabı ve açıklamayı göster

Cevap: The Customer channel setting is not selected on the published Knowledge article versions.

Cevap

The Customer channel setting is not selected on the published Knowledge article versions.
For an article to be visible to external portal users on Experience Cloud, it must satisfy three criteria: the user must have Read permission on Knowledge, the article must be tagged with a Data Category visible to the user's role/profile, and the article's Channel settings must explicitly include the target channel (such as 'Customer' for customer portals). If the Customer channel is not selected on the published article, it remains invisible to portal users regardless of Data Category rules.

Adım Adım Çözüm

1
Evaluate user license requirements for reading Knowledge articles
External Experience Cloud portal users only require object-level Read access on Knowledge and do not need a Knowledge User feature license to read published articles.
Feature licenses are restricted to authoring and administrative capabilities.
2
Evaluate Data Category visibility configuration
Profile-level Data Category Group visibility is set to 'All Categories', which ensures category-level security is not blocking access.
When category visibility is set to All at the profile level, users have access to all articles mapped to those categories assuming other publishing criteria are met.
3
Analyze Knowledge Article Publishing Channels
Salesforce Knowledge enforces Channel visibility (Internal App, Customer, Partner, Public KB). If the 'Customer' channel checkbox is unchecked on the article version, the article remains hidden from Experience Cloud customers despite being published and categorised.
Channel availability acts as an independent layer of visibility control alongside Data Categories and object permissions.

Anahtar Kavram

Salesforce Knowledge Article Channel Availability vs Data Category Visibility
Tahmini Süre:2m 30s
Soru 983Soru

A Salesforce administrator is setting up customer support automation for a service desk team. Which two statements correctly describe the standard capabilities of Case Assignment Rules and Case Auto-Response Rules? (Select TWO)

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

Cevabı ve açıklamayı göster

Cevap: Case Assignment Rules automatically assign newly created cases to specific users or support queues based on criteria defined in rule entries.; Case Auto-Response Rules automatically send targeted email responses to the case submitter based on specific case attributes.

Cevap

The statement that Case Assignment Rules automatically assign newly created cases to specific users or support queues based on criteria defined in rule entries, and the statement that Case Auto-Response Rules automatically send targeted email responses to the case submitter based on specific case attributes.
Case Assignment Rules assign new cases to users or queues based on case fields. Case Auto-Response Rules automatically send customized confirmation emails to the customer based on case entry criteria.

Adım Adım Çözüm

1
Identify the purpose of Case Assignment Rules.
Assignment rules specify how cases are routed to users or queues when created.
This automates initial case ownership distribution.
2
Identify the purpose of Case Auto-Response Rules.
Auto-response rules send automated confirmation emails to customers based on specified criteria upon case creation.
This provides immediate acknowledgment to customers using tailored templates.
3
Evaluate and eliminate incorrect statements regarding Case Escalation Rules.
Reassigning cases based on elapsed time or handling SLA breaches is the role of Case Escalation Rules, whereas unassigned case fallbacks are handled by the Default Case Owner.
Distinguishing initial creation rules from time-based escalation rules ensures proper Service Cloud configuration.

Anahtar Kavram

Core functions of Case Assignment Rules, Auto-Response Rules, and Escalation Rules
Tahmini Süre:1m 0s
Soru 984Soru

An administrator created a new Record Type called 'Vendor Support' on the Case object to track partner requests. Users assigned to the 'Tier 2 Support' profile report that when creating a new record using the 'Vendor Support' record type, a custom picklist field named 'Escalation Category' does not display the newly added picklist values, even though the field is visible on their assigned page layout. Which administrative action will resolve this issue?

Cevabı ve açıklamayı göster

Cevap: Edit the 'Vendor Support' record type settings to select and enable the required picklist values for the 'Escalation Category' field.

Cevap

Edit the 'Vendor Support' record type settings to select and enable the required picklist values for the 'Escalation Category' field.
In Salesforce, available picklist values must be explicitly assigned to each record type. Even if a field is visible on a page layout and accessible via Field-Level Security, the specific picklist options visible to the user are governed by the Record Type picklist configuration.

Adım Adım Çözüm

1
Identify the cause of the missing picklist options.
Recognize that picklist value availability is governed per record type independently of page layout visibility.
Creating a record type or adding new picklist values does not automatically make those values available on existing or new record types.
2
Navigate to Object Manager > Case > Record Types > Vendor Support.
Access the picklists available for editing under the specific record type.
Record type picklist assignments must be configured under the object's record type settings.
3
Edit the 'Escalation Category' picklist and add the required values to the Selected Values column.
The picklist options become available to users creating or editing records of this record type.
This updates the available values for the specified record type across all assigned profiles.

Anahtar Kavram

Record Type Picklist Value Assignment
Tahmini Süre:1m 30s
Soru 985Soru

An administrator wants field updates on Opportunity records, such as changes to the Amount and Stage fields, to automatically appear in the record feed. Which feature should the administrator enable and configure in Salesforce Setup?

Cevabı ve açıklamayı göster

Cevap: Feed Tracking

Cevap

Feed Tracking
Feed Tracking allows administrators to select specific standard or custom object fields to track. When users modify these fields, Salesforce automatically posts a change notification in the record's Chatter feed.

Adım Adım Çözüm

1
Identify the administrative requirement to show record field modifications in the Chatter feed.
Recognize that Salesforce provides a specific administration setting dedicated to tracking field updates in feeds.
Recording automated updates when key record fields change is controlled via object-level Feed Tracking.
2
Navigate to Feed Tracking settings under Chatter in Setup and enable it for the Opportunity object.
Selecting tracked fields (e.g., Amount, Stage) generates automated feed posts whenever those fields change.
Feed Tracking actively monitors up to 20 fields per object to post changes directly to record Chatter feeds.

Anahtar Kavram

Feed Tracking Configuration
Soru 986Soru

A support administrator at a medical device manufacturer sets up case automation rules. The system includes an active Case Assignment Rule that routes cases with Priority set to 'Critical' to the Urgent Tier 2 Queue, and an active Case Auto-Response Rule that sends an immediate confirmation email to the submitter when Priority is 'Critical'. During routine operations, a support agent manually opens an existing 'Medium' priority case on the record detail page, changes its Priority to 'Critical', and saves the record. However, the case remains assigned to the agent and no auto-response email is sent to the customer. Which statement accurately explains why these automated rules were not triggered by this update?

Cevabı ve açıklamayı göster

Cevap: Auto-Response Rules execute exclusively upon initial case creation, while manual record updates in the user interface require selecting the 'Assign using active assignment rule' checkbox to trigger Case Assignment Rules.

Cevap

Auto-Response Rules execute exclusively upon initial case creation, while manual record updates in the user interface require selecting the 'Assign using active assignment rule' checkbox to trigger Case Assignment Rules.
The correct answer accurately distinguishes between the execution contexts of case automation rules. Auto-Response rules fire exclusively when a case record is created. Conversely, Case Assignment rules can evaluate on record update via the user interface only when the user selects the 'Assign using active assignment rule' checkbox at the bottom of the edit layout (or if configured via page layout properties).

Adım Adım Çözüm

1
Analyze the triggering mechanism for Auto-Response Rules.
Auto-Response rules only fire during case creation (e.g., via Web-to-Case, Email-to-Case, or manual initial record save). They never execute on existing record updates.
Salesforce platform design limits auto-response emails to initial case receipt verification.
2
Analyze the UI behavior for manual Case updates regarding Assignment Rules.
When modifying an existing case via the record edit page, Case Assignment Rules do not automatically evaluate unless the 'Assign using active assignment rule' checkbox (or layout setting) is explicitly checked upon saving.
Prevents accidental reassignment of cases currently being worked on by support reps.
3
Synthesize the findings to determine why neither rule executed.
The auto-response rule did not fire because it was an update to an existing case, and the assignment rule did not fire because the re-assignment checkbox was not enabled during manual record save.
This combination of rules and standard UI execution mechanics accounts for both observed behaviors.

Anahtar Kavram

Case Automation Execution Contexts (Creation vs Update)
Soru 987Soru

A Salesforce Administrator at Pinnacle Financial is configuring a dedicated intake lifecycle for internal Compliance Audits on the Case object. The administrator created a custom page layout and a new Case record type named 'Compliance Audit'. However, when users create a Compliance Audit case, the Case Status picklist displays all standard support case statuses instead of the specific compliance audit lifecycle statuses. Which configuration step did the administrator omit?

Cevabı ve açıklamayı göster

Cevap: Creating a dedicated Support Process with the compliance status values and assigning it to the Compliance Audit record type.

Cevap

Creating a dedicated Support Process with the compliance status values and assigning it to the Compliance Audit record type.
On the Case object, available values for the Case Status field are determined by a Support Process. Creating a dedicated Support Process containing the required status values and assigning it to the Compliance Audit record type is necessary for the record type to display the correct lifecycle statuses.

Adım Adım Çözüm

1
Identify the dependency mechanism for the Case Status field on record types.
Recognize that Case Status picklist values on the Case object are controlled by Support Processes rather than standard record type picklist edits.
Salesforce uses business processes (Support Processes for Cases) to define valid lifecycle stages before binding them to record types.
2
Create the required Support Process.
Navigate to Setup > Support Processes, create a new Support Process, and select only the compliance audit status values.
This establishes the master picklist filter specific to the Compliance Audit lifecycle.
3
Associate the Support Process with the Record Type.
Assign the newly created Support Process to the 'Compliance Audit' Case Record Type.
Linking the Support Process forces the record type to display the restricted set of Case Status values.

Anahtar Kavram

Support Processes prerequisite dependency for Case Record Types
Soru 988Soru

A Salesforce Administrator is tasked with implementing a custom Service Level Agreement (SLA) for high-priority enterprise support cases. The requirement dictates enforcing a mandatory 2-hour initial response time and automatically sending an email notification to the Support Director 30 minutes before a milestone violation occurs. What is the correct sequence of administrative steps required to configure and deploy this Entitlement Process in Salesforce?

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

Cevabı ve açıklamayı göster

Cevap

The correct implementation sequence starts with creating the 'Initial Customer Response' Milestone Type in Setup, followed by creating the master Entitlement Process record, adding the Milestone with its 120-minute trigger time, configuring the 30-minute Warning Action email alert under the milestone, and finally activating the Entitlement Process.
The configuration follows Salesforce's mandatory object dependency lifecycle: global setup objects (Milestone Types) must precede process containers (Entitlement Processes), followed by child entries (Milestones and Milestone Actions), ending with process activation to lock structural changes and allow operational deployment.

Adım Adım Çözüm

1
Create the Milestone Type in Setup
The global milestone definition is established in the Salesforce org repository.
Milestone Types represent reusable SLA metrics (e.g., First Response, Resolution Time) and must exist globally before they can be assigned within an Entitlement Process.
2
Create the draft Entitlement Process master record
The container defining business hours, entry criteria, and exit criteria is created in draft status.
An Entitlement Process must be created first to act as the parent container for specific SLA rules and timeframes.
3
Add the Milestone Type to the Entitlement Process
The 120-minute target timeframe is attached to the Entitlement Process.
Adding the milestone defines when the SLA timer starts, how long it runs, and under what conditions it completes.
4
Add Warning Actions under the milestone
Automated workflow actions (email alert to Support Director at T-30 minutes) are bound to the milestone time trigger.
Milestone actions depend on the milestone's time criteria and must be configured as sub-components under the milestone definition.
5
Activate the Entitlement Process
The process transitions from draft to active, making it available for assignment to Entitlement records.
Salesforce locks active Entitlement Processes from structural milestone edits. Therefore, activation must be the final step after all milestones and workflow actions are finalized.

Anahtar Kavram

Entitlement Process and Milestone Configuration Workflow Sequence
Soru 989Soru

An administrator at Universal Containers created a custom quick action named 'Log Inspection' to allow users to quickly create records. The administrator added this action to the Global Publisher Layout so that users could access it from the Home page Chatter tab. However, sales representatives report that while 'Log Inspection' is visible on the Home page Chatter publisher, it does not appear in the Chatter publisher area on Opportunity record pages. Which configuration change should the administrator make to ensure the 'Log Inspection' quick action is available on Opportunity record pages?

Cevabı ve açıklamayı göster

Cevap: Override the predefined actions in the Salesforce Mobile and Lightning Experience Actions section of the Opportunity page layout and add the 'Log Inspection' quick action.

Cevap

Override the predefined actions in the Salesforce Mobile and Lightning Experience Actions section of the Opportunity page layout and add the 'Log Inspection' quick action.
Global Publisher Layouts populate actions on global feeds such as the Home tab, Chatter tab, and User Profile. However, action visibility on individual record pages is governed by the object's page layout. Adding the quick action to the Salesforce Mobile and Lightning Experience Actions section of the Opportunity page layout makes it visible on Opportunity record pages.

Adım Adım Çözüm

1
Analyze publisher layout scope
Identify that Global Publisher Layouts govern global locations (Home page, Chatter tab, User profile), whereas record pages are governed by object page layouts.
Actions defined globally do not automatically appear on object record pages if the object's page layout has customized actions.
2
Inspect Opportunity page layout configuration
Determine that the Opportunity Page Layout needs the custom quick action added to its Salesforce Mobile and Lightning Experience Actions list.
Customizing the page layout's Mobile & Lightning Actions section dictates which publisher and page actions appear on Opportunity record pages.
3
Confirm correct administrative action
Select the option to update the Opportunity page layout actions section.
This places 'Log Inspection' directly on the Opportunity record page publisher.

Anahtar Kavram

Publisher Layout Scope (Global vs Object Page Layouts)
Soru 990Soru

A Salesforce administrator at a maritime logistics management firm is configuring lead conversion settings to align with sales operations. The business requires that custom Lead fields representing 'Primary Freight Type' and 'Expected Annual Volume' are retained upon lead conversion by persisting their values onto the Account and Opportunity objects, respectively. Additionally, sales representatives should have the ability to suppress the automatic creation of an Opportunity when converting leads. Which two actions must the administrator take to satisfy these business requirements?

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

Cevabı ve açıklamayı göster

Cevap: Navigate to Lead Custom Field Mapping in Setup and map the custom Lead fields to custom fields of matching data types on the Account and Opportunity objects.; Select the 'Don't create a new Opportunity upon conversion by default' checkbox in Lead Conversion Settings.

Cevap

The administrator must map the custom Lead fields to custom fields of matching data types on the Account and Opportunity objects using Lead Custom Field Mapping, and select the 'Don't create a new Opportunity upon conversion by default' option in Lead Conversion Settings.
To retain lead data across conversion, custom fields on the Lead object must be mapped to custom fields of compatible data types on Account, Contact, or Opportunity via Lead Custom Field Mapping. To allow reps to skip creating an Opportunity during conversion by default, administrators enable the setting 'Don't create a new Opportunity upon conversion by default' in Lead Settings.

Adım Adım Çözüm

1
Configure custom field mapping for conversion data retention.
Ensure target custom fields exist on the Account and Opportunity objects with matching data types, then navigate to Setup > Object Manager > Lead > Fields & Relationships > Map Lead Fields to establish the mappings.
Custom lead field data is lost during conversion unless explicitly mapped to custom fields on target records.
2
Configure Opportunity creation behavior during lead conversion.
Navigate to Setup > Lead Settings (or Lead Conversion Settings) and check 'Don't create a new Opportunity upon conversion by default'.
This allows sales representatives to skip Opportunity creation when converting leads that do not yet represent qualified deals.

Anahtar Kavram

Lead Conversion Custom Field Mapping and Lead Settings
Soru 991Soru

An administrator at Northern Trail Outfitters creates a custom quick action for the Case object to log internal support notes. The administrator adds the action to the Global Publisher Layout, but support agents report that the action does not appear in the Chatter publisher area when viewing individual Case record pages. Which administrative modification will resolve this issue?

Cevabı ve açıklamayı göster

Cevap: Add the quick action to the Salesforce Mobile and Lightning Experience Actions section of the Case page layout.

Cevap

Add the quick action to the Salesforce Mobile and Lightning Experience Actions section of the Case page layout.
Global Publisher Layouts determine the actions available on non-record pages like the Home page and Chatter tab. When viewing a specific record page (such as a Case), the actions displayed in the Chatter publisher are driven by the Salesforce Mobile and Lightning Experience Actions section of that object's specific Page Layout. Adding the quick action to the Case page layout ensures it appears on Case record pages.

Adım Adım Çözüm

1
Identify the difference between Global Publisher Layouts and Object Page Layouts in Salesforce.
Global Publisher Layouts control actions on global pages (Home, Chatter tab), whereas Object Page Layouts control actions displayed on specific record pages.
The issue is specific to Case record pages.
2
Locate where record page publisher actions are configured.
In Object Manager, navigate to Case > Page Layouts and select the relevant page layout.
Page layouts override global actions when customized.
3
Add the custom quick action to the correct section.
Drag the quick action into the Salesforce Mobile and Lightning Experience Actions section of the Case page layout and save.
This exposes the action in the Chatter publisher for users viewing Case records.

Anahtar Kavram

Publisher Layouts vs. Object Page Layout Actions
Soru 992Soru

An administrator at Nexus Global Logistics is tasked with configuring a dedicated sales pipeline for a new government contracting division. The pipeline requires a distinct sequence of opportunity stages, custom probabilities, and specialized layout fields. Assuming all necessary stage picklist values have already been added to the master Stage field on the Opportunity object, place the remaining setup steps in the correct chronological execution order from first to last.

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

Cevabı ve açıklamayı göster

Cevap

The correct configuration order is: 1) Create a new Sales Process to map the active stages, 2) Create a new Opportunity Record Type associated with the Sales Process, 3) Assign the specialized Page Layout to the Record Type, and 4) Grant user Profiles or Permission Sets access to the Record Type.
In Salesforce Core Administration, the Opportunity object utilizes Sales Processes to manage the Stage picklist field. Because Opportunity Record Types depend on an existing Sales Process, an administrator must create the Sales Process first. Following Sales Process creation, the administrator creates the Opportunity Record Type and links it to the process. Page Layouts are then assigned to the Record Type across relevant profiles, and lastly, permissions/profile assignments are enabled so users can access the new Record Type.

Adım Adım Çözüm

1
Define the Sales Process
Establishes the subset of picklist values and stage flow specific to the government contracting business line.
Opportunity Record Types require a Sales Process to exist before they can be configured; Record Types cannot directly manage stage picklist selection on the Opportunity object.
2
Create the Opportunity Record Type
Links the newly defined Sales Process to page layouts and profile security.
Record Types act as the administrative container that connects a specific Sales Process with assigned Page Layouts.
3
Assign Page Layouts
Determines the user interface layout and field display for records created under this Record Type.
Page Layout assignments ensure users see relevant fields when viewing records categorized under the new Record Type.
4
Configure Access Security
Enables target users to create records with the new Record Type.
Without profile or permission set visibility enablement, users will not be able to select the new Record Type when creating opportunities.

Anahtar Kavram

Sales Process and Record Type Dependency Sequence
Soru 993Soru

A Salesforce Administrator needs to convert a custom object's standard page layout to Dynamic Forms using Lightning App Builder so that fields and sections can be managed individually. What is the correct sequence of steps the administrator must perform to complete this migration?

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

Cevabı ve açıklamayı göster

Cevap

The correct sequence begins with opening the Lightning Record Page in Lightning App Builder, selecting the standard Record Detail component on the canvas, clicking the Upgrade Now button in the properties panel to launch the wizard, selecting a source page layout to extract fields and sections, and finally setting component visibility rules before saving and activating the page.
The correct procedural order requires launching Lightning App Builder, selecting the standard Record Detail component to reveal its properties, clicking Upgrade Now to launch the migration wizard, choosing a source page layout to extract fields, and configuring component visibility filters on the separated fields prior to saving and activating the page.

Adım Adım Çözüm

1
Open the target Lightning Record Page in Lightning App Builder.
The page canvas opens in edit mode showing current components.
Page layouts and dynamic components are edited through Lightning App Builder.
2
Select the standard Record Detail component on the page canvas.
The component properties panel opens in the right sidebar.
The Dynamic Forms migration action is housed inside the Record Detail component's inspector.
3
Click the Upgrade Now button in the component inspector.
The Dynamic Forms migration wizard dialog opens.
The wizard automates the break-down of the single Record Detail component into flexible Field and Field Section components.
4
Choose the appropriate source page layout.
Existing fields and sections from the chosen page layout populate onto the canvas as individual components.
Selecting a page layout avoids having to manually re-add every field onto the new layout.
5
Configure dynamic component visibility rules as needed, then save and activate the page.
The page is published with dynamic behavior for end users.
Applying visibility rules customizes field display based on user attributes or record criteria before activation.

Anahtar Kavram

Dynamic Forms Migration Procedure in Lightning App Builder
Soru 994Soru

A support team manager at an online retail company wants customers to automatically receive a personalized confirmation email immediately after they submit a support ticket through the company's Web-to-Case form. Which Salesforce feature should an administrator configure to meet this requirement?

Cevabı ve açıklamayı göster

Cevap: Case Auto-Response Rules

Cevap

Case Auto-Response Rules should be configured to send an immediate automated email response to customers submitting cases.
Case Auto-Response Rules allow organizations to define criteria that determine which email template is automatically sent to customers who submit cases through Web-to-Case, Email-to-Case, or portals.

Adım Adım Çözüm

1
Identify the primary business requirement.
The requirement is sending an immediate automated email receipt to the customer upon case creation via Web-to-Case.
Understanding the trigger event and target audience determines which automation tool to select.
2
Evaluate standard Salesforce Case automation rule capabilities.
Case Auto-Response Rules are specifically designed to send automatic customer emails based on case criteria upon creation.
Assignment rules handle ownership routing, while escalation rules enforce SLAs over time.

Anahtar Kavram

Case Auto-Response Rules enable automatic email notifications to the person submitting a case via Web-to-Case or Email-to-Case based on record field criteria.
Tahmini Süre:45s
Soru 995Soru

A Salesforce administrator at a culinary institute is evaluating schema management rules for the organization's Salesforce environment. The system utilizes the standard Account object to track supplier facilities and a custom object named Kitchen Audit to record safety inspections. Which statement correctly describes a fundamental management capability or limitation regarding standard and custom objects?

Cevabı ve açıklamayı göster

Cevap: Standard objects cannot be deleted from the organization, whereas custom objects can be deleted if they are not referenced in components such as code or custom fields.

Cevap

Standard objects cannot be deleted from the organization, whereas custom objects can be deleted if they are not referenced in components such as code or custom fields.
Standard objects are native to Salesforce and cannot be deleted from the organization's schema (although their tabs can be hidden and standard field labels renamed). In contrast, custom objects created by administrators can be deleted as long as all dependencies, such as custom fields or Apex code, are first removed.

Adım Adım Çözüm

1
Analyze standard object management rules
Identify that standard objects (such as Account) are core components built into Salesforce and cannot be deleted from the org.
Standard objects form essential foundational schema elements of the Salesforce platform.
2
Analyze custom object management capabilities
Confirm that custom objects created by administrators can be deleted after removing dependent components like custom fields, Apex triggers, or Flow references.
Custom objects are user-defined schema extensions designed to be modifiable and removable when no longer needed.

Anahtar Kavram

Standard vs Custom Object Deletion and Schema Management Capabilities
Tahmini Süre:1m 30s
Soru 996Soru

A support manager wants to verify what level of support a customer is eligible to receive when they log a new case, such as phone support or 24/7 web coverage based on their contract. Which Salesforce Service Cloud feature should an administrator configure to represent a customer's specific support eligibility?

Cevabı ve açıklamayı göster

Cevap: Entitlements

Cevap

Entitlements
Configuring Entitlements allows support agents to view and verify the explicit type and level of customer support services a customer is entitled to receive based on their active service contract.

Adım Adım Çözüm

1
Identify the business requirement
The goal is to determine and track customer support service eligibility (such as phone or web coverage) when a customer opens a support case.
Different customers may purchase varying levels of support coverage under their service agreements.
2
Evaluate Salesforce Service Cloud capabilities
Entitlements represent units of customer support that define the support terms and eligibility for accounts, contacts, or assets.
Entitlements enable support representatives to verify whether a customer is entitled to specific support services.

Anahtar Kavram

Entitlements in Salesforce Service Cloud define and track customer support eligibility terms.
Tahmini Süre:45s
Soru 997Soru

A Salesforce Administrator needs to design a data model to establish a many-to-many relationship between a custom object named `Consultant__c` and a custom object named `Client_Project__c`. Additionally, management requires total logged hours to be automatically calculated and displayed directly on the `Client_Project__c` record. Which two configuration steps or behaviors are true for this implementation? (Choose 2 answers)

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

Cevabı ve açıklamayı göster

Cevap: A custom junction object must be created with two Master-Detail relationship fields pointing to `Consultant__c` and `Client_Project__c`.; Roll-Up Summary fields can be created on `Client_Project__c` to aggregate logged hours from the junction object records.

Cevap

To implement a many-to-many relationship with summary calculations, an administrator must create a junction object containing two Master-Detail relationship fields. Roll-Up Summary fields can then be defined on the master object to aggregate metrics from the junction object records.
Creating a custom junction object with two Master-Detail fields models the many-to-many relationship. Since `Client_Project__c` serves as a master to the junction object, Roll-Up Summary fields can be created on `Client_Project__c` to aggregate numeric values such as logged hours.

Adım Adım Çözüm

1
Identify the data modeling requirement for a many-to-many relationship.
Recognize that a junction object with two Master-Detail relationships to the master objects (`Consultant__c` and `Client_Project__c`) is required.
Salesforce achieves many-to-many functionality by placing a custom junction object between two master objects.
2
Evaluate the requirement for calculating totals on `Client_Project__c`.
Confirm that Roll-Up Summary fields can be built on `Client_Project__c` targeting fields on the junction object.
Master objects in Master-Detail relationships natively support Roll-Up Summary fields to aggregate child detail data.

Anahtar Kavram

Many-to-Many Relationships and Roll-Up Summary Capabilities
Soru 998Soru

Match each Salesforce administrative scenario related to page layouts and record types to its corresponding configuration method.

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

Öğeler

Display different fields and section arrangements on the Case object for Sales versus Support teams without restricting available picklist values.
Restrict the set of selectable Stage options for a newly introduced 'Partner Deal' sales channel on Opportunities.
Designate which Record Type is automatically selected when a specific User Profile creates a new record.
Ensure users with a single Profile view a 'Commercial' Page Layout for commercial records and an 'Individual' Page Layout for individual records.

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

The correct configuration matches each business requirement with the appropriate Page Layout, Record Type, or Profile settings page in Salesforce Setup.
Each administrative task corresponds directly to its specific setup area in Salesforce: general layout differences by profile use profile page layout assignments; picklist filtering per process occurs on the record type detail page; creation defaults are set in profile record type settings; and multi-layout rendering for a single profile across record types uses the assignment matrix.

Adım Adım Çözüm

1
Analyze requirement 1: Displaying different fields per profile without restricting picklists.
Assign distinct Page Layouts per Profile directly.
If picklist filtering is not needed, profile-to-page-layout assignment is sufficient.
2
Analyze requirement 2: Restricting picklist options for a specific process.
Edit picklists available on the target Record Type detail page.
Picklist values are customized per record type on the record type detail page.
3
Analyze requirement 3: Controlling default selection when creating records.
Configure Default Record Type under Profile Record Type Settings.
User profile settings define which record type is selected by default during creation.
4
Analyze requirement 4: Varying layouts for one profile across different record types.
Use the Page Layout Assignment matrix mapping Profile and Record Type to layouts.
The assignment matrix dictates which page layout displays for each Profile and Record Type combination.

Anahtar Kavram

Page Layouts and Record Types Assignment Matrix
Soru 999Soru

A System Administrator needs to configure Chatter Feed Tracking on a custom object named Project__c so team members can monitor key field changes. Which two rules or behaviors apply to Chatter Feed Tracking configuration? (Select TWO)

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

Cevabı ve açıklamayı göster

Cevap: Feed tracking must be enabled for the object in Setup before individual fields can be selected for tracking.; A maximum of 20 fields per object can be selected for feed tracking.

Cevap

Enabling feed tracking requires activating the object level setting before selecting fields, and Salesforce limits feed tracking to a maximum of 20 fields per object.
Chatter Feed Tracking must be enabled for the target object before selecting specific fields, and Salesforce enforces a limit of 20 tracked fields per object.

Adım Adım Çözüm

1
Identify object-level enablement requirements for Chatter Feed Tracking.
Confirm that an administrator must check 'Enable Feed Tracking' for the Project__c object before field checkboxes become available.
Object-level activation is a prerequisite for field-level feed tracking.
2
Recall system limitations for field tracking on an object.
Confirm that Salesforce allows tracking up to 20 fields per object.
This limit ensures feed performance and prevents excessive post generation.

Anahtar Kavram

Chatter Feed Tracking limits and object enablement configuration
Soru 1000Soru

BlueWave Communications maintains an Organization-Wide Default (OWD) sharing setting of Private for Cases. The support operations team needs to enable Tier 2 technical specialists and external partner consultants to collaborate on specific customer cases without granting them access to all case records. Additionally, internal support agents must be able to post internal-only notes on the Case Chatter feed that are hidden from external customer portal users who have access to the case. Which TWO features or settings should a Salesforce Administrator configure to satisfy these business requirements?

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

Cevabı ve açıklamayı göster

Cevap: Case Teams and predefined Case Team Roles with appropriate access levels (Read Only or Read/Write); Feed Item Visibility settings on Case page layouts to allow internal users to mark feed posts as Internal Only

Cevap

Configuring Case Teams with predefined Case Team Roles and enabling Feed Item Visibility on Case page layouts.
Case Teams allow administrators to define predefined roles with specified access levels (Read Only or Read/Write), enabling targeted multi-user collaboration on specific case records under a Private OWD. Furthermore, enabling Feed Item Visibility equips internal agents with the ability to mark Chatter posts and emails in the Case Feed as 'Internal Only', restricting their visibility so external community users cannot see sensitive internal communications.

Adım Adım Çözüm

1
Evaluate record sharing requirements for collaboration under Private OWD.
Identify Case Teams as the mechanism to grant explicit Read Only or Read/Write access to ad-hoc groups of users/contacts per case.
Case Teams extend record access on a case-by-case basis without altering global OWD sharing defaults.
2
Evaluate post visibility requirements on the Case Chatter feed.
Identify Feed Item Visibility as the feature to control post privacy.
Enabling Feed Item Visibility allows internal agents to toggle feed posts and emails between 'Internal Only' and visible to all users with case access.

Anahtar Kavram

Case Collaboration Tools (Case Teams and Case Feed Visibility)
ÖncekiSayfa 50 / 90Sonraki
Tüm alıştırma soruları — Salesforce Certified Administrator | Examkin