Which two methods should the developer implement to fulfill the business requirement?

Universal Containers recently transitioned from Classic to Lightning Experience.

One of its business processes requires certain values from the Opportunity cbject to be sent via an HTTP REST callout to its external order management system when the user presses a custom button on the Opportunity detail page.

Example values are as follows:

* Name

* Amount

* Account

Which two methods should the developer implement to fulfill the business requirement? Choose 2 answers
A . Create a Remote Action on the Opportunity object that executes an Apex immediate action to
perform the HTTP REST callout whenever the Opportunity Is updated.
B . Create a custom Visualforce quick action that performs the HTTP REST callout, and use a Visualforce quick action to expose the component on the Opportunity detail page.
C . Create a Lightning component quick action that performs the HTTP REST callout, and use a Lightning Action to expose the component on the Opportunity detail page.
D . Create an after update trigger on the Opportunity object that calls a helper method using @Future (Callour=true) to perform the HTTP REST callout.

View Answer

Answer: B, C

Explanation:

To send Opportunity values via an HTTP REST callout when a user presses a custom button in

Lightning Experience:

Option B: Create a custom Visualforce quick action

A Visualforce page with a custom controller can perform the callout.

The Visualforce page can be added as a quick action on the Opportunity page.

Reference: "You can use Visualforce to create custom quick actions."

― Salesforce Help: Quick Actions

Option C: Create a Lightning component quick action

A Lightning component can perform the callout when invoked.

The component can be added to the Opportunity page as a quick action.

Reference: "Use Lightning components to create custom actions that can be added to Lightning Experience and the Salesforce mobile app."

― Salesforce Help: Lightning Component Actions Why Other Options Are Incorrect:

Option A:

Remote Actions are used in Visualforce for client-side calls and are not applicable here. Performing the callout whenever the Opportunity is updated does not meet the requirement of initiating the action via a button click.

Option D:

An after-update trigger would execute on every update, not just when the user presses a button. Using @future methods may not execute immediately and can’t be invoked directly by the user action.