nerdexam
Salesforce

PDI · Question #18

Universal Containers recently transitioned from Classic to Lighting Experience. One of its business processes requires certain value from the opportunity object to be sent via HTTP REST callout to…

The correct answer is A. Create a Lightning component that performs the HTTP REST callout, and use a Lightning Action D. Create a Visualforce page that performs the HTTP REST callout, and use a Visualforce quick. To enable user-initiated HTTP REST callouts from an Opportunity page in Lightning Experience, a developer can use a Lightning component as a Lightning Action or a Visualforce page as a Visualforce quick action.

Submitted by miguelv· Apr 18, 2026User Interface

Question

Universal Containers recently transitioned from Classic to Lighting Experience. One of its business processes requires certain value from the opportunity object to be sent via HTTP REST callout to its external order management system based on a user-initiated action on the opportunity page. Example values are as follow:

Name Amount Account Which two methods should the developer implement to fulfill the business requirement? (Choose 2 answers)

Options

  • ACreate a Lightning component that performs the HTTP REST callout, and use a Lightning Action
  • BCreate a Process Builder on the Opportunity object that executes an Apex immediate action to
  • CCreate an after update trigger on the Opportunity object that calls a helper method using
  • DCreate a Visualforce page that performs the HTTP REST callout, and use a Visualforce quick

How the community answered

(14 responses)
  • A
    79% (11)
  • B
    7% (1)
  • C
    14% (2)

Why each option

To enable user-initiated HTTP REST callouts from an Opportunity page in Lightning Experience, a developer can use a Lightning component as a Lightning Action or a Visualforce page as a Visualforce quick action.

ACreate a Lightning component that performs the HTTP REST callout, and use a Lightning ActionCorrect

A Lightning component can be developed to perform the HTTP REST callout and then exposed as a Lightning Action on the Opportunity object layout, allowing users to trigger it directly from the Opportunity record page.

BCreate a Process Builder on the Opportunity object that executes an Apex immediate action to

Process Builder actions, even those invoking Apex, are typically automated processes that run in the background based on criteria, not direct user-initiated actions from the UI on a specific page.

CCreate an after update trigger on the Opportunity object that calls a helper method using

An `after update` trigger is a server-side automation that fires automatically after a record is saved; it is not a user-initiated action from the page's user interface.

DCreate a Visualforce page that performs the HTTP REST callout, and use a Visualforce quickCorrect

A Visualforce page can contain the logic for an HTTP REST callout, and this page can be configured as a Visualforce quick action on the Opportunity object, providing a user-initiated button for the callout.

Concept tested: User-initiated actions for HTTP callouts

Source: https://developer.salesforce.com/docs/atlas.en-us.lightning.meta/lightning/actions_creating.htm

Topics

#Lightning Experience#External Integrations#Quick Actions#Apex Callouts

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full PDI Practice