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 Salesforce Hyperautomation Specialist Topic 2 Question 10 Discussion

Actual exam question for Salesforce's Salesforce Hyperautomation Specialist exam
Question #: 10
Topic #: 2
[All Salesforce Hyperautomation Specialist Questions]

Northern Trail Outfitters is concerned about security in their Salesforce org regarding their newly created hyperautomation flow that calls a MuleSoft API. A mechanism needs to be implemented that restricts which users can invoke the flow.

Which setting is available to a hyperautomation practitioner that meets this security requirement?

Show Suggested Answer Hide Answer
Suggested Answer: A

In Flow Builder, Run and Debug modes have distinct functionalities:

Run Mode:

Executes the flow as it is, allowing you to see the end-to-end execution based on the latest saved version.

Typically used to verify that the flow works as expected under normal conditions.

Debug Mode:

Provides detailed information for each step of the flow, including input and output data, and any errors encountered.

Useful for troubleshooting and identifying issues within the flow, allowing developers to understand how the flow executes and where problems may arise.

Debug mode is specifically designed to aid in diagnosing and fixing issues by providing a granular view of the flow's execution.


Salesforce Flow Builder Documentation

Contribute your Thoughts:

Halina
4 days ago
I'm not sure, but I think configuring OAuth 2.0 in the connected app could also help restrict access to the flow.
upvoted 0 times
...
Sherill
6 days ago
I agree with Peggie. Assigning profiles or permission sets to users in the external service seems like the most secure option.
upvoted 0 times
...
Peggie
8 days ago
I think the answer is B) Assign an appropriate profile or permission set to users in the external service.
upvoted 0 times
...
Luisa
9 days ago
C seems like the obvious choice here. Restricting access to the connected app is the way to go.
upvoted 0 times
...

Save Cancel