Tüm alıştırma soruları

1784 soru

Soru 281Soru

An analytics manager at a global technology firm needs a single reporting view to evaluate Account performance across two disparate operational areas: active Sales Opportunities and open Customer Support Cases. The report must group records by Account Name and present independent summary totals and distinct column layouts for Opportunities and Cases side-by-side within the same report structure. Which report format or feature should the Salesforce Administrator select to fulfill this requirement?

Cevabı ve açıklamayı göster

Cevap: Joined Report format using separate blocks for Opportunities and Cases grouped by the common Account field

Cevap

The Joined Report format using separate blocks for Opportunities and Cases grouped by the common Account field is the correct selection.
The Joined Report format is specifically designed to combine up to five distinct report blocks from different standard or custom report types into a single view. When grouped by a common object or field (such as Account Name), each block displays its own unique field columns, summary totals, and layout rules side-by-side.

Adım Adım Çözüm

1
Analyze the reporting requirement across disparate objects
Identified that Opportunities and Cases are two separate child objects associated with Account.
Standard custom report types generally focus on a single primary object and its related child hierarchy.
2
Evaluate report format capabilities for side-by-side multi-type layouts
Joined reports permit adding multiple report blocks (up to 5) originating from different report types.
Each block maintains its own columns, summary fields, and formulas while sharing a common principal grouping field like Account Name.
3
Verify common grouping compatibility
Grouping all blocks by the common Account field creates the required side-by-side unified account performance view.
Common fields allow Joined report blocks to align horizontally by the shared entity.

Anahtar Kavram

Joined Report capabilities and common object grouping
Soru 282Soru

A Salesforce System Administrator at Cloud Kicks is designing an Opportunity report grouped by Account Name and Opportunity Stage. The business requires two specific calculations within the report:
1. Evaluating the elapsed duration in days between Created Date and Close Date for each individual opportunity record.
2. Calculating the percentage of total opportunity amount contributed by each Stage grouping relative to the parent Account Name grouping total.

Which two statements accurately describe the correct technical approach to fulfill these reporting requirements? (Select 2)

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

Cevabı ve açıklamayı göster

Cevap: A row-level formula must be created on the report to calculate the duration in days between Created Date and Close Date for each individual record.; A summary formula utilizing the PARENTGROUPVAL function must be created to calculate the percentage contribution of each Stage relative to its parent Account Name grouping.

Cevap

To satisfy the requirements, the administrator must create a row-level formula for the individual record duration calculation and a summary formula utilizing the PARENTGROUPVAL function to evaluate the stage subtotal percentage relative to the parent account grouping.
The solution requires two distinct report formula types based on evaluation context. First, evaluating record-level date differences requires a row-level formula because row-level formulas process individual detail records. Second, computing the ratio of a subgroup subtotal to its parent group total requires a summary formula with the PARENTGROUPVAL function, which explicitly references parent grouping values in report structures.

Adım Adım Çözüm

1
Analyze requirement 1 (record-level duration in days).
Since the calculation must be evaluated for each individual opportunity record row, a row-level formula is required.
Row-level formulas calculate values on detail rows record-by-record, whereas summary formulas only evaluate aggregated group rows.
2
Analyze requirement 2 (subgroup stage amount relative to parent account total).
Because this calculation compares a subgroup summary to its parent group summary, a summary formula using PARENTGROUPVAL is required.
PARENTGROUPVAL retrieves aggregated metric values from a specified parent group level to compute ratios or proportions across report hierarchy levels.
3
Evaluate distractor configurations against Salesforce platform limits.
Summary formulas cannot be used on detail rows, and roll-up summary fields cannot be created across lookup relationships.
Summary formulas lack detail row context, and declarative roll-up summary fields strictly mandate a master-detail relationship structure on standard/custom objects.

Anahtar Kavram

Distinguishing Row-Level vs. Summary Formulas and PARENTGROUPVAL Grouping Calculations
Soru 283Soru

A Salesforce Administrator at Cloud Kicks needs to set up an SLA management workflow using Entitlements and Milestones to ensure critical cases meet response time commitments. In what order should the administrator execute the administrative steps to build, configure, and apply this SLA 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 begins with creating the Milestone Types in Setup, followed by creating the Entitlement Process container, adding milestones and milestone actions to the process, activating the process, and finally assigning the active process to Entitlement records.
The proper administrative workflow in Salesforce requires creating master setup elements first (Milestone Types), assembling the process structure (Entitlement Process and its Milestone Actions), locks/enables the setup (Activation), and finally connecting the configuration to transactional data (Entitlement Records).

Adım Adım Çözüm

1
Create Milestone Types in Setup
Master SLA milestone records (such as 'First Response Time') become available for selection.
Salesforce requires milestone definitions to exist prior to adding them within an entitlement process.
2
Create the Entitlement Process container
An un-activated process shell with entry criteria and business hours is established.
Process-level properties must be set before defining specific milestone timelines and actions.
3
Add milestones and configure warning/violation actions
Time limits, business hour logic, and automated actions (field updates/email alerts) are tied to the process.
Milestone actions enforce SLA compliance triggers for warning or breach events.
4
Activate the Entitlement Process
The entitlement process becomes immutable and available for lookup assignment.
Unactivated entitlement processes cannot be assigned to customer entitlement records.
5
Assign the Entitlement Process to customer Entitlement records
Cases linked to the entitlement automatically trigger the milestone tracking workflows.
Entitlement processes take effect on support cases only when linked through customer entitlements.

Anahtar Kavram

Entitlement Process and Milestone Configuration Sequence
Soru 284Soru

A Salesforce administrator is tasked with executing several distinct data operations across standard and custom objects. Match each administrative requirement to the most appropriate data utility or operational mode.

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

Öğeler

Importing 30,000 Lead records while executing active lead assignment rules and detecting existing duplicate contact records.
Permanently deleting 80,000 obsolete custom log records to free storage space without sending them to the Recycle Bin.
Upserting 120,000 Opportunity records overnight via an automated, scheduled background script.
Exporting 400,000 Product records manually to a CSV file for a quarterly pricing audit.

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

1. Importing 30,000 Lead records with assignment rules matches Data Import Wizard.
2. Permanently deleting 80,000 records matches Data Loader Desktop Client (Bulk API with Hard Delete enabled).
3. Upserting 120,000 Opportunity records via automated script matches Data Loader Command Line Interface (CLI).
4. Exporting 400,000 Product records matches Data Loader Desktop Client (Standard Data Export).
The correct pairings evaluate tool capabilities based on record volume limits, object support, workflow/assignment rule execution, deletion types, and automation capability.

Adım Adım Çözüm

1
Analyze requirement 1 (30,000 Leads, assignment rules, duplicate matching)
Identify that record count is under 50,000, object is supported (Leads), and feature requirements (assignment rules, duplicate matching) are native to Data Import Wizard.
Data Import Wizard is the only tool that can trigger workflow rules and lead assignment rules directly during import.
2
Analyze requirement 2 (80,000 custom log records, permanent hard delete)
Identify that record count exceeds 50,000 and requires Hard Delete capabilities.
Hard Delete is only supported in Data Loader when Bulk API is enabled, bypassing the Recycle Bin.
3
Analyze requirement 3 (120,000 Opportunity records, automated scheduled overnight batch)
Identify that Opportunity object and 120,000 volume require Data Loader, and automation requires CLI execution.
Data Import Wizard does not support Opportunities or CLI/scheduled background execution.
4
Analyze requirement 4 (400,000 Product records export)
Identify that record count (400,000) and object (Products) necessitate Data Loader Desktop Client export.
Data Import Wizard does not support exporting data or standard objects like Products.

Anahtar Kavram

Selecting between Data Import Wizard and Data Loader based on record volume, object support, operation type, and automation requirements.
Tahmini Süre:1m 30s
Soru 285Soru

An administrator needs to build an autolaunched flow to update the resolution status of multiple high-priority Support Cases associated with an Account. Which two design configurations should the administrator implement to efficiently handle this logic while adhering to Salesforce governor limits?

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

Cevabı ve açıklamayı göster

Cevap: Execute a single Get Records element before the Loop to retrieve all matching Support Cases in a single query.; Add updated Case records to a Record Collection variable inside the Loop and execute a single Update Records element after the Loop.

Cevap

The administrator should execute a single Get Records element before entering the Loop, collect modified records into a Record Collection variable during iteration, and execute a single Update Records element after exiting the Loop.
Bulkifying flows requires keeping database operations (Get Records, Create Records, Update Records, Delete Records) outside of Loop elements. Fetching records prior to the loop and updating a collection after the loop completes guarantees the transaction stays well within governor limits.

Adım Adım Çözüm

1
Query records outside the loop
All required Case records are retrieved into a collection variable using a single SOQL query prior to loop iteration.
Prevents exceeding the total number of SOQL queries allowed per transaction.
2
Iterate and modify records in memory
The Loop processes each Case, updates field values, and appends the modified record to a new Record Collection variable via an Assignment element.
Stores modified records in memory without making database DML calls within the loop.
3
Commit changes in a single DML operation
A single Update Records element references the collection variable after the loop terminates.
Consolidates all database write operations into one DML statement to maintain bulkification.

Anahtar Kavram

Flow Bulkification and Loop Design Patterns
Soru 286Soru

A Salesforce Administrator wants to configure automated actions that execute immediately when a Case meets specific Workflow Rule criteria. Which two automated actions can be configured directly as standard Workflow Actions? (Select two.)

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

Cevabı ve açıklamayı göster

Cevap: Field Update to modify a record field value; Email Alert to send an email using a specified template

Cevap

Field Updates and Email Alerts are standard actions natively available in Workflow Rules.
Workflow Rules natively support four specific actions: Field Updates, Email Alerts, Tasks, and Outbound Messages. Field Updates and Email Alerts represent valid standard workflow actions.

Adım Adım Çözüm

1
Identify the core automated actions available natively in Salesforce Workflow Rules.
The four supported standard actions are Field Updates, Email Alerts, Tasks, and Outbound Messages.
Workflow Rules have a predefined set of four standard action types.
2
Evaluate the option choices against the supported workflow actions.
Field Update and Email Alert match the supported workflow action types, while Chatter Posts and Record Deletions require Flow Builder or Apex.
Direct Chatter feed posting and record deletion are not part of the standard Workflow Rule action capabilities.

Anahtar Kavram

Standard actions in Salesforce Workflow Rules are limited to Field Updates, Email Alerts, Tasks, and Outbound Messages.
Soru 287Soru

An administrator at a renewable energy firm needs to share confidential equipment installation manuals stored in Salesforce Files with external contractors. The administrator must allow contractors to preview the documents online without authenticating into Salesforce, while strictly preventing them from downloading the original file to protect intellectual property. Which configuration should the administrator use to satisfy these requirements?

Cevabı ve açıklamayı göster

Cevap: Create a Content Delivery for each file, enable web link previewing, and deselect the option that permits downloading the file.

Cevap

Create a Content Delivery for each file, enable web link previewing, and deselect the option that permits downloading the file.
Content Deliveries convert Salesforce Files into web links that can be shared externally. Administrators can configure delivery settings to allow online previewing while explicitly disabling file download capabilities.

Adım Adım Çözüm

1
Identify file sharing requirement
External unauthenticated users must preview files online without downloading original copies.
Security requires preventing local file downloads while enabling web preview access.
2
Evaluate Salesforce Files sharing features
Salesforce Content Deliveries provide targeted settings for public links.
Content Deliveries support restricting file downloads, password protection, and tracking views.
3
Configure Content Delivery settings
Generate link with preview enabled and download permissions removed.
This enforces the exact viewing and security constraints specified.

Anahtar Kavram

Salesforce Content Deliveries and Link Restrictions
Soru 288Soru

An administrator at Helios Logistics configures a sales performance dashboard stored in a public folder shared with all Regional Sales Managers. To provide managers with a broad overview of company-wide sales trends, the dashboard running user is explicitly set to a static user—the VP of Sales—who holds 'View All Data' administrative permissions. A Regional Sales Manager views the dashboard and clicks on a chart component showing total closed-won opportunities to examine specific deal details. When the underlying source report opens, the manager notices that far fewer records are listed in the report than were summarized in the dashboard chart component. What explains this discrepancy in record visibility between the dashboard component and the source report?

Cevabı ve açıklamayı göster

Cevap: The dashboard component displays aggregated metrics based on the security access of the VP of Sales, whereas the source report evaluates data using the logged-in manager's security access.

Cevap

The dashboard component displays aggregated metrics based on the security access of the VP of Sales, whereas the source report evaluates data using the logged-in manager's security access.
When a dashboard is configured with a static running user (such as the VP of Sales), all users who have folder access to view the dashboard will see component data evaluated using that static running user's security rights. However, when drilling down into the source report behind any component, Salesforce executes the report using the logged-in user's security settings. Because the Regional Sales Manager has restricted record-level sharing compared to the VP of Sales, fewer records are accessible and displayed in the source report.

Adım Adım Çözüm

1
Analyze the dashboard running user configuration.
The dashboard is set to run as a static user (VP of Sales) who has 'View All Data' access.
Dashboard components calculate and display metric summaries using the permissions of the specified running user.
2
Analyze source report execution behavior upon drill-down.
When a user clicks a dashboard component, Salesforce launches the source report under the logged-in user's individual security context.
Reports always enforce the viewing user's Organization-Wide Defaults, role hierarchy placement, and active sharing rules.
3
Compare the metric totals between the two views.
The manager sees all company records in the dashboard component via the VP's access, but only sees their own shared records in the source report.
This behavioral difference is by design in Salesforce security architecture for static running user dashboards.

Anahtar Kavram

Dashboard Running User vs. Source Report Execution Security
Soru 289Soru

An administrator is designing an autolaunched flow that processes multiple Shipment Item records related to a returned Shipment. The flow retrieves all related shipment items, sets the Return Status field to 'Returned to Inventory' on each record, and saves the changes. To adhere to Salesforce best practices and avoid hitting governor limits when processing large batches of records, what should the administrator do?

Cevabı ve açıklamayı göster

Cevap: Iterate through the retrieved collection using a Loop element, update the current item variable, add each updated item to a new collection variable using an Assignment element, and execute a single Update Records element on the new collection outside the loop.

Cevap

Iterate through the retrieved collection using a Loop element, update the current item variable, add each updated item to a new collection variable using an Assignment element, and execute a single Update Records element on the new collection outside the loop.
The correct pattern follows Salesforce Flow bulkification standards: records are processed in memory using the loop's current item variable, added to a new record collection variable using an Assignment element (`collectionVariable Add currentItemVariable`), and finally updated in a single Update Records DML operation positioned after the loop finishes. This consumes only one DML statement across all iterations.

Adım Adım Çözüm

1
Retrieve the target child records
A record collection variable containing all related Shipment Item records is stored in memory via a single Get Records element.
Data must be retrieved in bulk outside of any loop to consume only one SOQL query.
2
Loop through the collection and update field values in memory
For each iteration, the loop uses the current item record variable to modify the field values, then an Assignment element appends that modified record variable to a new record collection variable.
Record modifications are staged in memory without invoking database operations inside the loop.
3
Perform a single DML operation after the loop completes
An Update Records element executes on the newly populated record collection variable after the loop concludes.
Executing DML on the entire collection consumes exactly one DML statement regardless of how many records were processed.

Anahtar Kavram

Bulkification in Flow Builder using Loop elements, Assignment elements, and Collection variables
Tahmini Süre:1m 15s
Soru 290Soru

The operations department at an equipment rental company uses a custom object named Equipment_Inspection__c. The team requires two specific automated processes:

1. Immediately calculate and assign the Risk_Level__c field on the Equipment_Inspection__c record itself whenever it is created or updated, prior to the record being committed to the database.
2. Automatically evaluate all Equipment_Inspection__c records that failed inspection and create a related Maintenance_Task__c record for each one every night at 11:00 PM.

Which two flow types and trigger settings should be utilized to satisfy these requirements? (Choose two.)

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

Cevabı ve açıklamayı göster

Cevap: A Record-Triggered Flow on Equipment_Inspection__c set to Fast Field Updates (before-save) to calculate and assign the Risk Level field.; A Schedule-Triggered Flow scheduled to execute daily at 11:00 PM that queries failed inspections and creates related maintenance tasks.

Cevap

The two required configurations are a Record-Triggered Flow on Equipment_Inspection__c configured for Fast Field Updates (before-save) to update the Risk Level field, and a Schedule-Triggered Flow configured to run daily at 11:00 PM to process failed inspections and generate maintenance tasks.
For requirement 1, updating a field on the triggering record before database commit is the primary use case for Fast Field Updates (before-save record-triggered flow). For requirement 2, running batch creation of related records at a specific scheduled time (11:00 PM nightly) is the standard function of a Schedule-Triggered Flow.

Adım Adım Çözüm

1
Analyze requirement 1 regarding same-record field updates prior to database commit.
Identify that updates to the triggering record prior to database save must use a Record-Triggered Flow configured for Fast Field Updates (before-save).
Fast Field Updates run prior to database commit and update the triggering record up to 10 times faster than after-save updates without triggering recursive save cycles.
2
Analyze requirement 2 regarding recurring, time-based batch record processing and related record creation.
Identify that scheduled batch operations occurring nightly at 11:00 PM require a Schedule-Triggered Flow.
Schedule-Triggered Flows automatically query specified object records and execute defined actions, such as creating child or related records, on a scheduled frequency.
3
Evaluate and discard sub-optimal or invalid flow configurations.
Discard after-save record-triggered flow for same-record updates and non-triggered autolaunched flows for scheduled automation.
Actions and Related Records add unnecessary DML overhead for same-record updates, while autolaunched flows lack automated scheduled entry criteria.

Anahtar Kavram

Selecting optimal Flow trigger types based on execution timing (before-save vs after-save vs scheduled execution)
Tahmini Süre:1m 15s
Soru 291Soru

A Salesforce Administrator is configuring a report to group Support Cases for executive reporting without creating new custom fields in Object Manager. Which two statements describe valid capabilities of Bucket Fields in Salesforce reports?

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

Cevabı ve açıklamayı göster

Cevap: Bucket fields can be created on Picklist, Text, or Number field data types.; Bucket fields can be used as report column groupings to summarize and filter data.

Cevap

Bucket fields allow administrators to group records based on Picklist, Text, or Number fields, and these bucket fields can be used as report groupings to summarize and filter data.
Bucket fields provide a streamlined mechanism to group report records by categorizing values from Picklist, Text, or Numeric fields. Once defined, bucket fields can serve as grouping levels, allowing admins to filter, sort, and summarize records according to custom bucket categories without needing schema modifications in Object Manager.

Adım Adım Çözüm

1
Identify the supported field data types for report bucketing in Salesforce.
Bucket fields support Picklist, Text, and Numeric field data types.
This defines which report fields can be categorized into bucket groups.
2
Evaluate how bucket fields function within Salesforce report layouts.
Bucket fields can be placed in row or column grouping sections to organize, summarize, and filter data.
Bucket fields act as virtual fields in reports that enable sorting, filtering, and grouping without creating custom database fields.

Anahtar Kavram

Report Bucketing Capabilities and Limitations
Soru 292Soru

An organization is configuring the Salesforce Integration with Outlook for its account management team. The sales manager requests that representatives be able to log incoming customer emails directly to custom object records and insert Lightning Email Templates with Enhanced Letterheads from within the Outlook integration panel. Which TWO administrative configuration steps must the Salesforce administrator take to fulfill these requirements?

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

Cevabı ve açıklamayı göster

Cevap: Enable Enhanced Email in Setup to allow logged emails to be saved as EmailMessage records and related to custom objects.; Assign a permission set containing the 'Access Lightning Email Templates in Outlook and Gmail' user permission to the representatives.

Cevap

The administrator must enable Enhanced Email in Setup so that emails are created as EmailMessage records (which can be linked to custom objects), and assign a permission set containing the 'Access Lightning Email Templates in Outlook and Gmail' permission.
Enabling Enhanced Email is required because standard email logging saves emails as Task records, which lack direct custom object relationship fields. Enhanced Email creates EmailMessage records that can be related to custom objects. Additionally, users require the explicit 'Access Lightning Email Templates in Outlook and Gmail' permission (assigned through a Permission Set) to access and insert Lightning templates directly from the Outlook integration panel.

Adım Adım Çözüm

1
Identify the requirement for relating emails to custom objects.
Determine that standard tasks do not easily support custom object email mapping without Enhanced Email enabled.
Enhanced Email creates EmailMessage records that preserve full email functionality and can be linked to custom objects.
2
Identify the requirement for accessing Lightning Email Templates inside Outlook.
Determine the specific system permission required for integration template usage.
Users require the 'Access Lightning Email Templates in Outlook and Gmail' permission assigned via a Permission Set to see Lightning templates in the Outlook pane.

Anahtar Kavram

Salesforce Integration with Outlook setup, Enhanced Email capability, and Lightning Email Template permissions.
Soru 293Soru

A Salesforce Administrator needs to build a record-triggered flow on the Opportunity object that aggregates the Grand Total of all open Quote records related to the parent Account and updates a custom field on that Account, adhering strictly to bulkification best practices. Place the following Flow Builder steps in the correct 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 sequence of Flow Builder steps is: First, execute a Get Records element to fetch all relevant Quotes. Second, pass the collection into a Loop element. Third, assign each Quote's Grand Total to a running variable inside the loop. Fourth, set the Account record variable fields using an Assignment element after the loop completes. Finally, execute an Update Records element to commit the changes.
The correct design pattern follows bulkification best practices in Salesforce Flow Builder: initial query via Get Records, iteration over collection elements in a Loop, in-memory calculation using Assignment within the loop path, single record assignment after the loop completes, and a final database update via Update Records outside the loop.

Adım Adım Çözüm

1
Retrieve child Quote records using a Get Records element.
A record collection variable populated with open Quote records linked to the Account.
Data must be retrieved in a single bulkified query before processing.
2
Iterate through the collection with a Loop element.
Each Quote record is assigned to the loop iteration variable sequentially.
Flow Builder requires a loop to inspect individual field values within a record collection.
3
Aggregate values inside the loop using an Assignment element.
The running total variable increments by the Grand Total of each Quote.
In-memory variable manipulation inside a loop avoids governor limit violations.
4
Prepare the parent Account update after the loop finishes using an Assignment element.
The target Account record variable is populated with the Account ID and the total value.
Staging the record update in memory prevents multiple DML executions.
5
Commit changes using an Update Records element.
The parent Account record in the database is updated with the new total.
A single DML operation outside the loop executes efficiently and adheres to limits.

Anahtar Kavram

Flow Bulkification and Element Sequencing
Soru 294Soru

Solaria Energy Solutions operates two distinct sales divisions: B2B Commercial and B2C Residential. The B2C Residential sales team requires a streamlined three-stage sales pipeline (Qualification, Proposal, Closed Won/Lost), whereas the B2B Commercial team follows a complex six-stage pipeline. The Salesforce administrator has already created all necessary picklist values in the standard Stage field on the Opportunity object. Which set of administrative steps must the administrator perform next to ensure B2C sales representatives only select from the three relevant stages when creating opportunities?

Cevabı ve açıklamayı göster

Cevap: Create a new Sales Process for B2C Residential, select the three appropriate stages, create an Opportunity Record Type for B2C, and associate the Sales Process with the new Record Type.

Cevap

Create a new Sales Process for B2C Residential, select the three appropriate stages, create an Opportunity Record Type for B2C, and associate the Sales Process with the new Record Type.
On the Opportunity object, stage picklist values are governed by Sales Processes. To display different stages for different business lines, an administrator must first create a Sales Process containing the desired stage values, create an Opportunity Record Type, and link the Sales Process to that Record Type. Finally, the Record Type is assigned to the appropriate user profiles.

Adım Adım Çözüm

1
Create a Sales Process
Defines the subset of Opportunity Stage picklist values specifically needed for the B2C Residential sales pipeline.
In Salesforce, the standard Stage picklist on Opportunity is controlled by a Sales Process rather than direct picklist editing on Record Types.
2
Create an Opportunity Record Type
Establishes a distinct record type for B2C Residential opportunities.
Record Types allow different business processes, page layouts, and picklist values to be assigned to different users.
3
Associate the Sales Process with the Record Type
Links the configured B2C Sales Process to the B2C Opportunity Record Type.
This completes the binding so users assigned to the B2C Record Type see only the three selected stages.

Anahtar Kavram

Sales Processes and Opportunity Record Types
Soru 295Soru

A Salesforce administrator built and activated a custom Matching Rule on the Contact object to identify matching First Name, Last Name, and Email fields. However, users can still save duplicate records without receiving any warnings or prevention messages. Which configuration step must the administrator take to enforce duplicate blocking?

Cevabı ve açıklamayı göster

Cevap: Create and activate a Duplicate Rule on the Contact object that references the Matching Rule and sets the Action on Create to Block.

Cevap

The administrator must create and activate a Duplicate Rule on the Contact object that references the Matching Rule and sets the creation action to Block.
Matching rules determine how duplicate records are identified by defining matching criteria. To enforce restrictions such as blocking or alerting users upon record creation, an administrator must create and activate a Duplicate Rule that references the Matching Rule and sets the Action on Create setting to Block.

Adım Adım Çözüm

1
Understand the difference between Matching Rules and Duplicate Rules.
Recognize that a Matching Rule strictly defines criteria to identify duplicate records, whereas a Duplicate Rule determines the action taken when duplicates are detected.
Activating a Matching Rule alone does not enforce blocking or alerting during record entry.
2
Identify the missing configuration component.
Determine that a Duplicate Rule must be created, linked to the Matching Rule, and configured with a 'Block' action on creation.
Without an active Duplicate Rule, Salesforce will not trigger duplicate prevention behaviors.

Anahtar Kavram

Separation of Matching Rules (criteria definition) and Duplicate Rules (action enforcement)
Tahmini Süre:45s
Soru 296Soru

A Salesforce Administrator needs to evaluate whether an Opportunity record's Amount exceeds $50,000 and direct the flow down different execution paths based on the result. Which Flow Builder element should the administrator use to evaluate this condition and branch the flow?

Cevabı ve açıklamayı göster

Cevap: Decision element

Cevap

The Decision element is the standard Flow Builder element designed to evaluate conditional logic and branch flow execution paths.
The Decision element evaluates defined logical conditions (such as checking if an Opportunity Amount is greater than $50,000) and routes flow execution down specific outcome branches depending on whether those conditions evaluate to true.

Adım Adım Çözüm

1
Identify the requirement
The flow needs to evaluate field criteria ($50,000 threshold) and branch execution.
Branching execution paths requires a logic element capable of defining conditional outcome branches.
2
Select the appropriate Flow element
Choose the Decision element.
Decision elements contain outcome criteria (e.g., Amount greater than 50000) to control the direction of the flow.

Anahtar Kavram

Flow Builder Decision Element and Conditional Logic
Soru 297Soru

An administrator at a financial services firm is configuring a validation rule on the custom object Loan_Application__c. The business requirement states that whenever an existing loan application record is updated and its Status__c picklist field is set to 'Approved', the Manager_Approval_Code__c text field must not be left blank and must match a specific format starting with 'AC-' followed by numeric digits. Which TWO criteria or formula function expressions should the administrator include in the validation rule to meet these requirements accurately? (Select TWO answers.)

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

Cevabı ve açıklamayı göster

Cevap: NOT(ISNEW()) to restrict the rule evaluation strictly to record updates rather than new record creation.; AND(ISPICKVAL(Status__c, "Approved"), OR(ISBLANK(Manager_Approval_Code__c), NOT(REGEX(Manager_Approval_Code__c, "^AC-[0-9]+$")))) to evaluate status value and enforce required code format.

Cevap

The correct selections are the expression using NOT(ISNEW()) to limit execution to record updates, and the combined AND/OR formula with ISPICKVAL, ISBLANK, and NOT(REGEX(...)) to enforce pattern compliance and mandatory entry.
To validate existing records upon update, NOT(ISNEW()) ensures the rule fires only when existing records are updated. Furthermore, combining ISPICKVAL with an OR condition containing ISBLANK and NOT(REGEX(...)) correctly flags records where the status is set to Approved but the approval code is missing or does not match the required pattern.

Adım Adım Çözüm

1
Determine context condition for update operations.
Identify that NOT(ISNEW()) evaluates to true when modifying existing records.
The requirement specifically specifies existing records being updated.
2
Construct error condition for picklist and pattern requirements.
Combine ISPICKVAL(Status__c, 'Approved') with OR(ISBLANK(...), NOT(REGEX(...))).
Validation rules fire when the formula expression returns true, so invalid states (blank code or non-matching REGEX pattern) must evaluate to true when status is Approved.

Anahtar Kavram

Validation Rule Logic and Pattern Enforcements with REGEX and Record Context Functions
Soru 298Soru

A Salesforce Administrator creates a new custom field on the Position object. HR managers report that the new field is missing when they create reports using an existing Custom Report Type titled 'Positions with Job Applications'. Additionally, the HR team wants to display the Hiring Manager's Email (a field on the User object referenced via a lookup field on Position) in reports without creating a duplicate custom field. Which TWO actions should the administrator take in the Custom Report Type setup to satisfy these requirements? (Select 2 answers)

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

Cevabı ve açıklamayı göster

Cevap: Edit the field layout of the Custom Report Type and drag the newly created custom field from the field palette into a report section.; Click 'Add fields related via lookup' in the Custom Report Type layout editor, traverse the Hiring Manager lookup, and select the Email field.

Cevap

To resolve both requirements, the administrator must edit the field layout of the Custom Report Type to add the new custom field from the palette, and use the 'Add fields related via lookup' feature to include the Hiring Manager's Email field from the related User object.
When new custom fields are added to an object, Salesforce automatically includes them in standard report types, but existing Custom Report Types must be manually updated by editing the report type layout and dragging the field from the palette. Additionally, Salesforce allows admins to include fields from lookup-related objects (up to 4 levels) in a Custom Report Type layout using the 'Add fields related via lookup' option, avoiding the need for redundant custom formula fields.

Adım Adım Çözüm

1
Address missing custom field on existing Custom Report Type
Recognize that creating a custom field on an object automatically adds it only to standard report types, not existing Custom Report Types.
Existing Custom Report Types require manual layout editing to add new fields.
2
Access Custom Report Type layout editor
Navigate to Setup > Custom Report Types > 'Positions with Job Applications' > Edit Layout.
This is where field inclusion, section grouping, and display names are managed.
3
Add the new custom field and the lookup field
Drag the new field from the right-hand field palette into the layout section, and click 'Add fields related via lookup' to traverse to the User object and select Email.
Lookup traversal avoids creating redundant formula fields on the primary object while making related data available for reporting.

Anahtar Kavram

Custom Report Type Layout Customization and Lookup Field Traversal
Soru 299Soru

A Service Cloud administrator is auditing system performance and order of execution for incoming case creation. Place the following case processing automation steps in the correct sequential order in which Salesforce evaluates and executes them upon record creation.

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

Cevabı ve açıklamayı göster

Cevap

The correct order of execution for incoming Case automation is: Validation Rules, Case Assignment Rules, Case Auto-Response Rules, and Case Escalation Rules.
In Salesforce, incoming Case automation follows a defined order of execution. System and custom validation rules execute first to ensure valid record creation. Case Assignment Rules execute second to assign ownership to an agent or queue. Case Auto-Response Rules execute third to send personalized acknowledgment emails to customers. Finally, Case Escalation Rules evaluate to schedule SLA timers and escalation triggers.

Adım Adım Çözüm

1
Identify the initial record validation phase.
Validation rules run first to ensure incoming Case data is valid prior to executing automation.
Invalid records cannot be saved or assigned to queues.
2
Determine ownership routing sequence.
Case Assignment Rules execute next to assign ownership to the designated user or queue.
Ownership must be established before sending auto-responses that depend on owner or queue details.
3
Identify customer auto-communication execution.
Case Auto-Response Rules execute after assignment rules to send automated confirmation emails.
Auto-response templates use criteria and owner details populated during assignment.
4
Identify SLA monitoring and escalation timing.
Case Escalation Rules evaluate last to schedule monitoring timers for SLA compliance.
Escalation rules rely on finalized case attributes and assigned queue structures to manage resolution targets.

Anahtar Kavram

Salesforce Order of Execution for Case Automation Rules
Tahmini Süre:1m 30s
Soru 300Soru

A Salesforce Administrator is designing an autolaunched flow to update related records when a Project record's status changes to 'Completed'. The flow must set the status of all open child Project Task records to 'Closed'. Which TWO implementation strategies should the administrator use within Flow Builder to fulfill this business requirement efficiently without exceeding governor limits?

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

Cevabı ve açıklamayı göster

Cevap: Execute a single Get Records element before any loop to retrieve all open Project Task records associated with the Project.; Iterate through the retrieved records, modify the status using an Assignment element inside the loop, and execute a single Update Records element outside the loop on the record collection variable.

Cevap

The administrator should execute a single Get Records element outside any loop to query the necessary Project Task records and use an Assignment element inside the loop to aggregate modified records into a collection variable, followed by a single Update Records element outside the loop.
To maintain optimal flow execution and adhere to Salesforce governor limits, data retrieval (Get Records) and data manipulation (Update Records) elements must always be placed outside of loops. Using an Assignment element inside the loop allows for field values to be set in a collection variable in memory, enabling a single bulk update operation once loop processing completes.

Adım Adım Çözüm

1
Query related open Project Task records using a Get Records element positioned prior to any loop construct.
All target records are stored in a record collection variable using a single SOQL query.
Placing data query elements outside loops adheres to Salesforce governor limit best practices.
2
Loop through the record collection, using an Assignment element to update the field values on a current loop item and add it to a secondary output collection variable.
Record field modifications are staged in memory without triggering database transactions.
In-memory variable manipulation consumes no DML governor limits.
3
Pass the populated secondary record collection to a single Update Records element located after the Loop path completes.
All modified Project Task records are written to the database in one bulk transaction.
A single DML statement updates all records efficiently in batch mode.

Anahtar Kavram

Flow Bulkification and Governor Limit Prevention
ÖncekiSayfa 15 / 90Sonraki
Tüm alıştırma soruları — Salesforce Certified Administrator | Examkin