Legit PDI Exam Download

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

The @HttpInvocable annotation is used to expose an Apex class as a RESTful web service. This allows the class to be invoked by a REST client, enabling external systems to interact with Salesforce via the API. The methods within the class that are exposed as REST web services must be static and global or public. References: Apex Developer Guide

The @InvocableMethod annotation is used to identify methods that can be run as invocable actions from a flow, a bot, or an NBA. There are some considerations when using this annotation in Apex, such as:

• A method using the @InvocableMethod annotation must define a return value, even if it is null. This is because the invocable action must return a value to the flow, bot, or NBA that invokes it.
• A method using the @InvocableMethod annotation can have only one input parameter, which can be a list of a primitive data type, a list of a specific sObject type, or a list of a generic sObject type. This is because the invocable action can accept only one input value from the flow, bot, or NBA that invokes it.
• A method using the @InvocableMethod annotation must be declared as static, because it is not associated with a specific instance of the class that defines it. Static methods can be invoked without creating an object of the class.
• A method using the @InvocableMethod annotation can be declared as either public or global, depending on the visibility of the invocable action. Public methods are visible within the same namespace, while global methods are visible across namespaces.
• Only one method using the @InvocableMethod annotation can be defined per Apex class, because each invocable action is associated with a single Apex class. Multiple invocable methods in the same class would cause ambiguity and confusion.

References: InvocableMethod Annotation | Apex Developer Guide, How to Invoke Apex from Flows Using InvocableMethod Annotation

• By providing device-awareness for mobile and desktops. This is true because the Lightning Component framework is a UI framework for developing Lightning components for mobile and desktop devices. Lightning web components and Aura components can coexist and interoperate on a page. The framework takes care of rendering the components appropriately for different devices and screen sizes1.
• By providing an Agile process with default steps. This is false because the Lightning Component framework does not provide any specific process or methodology for developing solutions. Developers can use any process that suits their needs, such as Agile, Waterfall, or Scrum2.
• By providing code review standards and processes. This is false because the Lightning Component framework does not provide any code review standards or processes. Developers are responsible for ensuring the quality and maintainability of their code, and they can use tools such as code analysis, testing, and debugging to help them3.
• By providing change history and version control. This is false because the Lightning Component framework does not provide any change history or version control features. Developers can use tools such as Git, SVN, or Salesforce DX to manage their source code and track changes.

References:

• 1: Introducing Aura Components
• 2: Agile Development with Salesforce
• 3: Code Quality and Code Analysis
• : Source Control and Salesforce Development