Examkin

Tüm alıştırma soruları

1784 soru

Tüm türler1,784Çoktan seçmeli918Çoklu seçim587Eşleştirme142Sıralama137
Soru 1261Soru →

An administrator needs to automatically update a custom status field on all related Contact records whenever an Account's status changes to 'Inactive'. Which capability of Process Builder allows the administrator to accomplish this requirement without custom code?

Cevabı ve açıklamayı göster

Cevap: Executing an Update Records action that specifies child records related to the Account

Cevap

Process Builder allows administrators to configure an Update Records action that directly updates related child records (such as Contacts related to an Account) without writing Apex code.
Process Builder includes built-in declarative capabilities to create an 'Update Records' action that selects records related to the record that started the process, allowing seamless updates to child records such as Contacts on an Account.

Adım Adım Çözüm

1
Identify the automation requirement
The requirement involves updating child records (Contacts) when a parent record (Account) undergoes a field change.
Understanding record relationships is necessary to select the proper automation capability.
2
Evaluate Process Builder capabilities for cross-object updates
Process Builder features a built-in 'Update Records' action type capable of referencing records related to the main object.
This avoids unnecessary code development by using standard declarative functionality.

Anahtar Kavram

Process Builder Cross-Object Child Record Updates
Soru 1262Soru →

A Salesforce Administrator at Apex Financial Services is configuring a Lightning Service Console application for the tier-1 support desk. Support agents report that when they click on a related Contact record from an open Case primary tab, the Contact record opens in a separate primary tab instead of under the Case record tab, causing workspace clutter. Which administration setting should the administrator modify to ensure Contact records open as subtabs of the Case primary tab?

Cevabı ve açıklamayı göster

Cevap: Edit the Lightning Console App settings in App Manager and configure Navigation Rules to set Contact as a subtab of Case.

Cevap

Edit the Lightning Console App settings in App Manager and configure Navigation Rules to set Contact as a subtab of Case.
In Salesforce Lightning Console apps, navigation rules determine how records open when selected. Administrators configure these rules in App Manager by editing the specific Lightning Console application and adjusting the Navigation Rules tab to set child/related records (such as Contact) to open as subtabs of a primary parent record (such as Case).

Adım Adım Çözüm

1
Navigate to Setup and search for App Manager.
Access the list of all Lightning and Classic applications configured in the org.
Console application tab behaviors are configured at the application level in App Manager.
2
Locate the targeted Lightning Service Console app, click the dropdown menu, and select Edit.
Opens the Lightning App Builder App Settings interface.
Allows modification of console options, utility items, and navigation rules.
3
Select Navigation Rules and define the relationship rule so Contact records open as a subtab of Case records.
Ensures that when agents navigate from a Case to a Contact, it automatically groups as a subtab under the parent Case primary tab.
Navigation rules specifically dictate whether records open as primary tabs or subtabs under related objects.

Anahtar Kavram

Lightning Service Console Navigation Rules Configuration
Soru 1263Soru →

A sales manager at Northern Trail Outfitters wants to display the calculated difference in days between the Created Date and Close Date for each individual Opportunity record directly inside an Opportunity report. Which Salesforce reporting feature should an administrator use to meet this requirement?

Cevabı ve açıklamayı göster

Cevap: A row-level formula created directly in the report builder

Cevap

A row-level formula created directly in the report builder
A row-level formula in the report builder allows administrators to write logic that calculates values for each individual record row in the report output. Subtracting the Created Date from the Close Date for each record requires row-level evaluation.

Adım Adım Çözüm

1
Identify the level of evaluation required for the calculation.
The calculation must evaluate individual Opportunity rows record by record.
The requirement specifies subtracting dates for each individual opportunity rather than summarizing group totals.
2
Select the appropriate report feature for record-level evaluation.
Choose a row-level formula in the report builder.
Row-level formulas execute logic across individual records displayed in report detail rows.

Anahtar Kavram

Row-Level Report Formulas vs. Summary Formulas
Tahmini Süre:1m 0s
Soru 1264Soru →

A Salesforce Administrator is configuring a Workflow Rule on the Case object for a customer support team. The business requirement states that whenever a Case is edited and its Priority is set to 'High', an immediate Field Update must mark the record, and a follow-up Task must be scheduled automatically 72 hours after the modification. During setup, the administrator successfully configures the rule criteria but finds that the 'Add Time Trigger' button is completely unavailable on the Workflow Rule detail page. Which configuration setting is the root cause of this limitation?

Cevabı ve açıklamayı göster

Cevap: The evaluation criteria was configured as 'created, and every time it's edited'.

Cevap

The evaluation criteria was configured as 'created, and every time it's edited'.
In Salesforce Core Administration, time-dependent workflow actions are supported ONLY for rules with evaluation criteria set to 'created' or 'created, and any time it's edited to subsequently meet criteria'. When a rule is configured with 'created, and every time it's edited', Salesforce automatically disables time triggers to prevent recursive queuing of background actions upon repeated edits.

Adım Adım Çözüm

1
Analyze the reported administration issue
The administrator cannot see or add a Time Trigger to the Workflow Rule detail page.
Understanding why a setup feature is disabled requires reviewing declarative rule constraints in Salesforce.
2
Evaluate Salesforce platform restrictions on time-dependent workflow actions
Time-dependent actions are disabled when evaluation criteria is set to 'created, and every time it's edited'.
If Salesforce allowed time triggers for rules that fire every time a record is edited, continuous record updates could continually add duplicate delayed actions to the time-based workflow queue.
3
Determine the required resolution
Change the evaluation criteria to 'created, and any time it's edited to subsequently meet criteria'.
This evaluation setting re-enables time-dependent actions while satisfying the business logic for modified Case records.

Anahtar Kavram

Workflow Rule Evaluation Criteria Limitations with Time-Dependent Actions
Soru 1265Soru →

A healthcare consulting firm uses the Gmail Integration with Salesforce. Representatives report that when composing emails using the integration side panel, they are unable to see or select Lightning Email Templates stored in shared template folders. The administrator confirms that folder sharing was set up correctly. What administrative action is required to enable representatives to access these shared Lightning Email Templates from the integration pane?

Cevabı ve açıklamayı göster

Cevap: Assign a permission set containing the 'Use Lightning Email Templates' system permission to the representatives.

Cevap

Assign a permission set containing the 'Use Lightning Email Templates' system permission to the representatives.
In Salesforce, accessing and selecting shared Lightning Email Templates from the Gmail or Outlook integration panel requires users to have the 'Use Lightning Email Templates' permission. Assigning this permission via a permission set follows best practices for additive access control.

Adım Adım Çözüm

1
Identify the feature permissions needed for Lightning Email Templates.
Recognize that accessing Lightning Email Templates within email integrations requires the 'Use Lightning Email Templates' permission.
Folder sharing alone is insufficient if users lack the underlying system permission to interact with Lightning templates.
2
Evaluate the standard Salesforce administrative best practice for granting functional permissions.
Determine that permissions should be added dynamically using permission sets rather than duplicating user profiles.
Permission sets allow flexible, additive permission assignments while keeping profile management streamlined.

Anahtar Kavram

Salesforce Integration with Gmail and Lightning Email Template Permissions
Soru 1266Soru →

A Salesforce Administrator is tasked with configuring a custom Opportunity report to track annual cloud subscription renewals. The business requirements state:

1. Group Opportunities into three revenue tiers ('Tier 1', 'Tier 2', and 'Tier 3') based on the Amount field without modifying object metadata or creating custom fields.
2. Include Opportunities that are either in the 'Closed Won' Stage OR have an Amount greater than $100,000 with a Probability greater than 70%.
3. Restrict all report results exclusively to records where Type equals 'Cloud Subscription'.

Which TWO configuration steps must the administrator execute to fulfill these requirements? (Select TWO)

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

Cevabı ve açıklamayı göster

Cevap: Add a Bucket Field based on the Amount field to categorize records into 'Tier 1', 'Tier 2', and 'Tier 3' ranges.; Set the Filter Logic to (1 OR (2 AND 3)) AND 4, where 1 is Stage = Closed Won, 2 is Amount > 100000, 3 is Probability > 70%, and 4 is Type = Cloud Subscription.

Cevap

The administrator must create a Bucket Field on the Amount field to define revenue tiers without custom schema fields, and configure custom Filter Logic formatted as (1 OR (2 AND 3)) AND 4 to enforce correct Boolean grouping across the stage, amount, probability, and type criteria.
Creating a Bucket Field directly on the Amount column satisfies the grouping requirement without requiring custom fields or Object Manager configuration. Applying filter logic structured as (1 OR (2 AND 3)) AND 4 ensures that either the Closed Won criteria or the high-value/high-probability pipeline criteria is met while mandating that every matching record belongs to the 'Cloud Subscription' Type.

Adım Adım Çözüm

1
Address Requirement 1 by selecting the Amount field column menu in the report builder and choosing 'Bucket This Column'.
Defines discrete categories ('Tier 1', 'Tier 2', 'Tier 3') directly in the report without creating schema-level custom fields.
Bucket fields provide inline record categorization for text, numeric, and picklist fields inside Salesforce reports.
2
Add individual field filters for Stage, Amount, Probability, and Type in the report filter panel.
Filter 1: Stage EQUALS Closed Won; Filter 2: Amount GREATER THAN 100000; Filter 3: Probability GREATER THAN 50 (or 70); Filter 4: Type EQUALS Cloud Subscription.
Each specific condition must first exist as an individual numbered filter line before filter logic can be applied.
3
Configure Filter Logic using explicit parentheses grouping: (1 OR (2 AND 3)) AND 4.
Ensures the OR evaluation between Closed Won and high-value pipeline is isolated, while Filter 4 (Type) applies universally across all returned records.
Without explicit parentheses around the OR and inner AND statements, Salesforce standard precedence (AND before OR) returns inaccurate record sets.

Anahtar Kavram

Report Bucket Fields and Boolean Filter Logic Grouping
Tahmini Süre:2m 0s
Soru 1267Soru →

A Customer Support Director wants to analyze Case distribution across different Account Industries. The report must list all Accounts regardless of whether they have associated Cases, and display a grid total of Case counts summarized simultaneously by Account Industry along the rows and Case Status across the columns. Which Custom Report Type object relationship and Report Format selection meets these business requirements?

Cevabı ve açıklamayı göster

Cevap: Define a Custom Report Type with Accounts as the primary object and Cases as 'Each record may or may not have related records', then select the Matrix report format.

Cevap

Define a Custom Report Type with Accounts as the primary object and Cases as 'Each record may or may not have related records', then select the Matrix report format.
To include Accounts without associated Cases, an outer join is required by setting the Custom Report Type relationship so that 'Each record may or may not have related records'. To group data simultaneously by rows (Account Industry) and columns (Case Status), a Matrix report format must be used.

Adım Adım Çözüm

1
Determine the required object relationship logic for record visibility
Configuring 'Each record may or may not have related records' (outer join) on the Custom Report Type ensures Accounts without Cases are retained in the report output.
An inner join ('Each record must have at least one related record') would filter out unserviced Accounts.
2
Select the appropriate Salesforce report format for two-dimensional grouping
Choosing the Matrix report format enables grouping row data by Account Industry and column data by Case Status.
Summary reports only allow row groupings, whereas Matrix reports provide grid-style summarization across both rows and columns.

Anahtar Kavram

Custom Report Type Object Relationships ('with' vs 'with or without') and Matrix Report Format Selection
Tahmini Süre:1m 30s
Soru 1268Soru →

A support manager at a fintech enterprise requires cases that remain in the 'New' status without an owner assignment change for longer than 4 hours to automatically transfer ownership to the Tier 2 Queue and send an alert email to the support supervisor. Which Salesforce automation feature should the administrator configure to meet this time-elapsed requirement?

Cevabı ve açıklamayı göster

Cevap: Case Escalation Rules

Cevap

Case Escalation Rules should be used because they allow administrators to define criteria and elapsed time thresholds (such as 4 hours) to automatically reassign cases and send notification emails.
Case Escalation Rules evaluate open cases against time thresholds (e.g., 4 hours since creation) and perform automated actions such as changing case ownership to a queue and notifying designated users or supervisors.

Adım Adım Çözüm

1
Identify the core requirement
The requirement demands time-based automated actions (reassignment and email alert) triggered after a case remains open/unassigned for 4 hours.
Different automation tools in Salesforce handle record creation versus time-elapsed milestones differently.
2
Evaluate Salesforce Case Automation rule capabilities
Case Assignment Rules handle initial routing upon record entry; Auto-Response Rules send customer emails on entry; Escalation Rules trigger actions when cases hit time-based SLA thresholds.
Escalation rules uniquely support time-based rule entries and escalation actions based on case age or creation date.
3
Select the appropriate feature
Configure a Case Escalation Rule entry set for 4 hours of elapsed time, specifying ownership transfer to the Tier 2 Queue and adding the supervisor as an escalation notification recipient.
This directly fulfills both the ownership transfer and notification requirements without custom flow complexity.

Anahtar Kavram

Case Escalation Rules
Soru 1269Soru →

A Salesforce Administrator is configuring a flow to evaluate record conditions and process multiple records efficiently. Which TWO design practices represent correct usage of Flow Builder elements and logic? (Select 2 answers)

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

Cevabı ve açıklamayı göster

Cevap: Place data manipulation (DML) elements, such as Update Records, outside of Loop elements to operate on record collections.; Use a Decision element with defined outcome criteria to route execution paths based on resource values.

Cevap

The correct practices are placing data manipulation (DML) elements outside of loops to operate on collections, and using Decision elements to evaluate outcome criteria and branch flow execution paths.
Placing data manipulation (DML) operations outside of loops ensures the flow operates on collections in a single transaction, maintaining bulkification standards. Additionally, Decision elements are the standard Flow Builder element used to evaluate conditional logic and determine execution paths.

Adım Adım Çözüm

1
Identify flow logic elements responsible for branching and bulkification.
Recognize that Decision elements handle conditional routing and DML elements must process collections outside loops.
Flow Builder design standards require bulkification to respect governor limits and clear decision logic for path routing.
2
Evaluate anti-patterns in wrong options.
Identify that executing SOQL queries (Get Records) inside loops and misapplying roll-up logic across lookup relationships are invalid.
SOQL queries in loops violate governor limits, and roll-ups are restricted to master-detail relationships.

Anahtar Kavram

Flow Builder element logic, decision branching, and bulkification best practices
Soru 1270Soru →

A Salesforce Administrator is building an autolaunched flow to update several Lead records based on specific business criteria. The administrator retrieves a collection of target Leads using a Get Records element. Next, the flow needs to change the Lead Status to 'Closed - Not Converted' and set a custom field value on each record in the collection. Which design pattern should the administrator follow to process and update these records efficiently while staying within Salesforce governor limits?

Cevabı ve açıklamayı göster

Cevap: Loop through the Lead collection, use an Assignment element inside the loop to set field values and add each updated record to a new record collection variable, and place a single Update Records element outside the loop.

Cevap

The administrator should loop through the Lead collection, assign the updated values and collect records using an Assignment element inside the loop, and execute a single Update Records element outside the loop.
The correct approach follows bulkification best practices by accumulating modified record variables into a collection using Assignment elements inside the loop, followed by a single Update Records DML element executed outside the loop.

Adım Adım Çözüm

1
Retrieve Lead records into a collection variable
A record collection containing the target Lead records is populated using a single Get Records element.
Querying data once into a collection avoids repeated database calls.
2
Process records in a loop using Assignment elements
Each record in the loop has its field values updated in memory, and the updated record is added to a target output record collection.
Performing assignment operations in memory does not consume DML governor limits.
3
Execute Update Records outside the loop
All record modifications staged in the collection variable are committed to the database in a single transaction.
Executing a single DML operation outside the loop ensures the flow is bulkified and adheres to Salesforce governor limits.

Anahtar Kavram

Bulkification in Flow Builder
Soru 1271Soru →

A Salesforce Administrator needs to design an autolaunched flow that processes a collection of Vendor Rating custom object records, calculates aggregate metrics, and updates the parent Vendor account. To ensure optimal performance and avoid hitting SOQL and DML governor limits, in what sequence should the administrator place the Flow elements?

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

Cevabı ve açıklamayı göster

Cevap

The proper bulkified flow order is: 1) Get Records to query the Vendor Rating records, 2) Decision element to verify the collection is not empty, 3) Loop element to iterate through the collection, 4) Assignment element inside the loop to aggregate metrics and populate an output collection variable, and 5) Update Records element after the loop completes to bulk update the collection.
The correct sequence follows Salesforce Flow bulkification design patterns: query records first with Get Records, check for non-empty results using a Decision element, iterate through records with a Loop element, calculate values and stage updates in memory using an Assignment element inside the loop, and perform a single DML update using an Update Records element after loop execution completes.

Adım Adım Çözüm

1
Query the target child records using a Get Records element.
A collection variable populated with child records is created.
Data must be retrieved from the database before it can be evaluated or looped over.
2
Evaluate the retrieved record collection with a Decision element.
Determines whether to proceed into the loop or exit safely.
Prevents redundant execution or unexpected errors when no records match the filter criteria.
3
Pass the non-empty collection into a Loop element.
Sequentially processes each record in the collection.
Looping provides a context to inspect and manipulate individual record field values.
4
Use an Assignment element inside the loop body.
Calculates running totals in memory and appends modified records to a target collection variable.
Performing data manipulation (DML) inside loops consumes governor limits; assignments keep operations in memory.
5
Place an Update Records element on the path exiting the Loop element.
Performs a single, bulkified DML operation to update all modified records in the database.
Executing database updates outside the loop body maintains bulkification compliance.

Anahtar Kavram

Bulkification in Salesforce Flow Builder requires performing data retrieval (Get Records) and data manipulation (Update Records) outside of Loop elements using collection variables and Assignment elements.
Soru 1272Soru →

A Salesforce Administrator is evaluating declarative automation options. Which of the following native actions can be executed directly as immediate actions within Process Builder without writing custom Apex code? (Select TWO answers)

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

Cevabı ve açıklamayı göster

Cevap: Create a new record of a standard or custom object.; Post a custom notification message directly to a Chatter feed.

Cevap

Process Builder natively supports creating new records and posting messages to Chatter feeds as immediate actions.
Process Builder includes out-of-the-box support for creating new records (standard or custom) and posting messages directly to Chatter feeds as immediate or scheduled actions.

Adım Adım Çözüm

1
Review supported declarative actions in Process Builder.
Process Builder supports creating records, updating related records, sending email alerts, posting to Chatter, calling Apex, launching flows, and submitting records for approval.
Identifies native capabilities provided by the Process Builder tool.
2
Analyze platform limitations and execution timing.
Process Builder cannot perform record deletions natively, and its actions run after-save rather than before validation rules.
Eliminates actions requiring Flow Builder, Apex, or before-save trigger execution logic.

Anahtar Kavram

Process Builder Action Capabilities and Limitations
Soru 1273Soru →

A Salesforce Administrator at a hospitality management company is creating a centralized Lightning Experience dashboard to track guest satisfaction and reservation metrics across multiple hotel locations. The administrator adds a dashboard filter based on the 'Region' picklist field on the Account object. However, one specific component displaying guest survey ratings does not change when users select a value from the 'Region' filter dropdown. Which explanation identifies the root cause of this issue?

Cevabı ve açıklamayı göster

Cevap: The source report for the component does not include a field that can be mapped to the 'Region' dashboard filter.

Cevap

The source report for the component does not include a field that can be mapped to the 'Region' dashboard filter.
Dashboard filters depend on field mapping between the dashboard filter field and the fields present in each component's source report. If a component's source report does not contain a field with a compatible data type (or if the administrator did not map an equivalent field for that report), the filter cannot filter that component's data.

Adım Adım Çözüm

1
Analyze why dashboard dynamic filters apply to some components but not others.
Identify that dashboard filters require explicit field mapping between the dashboard filter field and an equivalent field in each component's source report.
If a source report does not contain the filter field or a compatible field type, the filter cannot be mapped to that component, causing it to display unfiltered data.
2
Evaluate the underlying source report structure for the un-filtered component.
Determine that the report lacks a field compatible with 'Region'.
Without a mapped field in the source report, selecting a filter value has no effect on that component.

Anahtar Kavram

Dashboard Dynamic Filter Field Mapping
Tahmini Süre:1m 30s
Soru 1274Soru →

A Salesforce Administrator configures a single Workflow Rule on the Account object that includes all four standard types of immediate workflow actions: Email Alert, Field Update, Outbound Message, and Task. When a record update triggers this rule, in which precise sequence does Salesforce process and execute these immediate workflow actions?

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

Cevabı ve açıklamayı göster

Cevap

The correct execution sequence for immediate workflow actions is Field Updates first, followed by Email Alerts, then Tasks, and finally Outbound Messages.
Salesforce enforces a strict, deterministic sequence when executing immediate workflow actions associated with a single Workflow Rule: 1. Field Updates, 2. Email Alerts, 3. Tasks, 4. Outbound Messages. This design ensures that field modifications occur internally before notifications are sent or external endpoints are called.

Adım Adım Çözüm

1
Determine the action type processed first upon workflow evaluation.
Field Updates are executed first.
Salesforce executes Field Updates before any communication actions so that updated record values are reflected across all subsequent steps.
2
Determine the action type processed second.
Email Alerts are executed second.
Email notifications rely on current record fields and are generated immediately after field changes are committed in memory.
3
Determine the action type processed third.
Tasks are created third.
Internal task creation occurs after email notifications have been queued.
4
Determine the final action type processed.
Outbound Messages are dispatched last.
Outbound SOAP messages transmit payload data to external endpoints as the final immediate workflow action.

Anahtar Kavram

Order of Execution for Immediate Workflow Action Types
Soru 1275Soru →

A company requires department supervisors to initiate approval requests for travel expenses on behalf of team members. Which configuration component of a Salesforce approval process specifies which users or groups are authorized to start the approval workflow for a record?

Cevabı ve açıklamayı göster

Cevap: Allowed Submitters

Cevap

The Allowed Submitters configuration setting specifies which users, roles, or groups are permitted to submit records for approval.
The 'Allowed Submitters' setting directly defines which users, public groups, roles, or record roles (such as Owner or Creator) are granted permission to initiate the approval process for a given record.

Adım Adım Çözüm

1
Identify the requirement
The requirement asks how to restrict or grant permissions for users to initiate an approval process.
Different users or roles may need to submit records on behalf of others.
2
Evaluate Salesforce approval process setup sections
The 'Allowed Submitters' section controls submission eligibility by specifying user types, roles, portal types, or public groups.
Initial submission actions, entry criteria, and final actions serve execution logic rather than user submission access control.

Anahtar Kavram

Approval Process Allowed Submitters
Tahmini Süre:45s
Soru 1276Soru →

An organization requires a Record-Triggered Flow on the Opportunity object that fires when an Opportunity reaches the 'Closed Won' stage. For each child Opportunity Line Item belonging to a specific Product Family, the automation must generate a corresponding custom Renewal Contract record and calculate an aggregated total renewal amount to update on the parent Account record. To adhere strictly to Salesforce governor limits and Flow Builder best practices, how should the administrator design the Flow elements and logic?

Cevabı ve açıklamayı göster

Cevap: Fetch child Opportunity Line Items using a Get Records element, iterate using a Loop element, use Assignment elements inside the loop to accumulate the renewal amount into a Currency variable and add instantiated Renewal Contract records to a Record Collection variable, then invoke a single Create Records element and a single Update Records element outside the loop.

Cevap

Use a Get Records element to retrieve line items, iterate through them with a Loop element, collect instantiated records into a collection variable and sum metrics using Assignment elements, and perform DML operations using Create Records and Update Records elements placed outside the loop.
Bulkification in Flow Builder requires accumulating data changes in variable collections during iteration and executing a single database element outside the loop. Using Assignment elements within the loop to populate a Record Collection and aggregate amounts, followed by executing Create Records and Update Records outside the loop, keeps SOQL and DML counts at 1 regardless of the number of line items processed.

Adım Adım Çözüm

1
Retrieve related child records outside of any loop structure.
Obtain all required Opportunity Line Item records in a single SOQL query via a Get Records element.
Prevents executing data queries inside iteration loops.
2
Iterate over the retrieved record collection using a Loop element.
Process each line item sequentially using current item loop variables.
Allows individual evaluation and assignment of values for each record.
3
Use Assignment elements inside the loop to populate record variables and collection variables.
Accumulate values in a total currency variable and add individual record instances to a Record Collection variable.
Prepares all memory variables without executing database operations during loop iterations.
4
Perform database operations using single DML elements outside the loop.
Execute one Create Records operation for the collection and one Update Records operation for the parent Account.
Ensures the flow remains fully bulkified and complies with DML governor limits.

Anahtar Kavram

Flow Builder Bulkification and Data Manipulation Logic
Soru 1277Soru →

A Salesforce administrator is evaluating reporting capabilities to calculate custom metrics on an operational report. Which two statements correctly describe the features and limitations of row-level formulas in Salesforce reports? (Select TWO)

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

Cevabı ve açıklamayı göster

Cevap: A single report can contain a maximum of one row-level formula.; Row-level formulas evaluate expressions on individual record rows line by line.

Cevap

Row-level formulas evaluate expressions on individual record rows line by line, and a single report can contain a maximum of one row-level formula.
Row-level formulas calculate values for each distinct record row individually, and Salesforce limits each report to a maximum of one row-level formula.

Adım Adım Çözüm

1
Determine the evaluation scope of row-level formulas.
Row-level formulas execute calculations for each individual record line in the report.
This sets them apart from summary formulas, which calculate metrics across grouped summary rows.
2
Verify platform governor limits regarding report formula fields.
Salesforce limits each report to exactly one row-level formula.
Understanding reporting limits is critical for designing compliant Salesforce reports.

Anahtar Kavram

Row-Level Formula Scope and Limits
Soru 1278Soru →

A Salesforce administrator at a logistics management firm needs to execute several distinct data operations across standard and custom objects. Match each administrative requirement to the appropriate data utility tool and configuration.

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

Öğeler

Import 4,000 Lead records while suppressing duplicate creation using Email matching and automatically triggering Lead Assignment Rules.
Export 300,000 Shipment__c custom object records weekly via an automated scheduled background batch process.
Permanently purge 12,000 inactive Asset records directly from the database without storing them in the Recycle Bin.
Upsert 85,000 Account records mapped to parent accounts using an External ID field.

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Each administrative data task matches its specific tool based on record volume, automation requirements, operation type, and feature capabilities: Importing 4,000 Leads with rule triggers matches Data Import Wizard; Scheduled export of 300,000 records matches Data Loader CLI; Hard deleting 12,000 Assets matches Data Loader with Bulk API Hard Delete; Upserting 85,000 Accounts with External IDs matches Data Loader Desktop GUI.
The correct pairings align with Salesforce utility specifications: Data Import Wizard handles under 50,000 records with assignment rule triggers; Data Loader CLI enables automated batch exports of large data sets; Data Loader with Bulk API Hard Delete allows direct database purges; and Data Loader Desktop GUI processes large-volume upserts exceeding 50,000 records.

Adım Adım Çözüm

1
Evaluate record volume limits for each requirement.
Operations under 50,000 records (such as 4,000 Leads and 12,000 Assets) can theoretically use either tool, whereas operations exceeding 50,000 records (300,000 Shipments and 85,000 Accounts) strictly require Data Loader.
Data Import Wizard is capped at 50,000 records per operation, while Data Loader handles up to 5,000,000 records.
2
Analyze special operational capabilities such as rule execution, scheduled automation, and hard deletion.
Triggering assignment rules and built-in duplicate matching is unique to Data Import Wizard. Automated script scheduling requires Data Loader CLI. Permanently purging records (hard delete) requires Data Loader using Bulk API.
Data Import Wizard cannot execute hard deletes or automated CLI scripting, while Data Loader cannot natively trigger Lead assignment rules during import.
3
Map each business requirement to the precise matching utility.
Pairs are accurately aligned based on feature availability and constraints.
Correct tool selection ensures compliance with Salesforce administrative capabilities and limits.

Anahtar Kavram

Selecting between Data Import Wizard and Data Loader based on record volume, supported objects, operation types, and automated execution constraints.
Soru 1279Soru →

An administrator configured a custom matching rule to identify duplicate Account records based on custom registration numbers. During testing, duplicate Accounts are successfully blocked when created manually through the Salesforce user interface. However, an automated bulk import using Data Loader continues creating duplicate Account records without failing or raising errors. What configuration change in the Duplicate Rule is required to prevent duplicate creation during bulk data imports?

Cevabı ve açıklamayı göster

Cevap: Change the Action on Create setting in the Duplicate Rule from Allow (with Alert) to Block.

Cevap

Change the Action on Create setting in the Duplicate Rule from Allow (with Alert) to Block.
Salesforce Duplicate Rules treat interactive user interface requests differently from non-interactive API requests (such as Data Loader imports). When a Duplicate Rule is configured with 'Allow' on create with 'Alert' enabled, human users in the browser see a duplicate warning prompt, but API operations bypass alerts and insert the record. To stop API calls and Data Loader imports from creating duplicate records, the Duplicate Rule's Action on Create must be explicitly configured to 'Block'.

Adım Adım Çözüm

1
Analyze how Salesforce Duplicate Rules interact with interactive UI vs non-interactive API operations.
Interactive UI sessions display alert popups when Action on Create is set to 'Allow' with 'Alert' checked, whereas non-interactive API tools (like Data Loader) cannot render UI alerts.
Because API requests cannot display prompt dialogs to human users, 'Allow' with 'Alert' permits record insertion automatically without blocking.
2
Determine the necessary Duplicate Rule setting to enforce data cleanliness during API operations.
Setting Action on Create to 'Block' ensures that both UI entries and API insertions triggering matching records are stopped and rejected.
Only the explicit 'Block' action prevents API operations from inserting duplicate records.

Anahtar Kavram

Duplicate Rule Execution Behavior Across API and User Interface Contexts
Tahmini Süre:2m 0s
Soru 1280Soru →

A logistics firm configures automated communication for its order fulfillment process. When an Order record's status is changed to 'Processing', a workflow rule with evaluation criteria set to 'created, and any time it's edited to subsequently meet criteria' triggers a time-dependent Email Alert to be sent 14 days later if the order remains in 'Processing'. Five days after an order enters 'Processing' and the email is placed in the queue, an agent updates the Order status to 'Cancelled'. What happens to the scheduled email action in the time-based workflow queue?

Cevabı ve açıklamayı göster

Cevap: The scheduled email action is automatically removed from the time-based workflow queue because the record no longer satisfies the rule criteria.

Cevap

The scheduled email action is automatically removed from the time-based workflow queue because the record no longer satisfies the rule criteria.
In Salesforce, when a record is updated and no longer meets the workflow rule criteria, any associated pending time-dependent actions are automatically removed from the time-based workflow queue.

Adım Adım Çözüm

1
Identify the workflow evaluation criteria and action type.
The rule uses 'created, and any time it's edited to subsequently meet criteria' with a time-dependent Email Alert delayed by 14 days.
Time-dependent actions are evaluated against the record state while resting in the queue.
2
Analyze the effect of updating the record status from 'Processing' to 'Cancelled'.
The record criteria (Status = 'Processing') is no longer met.
Salesforce continuously monitors queued items; if record field values change such that the rule criteria evaluate to false, Salesforce clears the pending actions.
3
Determine the outcome in the time-based workflow queue.
The pending Email Alert action is removed from the queue immediately upon saving the edit.
This behavior prevents invalid automated communications from firing after record state changes.

Anahtar Kavram

Time-Dependent Workflow Queue Lifecycle and Invalidation
Tahmini Süre:1m 30s
ÖncekiSayfa 64 / 90Sonraki
Tüm alıştırma soruları — Salesforce Certified Administrator | Examkin