New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Certified Platform Developer II (Plat-Dev-301) Exam - Topic 5 Question 112 Discussion

Actual exam question for Salesforce's Salesforce Certified Platform Developer II (Plat-Dev-301) exam
Question #: 112
Topic #: 5
[All Salesforce Certified Platform Developer II (Plat-Dev-301) Questions]

A developer needs to send Account records to an external system for backup purposes. The process must take a snapshot of Accounts as they are saved and then make a callout to a RESTful web service. The web service can only receive, at most, one record per call.

What should a developer do to implement these requirements?

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

0/2000 characters
Ettie
2 months ago
Wait, can we really only send one record at a time? That seems limiting.
upvoted 0 times
...
Yen
3 months ago
Definitely agree with A, it fits the requirements perfectly!
upvoted 0 times
...
Yuriko
3 months ago
I’m not sure about B, platform events might be overkill for this.
upvoted 0 times
...
Elza
3 months ago
C sounds interesting, but is exposing an Apex class really necessary here?
upvoted 0 times
...
Filiberto
3 months ago
I think option A is the best choice for handling multiple records.
upvoted 0 times
...
Lera
3 months ago
Exposing an Apex class as a web service sounds familiar, but I can't recall if it would allow for the necessary snapshot functionality when saving the Account records.
upvoted 0 times
...
Mariann
4 months ago
I practiced a similar question about making callouts, and I feel like a future method might be the right choice here, but I need to double-check if it can handle the snapshot requirement.
upvoted 0 times
...
Gail
4 months ago
I think platform events could be a good option since they allow for asynchronous processing, but I'm not entirely clear on how they would work with the REST callout.
upvoted 0 times
...
Josephine
4 months ago
I remember studying the Queueable interface, but I'm not sure if it's the best fit for this scenario since it might not handle the one record per call requirement effectively.
upvoted 0 times
...
Lynette
4 months ago
I'm pretty confident that the future method is the best solution here. It will allow me to handle the callout to the web service asynchronously, which should meet the requirements.
upvoted 0 times
...
Franklyn
4 months ago
Exposing an Apex class as a web service could work, but I'm not sure if that's the most efficient approach given the requirement to only send one record per call.
upvoted 0 times
...
Nathan
5 months ago
Hmm, I think the platform events option might be the way to go here. That would allow me to capture the snapshot of the Accounts and then trigger the callout to the web service.
upvoted 0 times
...
Irene
5 months ago
This seems like a tricky one. I'm not sure if I should go with the Queueable interface or the future method. I'll need to think this through carefully.
upvoted 0 times
...
Dorothy
10 months ago
Exposing an Apex class as a web service? Sounds like the developer's going to need some serious API-fu to pull this off.
upvoted 0 times
Deja
9 months ago
D) Create a future method.
upvoted 0 times
...
Hillary
9 months ago
C) Expose an Apex class as a web service.
upvoted 0 times
...
Valene
10 months ago
B) Implement platform events.
upvoted 0 times
...
Mira
10 months ago
A) Implement the Queueable interface.
upvoted 0 times
...
...
Malcolm
10 months ago
Future method all the way! Gotta love that asynchronous goodness.
upvoted 0 times
Shalon
10 months ago
Create a future method.
upvoted 0 times
...
Ruby
10 months ago
Implement the Queuable interface.
upvoted 0 times
...
...
Tashia
11 months ago
I think implementing platform events could be a good option too, as it would provide a way to trigger the process when an Account record is saved.
upvoted 0 times
...
Virgilio
11 months ago
Queveable interface? What is this, a Harry Potter spell? C is clearly the correct answer here.
upvoted 0 times
...
Tashia
11 months ago
I believe creating a future method could also work, as it would allow for the callout to the RESTful web service.
upvoted 0 times
...
Mari
11 months ago
B sounds interesting, but I'm not sure platform events are the best fit for a one-to-one backup process.
upvoted 0 times
Precious
9 months ago
Denae: I think Queueable is more efficient for this specific requirement.
upvoted 0 times
...
Stephane
9 months ago
User 3: D) Create a future method could also work for this scenario.
upvoted 0 times
...
Denae
9 months ago
User 2: Denae is right, that would be the best option.
upvoted 0 times
...
Melvin
9 months ago
User 1: A) Implement the Queueable interface.
upvoted 0 times
...
Emile
9 months ago
D) Create a future method.
upvoted 0 times
...
Fidelia
10 months ago
C) Expose an Apex class as a web service.
upvoted 0 times
...
Broderick
10 months ago
B) I agree, platform events might not be the best fit for this scenario.
upvoted 0 times
...
Candida
10 months ago
A) Implement the Queueable interface.
upvoted 0 times
...
...
Valentin
11 months ago
I'd go with D - a future method can handle the callout and make sure it doesn't hold up the main process.
upvoted 0 times
...
Tamra
11 months ago
I agree with Samira. Using Queueable interface would allow for asynchronous processing of the records.
upvoted 0 times
...
Monroe
11 months ago
C is the way to go! Exposing an Apex class as a web service is the perfect solution to handle this requirement.
upvoted 0 times
Leonora
10 months ago
That's right! It's the most efficient way to meet the requirement of sending Account records to the external system for backup.
upvoted 0 times
...
Ivette
10 months ago
I agree, using an Apex class as a web service will allow the developer to send one record per call to the external system.
upvoted 0 times
...
Shawnta
10 months ago
C is the way to go! Exposing an Apex class as a web service is the perfect solution to handle this requirement.
upvoted 0 times
...
...
Samira
11 months ago
I think the developer should implement the Queueable interface.
upvoted 0 times
...

Save Cancel