Salesforce Exam Platform Developer II Topic 1 Question 87 Discussion

Actual exam question for Salesforce's Platform Developer II exam

Question #: 87
Topic #: 1

As part of point-to-point integration, a developer must call an external web service which, due to high demand, takes a long time to provide a response. As part of the request, the developer must collect key Inputs from the end user before making the callout. Which two elements should the developer use to Implement these business requirements?

Choose 2 answers

ALightning web component

B2 Apex method that returns a Continuation object

CScreen Flow

DProcess Builder

Show Suggested Answer

Suggested Answer: A, B

by Judy at Apr 12, 2024, 03:08 AM

Limited Time Offer

25%

Off

Get Premium Platform Developer II Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Cyril

1 years ago

I believe Screen Flow may also be useful for collecting key inputs from the end user before making the callout.

upvoted 0 times

...

Tresa

1 years ago

What about using a Quidditch broom to call the web service? I heard that's the latest Salesforce technology. Joking aside, B and C seem like the way to go.

upvoted 0 times

...

Marcelle

1 years ago

Ha! Process Builder? Really? That's like trying to use a hammer to screw in a lightbulb. A and C all the way!

upvoted 0 times

Pamella

12 months ago

C) Screen Flow

upvoted 0 times

...

Tresa

12 months ago

A) Lightning web component

upvoted 0 times

...

Marsha

12 months ago

C) Screen Flow

upvoted 0 times

...

Alison

1 years ago

A) Lightning web component

upvoted 0 times

...

Vallie

1 years ago

C) Screen Flow

upvoted 0 times

...

Trina

1 years ago

A) Lightning web component

upvoted 0 times

...

Thomasena

1 years ago

I agree with Lightning web component, but we also need Apex methods that return Continuation object for handling the long response time.

upvoted 0 times

...

Tracey

1 years ago

I'm not sure about B. Isn't that for long-running Apex jobs? I think A and C are better options here.

upvoted 0 times

Domonique

1 years ago

C) Screen Flow

upvoted 0 times

...

Alba

1 years ago

A) Lightning web component

upvoted 0 times

...

Ressie

1 years ago

Definitely B and C! Async Apex and Flows are perfect for handling long-running external service calls.

upvoted 0 times

Edgar

1 years ago

C) Screen Flow

upvoted 0 times

...

Vanesa

1 years ago

B) 2 Apex method that returns a Continuation object

upvoted 0 times

...

Stefania

1 years ago

I think we should use Lightning web component for this.

upvoted 0 times

...

Charlene

1 years ago

Hmm, I don't know, the Process Builder option seems a bit odd for this kind of scenario. I can't really see how that would fit in with the requirement to collect user input.

upvoted 0 times

...

Judy

1 years ago

You know, I was thinking the same thing. The Screen Flow could be a nice way to handle the UI, and then the Apex Continuation object could manage the asynchronous web service call.

upvoted 0 times

Catarina

1 years ago

C) Screen Flow

upvoted 0 times

...

Laurel

1 years ago

B) 2 Apex method that returns a Continuation object

upvoted 0 times

...

Marge

1 years ago

Ooh, I bet the Screen Flow option could be really useful here. The developer could use that to collect the user input, and then kick off the web service call in the background.

upvoted 0 times

...

Jovita

1 years ago

Yeah, the options given seem to point towards using some kind of asynchronous processing. I'm guessing the Continuation object in Apex might be a good choice, but I'm not sure how that would integrate with the user input collection.

upvoted 0 times

...

Mitzie

1 years ago

I agree, the key here is to avoid blocking the user while waiting for the web service response. I think the developer should use a combination of approaches to achieve this.

upvoted 0 times

...

Mollie

1 years ago

Hmm, this question seems focused on handling long-running web service calls. I think the developer needs a way to collect user input and then asynchronously process the request without locking up the user interface.

upvoted 0 times

...