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 ADX-211 Exam - Topic 6 Question 51 Discussion

Actual exam question for Salesforce's ADX-211 exam
Question #: 51
Topic #: 6
[All ADX-211 Questions]

AW Computing wants to create a process to assign accounts to different salespeople based on the annual revenue.... of the company. The administrator has decided to create a flow.

Which two consideration should the administrator make sure to remember when creating the flow? Choose 2 answers

Show Suggested Answer Hide Answer

Contribute your Thoughts:

0/2000 characters
Chan
3 months ago
C is crucial, otherwise you'll run into issues with multiple updates.
upvoted 0 times
...
Tawna
3 months ago
A is a must, hard coding is just asking for trouble.
upvoted 0 times
...
Glenn
3 months ago
Surprised by D! I thought updating inside the loop was a no-go.
upvoted 0 times
...
Solange
4 months ago
I disagree with B, the running user is usually the one who triggers it, not saves it.
upvoted 0 times
...
Lezlie
4 months ago
Definitely A and C! Makes total sense.
upvoted 0 times
...
Cherelle
4 months ago
I’m a bit confused about the placement of update record elements. I thought it might be okay to put them inside the loop, but now I'm not so sure.
upvoted 0 times
...
Eleonora
4 months ago
I feel like we practiced a question about where to place update record elements, and I think it was better to keep them outside the loop to avoid issues.
upvoted 0 times
...
Cheryl
4 months ago
I think I read somewhere that the running user of a flow is the one who last saved it, but I can't recall if that affects how we assign accounts.
upvoted 0 times
...
Paz
5 months ago
I remember we discussed the importance of using Get Record components to avoid hard coding, but I'm not entirely sure if that's the best option here.
upvoted 0 times
...
Nickolas
5 months ago
This looks like a good opportunity to demonstrate my understanding of flow best practices. I'll carefully review each option and choose the two most relevant considerations.
upvoted 0 times
...
Lacresha
5 months ago
Ah, I see - the question is asking about two specific considerations, so I'll need to make sure I select the right two answers from the options provided.
upvoted 0 times
...
Nadine
5 months ago
Hmm, I'm a little unsure about the difference between using a Get Record component and hard-coding record IDs. I'll need to think that one through carefully.
upvoted 0 times
...
Jeanice
5 months ago
This seems like a pretty straightforward question about best practices when creating a flow. I'm confident I can handle this one.
upvoted 0 times
...
Nieves
5 months ago
Okay, the key here is remembering where to place the Update Record elements. I think it depends on whether I need to update records inside or outside the flow loop.
upvoted 0 times
...
Tu
5 months ago
This looks like a straightforward question on security management processes. I'll review the options carefully and choose the one that best fits the implementation features.
upvoted 0 times
...
Mitsue
5 months ago
This looks like a straightforward HTML question. I think I can handle this one.
upvoted 0 times
...
Jolene
9 months ago
Wait, the running user of the flow is the last person to save it? Looks like the admin is trying to create a 'flow' of confusion and chaos. Maybe they should just let the salespeople play 'rock, paper, scissors' for the accounts instead.
upvoted 0 times
Kate
8 months ago
B) The running user of a flow is the user that last saved the flow.
upvoted 0 times
...
Mary
8 months ago
Haha, 'rock, paper, scissors' would definitely be a more fun way to assign accounts!
upvoted 0 times
...
Whitley
8 months ago
C) Update record elements should be placed outside the flow loop.
upvoted 0 times
...
Gennie
9 months ago
A) Use a Get Record component instead of hard coding record IDs.
upvoted 0 times
...
...
Cristen
10 months ago
I bet the administrator is going to have a real 'flow' of frustration if they don't get this right. Maybe they should just let the salespeople fight it out for the accounts. That would be more entertaining to watch.
upvoted 0 times
Bev
9 months ago
I think the administrator should definitely consider those two points to make the flow work smoothly.
upvoted 0 times
...
Chara
9 months ago
C) Update record elements should be placed outside the flow loop.
upvoted 0 times
...
Chana
9 months ago
A) Use a Get Record component instead of hard coding record IDs.
upvoted 0 times
...
...
Andra
10 months ago
The running user of the flow being the last person to save it? That's like putting the janitor in charge of the nuclear launch codes. Not the best idea, if you ask me.
upvoted 0 times
...
Iraida
10 months ago
Placing the Update Record elements outside the flow loop? That's just asking for trouble! You'll end up updating the wrong records, and that's not going to fly with the salespeople.
upvoted 0 times
Jerry
9 months ago
I agree, placing Update Record elements inside the flow loop can cause issues with updating the wrong records.
upvoted 0 times
...
Deeann
9 months ago
C) Update record elements should be placed outside the flow loop.
upvoted 0 times
...
Hermila
10 months ago
A) Use a Get Record component instead of hard coding record IDs.
upvoted 0 times
...
...
Julio
11 months ago
Using a Get Record component instead of hard coding record IDs is definitely the way to go. That way, the flow can be more dynamic and adaptable to changes in the data.
upvoted 0 times
Lorrie
10 months ago
C) Update record elements should be placed outside the flow loop.
upvoted 0 times
...
Helene
10 months ago
A) Use a Get Record component instead of hard coding record IDs.
upvoted 0 times
...
...
Alida
11 months ago
I believe the running user of a flow is the user that last saved the flow. So, that's another important consideration.
upvoted 0 times
...
Reuben
11 months ago
I agree with Cecilia. It's important to avoid hard coding record IDs for flexibility.
upvoted 0 times
...
Cecilia
11 months ago
I think the administrator should remember to use a Get Record component instead of hard coding record IDs.
upvoted 0 times
...

Save Cancel