Tüm alıştırma soruları

1784 soru

Soru 901Soru

Northern Trail Outfitters configured a custom object named Billing_Account__c with two Record Types: Commercial and Individual. An administrator creates a new custom picklist field called Account_Tier__c with active values Tier 1, Tier 2, Tier 3, and Tier 4. However, when users create a Commercial Billing Account record, only Tier 1 and Tier 2 appear in the Account_Tier__c dropdown menu.

Which administrative action is required to make all four tier values selectable when creating Commercial Billing Account records?

Cevabı ve açıklamayı göster

Cevap: Edit the Account_Tier__c picklist settings under the Commercial Record Type configuration in Object Manager.

Cevap

The administrator must edit the Account_Tier__c picklist settings under the Commercial Record Type detail page in Object Manager to include Tier 3 and Tier 4 in the list of selected values.
When an object has multiple record types, each record type maintains its own subset of available picklist values for custom picklist fields. To make new or existing picklist values available to users, the administrator must navigate to Object Manager, select the specific object and Record Type, and edit the picklist field selection under 'Picklists Available for Editing'.

Adım Adım Çözüm

1
Identify the mechanism that controls picklist value availability for records.
Recognize that Record Types govern which picklist values are accessible to users when creating or editing records of that record type.
When a new picklist field is added after record types are created, new values are not automatically assigned to existing record types unless configured.
2
Navigate to Object Manager > Billing_Account__c > Record Types > Commercial.
Locate the 'Picklists Available for Editing' section for the Commercial record type.
Record Type detail pages list all custom picklists on the object and allow admins to edit available values individually.
3
Edit the Account_Tier__c picklist and move Tier 3 and Tier 4 to the Selected Values list.
All four tier options become available to users creating or editing Commercial Billing Account records.
Saving the updated record type picklist selection directly updates the available picklist choices for records using that record type.

Anahtar Kavram

Record Type Picklist Value Assignment
Soru 902Soru

An administrator at Solar West needs to optimize sales workflow efficiency for reps using the Lightning Sales Console. Reps frequently perform a repetitive series of manual actions on open opportunities: updating the stage to 'Closed Won', creating a follow-up onboarding Task, and sending a template-based email to the primary contact. Additionally, the team requires that when reps open a Contact record from an Account workspace tab, the Contact must open automatically as a subtab rather than replacing the Account tab. Which two configurations should the administrator implement to meet these business requirements? (Select 2 options)

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

Cevabı ve açıklamayı göster

Cevap: Configure a Macro in the Sales Console to automate updating the opportunity stage, creating the onboarding task, and sending the email.; Define Navigation Rules for the Sales Console app to open Contact records as subtabs of the parent Account record.

Cevap

The administrator should configure a Macro in the Sales Console to automate the multi-step record update, task creation, and email process, and set up Navigation Rules to ensure Contact records open as subtabs of the parent Account record.
Configuring a Macro empowers console users to perform sequential tasks such as updating opportunity stages, creating follow-up tasks, and sending email communications in a single action. Setting Navigation Rules in the Lightning App Builder for the console app allows administrators to define context relationships, ensuring related child records like Contacts automatically open as subtabs under primary Account workspace tabs.

Adım Adım Çözüm

1
Identify the solution for automating multi-step user actions in the console.
Recognize that Salesforce Macros in Lightning Console enable users to execute multi-step operations (field updates, task creation, sending emails) efficiently.
Macros are specifically built to streamline repetitive sales representative actions inside the console.
2
Identify the solution for managing tab hierarchy in the Sales Console.
Recognize that app Navigation Rules control whether records open as primary workspace tabs or subtabs.
Setting navigation rules ensures Contact records open directly under their parent Account tab as subtabs, keeping sales reps in context.
3
Evaluate the incorrect options.
Eliminate options involving Lead Conversion field mapping and Sales Processes.
Lead field mapping only controls data movement during conversion, and Sales Processes only filter available stage picklist values.

Anahtar Kavram

Sales Console Navigation Rules and Console Macros
Soru 903Soru

Global Logistics Inc. wants to allow external cross-functional specialists to collaborate on high-priority customer cases. The administrator needs to grant these specific specialists access to individual cases without changing the organization-wide defaults for Cases from Private or granting access to all cases across the company. Additionally, updates posted by these specialists on the Case record should be tracked cleanly. Which feature should the administrator implement to meet this requirement?

Cevabı ve açıklamayı göster

Cevap: Add the specialists to Case Teams on specific records with appropriate Case Access roles.

Cevap

Add the specialists to Case Teams on specific records with appropriate Case Access roles.
Case Teams enable flexible collaboration by allowing users to be added to specific case records with designated roles (e.g., Support Specialist) that grant Read Only or Read/Write access to the case, regardless of the default sharing settings.

Adım Adım Çözüm

1
Analyze access requirement
Access must be granted on an ad-hoc, record-by-record basis without relaxing the global Private Organization-Wide Default (OWD) for Cases.
Maintaining strict data access control requires targeted sharing mechanisms rather than broad administrative overrides.
2
Evaluate Salesforce collaboration features
Case Teams provide precise sharing controls by assigning specific users or predefined teams to individual Case records with explicit access levels (Read Only or Read/Write).
Case Teams directly fulfill ad-hoc record collaboration requirements while working alongside Case Feed for activity tracking.

Anahtar Kavram

Case Teams and Ad-Hoc Case Collaboration
Tahmini Süre:1m 15s
Soru 904Soru

A Salesforce Administrator at Cloud Prism Tech is configuring access for a newly hired compliance auditor who requires temporary read access to custom Financial Audit records and works from a dedicated remote network. The administrator must ensure proper user provisioning while following security and privilege best practices. Which TWO actions should the administrator take? (Select TWO)

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

Cevabı ve açıklamayı göster

Cevap: Assign a standard base profile to the user and grant access to the Financial Audit object using a Permission Set.; Configure Login IP Ranges directly on the user's assigned Profile to restrict or allow access strictly from the remote network location.

Cevap

The administrator should assign a standard base profile and grant Financial Audit access using a Permission Set, while configuring Profile Login IP Ranges on the profile to manage network access.
Best practices in Salesforce user provisioning require keeping profiles minimal and broad, while utilizing Permission Sets for specialized or temporary access such as auditing custom objects. Furthermore, network access control at the user profile level is enforced via Profile Login IP Ranges.

Adım Adım Çözüm

1
Determine the optimal profile and permission assignment strategy
Identify that additive object permissions for a single user should be managed via Permission Sets rather than creating a new Profile.
Profiles establish baseline access and defaults, whereas Permission Sets grant supplementary permissions flexibly.
2
Configure network security settings
Configure Profile Login IP Ranges to enforce login access boundaries from the auditor's specific remote network.
Profile-level IP restrictions define precise login boundaries for users on that profile.

Anahtar Kavram

User Provisioning via Profiles, Permission Sets, and Profile IP Ranges
Soru 905Soru

An administrator at a financial services firm is configuring a custom data model to manage vendor compliance. Each Security Audit record must be linked to a parent Vendor record. The business requirements specify that deleting a Vendor record must automatically delete all associated Security Audit records. Furthermore, compliance managers must be able to view a real-time aggregate total of completed Security Audits directly on the Vendor record detail page using standard declarative functionality.

Which relationship type should the administrator establish on the Security Audit object to fulfill these requirements?

Cevabı ve açıklamayı göster

Cevap: Create a Master-Detail relationship field on the Security Audit object referencing the Vendor object.

Cevap

Create a Master-Detail relationship field on the Security Audit object referencing the Vendor object.
Establishing a Master-Detail relationship on the Security Audit custom object with Vendor as the master satisfies both key business requirements natively: deleting a Vendor automatically cascades deletion to child Security Audit records, and administrators can immediately build a standard Roll-Up Summary field on Vendor to count related audits.

Adım Adım Çözüm

1
Analyze deletion cascade requirement
Master-Detail relationships enforce record deletion cascade, automatically deleting detail records when the master record is deleted.
Lookup relationships retain child records by default when a parent is deleted, failing the business constraint unless custom automation is built.
2
Analyze standard aggregation requirement
Native Roll-Up Summary fields are exclusively supported on the master object in Master-Detail relationships.
Standard declarative Roll-Up Summary fields cannot be created on parent records linked through Lookup relationships.
3
Determine field placement
The relationship custom field must be created on the child object (Security Audit), selecting Vendor as the master object.
In Salesforce data modeling, relationship fields are always defined on the child/detail side of the relationship.

Anahtar Kavram

Master-Detail Relationship Capabilities and Roll-Up Summary Field Dependencies
Tahmini Süre:1m 30s
Soru 906Soru

Cloud Kicks is establishing a dedicated Partner Vendor Escalation team to handle complex third-party warranty and hardware replacement cases. This team requires a customized Case lifecycle with specialized Case Status picklist values, including 'Vendor Review', 'Awaiting RMA', and 'Vendor Resolved', which must not be visible to the general Customer Support team. While creating a new Case Record Type for this team, the Salesforce Administrator notices that the required custom Case Status values cannot be selected or assigned directly within the record type picklist edit menu. Which two configuration steps must the administrator perform to make these specialized Case Status values available for the new Case Record Type? (Select 2)

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

Cevabı ve açıklamayı göster

Cevap: Create a new Support Process and select the appropriate Case Status picklist values required for the vendor escalation lifecycle.; Associate the newly created Support Process with the new Case Record Type during or after record type creation.

Cevap

The administrator must create a new Support Process containing the required custom Case Status values and then assign that Support Process to the new Case Record Type.
On the Case object, the Case Status field is controlled by Support Processes. Before custom Case Status values can be used on a specific Case Record Type, an administrator must create a dedicated Support Process that includes those status values, and then assign that Support Process to the Case Record Type.

Adım Adım Çözüm

1
Identify the dependency mechanism for Case Status picklist values.
Recognize that Case Status picklist availability is governed by Support Processes, not direct picklist edit menus on Record Types.
Salesforce enforces business process controls on stage-like fields (such as Opportunity Stage, Lead Status, and Case Status).
2
Create a customized Support Process.
Define a new Support Process containing 'Vendor Review', 'Awaiting RMA', 'Vendor Resolved', and any standard lifecycle statuses required.
A Support Process acts as the master filter for valid Case Status values.
3
Assign the Support Process to the Case Record Type.
Link the newly created Support Process to the Partner Vendor Escalation Case Record Type.
A Case Record Type requires an assigned Support Process to dictate which Case Status values are available to users.

Anahtar Kavram

Support Processes must be created before Case Record Types when customizing Case Status picklist values.
Tahmini Süre:2m 0s
Soru 907Soru

Quantum Health Systems manages medical device support cases where Organization-Wide Defaults (OWD) for the Case object are configured as Private. When a critical case is logged, a designated Tier-3 Specialist and a Compliance Manager must be granted temporary Read/Write access to the specific case record without changing ownership or granting broad object-level permissions. Furthermore, automated email notifications must alert these specialists as soon as they are assigned to assist on the case. Which administrative configuration fulfills all of these requirements?

Cevabı ve açıklamayı göster

Cevap: Define Case Team Roles with Read/Write access, configure a Predefined Case Team, and utilize an automated process or assignment workflow to add the predefined team to the case.

Cevap

Configure Case Team Roles specifying Read/Write access, build a Predefined Case Team, and automate the addition of the team to critical cases.
Predefined Case Teams combined with Case Team Roles allow administrators to grant explicit Read/Write record access to extra team members on specific cases when OWD is Private, without reassigning record ownership.

Adım Adım Çözüm

1
Analyze access requirements
Identified that specific users require explicit Read/Write access on individual records while OWD remains Private and original record ownership is preserved.
Standard record sharing mechanisms like OWD or Queues either alter record ownership or grant access too broadly.
2
Configure Case Collaboration components
Created Case Team Roles (Tier-3 Specialist, Compliance Manager) with Read/Write access and enabled record update notifications.
Case Team Roles explicitly dictate access levels (Private, Read Only, Read/Write) and notification settings for team members added to a case.
3
Group members into a Predefined Case Team and automate assignment
Predefined Case Teams allow standard groups of collaborators to be automatically added to high-priority cases via Flow or Case Assignment processes.
Predefined Case Teams streamline assigning consistent sets of specialists to complex cases while enforcing the configured access rights.

Anahtar Kavram

Case Teams and Predefined Case Teams Access Control
Soru 908Soru

Nexus Logistics utilizes a custom object named Asset_Maintenance__c to record equipment inspection reports. The Organization-Wide Default (OWD) for Asset_Maintenance__c is set to Private. Under default Salesforce security settings, regional managers can automatically view all inspection reports owned by branch supervisors below them in the role hierarchy. However, strict internal audit compliance requires that high-priority maintenance reports owned by branch supervisors be shared with the Quality Assurance team, while preventing managers higher in the role hierarchy from inheriting access to these specific records.

Which configuration change should the System Administrator make on the Asset_Maintenance__c object to satisfy these requirements?

Cevabı ve açıklamayı göster

Cevap: Deselect the 'Grant Access Using Hierarchies' setting for the Asset_Maintenance__c object in Organization-Wide Defaults, then create a criteria-based sharing rule to share high-priority records with the Quality Assurance group.

Cevap

Deselect the 'Grant Access Using Hierarchies' setting for the Asset_Maintenance__c object in Organization-Wide Defaults, then create a criteria-based sharing rule to share high-priority records with the Quality Assurance group.
For custom objects, the 'Grant Access Using Hierarchies' checkbox in Organization-Wide Defaults is enabled by default. When enabled, any record access granted to a role (via ownership or sharing rules) automatically rolls up to managers higher in the role hierarchy. Unchecking this setting disables automatic hierarchy access for the custom object, allowing criteria-based sharing rules to share records exclusively with specified groups such as Quality Assurance.

Adım Adım Çözüm

1
Analyze standard role hierarchy record access behavior for custom objects in Salesforce.
By default, Salesforce custom objects have 'Grant Access Using Hierarchies' enabled, meaning managers always inherit record access granted to lower-level roles.
To prevent managers up the role hierarchy from gaining access to records shared with or owned by subordinates, hierarchy-based access inheritance must be explicitly disabled on the custom object.
2
Disable hierarchy access propagation in Organization-Wide Defaults (OWD).
Unchecking 'Grant Access Using Hierarchies' for Asset_Maintenance__c prevents higher-level roles from automatically seeing records owned by or shared with subordinates.
This is the only setting that isolates record sharing to specifically targeted groups without propagating access upwards.
3
Define targeted record sharing using criteria-based sharing rules.
A criteria-based sharing rule evaluates fields (e.g., Priority = High) and shares matching Asset_Maintenance__c records with the Quality Assurance public group.
This grants access strictly to the required team while respecting the disabled hierarchy access.

Anahtar Kavram

Disabling 'Grant Access Using Hierarchies' on Custom Objects in Organization-Wide Defaults
Soru 909Soru

A Salesforce administrator at a bio-pharmaceutical supply firm is configuring lead conversion settings to align with sales operations. The business requires that when a sales representative converts a qualified Lead:
1. Data from a custom Lead field tracking compliance audit dates must automatically populate a corresponding custom field on the newly created Contact record.
2. Representatives must have the ability to opt out of creating an Opportunity record if one is not required.

Which two configuration steps must the administrator implement to satisfy these business requirements?

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

Cevabı ve açıklamayı göster

Cevap: Configure Lead Custom Field Mapping in Setup to map the custom compliance audit date Lead field to the custom field on the Contact object.; Instruct users to select the 'Don't create a new opportunity upon conversion' checkbox in the lead conversion window when an opportunity is not needed.

Cevap

The administrator must map the custom compliance audit date field on the Lead object to the corresponding field on the Contact object using Lead Custom Field Mapping, and instruct users to select the 'Don't create a new opportunity upon conversion' option when converting the lead.
Configuring Lead Custom Field Mapping establishes the exact data relationship required to pass custom compliance date values from the Lead to the Contact. Selecting the 'Don't create a new opportunity upon conversion' checkbox during conversion satisfies the requirement to suppress opportunity creation.

Adım Adım Çözüm

1
Determine how custom Lead field data is transferred during conversion.
Custom Lead fields must be mapped to custom Account, Contact, or Opportunity fields of compatible data types within Lead Custom Field Mapping settings.
Standard field mapping settings govern data persistence across records created during lead conversion.
2
Determine how Opportunity creation can be prevented during lead conversion.
The standard conversion interface features a checkbox option labeled 'Don't create a new opportunity upon conversion'.
This allows sales reps to convert leads into Account and Contact records without cluttering the pipeline with unnecessary Opportunities.

Anahtar Kavram

Lead Custom Field Mapping & Optional Opportunity Creation
Soru 910Soru

A Salesforce Administrator at Solaris Biotech is creating a custom price book named 'Government Healthcare Price Book' to offer discounted rates for public sector clients. However, when the administrator tries to add a newly created and activated product, 'BioScan Pro', to this custom price book, the system prevents the action. What must the administrator do to allow the product to be added to the custom price book?

Cevabı ve açıklamayı göster

Cevap: Add an active list price entry for the product in the Standard Price Book.

Cevap

Add an active list price entry for the product in the Standard Price Book.
Salesforce enforces a standard architecture requirement where a product must have an active price in the Standard Price Book before it can be included in any custom price book. Creating and activating the standard price entry resolves the issue.

Adım Adım Çözüm

1
Identify the mandatory prerequisite for custom price book entries.
Salesforce architecture requires every product to exist in the Standard Price Book with an active standard price.
Custom price books reference standard price entries as a baseline reference point.
2
Add a standard price entry to the product record.
The product 'BioScan Pro' now has an active standard price in the Standard Price Book.
This satisfies the standard architecture requirement.
3
Add the product to the custom price book.
The administrator can successfully assign 'BioScan Pro' to the 'Government Healthcare Price Book'.
With standard pricing established, custom price book entries are permitted.

Anahtar Kavram

Standard Price Book Prerequisite for Custom Price Books
Soru 911Soru

Meridian Retail Solutions requires that only three Compliance Officers out of fifty standard users have access to view and edit the sensitive Social_Security_Number__c field on the Customer__c custom object. All other standard users must be prevented from seeing or modifying this field across all interfaces and API calls. What is the recommended configuration solution a System Administrator should implement?

Cevabı ve açıklamayı göster

Cevap: Restrict Field-Level Security for the field on all base profiles, and assign a Permission Set with Read and Edit field permissions to the three Compliance Officers.

Cevap

Restrict Field-Level Security for the field on all base profiles, and assign a Permission Set with Read and Edit field permissions to the three Compliance Officers.
Field-Level Security (FLS) is the primary security feature in Salesforce to control field visibility and editing across all tools (UI, API, reports, and list views). Setting baseline FLS to hidden/restricted across standard profiles and granting explicit field access via a Permission Set ensures strict data protection while maintaining an efficient administrative structure.

Adım Adım Çözüm

1
Evaluate the security layer required for restricting a specific field
Identify that Field-Level Security (FLS) is the authoritative mechanism to control field visibility and editability across UI and API.
Record sharing (OWD) controls record access, whereas FLS controls field access within records.
2
Determine the baseline FLS setting
Remove Read and Edit access on the Social_Security_Number__c field for base profiles, including the Standard User profile.
Ensures the baseline security access restricts sensitive data for all users by default.
3
Apply additive access for the specific user group
Create a Permission Set granting Read and Edit access to Social_Security_Number__c, and assign it to the three Compliance Officers.
Permission Sets provide flexible, additive permission management without creating redundant custom profiles.

Anahtar Kavram

Field-Level Security and Permission Sets
Tahmini Süre:1m 30s
Soru 912Soru

An administrator needs to share a sales presentation stored in Salesforce Files with an external prospect who does not have a Salesforce user license. The administrator must ensure that access to the shared file automatically expires after 14 days. Which feature should the administrator use?

Cevabı ve açıklamayı göster

Cevap: Generate a Content Delivery or File Public Link and configure an expiration date.

Cevap

Generate a Content Delivery or File Public Link and configure an expiration date.
Generating a Content Delivery or File Public Link allows users to share Salesforce Files externally with individuals who do not possess a Salesforce license. It natively supports security enforcement like password protection and setting an automatic link expiration date.

Adım Adım Çözüm

1
Analyze the requirement for external file access and security controls.
Identify that the recipient does not have a Salesforce user license and requires time-limited access.
Internal security mechanisms like OWD or Permission Sets apply only to authenticated Salesforce users within the organization.
2
Select the appropriate Salesforce Content feature for sharing files with non-licensed external individuals.
Choose Content Deliveries or File Public Links with an explicit expiration date.
These features generate web URLs that can be sent to external people with options to set expiration dates and password restrictions.

Anahtar Kavram

Salesforce Files Public Links and Content Deliveries
Soru 913Soru

Apex SaaS Solutions is introducing a specialized Enterprise Subscriptions sales division alongside its existing Consulting Services team. This new division requires a unique sales pipeline with customized Opportunity stages, distinct probability percentages, and tailored page layouts. In what sequence should a System Administrator execute the administrative steps to configure Salesforce for the new Enterprise Subscriptions pipeline?

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

Cevabı ve açıklamayı göster

Cevap

The correct order of administrative steps is: 1) Add the new custom Opportunity stage picklist values, 2) Create a new Sales Process for Enterprise Subscriptions selecting the appropriate stages, 3) Create a new Opportunity Record Type and associate it with the Sales Process, and 4) Assign the new Record Type and Page Layout to relevant user profiles.
Configuring a custom sales pipeline in Salesforce enforces strict administrative dependencies. Custom stage picklist values must first be added to the master Opportunity object fields. Next, a custom Sales Process must be created to select and filter which stages apply to that specific business process. Then, an Opportunity Record Type is created and tied directly to the Sales Process. Finally, profile assignments are updated to grant user access to the new Record Type and Page Layout.

Adım Adım Çözüm

1
Define Stage Picklist Values
New stage names, probability values, and stage types become available in the master Opportunity Stage field.
Sales processes cannot reference stage values that do not yet exist in the master picklist.
2
Configure Sales Process
A customized Sales Process entity is established containing only the stages needed for Enterprise Subscriptions.
Record types on the Opportunity object rely on a Sales Process to determine stage availability rather than direct picklist assignment.
3
Build Opportunity Record Type
An Enterprise Subscriptions Record Type is created and linked directly to the Enterprise Subscriptions Sales Process.
When creating an Opportunity Record Type, selecting a pre-existing Sales Process is a mandatory field requirement.
4
Assign to Profiles & Layouts
Sales representatives in the Enterprise division gain access to create and manage opportunities with the correct pipeline stages and page layouts.
Record Type creation does not automatically grant visibility to users until explicitly assigned at the profile level.

Anahtar Kavram

Sales Process and Opportunity Record Type Dependency Sequence
Soru 914Soru

Apex Cloud Solutions is implementing Salesforce Service Cloud to manage distinct workflows for Tier 1 Technical Escalations and Billing Inquiries. Match each Salesforce administration component on the left to its corresponding functional role in configuring this Case management architecture on the right.

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

Öğeler

Support Process
Case Record Type
Page Layout
Master Case Status Picklist

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Support Process matches with defining the specific subset of Case Status picklist values; Case Record Type matches with associating a Support Process with a layout and controlling profile access; Page Layout matches with organizing fields and related lists; Master Case Status Picklist matches with maintaining the complete repository of all status values.
Each administrator component fulfills a specific role in Case configuration: Support Processes filter Case Status values for specific lifecycles; Record Types tie Support Processes to layouts and assign profile access; Page Layouts control the visual presentation of fields and components; and the Master Case Status Picklist holds all global status options.

Adım Adım Çözüm

1
Identify the primary function of a Support Process in Salesforce Case management.
Recognize that Support Processes directly control which Case Status values are available for a given support lifecycle.
Before creating a Case Record Type, a Support Process must be established to dictate the status stage progression.
2
Determine how Case Record Types tie together UI and lifecycle configurations.
Confirm that Record Types assign a Support Process along with Page Layouts to target User Profiles.
Record Types act as the administrative bridge connecting Support Processes, Page Layouts, and Profile permissions.
3
Distinguish between Page Layout responsibilities and Master Picklist definitions.
Associate Page Layouts with field organization and Master Picklists with storing all global Case Status options.
Page Layouts handle visual field positioning, whereas the master field definition stores all picklist values prior to process filtering.

Anahtar Kavram

Support Process and Case Record Type Architecture
Soru 915Soru

A System Administrator is setting up automated case management processes for a customer support team in Salesforce. Which two business requirements can be fulfilled specifically by configuring Case Escalation Rules? (Select two.)

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

Cevabı ve açıklamayı göster

Cevap: Automatically reassign an open case to a escalation queue if it remains unresolved for more than four hours.; Send notification email alerts to support managers when a high-priority case breaches its resolution timeframe.

Cevap

Case Escalation Rules are used to reassign open cases to higher-tier queues after a specified elapsed time and to send alert emails to managers when time-based SLA thresholds are exceeded.
Case Escalation Rules execute time-sensitive escalation actions when cases remain open longer than defined time limits. Valid actions include reassigning the case to a different user or queue and sending alert emails to case owners, managers, or additional recipients.

Adım Adım Çözüm

1
Identify the core purpose of Case Escalation Rules.
Escalation rules perform time-based actions (such as reassigning cases or notifying managers/owners) when a case remains open beyond specified criteria.
Escalation rules exist to enforce SLAs and prevent cases from sitting unresolved without manager awareness.
2
Distinguish Escalation Rules from Assignment and Auto-Response Rules.
Assignment Rules determine initial case ownership upon record creation, while Auto-Response Rules send automated email acknowledgments to external customers upon submission.
Each Salesforce automation rule type has a distinct execution window and functional responsibility.

Anahtar Kavram

Case Escalation Rules perform time-triggered actions on unresolved cases, such as reassigning ownership and emailing notifications when SLAs are threatened.
Soru 916Soru

A Salesforce administrator is configuring Knowledge access and article management for a support organization. Match each Salesforce Knowledge component on the left with its correct setup function on the right.

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

Öğeler

Knowledge User Feature License
Data Category Groups
Article Publication Workflow
Knowledge Record Types

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Knowledge User Feature License matches granting article management permissions; Data Category Groups match organizing articles to control visibility; Article Publication Workflow matches defining approval processes and lifecycle transitions; Knowledge Record Types match determining custom fields and page layouts for different article content types.
Each feature maps to its distinct administrative function in Salesforce Knowledge: feature licenses enable authoring abilities, data categories govern article taxonomy and visibility, publication workflows manage draft approvals, and record types specify fields and page layouts.

Adım Adım Çözüm

1
Identify the purpose of user feature licensing in Salesforce Knowledge.
Confirm that the Knowledge User license grants authoring and publishing permissions.
Users cannot create or publish articles without the Knowledge User feature license checkbox enabled on their user detail record.
2
Identify how article visibility and organization are configured.
Associate Data Category Groups with organizing and restricting article visibility.
Data categories structure knowledge bases and govern article visibility mapped to user roles or profiles.
3
Identify how article lifecycle governance is handled.
Associate Article Publication Workflows with managing drafts and approval steps.
Approval processes and publication workflows control state transitions before content goes live.
4
Identify how different article content structures are rendered.
Associate Knowledge Record Types with custom fields and layout definitions.
Record Types differentiate page layouts and fields for varied article formats like FAQs or Troubleshooting Guides.

Anahtar Kavram

Salesforce Knowledge Setup and Component Management
Soru 917Soru

A Salesforce Administrator needs to convert a custom object record page to use Dynamic Forms so fields and sections can be conditionally displayed. Arrange the steps required to migrate an existing page layout to Dynamic Forms using the Lightning App Builder into the correct sequential order.

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

Cevabı ve açıklamayı göster

Cevap

The correct sequential order begins with selecting the Record Detail component in Lightning App Builder, clicking Upgrade Now, choosing the source page layout, setting component properties and dynamic visibility rules on individual fields or sections, and finally saving and activating the page.
To migrate an existing record page to Dynamic Forms, the administrator opens the record page in Lightning App Builder and selects the Record Detail component. Clicking 'Upgrade Now' launches the migration wizard, where the administrator selects a source page layout. Once the wizard finishes converting the layout into individual Field and Field Section components on the canvas, the administrator can set conditional visibility filters and field properties. Finally, saving and activating the page makes the Dynamic Forms configuration live for assigned users.

Adım Adım Çözüm

1
Select the Record Detail component in Lightning App Builder
The right-hand properties pane updates to display component details and the upgrade prompt.
Migration to Dynamic Forms is initiated directly from the properties pane of an existing Record Detail component.
2
Click Upgrade Now
The Dynamic Forms Migration wizard opens.
The wizard automates converting monolithic page layout sections into granular Lightning components.
3
Select the source page layout in the wizard
Fields and field sections from the selected layout are placed onto the canvas as Field Section and Field components.
The selected page layout serves as the template for populating fields onto the converted canvas.
4
Configure Field Section properties and visibility filters
Specific fields or sections are set to display dynamically based on record values, user profiles, or device types.
Granular dynamic visibility can only be applied after fields are upgraded to separate canvas components.
5
Save and activate the Lightning Record Page
The page assignment takes effect for the specified apps, record types, or profiles.
Changes in Lightning App Builder are not visible to end users until the page is saved and activated.

Anahtar Kavram

Dynamic Forms Migration Workflow
Soru 918Soru

A Salesforce Administrator is designing a custom data model for an event management company to track relationships between Trade Shows (`Trade_Show__c`) and Exhibitors (`Exhibitor__c`). Multiple exhibitors can register for multiple trade shows, and each registration record must capture specific details such as Booth Location and Registration Fee. Additionally, if a trade show record is deleted, all related registration records must automatically be removed, and the administration must automatically aggregate the total registration fees collected directly on the trade show record. Which two configuration steps 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 custom junction object that contains Master-Detail relationship fields referencing both the Trade Show and Exhibitor objects.; Create a Roll-Up Summary field on the Trade Show object to sum the Registration Fee field from the related registration records.

Cevap

To model a many-to-many relationship with automatic cascade deletion and aggregate calculations, the administrator must create a custom junction object with Master-Detail relationships to both objects and create a Roll-Up Summary field on the master (Trade Show) object.
Establishing a junction object with Master-Detail relationships satisfies the requirement to model a many-to-many relationship between Trade Show and Exhibitor while providing automatic cascading record deletion. Adding a Roll-Up Summary field on the Trade Show object allows the administrator to natively sum the registration fees from the underlying child records without custom code.

Adım Adım Çözüm

1
Determine the required relationship model for Many-to-Many requirements
A custom junction object with two Master-Detail relationships allows many-to-many modeling between Trade Show and Exhibitor while enforcing cascade delete.
Master-Detail relationships cause child records to be automatically deleted when the master record is deleted.
2
Select the appropriate field type for aggregating financial metrics
Create a Roll-Up Summary field on the Trade Show object using the SUM aggregate function on the detail object's fee field.
Roll-Up Summary fields calculate values from related detail records and require a Master-Detail relationship.

Anahtar Kavram

Many-to-Many Relationships and Roll-Up Summary Requirements
Soru 919Soru

Match each Salesforce administrative configuration component related to page layouts and record types to its primary administrative function.

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

Öğeler

Page Layout Assignment Matrix
Record Type Picklist Selection
Profile Default Record Type
Page Layout Field Properties

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Page Layout Assignment Matrix pairs with mapping profile and record type combinations to page layouts; Record Type Picklist Selection pairs with restricting picklist values per record type; Profile Default Record Type pairs with setting the pre-selected record type upon creation; Page Layout Field Properties pairs with controlling field visibility, read-only/required attributes, and section ordering.
Each Salesforce administrative tool serves a distinct role in page layout and record type management: the Page Layout Assignment Matrix assigns layouts based on Profile and Record Type combinations; Record Type settings restrict available picklist values; Profile settings establish the default record type pre-selection; and Page Layouts dictate field placement and UI field rules.

Adım Adım Çözüm

1
Evaluate Page Layout Assignment Matrix function
Matched with mapping profile and record type combinations to designated page layouts.
The Page Layout Assignment setup tool uses a grid matrix of Profiles vs Record Types to assign page layouts.
2
Evaluate Record Type Picklist Selection function
Matched with restricting available picklist choices per record type.
Selecting picklist values under Record Type configuration determines which picklist values are accessible for that record type.
3
Evaluate Profile Default Record Type function
Matched with setting the pre-selected record type during record creation.
Profiles define default record type settings to streamline user workflows during new record creation.
4
Evaluate Page Layout Field Properties function
Matched with controlling field UI properties, read-only/required state, and section ordering.
Page Layouts govern page structure and UI-level field behavior.

Anahtar Kavram

Page Layouts and Record Types Assignment
Soru 920Soru

A Salesforce administrator at a marine conservation non-profit is designing a custom data model to track scientific research trips using a custom object named Research Expedition and associated findings using a custom object named Specimen Observation. The organization requires that deleting a Research Expedition record automatically deletes all related Specimen Observation records. Additionally, leadership needs a field on the Research Expedition object that automatically calculates the total number of related Specimen Observation records. Which relationship configuration should the administrator implement to meet these business requirements?

Cevabı ve açıklamayı göster

Cevap: Create a Master-Detail relationship field on the Specimen Observation object pointing to Research Expedition, and create a Roll-Up Summary field on the Research Expedition object.

Cevap

Create a Master-Detail relationship field on the Specimen Observation object pointing to Research Expedition, and create a Roll-Up Summary field on the Research Expedition object.
Creating a Master-Detail relationship field on the child object (Specimen Observation) pointing to the parent object (Research Expedition) satisfies both requirements: deleting a Research Expedition record automatically cascades and deletes all related Specimen Observation records, and native Roll-Up Summary fields can be created on the master object to calculate the total observation count.

Adım Adım Çözüm

1
Identify the parent and child objects based on the deletion and summary requirements.
Research Expedition is the master parent object, and Specimen Observation is the detail child object.
Child records must be removed upon parent deletion, and summary metrics belong on the parent record.
2
Select the appropriate relationship type.
A Master-Detail relationship is required.
Master-Detail relationships natively enforce cascading deletion of child records and enable standard Roll-Up Summary fields on the master.
3
Configure the relationship and summary fields on the correct objects.
Place the Master-Detail relationship field on Specimen Observation pointing to Research Expedition, and create the Roll-Up Summary field on Research Expedition.
Custom relationship fields are defined on the detail child object, whereas Roll-Up Summary fields are created on the master parent object.

Anahtar Kavram

Master-Detail Relationship Behavior and Roll-Up Summary Fields
Tahmini Süre:1m 30s
ÖncekiSayfa 46 / 90Sonraki
Tüm alıştırma soruları — Salesforce Certified Administrator | Examkin