Examkin

Tüm alıştırma soruları

1784 soru

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

A Salesforce Administrator at a commercial property management company is tasked with configuring an Account report for the regional operations team. The report must include accounts that meet the following criteria:
1. Account Rating is equal to 'Hot' OR Annual Revenue is greater than $10,000,000.
2. Account Type is equal to 'Commercial Tenant'.

The administrator creates the following field filters on the Account report:
Filter 1: Rating equals Hot
Filter 2: Annual Revenue greater than 10,000,000
Filter 3: Type equals Commercial Tenant

Which custom filter logic statement must the administrator apply to return only the records matching the business requirement?

Cevabı ve açıklamayı göster

Cevap: (1 OR 2) AND 3

Cevap

The custom filter logic statement '(1 OR 2) AND 3' correctly groups the optional conditions in parentheses while enforcing the required account type condition.
Enclosing Filters 1 and 2 in parentheses creates a single logical evaluation unit for the disjunctive 'Hot rating OR high annual revenue' criteria. Combining this unit with AND 3 ensures that every returned account fulfills the mandatory Type requirement.

Adım Adım Çözüm

1
Identify the disjunctive (OR) requirement
Filters 1 (Rating equals Hot) and 2 (Annual Revenue > 10,000,000) are alternative conditions.
The business prompt specifies that accounts meeting either rating or revenue thresholds qualify.
2
Identify the conjunctive (AND) requirement
Filter 3 (Type equals Commercial Tenant) is mandatory for all returned records.
The business prompt requires that every qualifying record must be a Commercial Tenant.
3
Apply parenthesization to maintain correct operator precedence
Combine as (1 OR 2) AND 3.
Parentheses force the evaluation of the OR clause prior to evaluating the mandatory AND clause.

Anahtar Kavram

Boolean filter logic parenthesization and operator precedence in Salesforce Reports
Soru 1502Soru →

Universal Containers requires a Screen Flow that allows customer support representatives to select multiple active Asset records associated with an Account and update their Warranty Expiration Date to a newly selected date. The flow must process up to 200 Asset records in a single execution without breaching Salesforce governor limits. What should the administrator configure in Flow Builder to fulfill this requirement?

Cevabı ve açıklamayı göster

Cevap: Iterate through the selected Asset collection using a Loop element, update the Warranty Expiration Date on the loop record using an Assignment element, append the loop record to a new Asset record collection variable, and execute a single Update Records element after the loop finishes using the new collection variable.

Cevap

The administrator should iterate through the Asset collection, update field values on the loop item using an Assignment element, add each updated record item to a secondary record collection variable inside the loop, and place a single Update Records element outside the loop referencing the secondary record collection.
The correct approach bulkifies database operations by modifying record field values in memory during loop execution, populating a new collection variable, and issuing a single Update Records DML call after loop iteration finishes.

Adım Adım Çözüm

1
Configure a Loop element to iterate through the input collection of selected Asset records.
Each Asset record in the collection is made available sequentially as the loop record variable.
Iterating over existing collection resources avoids performing SOQL queries inside loop paths.
2
Add an Assignment element inside the loop to set the new Warranty Expiration Date on the current loop item, and add a second assignment line to add the current loop item into a target record collection variable.
Field values are modified in memory and staged within a secondary collection without firing DML statements.
Staging records in memory across loop iterations preserves transaction resources and bulkifies data manipulation.
3
Place an Update Records element after the loop completes and set it to update records from the target record collection variable.
All updated Asset records are committed to the database in a single bulk DML statement.
Executing DML outside of loops ensures the flow stays well within the governor limit of 150 DML statements per transaction.

Anahtar Kavram

Flow Bulkification and Data Manipulation Best Practices
Tahmini Süre:2m 0s
Soru 1503Soru →

A Salesforce Administrator needs to configure a new Workflow Rule on the Lead object to automate lead assignment follow-ups and notifications. Place the administrative configuration steps in the correct sequential order from initial rule creation to deployment.

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

Cevabı ve açıklamayı göster

Cevap

The correct order to set up a Workflow Rule is: (1) Select the Lead object and specify the Rule Name and Evaluation Criteria, (2) Define the Rule Criteria using field criteria or a custom formula, (3) Configure immediate workflow actions such as Field Updates, Email Alerts, or Tasks, (4) Specify time triggers and add time-dependent workflow actions, and (5) Activate the Workflow Rule.
Building a Salesforce Workflow Rule follows a strict administrative sequence: object selection and evaluation timing must be defined first, followed by rule criteria filters. Once entry conditions exist, immediate actions and time-dependent triggers can be attached. Finally, the rule is activated to process records.

Adım Adım Çözüm

1
Select Object and Evaluation Criteria
Defines the target object context and determines whether the rule runs on creation, update, or re-evaluation.
Salesforce requires an object and evaluation context before any rule logic can be built.
2
Specify Rule Criteria
Establishes filter criteria or formula conditions required to trigger automated processing.
Entry conditions dictate which record records qualify for the workflow actions.
3
Add Immediate Actions
Attaches immediate Field Updates, Email Alerts, Tasks, or Outbound Messages to the rule.
Actions define the work performed as soon as a record meets criteria.
4
Add Time-Dependent Actions
Schedules delayed actions based on specified date fields or time offsets.
Time-dependent actions rely on existing rule criteria and require establishing time triggers.
5
Activate Rule
Enables the workflow rule for live record processing.
Rules remain inactive until explicitly activated by an administrator.

Anahtar Kavram

Workflow Rule Setup Lifecycle
Soru 1504Soru →

An administrator needs to implement an automated solution on a custom object named Vendor_Evaluation__c. Whenever a Vendor_Evaluation__c record is created or updated, the system must evaluate its numerical performance score and populate a Risk_Rating__c field on the triggering record before the record is saved to the database. The solution must maximize processing speed and avoid consuming extra DML statements within the execution transaction. Which flow trigger design should the administrator implement?

Cevabı ve açıklamayı göster

Cevap: A Record-Triggered Flow configured for Fast Field Updates (before-save) that updates the fields on the triggering record.

Cevap

A Record-Triggered Flow configured for Fast Field Updates (before-save) that updates the fields on the triggering record.
Configuring a Record-Triggered Flow for Fast Field Updates (before-save) allows field values on the triggering record to be updated in memory before database commit. This approach optimizes performance and avoids extra DML statements.

Adım Adım Çözüm

1
Analyze the automation requirement
The requirement specifies updating fields on the exact same record that initiated the trigger prior to committing to the database.
Identifying whether changes affect the triggering record or external/related records determines the optimal flow trigger type.
2
Evaluate execution order and transaction impact
Fast Field Updates (before-save) run up to 10 times faster than after-save automations because values are modified directly in memory ($Record) before saving to the database without explicit DML calls.
Updating same-record fields before save avoids additional DML statements, database round-trips, and secondary execution order cycles.
3
Select the correct Flow configuration
Choose a Record-Triggered Flow set to Fast Field Updates.
This configuration natively supports immediate, high-performance updates on the triggering record.

Anahtar Kavram

Fast Field Updates (Before-Save Record-Triggered Flows) for Same-Record Operations
Tahmini Süre:2m 0s
Soru 1505Soru →

A system administrator at a software enterprise needs to automate two separate data management requirements for a custom Subscription object linked to the standard Account object via a lookup relationship:

1. Automatically populate a custom Tier field on the triggering Subscription record prior to database commit whenever a new Subscription is created.
2. Update the parent Account record's Active Contract Status field immediately after a Subscription record is saved with an active status.

Which TWO automation design options adhere strictly to Salesforce architectural best practices for performance and capability limits? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Implement a Record-Triggered Flow configured for Fast Field Updates (Before-Save) to evaluate and update the Tier field on the triggering Subscription record.; Implement a Record-Triggered Flow configured for Actions and Related Records (After-Save) to update the parent Account record's Active Contract Status field.

Cevap

The correct architecture requires a Record-Triggered Flow configured for Fast Field Updates (Before-Save) for same-record updates, and a Record-Triggered Flow configured for Actions and Related Records (After-Save) for cross-object updates.
For same-record field modifications, Salesforce best practice dictates using a Record-Triggered Flow optimized for Fast Field Updates (Before-Save), as it modifies record values in memory prior to database storage without generating additional DML statements. For updates involving related objects (such as updating the parent Account), an Actions and Related Records (After-Save) Record-Triggered Flow must be used.

Adım Adım Çözüm

1
Analyze same-record field update requirements
Updating fields on the record that launched the flow must use a Fast Field Update (Before-Save) flow to execute before database save and prevent redundant DML operations.
Before-save flows run faster and eliminate additional save execution loops.
2
Analyze related-record update requirements
Updating fields on a parent or related record requires an Actions and Related Records (After-Save) flow because access to related records and system variables requires post-save context.
Cross-object record updates cannot take place in a before-save trigger context.
3
Evaluate relationship constraints for declarative aggregation
Declarative roll-up summary fields cannot be created on lookup relationships.
Salesforce standard Roll-Up Summary fields strictly require a Master-Detail relationship.

Anahtar Kavram

Selecting optimal record-triggered flow trigger timing and declarative tool limits for related records
Soru 1506Soru →

Universal Containers requires travel requests to be approved by a designated project lead identified in a custom User lookup field on the record, rather than the submitter's direct manager. Which approval step configuration allows the system to dynamically route the approval request to the user specified in that custom field?

Cevabı ve açıklamayı göster

Cevap: Select Automatically assign using the user field selected below and choose the custom User lookup field.

Cevap

Select 'Automatically assign using the user field selected below' and choose the custom User lookup field in the approval step settings.
In Salesforce approval step configuration, administrators can choose to assign approval requests automatically using a custom User lookup field present on the object. This allows dynamic routing to non-standard approvers without altering the record owner or modifying the standard user manager hierarchy.

Adım Adım Çözüm

1
Identify the routing requirement
Approval routing must be based on a custom User lookup field on the target record instead of the default manager hierarchy.
Standard manager routing evaluates the User.Manager hierarchy, whereas custom routing relies on custom User lookup fields.
2
Configure approval step assignment options
Select 'Automatically assign using the user field selected below' and choose the target lookup field.
Salesforce approval step settings natively support automated assignment via standard or custom User lookup fields defined on the record.

Anahtar Kavram

Dynamic Approval Routing via Custom User Fields
Tahmini Süre:1m 30s
Soru 1507Soru →

A Salesforce Administrator needs to enforce data quality standards on the Account object. Business policy requires that an error message be displayed to prevent saving an Account record under either of the following independent conditions:
1. The Account Type picklist is set to 'Partner' and the custom field Tax_ID__c is left blank.
2. The Account Rating picklist is set to 'Hot' and the AnnualRevenue numeric field is either blank or less than or equal to zero.

Which validation rule formula expressions will successfully evaluate to TRUE to enforce these data quality requirements? (Select TWO answers)

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

Cevabı ve açıklamayı göster

Cevap: AND(ISPICKVAL(Type, "Partner"), ISBLANK(Tax_ID__c)); AND(ISPICKVAL(Rating, "Hot"), OR(ISBLANK(AnnualRevenue), AnnualRevenue <= 0))

Cevap

The validation rules must evaluate to TRUE when data quality criteria are violated. The expression checking the Type picklist and the blank Tax_ID__c field using ISPICKVAL and ISBLANK, along with the expression checking the Rating picklist while incorporating ISBLANK and numeric comparison for AnnualRevenue, are the two correct formula expressions.
Validation rules trigger an error when the formula evaluates to TRUE. The formula combining ISPICKVAL(Type, "Partner") with ISBLANK(Tax_ID__c) correctly identifies when a Partner account is saved without a tax ID. The formula combining ISPICKVAL(Rating, "Hot") with OR(ISBLANK(AnnualRevenue), AnnualRevenue <= 0) correctly handles both blank and non-positive numerical values.

Adım Adım Çözüm

1
Analyze Condition 1 for the Account Type picklist and custom Tax_ID__c field.
The Type field is a picklist, requiring ISPICKVAL(Type, "Partner"). The Tax_ID__c field requires ISBLANK(Tax_ID__c). Combining them with AND() returns TRUE when both criteria are met.
Validation rules fire when the expression evaluates to TRUE.
2
Analyze Condition 2 for the Rating picklist and numeric AnnualRevenue field.
The Rating check requires ISPICKVAL(Rating, "Hot"). The revenue requirement must account for both null values and non-positive numbers: OR(ISBLANK(AnnualRevenue), AnnualRevenue <= 0).
Proper null handling ensures that unpopulated numerical fields trigger the validation rule properly alongside values <= 0.

Anahtar Kavram

Salesforce Validation Rule Formula Writing and Null Value Handling
Soru 1508Soru →

An administrator is designing an autolaunched flow to update secondary contact details across multiple related Contact records whenever a Partner Account undergoes a tier recalculation. To process the updates efficiently and avoid hitting SOQL and DML governor limits, which two design patterns should the administrator implement when manipulating record data in the flow?

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

Cevabı ve açıklamayı göster

Cevap: Iterate through the Contact collection using a Loop element, use an Assignment element to modify the fields on the current loop item, and use a second Assignment element to add the loop item to a new output collection variable.; Place a single Update Records element after the loop completes and pass the staged collection variable containing all modified Contact records to execute a bulk DML statement.

Cevap

The administrator should use Assignment elements inside the loop to modify fields and stage items into a collection variable, and then execute a single Update Records element outside the loop using that collection variable.
To follow Flow bulkification best practices, data manipulation must be performed in memory while inside a loop using Assignment elements to stage changes in a collection variable. Once the loop finishes, a single Update Records element is executed using the collection variable to update all records in one transaction statement.

Adım Adım Çözüm

1
Retrieve related records into a collection variable outside of any loops
Obtain all target records using a single Get Records element, consuming only 1 SOQL query.
Prevents issuing SOQL queries inside a loop.
2
Loop through the collection and stage changes in memory
In each iteration, update field values on the loop item using an Assignment element, then add the item to a new output collection variable using a second Assignment element.
In-memory collection manipulation does not count against governor limits.
3
Perform bulk DML operation after loop completion
Pass the staged collection variable into an Update Records element placed after the loop path finishes.
Executes a single bulk update, consuming only 1 DML statement for all processed records.

Anahtar Kavram

Flow Bulkification and Collection Data Manipulation Best Practices
Tahmini Süre:2m 0s
Soru 1509Soru →

A healthcare provider processes high-volume bulk imports of Patient Intake records daily. An administrator must implement an automation requirement: whenever a Patient Intake record is created or updated with a status of 'Completed' and a pending insurance verification flag, a custom date field named Verification Due Date on that same Patient Intake record must immediately be set. The architecture team mandates that the solution must maximize system performance, minimize CPU consumption during bulk operations, and strictly adhere to Salesforce automation guidelines. Which automation solution should the administrator implement?

Cevabı ve açıklamayı göster

Cevap: A Record-Triggered Flow configured for Fast Field Updates (Before-Save)

Cevap

A Record-Triggered Flow configured for Fast Field Updates (Before-Save)
The correct solution is a Record-Triggered Flow configured for Fast Field Updates (Before-Save). Salesforce architectural best practices dictate using before-save record-triggered flows whenever updating fields on the record that triggered the automation. Because updates occur in-memory prior to committing the record to the database, this approach executes up to 10 times faster than after-save automation and avoids triggering redundant system execution steps.

Adım Adım Çözüm

1
Analyze the automation requirement and target record scope.
The field update is performed strictly on the same record that triggers the execution when created or updated.
Identifying whether the target is the triggering record or a related record determines the optimal flow trigger type.
2
Evaluate execution performance and governor limit implications.
Before-save flows run significantly faster than after-save flows because changes are applied directly to the record in memory before it is written to the database.
Fast Field Updates avoid additional DML statements, extra database writes, re-evaluation of validation rules, and cascading execution events.
3
Select the appropriate declarative tool matching Salesforce architectural best practices.
Choose Record-Triggered Flow (Fast Field Updates / Before-Save).
Salesforce architecture guidelines specifically prescribe before-save record-triggered flows for same-record field modifications.

Anahtar Kavram

Automation Tool Selection: Fast Field Updates (Before-Save Flow) vs Actions and Related Records (After-Save Flow)
Tahmini Süre:2m 0s
Soru 1510Soru →

An administrator at CloudData SaaS is designing automation for the custom object Subscription_Contract__c. The business requires the following two automated processes:

1. Whenever a Subscription_Contract__c record's status is changed to "Pending Renewal", the system must automatically calculate and update the Renewal_Discount__c field on that same triggering contract record prior to committing changes to the database.
2. Whenever a Subscription_Contract__c record's status is changed to "Renewed", the system must create a child Renewal_Notice__c record and execute an outbound callout notification to an external billing endpoint.

Which TWO flow trigger configurations should the administrator select to fulfill these requirements in accordance with Salesforce best practices? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Configure a Record-Triggered Flow optimized for Fast Field Updates (Before-Save) to handle the same-record field update on Subscription_Contract__c.; Configure a Record-Triggered Flow set to Actions and Related Records (After-Save) to create the child Renewal_Notice__c record and initiate the external outbound callout.

Cevap

The administrator should use a Before-Save (Fast Field Updates) Record-Triggered Flow to update fields on the triggering Subscription_Contract__c record, and an After-Save (Actions and Related Records) Record-Triggered Flow to create the child Renewal_Notice__c record and make external callouts.
The solution requires two distinct trigger types according to Salesforce automation best practices. Fast Field Updates (Before-Save) flows are designed specifically for updating fields on the record that launched the flow prior to committing to the database. Actions and Related Records (After-Save) flows are required when performing operations on related records (such as inserting child records) or performing integrations and external callouts.

Adım Adım Çözüm

1
Analyze Requirement 1 for same-record field updates prior to database commit.
Identified that Fast Field Updates (Before-Save Record-Triggered Flow) is the optimal trigger type because it modifies values on `$Record` directly before saving, avoiding unnecessary DML overhead.
Before-save triggers run 10x faster than after-save triggers for same-record updates and do not require DML elements.
2
Analyze Requirement 2 for creating child records and calling external endpoints upon renewal.
Identified that Actions and Related Records (After-Save Record-Triggered Flow) is required.
Creating related records (DML operations on other objects) and executing callouts/actions require the record ID to exist and the database transaction to be in the after-save phase.

Anahtar Kavram

Selecting between Before-Save (Fast Field Updates) and After-Save (Actions and Related Records) Flow triggers based on target object scope and execution capabilities.
Soru 1511Soru →

A Salesforce Administrator needs to design an autolaunched flow that processes multiple related Opportunity records associated with an Account. The business requirement demands updating specific field values across all related open opportunities while maintaining optimal performance and strictly adhering to Salesforce governor limits. Which TWO design practices should the administrator implement in Flow Builder?

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

Cevabı ve açıklamayı göster

Cevap: Use an Assignment element inside the loop to accumulate modified records into a collection variable, then place a single Update Records element outside the loop.; Apply filter conditions in the Get Records element to retrieve only open Opportunities, minimizing the dataset before entering the loop.

Cevap

The administrator should accumulate updated records into a collection variable inside the loop and perform a single Update Records operation outside the loop, as well as pre-filter the Get Records element to only query open Opportunities.
To maintain optimal flow performance and comply with Salesforce governor limits, flows processing multiple records must be bulkified. Filtering query results in the Get Records element ensures that only target records enter the transaction. Accumulating field updates into a collection variable via Assignment elements during iteration allows the entire set to be updated in a single DML statement placed outside the loop.

Adım Adım Çözüm

1
Filter query results at the data source
Only open Opportunities are retrieved into the flow variable.
Reduces record count and prevents evaluating unnecessary records inside the loop.
2
Assign updated field values to a record collection variable inside the loop
All changes are held in memory without issuing database updates per iteration.
Consolidates multiple record updates into a single collection structure.
3
Execute the Update Records element after loop execution completes
A single DML statement updates all records in the collection at once.
Prevents exceeding the Salesforce governor limit for maximum DML statements.

Anahtar Kavram

Flow Bulkification and Governor Limit Prevention
Soru 1512Soru →

An IT Asset Manager at a healthcare enterprise wants to automatically send an automated XML message to an external enterprise resource planning (ERP) system whenever a custom object record tracking Medical Equipment is updated to a status of 'Needs Maintenance'. The requirement specifies that this integration must be accomplished using native declarative Workflow capabilities without custom Apex code. Which workflow action should the administrator configure to satisfy this requirement?

Cevabı ve açıklamayı göster

Cevap: Outbound Message

Cevap

Outbound Message is the correct workflow action to send structured XML messages to an external system endpoint declaratively.
Outbound Message is one of the four core actions available in Workflow Rules. It enables sending a designated SOAP XML message to a specified external endpoint URL automatically when the workflow criteria are met, completely declaratively without custom Apex development.

Adım Adım Çözüm

1
Analyze the requirements for automated external system notification.
The requirement specifies sending an XML message to an external ERP system URL declaratively upon record update.
Salesforce Workflow Rules support 4 native actions: Tasks, Email Alerts, Field Updates, and Outbound Messages.
2
Evaluate the capability of each workflow action type.
Only Outbound Messages send a SOAP formatted XML payload to an external endpoint URL natively without writing Apex callouts.
Outbound Messages allow designated fields to be transmitted securely to listening web servers.

Anahtar Kavram

Workflow Outbound Messages for External System Integrations
Soru 1513Soru →

A Salesforce Administrator is building an autolaunched flow to automatically update open Opportunities when a partner Account is set to Inactive. To adhere to Salesforce governor limits and bulkification design patterns, in what sequence should the administrator place the Flow elements to update the stage of these Opportunities to 'Closed Lost'?

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

Cevabı ve açıklamayı göster

Cevap

The correct sequence for bulkified flow execution is: 1) Get Records to query open Opportunities, 2) Loop to iterate through the retrieved collection, 3) Assignment element inside the loop to modify field values and add records to a new collection variable, and 4) Update Records element placed after the loop to perform a single DML operation.
Following standard bulkification practices, data must first be retrieved via Get Records into a collection. A Loop element then steps through each record while an Assignment element updates field values in memory and collects them into a new collection variable. Finally, an Update Records element executes once on the 'After Last Item' path to commit all record changes in a single transaction.

Adım Adım Çözüm

1
Execute Get Records element outside any loop.
Obtains a Record Collection of all target Opportunity records efficiently with one SOQL query.
Prevents SOQL governor limit errors by avoiding data queries inside iterative steps.
2
Pass the retrieved collection into a Loop element.
Iterates through each Opportunity record sequentially.
Allows field assignment logic to evaluate every individual record in memory.
3
Use an Assignment element within the Loop iteration path.
Sets StageName to 'Closed Lost' and adds the modified record to a secondary collection variable.
Staging modifications in a collection variable keeps all changes in memory during loop execution.
4
Connect the 'After Last Item' path of the Loop to an Update Records element.
Persists all modifications to the database in a single DML operation.
Performing DML outside the loop adheres to Salesforce bulkification best practices.

Anahtar Kavram

Flow Bulkification and Element Sequencing
Tahmini Süre:1m 30s
Soru 1514Soru →

A Salesforce Administrator at a medical equipment supplier is building a custom report to analyze company assets. Management has specified two key requirements for this report:
1. Categorize asset records into three pricing tiers based on numeric value ranges without creating a new custom field on the object schema.
2. Limit the report display so it only includes Account records that currently have at least one related Service Contract.

Which two report configuration options should the administrator implement to satisfy these business 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 asset purchase price field to define custom numeric ranges.; Add a Cross Filter to the report specifying Accounts with Service Contracts.

Cevap

The administrator should add a Bucket Field on the asset price field to group records into pricing tiers and apply a Cross Filter on Accounts with Service Contracts to isolate accounts with related contract records.
Creating a Bucket Field on the numeric asset price field fulfills the requirement of grouping values into custom tiers directly within the report editor without modifying the underlying database schema. Applying a Cross Filter set to 'Accounts with Service Contracts' enforces the requirement to include only account records that possess associated child service contract records.

Adım Adım Çözüm

1
Identify the requirement for grouping records without schema changes
Recognize that creating a Bucket Field directly in the report editor categorizes values without adding custom fields to the Salesforce object.
Bucket fields are designed for ad-hoc report categorization of numeric, text, or picklist values.
2
Identify the requirement for filtering across related objects
Determine that a Cross Filter (Accounts WITH Service Contracts) restricts the report output based on child record existence.
Cross filters evaluate parent-child relationships dynamically within Salesforce reports.

Anahtar Kavram

Report Filtering, Filter Logic, and Bucketing
Soru 1515Soru →

A Salesforce Administrator is configuring an approval process for high-value Opportunity records requiring executive sign-off. Which two automated action types can be added directly to Final Approval Actions within a Salesforce Approval Process? (Select 2 options)

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

Cevabı ve açıklamayı göster

Cevap: Field Update to modify a field value on the submitted record or its master parent record; Email Alert to send automated notifications using specified email templates

Cevap

The two automated action types that can be directly added to Final Approval Actions are Field Update and Email Alert.
Salesforce Approval Processes natively support four distinct automated actions across all stages (Initial Submission, Step Actions, Final Approval, Final Rejection, and Recall): Field Update, Email Alert, Task creation, and Outbound Message. Field Update allows updating fields on the record or its master detail parent, and Email Alert sends formatted notifications.

Adım Adım Çözüm

1
Identify native automated actions supported by Salesforce Approval Processes
Salesforce Approval Processes natively support four types of automated actions: Field Updates, Email Alerts, Tasks, and Outbound Messages.
These four actions can be configured in Initial Submission Actions, Approval Step Actions, Final Approval Actions, Final Rejection Actions, and Recall Actions.
2
Evaluate the proposed options against standard configuration capabilities
Field Update and Email Alert are directly supported. Creating a arbitrary record or directly calling an Autolaunched Flow are not selectable actions in the approval action builder.
Actions like record creation or Flow triggering require post-approval record updates to trigger a record-triggered flow or Apex.

Anahtar Kavram

Salesforce Approval Process Automated Action Types
Tahmini Süre:1m 0s
Soru 1516Soru →

An operations manager at a logistics company requires automated processing on the custom object Shipment__c. When a shipment status changes to "Delayed", an immediate Outbound Message must be sent to an external tracking service. Additionally, if the shipment status remains "Delayed" for 24 hours, a time-dependent Task should be assigned to the Logistics Supervisor. While attempting to configure the workflow rule, the administrator discovers that the option to add a time trigger is unavailable. Which evaluation criteria selection is preventing the administrator from adding the time-dependent action?

Cevabı ve açıklamayı göster

Cevap: Created, and every time it's edited

Cevap

The evaluation criteria 'Created, and every time it's edited' prevents the addition of time-dependent workflow actions.
In Salesforce Workflow Rules, time-dependent actions cannot be defined for rules set to evaluate 'Created, and every time it's edited'. To configure time triggers, the workflow rule evaluation criteria must be set to 'Created' or 'Created, and any time it's edited to subsequently meet criteria'.

Adım Adım Çözüm

1
Identify the requirement
The business process requires both an immediate action (Outbound Message) and a time-dependent action (Task scheduled after 24 hours).
Time-dependent actions require specific evaluation criteria support in workflow rules.
2
Analyze Salesforce Workflow Rule evaluation criteria limitations
Salesforce prohibits time-based triggers on workflow rules configured to evaluate 'Created, and every time it's edited' to prevent infinite or ambiguous queueing of time actions on successive record edits.
Without a clear entry/exit transition condition, time triggers could re-evaluate unpredictably on every save.
3
Select the option that causes the trigger restriction
Selecting 'Created, and every time it's edited' disables the 'Add Time Trigger' feature in the workflow rule setup interface.
To enable time triggers, the administrator must choose either 'Created' or 'Created, and any time it's edited to subsequently meet criteria'.

Anahtar Kavram

Workflow Rule Evaluation Criteria and Time-Dependent Action Restrictions
Soru 1517Soru →

A logistics enterprise uses a custom object named Freight Shipment to track international deliveries. The operations team has defined two requirements when a Freight Shipment record is updated:

1. Automatically calculate and update the Estimated Delivery Date and Risk Status fields on the triggering Freight Shipment record prior to saving changes to the database.
2. If the shipment status is updated to 'Delayed', automatically create a related Audit Task record assigned to the logistics manager.

Which automation design adheres to Salesforce architecture best practices while optimizing performance?

Cevabı ve açıklamayı göster

Cevap: Implement a before-save Record-Triggered Flow (Fast Field Updates) for updating the Freight Shipment fields, and an after-save Record-Triggered Flow (Actions and Related Records) to create the Audit Task record.

Cevap

Implement a before-save Record-Triggered Flow (Fast Field Updates) for updating the Freight Shipment fields, and an after-save Record-Triggered Flow (Actions and Related Records) to create the Audit Task record.
The requirement specifies modifying fields on the triggering record as well as creating a related Audit Task record. Salesforce best practice dictates using a before-save Record-Triggered Flow (Fast Field Updates) to modify fields on the triggering record without incurring extra DML overhead, and using an after-save Record-Triggered Flow (Actions and Related Records) to create related records after the primary record has been committed to the database.

Adım Adım Çözüm

1
Analyze the requirement for same-record field updates.
Field updates on the triggering record before database commit require a Fast Field Updates (before-save) Record-Triggered Flow.
Before-save flows execute up to 10x faster than after-save updates because they modify values in memory before the record is saved to the database.
2
Analyze the requirement for creating a related record (Audit Task).
Creating related records requires an Actions and Related Records (after-save) Record-Triggered Flow.
Before-save flows cannot generate record IDs or create external/related objects like Task.
3
Combine into an architectural automation tool choice.
Use a combination of before-save for same-record field updates and after-save for related record creation.
This complies with Salesforce architectural recommendations for optimal performance and governor limit efficiency.

Anahtar Kavram

Selecting optimal Record-Triggered Flow trigger types (Fast Field Updates vs. Actions and Related Records) based on execution timing and target record context.
Soru 1518Soru →

A Salesforce Administrator is building an After-Save Record-Triggered Flow on the Account object that executes when an Account's rating changes to 'Hot'. The requirement is to set the Status of all related open Cases to 'Escalated' while adhering to Salesforce governor limits and best practices. Which design pattern should the administrator implement within Flow Builder to accomplish this outcome?

Cevabı ve açıklamayı göster

Cevap: Query related open Cases using a Get Records element into a record collection variable, iterate over the collection with a Loop element using an Assignment element to modify the Status field in memory, and execute a single Update Records element passing the collection variable after the loop finishes.

Cevap

Query related open Cases into a record collection variable using a Get Records element, loop through the collection to modify the Status field using an Assignment element inside the loop, and perform a single Update Records operation on the collection variable after the loop completes.
The correct pattern uses a Get Records element to gather related records into a collection, iterates over the collection to make field modifications using an Assignment element inside the loop, and then uses a single Update Records element outside the loop to update the entire collection in one DML transaction. This ensures optimal performance and prevents hitting governor limits.

Adım Adım Çözüm

1
Retrieve related records into memory using Get Records
A record collection variable containing all open Cases associated with the Account is populated in a single SOQL query.
Bulkifying data retrieval avoids governor limits on database queries.
2
Iterate and modify fields in memory using Loop and Assignment elements
The Status field of each Case record in the collection variable is updated to 'Escalated' without invoking DML statements.
Assignment elements perform in-memory changes without performing database transactions inside the loop.
3
Commit all changes to the database using a single Update Records element after the loop
All updated Case records in the collection are written to Salesforce in a single DML statement.
Executing DML outside the loop ensures the flow consumes only 1 DML statement regardless of how many child records are processed.

Anahtar Kavram

Bulkification in Flow Builder using collections, loops, and external DML elements
Soru 1519Soru →

An administrator needs to enforce a data quality requirement on the Contact object. Whenever a contact's custom picklist field `Contact_Status__c` is set to 'Active', the `Tax_Identification_Number__c` text field must not be left blank. Which validation rule formula correctly prevents saving the record when this requirement is violated?

Cevabı ve açıklamayı göster

Cevap: AND( ISPICKVAL(Contact_Status__c, 'Active'), ISBLANK(Tax_Identification_Number__c) )

Cevap

The correct formula is AND( ISPICKVAL(Contact_Status__c, 'Active'), ISBLANK(Tax_Identification_Number__c) ). Validation rules trigger an error when the formula evaluates to TRUE. Combining ISPICKVAL for picklist evaluation and ISBLANK for text field null checking within an AND statement ensures the error only fires when the status is Active and the required field is missing.
The formula correctly uses ISPICKVAL to evaluate the custom picklist value and ISBLANK to verify whether the text field is empty. Enclosing both conditions within the AND function ensures that the validation error fires only when the contact is set to 'Active' and the Tax Identification Number is missing.

Adım Adım Çözüm

1
Identify picklist function requirements
Use ISPICKVAL(Contact_Status__c, 'Active') to test picklist values in validation rule syntax.
Standard equality operators cannot directly evaluate picklist fields in standard formula fields unless converted or wrapped in ISPICKVAL.
2
Identify blank value checking requirements
Use ISBLANK(Tax_Identification_Number__c) to determine if the text field lacks data.
ISBLANK is the recommended function in Salesforce for checking null or empty text field values.
3
Combine logical conditions
Wrap both functions in an AND() logical operator so the formula evaluates to TRUE only when both conditions occur simultaneously.
Validation rules display an error message and block save operations when the formula condition evaluates to TRUE.

Anahtar Kavram

Validation Rule Logic and Null Value Handling
Tahmini Süre:1m 30s
Soru 1520Soru →

A Salesforce Administrator at a telecommunications provider needs to build a report displaying Accounts that have active Contracts but do not have any open Cases. Additionally, executive leadership wants the report to group Accounts into three distinct spending tiers ("Enterprise", "Mid-Market", and "SMB") based on their Annual Revenue, without creating custom fields on the Account object. Which combination of reporting features should the administrator use to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Add a Cross Filter for Accounts WITH Contracts, add a Cross Filter for Accounts WITHOUT Cases, and create a Bucket Field based on Annual Revenue.

Cevap

The administrator should add a Cross Filter for Accounts WITH Contracts, a Cross Filter for Accounts WITHOUT Cases, and create a Bucket Field based on Annual Revenue.
Cross Filters allow reports to filter parent object records (Accounts) by the presence (WITH) or absence (WITHOUT) of related child object records (Contracts and Cases). Bucket Fields allow users to group numeric values like Annual Revenue into custom defined ranges ('Enterprise', 'Mid-Market', 'SMB') within the report builder without requiring custom fields.

Adım Adım Çözüm

1
Identify the requirement for filtering Accounts based on related child objects (Contracts and Cases).
Determine that Cross Filters are required to filter Accounts WITH Contracts and Accounts WITHOUT Cases.
Standard field filters cannot filter parent records based on the existence or absence of related child object records.
2
Identify the requirement to categorize Accounts into spending tiers based on Annual Revenue without adding schema fields.
Determine that a Bucket Field on the numeric Annual Revenue field should be defined.
Bucket fields allow report builders to quickly categorize numerical ranges, picklists, or text fields into custom buckets directly inside the report interface without admin schema modifications.

Anahtar Kavram

Cross Filters and Bucket Fields in Salesforce Reporting
ÖncekiSayfa 76 / 90Sonraki
Tüm alıştırma soruları — Salesforce Certified Administrator | Examkin