Q: 9
Cloud Kicks has asked the administrator to test a new screen flow that create contacts.
What are two key components of testing the flow?
Choose 2 answers
Options
Discussion
I get why B is tempting since actually running the flow creates contacts, but I’d say B, D. Debug feels like a trap here.
C/D? Debug lets you step through the flow logic and a sandbox keeps your data safe. Pretty standard Salesforce practice. Not 100 percent but that's always how they push it in admin prep.
Why not A instead of B? Setting up a flow interview also tests with input but isn’t listed as correct here.
Yeah, C and D make sense here. Debug lets you walk through the logic in Flow Builder and see exactly what happens, and sandbox means you aren't messing up real data while testing. Pretty confident that's what Salesforce pushes as best practice, but if someone thinks B fits too, let me know.
Guessing C and D. Saw something like this in exam reports, sandbox testing and debug feature are safest for flows.
Option B. not C. Running the flow to create contacts feels more direct than Debug, right?
D . Debug in Flow Builder (C) helps catch logic errors, and sandbox (D) prevents production mistakes. B is tempting but running flows in prod isn’t really safe for initial tests. I could see some picking B, but I think C/D fits Salesforce best practices more-correct me if I missed anything.
Wouldn't B only apply if they're specifically asking about production testing, not initial flow validation?
B tbh. Running the flow and creating contacts actually tests if it works end to end, right? Feels like C is important for debugging, but real testing happens when you run it for actual outcomes. Anyone see it this way or am I off?
C/D imo, saw a similar question pop up on my last practice test and they went with debug and sandbox every time for safe flow testing.
Be respectful. No spam.
