MENU
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?
Suggested Answer: A
Get Premium Salesforce Certified MuleSoft Hyperautomation Developer (Mule-Dev-202) Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
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.
34 comments · newest first
MI
Micheal
11 months ago
I’m surprised there’s not a simpler way to handle this!
CR
Cristy
11 months ago
Option A seems more secure to me.
LO
Lore
12 months ago
Wait, can you really restrict access just with profiles?
SH
Sharika
12 months ago
Definitely agree with that!
NO
Norah
1 year ago
I think option C is the way to go.
PA
Patria
1 year ago
I think assigning profiles or permission sets is crucial, but I can't remember if it should be for the external service or the connected app.
ER
Erinn
1 year ago
I feel like configuring OAuth 2.0 is important, but I can't recall if it should be done in the connected app or the external service.
AL
Alline
1 year ago
I remember a practice question about permission sets, and it seems like assigning them to users in the connected app could be the right approach here.
NO
Noah
1 year ago
I think we discussed OAuth 2.0 in class, but I'm not sure if it's specifically for the connected app or the external service.
EL
Elke
1 year ago
Okay, let's think this through step-by-step. The question is asking about a security mechanism to restrict who can invoke the flow. I'm guessing the answer has to do with managing permissions and access controls, but I'll need to evaluate each option to determine the best fit.
CA
Carlee
1 year ago
Hmm, I'm a bit unsure about this one. Restricting access to a hyperautomation flow that calls a MuleSoft API - that's a new one for me. I'll have to read through the options closely and see if I can spot the right approach.
IS
Isadora
1 year ago
This seems like a straightforward security question. I'll need to think through the different options carefully, but I'm confident I can figure this out.
JU
Junita
1 year ago
This is a tricky one. I know we've covered security best practices for Salesforce, but I'm not sure if I've seen anything specific about restricting access to a hyperautomation flow. I'll have to really focus and try to apply my general knowledge to this specific scenario.
BE
Bette
1 year ago
I've worked with Salesforce objects before, so I think I've got a good handle on this. I'll just need to double-check my understanding of the key differences.
LO
Lorenza
1 year ago
I heard Salesforce is hiring a new security guard - must be a real 'Salesforce' to be reckoned with!
TH
Theron
1 year ago
C, no doubt about it. I'm going to ace this exam, just watch me!
AS
Ashleigh
1 year ago
User 4: Yeah, C sounds like the best way to restrict access to the flow.
TA
Tammi
1 year ago
User 3: I think I'll go with C too, seems like the most secure option.
SH
Shaunna
1 year ago
User 2: Good choice, that's the right answer for sure.
ET
Ettie
1 year ago
User 1: C) Assign an appropriate profile or permission set to users in the connected app.
DE
Deane
2 years ago
I'm going to go with C. It's the only one that mentions the connected app directly, and that's where the security needs to be implemented.
JO
Josephine
1 year ago
User 3: Definitely, C seems like the most secure option for restricting access to the hyperautomation flow.
CA
Carla
1 year ago
User 2: Yeah, I agree. It's important to assign the appropriate profile or permission set to users in the connected app for security.
ME
Melissa
1 year ago
User 1: I think C is the right choice too. It mentions the connected app, which is where the security needs to be applied.
FA
Fannie
2 years ago
Hmm, I'm not sure. I think B might work too, but C sounds more specific to the connected app.
HA
Halina
2 years ago
I'm not sure, but I think configuring OAuth 2.0 in the connected app could also help restrict access to the flow.
SH
Sherill
2 years ago
I agree with Peggie. Assigning profiles or permission sets to users in the external service seems like the most secure option.
PE
Peggie
2 years ago
I think the answer is B) Assign an appropriate profile or permission set to users in the external service.
LU
Luisa
2 years ago
C seems like the obvious choice here. Restricting access to the connected app is the way to go.
ST
Stefany
1 year ago
C) Assign an appropriate profile or permission set to users in the connected app.
NO
Novella
1 year ago
B) Assign an appropriate profile or permission set to users in the external service.
DE
Deeann
1 year ago
C) Assign an appropriate profile or permission set to users in the connected app.
GL
Glendora
1 year ago
A) Configure OAuth 2.0 in the connected app.
HA
Halina
2 years ago
A) Configure OAuth 2.0 in the connected app.