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 Exam CRT-211 Topic 8 Question 113 Discussion

Actual exam question for Salesforce's CRT-211 exam
Question #: 113
Topic #: 8
[All CRT-211 Questions]

An administrator at Cloud kicks recently built a screen flow in a sandbox that creates a case and follow-up task. When the flow runs in the sandbox, it works just as expected. When tested in production, the flow errors when creating the records.

Choose 2 answers

Show Suggested Answer Hide Answer
Suggested Answer: B, D

Opening the flow in Debug mode and running it as another user allows simulating how the flow behaves for different users with different permissions and settings. This can help identify any issues related to user


Contribute your Thoughts:

Tandra
14 days ago
I would also consider option D, logging in as another user to see if the issue persists.
upvoted 0 times
...
Kattie
16 days ago
Hmm, option A sounds like it could be a quick fix, but I'm not sure if that's really addressing the root cause. Maybe try option B first?
upvoted 0 times
...
Mozell
22 days ago
Changing the Default Case Creator to the user's manager might solve the issue, but I'm not sure if that's the best solution. Option D could also work.
upvoted 0 times
Kami
13 days ago
B) Open the flow In Debug mode and Run the Flow as another user.
upvoted 0 times
...
Marjory
16 days ago
A) Change the user experiencing the issue to the System Administrator profile.
upvoted 0 times
...
...
Minna
24 days ago
I agree with Dino, running the flow in debug mode could help identify the issue.
upvoted 0 times
...
Dino
30 days ago
I think option B is the best choice.
upvoted 0 times
...
Brett
2 months ago
I think the issue could be with the user's permissions. Option B sounds like a good way to debug the problem.
upvoted 0 times
Charlena
16 days ago
Let's try running the flow as another user first. Option D could help us troubleshoot the issue.
upvoted 0 times
...
Mel
1 months ago
I agree, changing the user's permissions could solve the problem. Option A might also be worth trying.
upvoted 0 times
...
Giovanna
1 months ago
Option B sounds like a good idea. Running the flow in Debug mode could help identify the issue.
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77