Deal of The Day! 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 (Plat-Dev-201) Exam - Topic 2 Question 92 Discussion

Actual exam question for Salesforce's Salesforce Certified Platform Developer (Plat-Dev-201) exam
Question #: 92
Topic #: 2
[All Salesforce Certified Platform Developer (Plat-Dev-201) Questions]

An org has an existing flow that edits an Opportunity with an Update Records element. A developer must update the flow to also create a Contact and store the created Contact's ID on the Opportunity.

Which update must the developer make in the flow?

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

0/2000 characters
Janey
6 days ago
Agreed, C is the way to go!
upvoted 0 times
...
Melina
12 days ago
Definitely need to add a new Create Records element.
upvoted 0 times
...
Arminda
18 days ago
I’m a bit confused. Wouldn't we need a Get Records element to retrieve the Contact ID after creating it? Or is that not necessary?
upvoted 0 times
...
Vincenza
23 days ago
I practiced a similar question where we had to create a record and then reference it later. I feel like we definitely need to add a Create Records element here.
upvoted 0 times
...
Sommer
28 days ago
I'm not entirely sure, but I remember something about needing to update the Opportunity after creating the Contact. Would that mean we need an Update Records element?
upvoted 0 times
...
Kris
1 month ago
I think we need to create a new Contact, so maybe we should add a Create Records element? That sounds right.
upvoted 0 times
...
Filiberto
1 month ago
Hmm, I'm a bit confused. Do I need to add a Roll Back Records element to handle any errors that might occur? Or should I just focus on the Create Records and Update Records steps? I want to make sure I cover all the bases here.
upvoted 0 times
...
Stevie
1 month ago
I've got this! The key is to add a Create Records element to the flow to create the new Contact, and then use an Update Records element to update the Opportunity with the Contact's ID. Simple as that!
upvoted 0 times
...
Margot
1 month ago
Okay, let me think this through. We need to create a new Contact and store its ID on the Opportunity. I'm not sure if I should use a Create Records or a Get Records element for that. I'll have to double-check the flow elements to decide the best approach.
upvoted 0 times
...
Miles
1 month ago
Hmm, this seems straightforward. I think I'll need to add a Create Records element to the flow to create the new Contact, and then update the Opportunity with the Contact's ID.
upvoted 0 times
...
Sue
1 month ago
Ah, I see. Option D looks like the right approach - setting the Identity Provider as default and enabling the Redirect to the Identity Provider setting on the SAML Configuration.
upvoted 0 times
...
Ria
1 month ago
Discrimination training was mentioned a lot in class, but I don't see how that fits here. It's definitely confusing!
upvoted 0 times
...
Bo
2 months ago
Hmm, the use of `transform()` and `for_each()` on the different containers has me a bit confused. I'll need to review how those functions work to figure out the expected output.
upvoted 0 times
...
Catrice
6 months ago
You know, I was almost tempted to go with the Get Records option, but that wouldn't actually create the new Contact, would it? C is the clear winner here.
upvoted 0 times
Willis
4 months ago
Definitely not Get Records, C is the best option for creating a new Contact.
upvoted 0 times
...
Elly
5 months ago
Get Records wouldn't create a new Contact, so C is the way to go.
upvoted 0 times
...
Heidy
5 months ago
Adding a new Create Records element makes the most sense in this scenario.
upvoted 0 times
...
India
5 months ago
I agree, C is the correct choice. It will create a new Contact.
upvoted 0 times
...
...
Yuonne
7 months ago
Haha, this is a tricky one. I was thinking of adding a Roll Back Records element to undo everything, but that's just me being a little too cautious.
upvoted 0 times
Joana
6 months ago
No, that would only edit the Opportunity, not create a new Contact.
upvoted 0 times
...
Viola
6 months ago
I agree, that would allow them to create a Contact and store the ID on the Opportunity.
upvoted 0 times
...
...
Joni
7 months ago
I'm not sure, but I think adding a new Get Records element could also work to retrieve the Contact's ID and store it on the Opportunity.
upvoted 0 times
...
Stevie
7 months ago
I agree with Leoma. Adding a new Create Records element would allow the flow to create a Contact and store its ID on the Opportunity.
upvoted 0 times
...
Dorathy
7 months ago
Ah, I see. So we need to create a new Contact and link it to the existing Opportunity. C is definitely the way to go here.
upvoted 0 times
...
Wei
7 months ago
Hmm, I think the correct answer is C. Adding a new Create Records element to create the Contact and store its ID on the Opportunity seems like the logical step.
upvoted 0 times
Maia
6 months ago
Yes, that would be the best way to update the flow and achieve the desired outcome.
upvoted 0 times
...
Portia
6 months ago
Adding a new Create Records element is definitely the way to go.
upvoted 0 times
...
Krissy
7 months ago
I think so too, it would allow us to create the Contact and store its ID on the Opportunity.
upvoted 0 times
...
Nicolette
7 months ago
I agree, adding a new Create Records element makes sense.
upvoted 0 times
...
...
Leoma
7 months ago
I think the developer should add a new Create Records element.
upvoted 0 times
...
Derrick
7 months ago
I'm not sure, but I think adding a new Get Records element could also work to retrieve the Contact's ID and store it on the Opportunity.
upvoted 0 times
...
Barbra
7 months ago
I agree with Cruz. Adding a new Create Records element would allow the flow to create a Contact and store its ID on the Opportunity.
upvoted 0 times
...
Cruz
7 months ago
I think the developer should add a new Create Records element.
upvoted 0 times
...

Save Cancel