Salesforce Updated PDI Exam Questions and Answers by teodora

A record-triggered flow is an automation tool that allows you to run a flow when a record is created, updated, or deleted1. You can use a record-triggered flow to meet the business requirement of deleting associated opportunity records when the related account is deleted. You can configure the flow to trigger when an account is deleted, and then use the Get Records element to query the related opportunities. Then, you can use the Delete Records element to delete the queried opportunities2. This way, you can ensure that the opportunity records are proactively deleted when the account is deleted, without writing any code.

Workflow rules and process builder are also automation tools that can run when a record is created, updated, or deleted, but they cannot delete records directly. You would need to use an Apex action or a custom field update to achieve the same functionality3 . Scheduled jobs are Apex classes that run at specified intervals, such as daily or weekly. They are not suitable for the business requirement of deleting records when another record is deleted, as they are not triggered by record changes.

References:

• Record-Triggered Flows | Salesforce Help
• Delete Records with a Record-Triggered Flow | Salesforce Trailhead
• Workflow Rules | Salesforce Help
• [Process Builder | Salesforce Help]
• [Scheduled Apex | Apex Developer Guide | Salesforce Developers]

A Paused Flow Interview is a flow instance that has been paused by a Wait element or a Pause element. A developer can find information about a Paused Flow Interview on the Paused Flow Interviews related list for a given record, if the flow is configured to store the record ID in the Interview Label field. This allows the developer to resume, delete, or view the details of the paused flow interview from the record page1. The other options are not valid ways to find information about a Paused Flow Interview in the Lightning UI.

References:

• 1: Manage Paused Flow Interviews

An Apex REST class is a custom class that defines methods that can be invoked via HTTP requests. The developer can use the @RestResource annotation to expose the class as a REST resource, and use the @HttpGet, @HttpPost, @HttpPut, or @HttpDelete annotations to define the methods that correspond to the HTTP verbs. The developer can also use the RestContext class to access the request and response information, such as the parameters, headers, and body. An Apex REST class can be used to integrate with an external order management system by sending and receiving JSON or XML data, and parsing and serializing it using the built-in Apex methods. The developer can then use the flow:callApex action in the flow to invoke the Apex REST class and pass the data to the screen element. An Apex REST class is different from the other options listed, as they are not suitable for this requirement. An Apex controller is a class that provides logic and data for a Visualforce page or a Lightning component, not a flow. An outbound message is a message that is sent from Salesforce to an external system when a workflow rule is triggered, not when a flow is executed. An invocable method is a method that is annotated with @InvocableMethod and can be called from a process, a flow, or a REST API, but it cannot make HTTP requests to an external system. References:

• Apex REST Methods from the Apex Developer Guide
• Call Apex from Flow from the Salesforce Help
• Integrate with External Systems Using Apex REST Services from the Salesforce Trailhead

An Assignment Flow element is a logic element that allows you to set values in variables, collection variables, record variables, record collection variables, and global variables1. You can use an Assignment Flow element to assign the support representative name to the custom field on the Case object based on the case origin. This way, you can automate the case assignment process without writing any code or using any formula. A trigger, a formula field, and a validation rule are not the best solutions for this scenario, as they either require code, are not dynamic, or do not change the field value. References: 1: Flow Element: Assignment - Salesforce