MENU
The security team at Universal Containers (UC) has identified exporting reports as a high-risk action and would like to require users to be logged into Salesforce with their Active Directory (AD) credentials when doing so. For all other users of Salesforce, users should be allowed to use AD Credentials or Salesforce credentials. What solution should be recommended to prevent exporting reports except when logged in using AD credentials while maintaining the ability to view reports when logged in with Salesforce credentials?
Suggested Answer: B
Get Premium Salesforce Certified Platform Identity and Access Management Architect (Plat-Arch-203) Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
36 comments · newest first
RI
Rima
11 months ago
B could work, but it feels a bit complicated for just exporting reports.
RE
Rex
11 months ago
Wait, can we really block report exports like that? Sounds tricky!
DI
Dierdre
12 months ago
A is too restrictive, users need access for other tasks too.
AN
Anissa
12 months ago
I think D is the best choice, dynamic permission sets are super flexible!
VA
Vanesa
1 year ago
Option C seems solid, raising session levels is a good move.
CH
Cheryl
1 year ago
I’m leaning towards option B, but I’m a bit confused about how Custom SAML JIT Provisioning works in this context.
LI
Lillian
1 year ago
I practiced a similar question about permission sets, and I feel like option D might be the right approach since it mentions dynamically adding/removing permissions.
TE
Tegan
1 year ago
I think option C sounds familiar, treating SAML sessions as High Assurance could be a good way to manage access, but I’m not completely confident.
RO
Rolland
1 year ago
I remember we discussed SAML Federated Authentication in class, but I'm not sure how it specifically applies to blocking report exports.
ME
Meghann
1 year ago
This is a great example of how we need to really understand the security features and capabilities of Salesforce to solve these types of challenges. I'm feeling confident I can work through this.
AV
Avery
1 year ago
I'm a bit confused by the different options here. I'll need to review the details of SAML federated authentication and how it can be used to restrict access to specific actions.
EL
Elinore
1 year ago
Okay, I think I've got a handle on this. The key is using SAML federated authentication to control access to the report export functionality.
CE
Cecil
1 year ago
Hmm, this seems like a tricky one. I'll need to carefully read through the options and think about the implications of each approach.
TI
Tiera
1 year ago
I've seen this type of question before. I think option C is the way to go - using SAML federated authentication and raising the session level required for exporting reports.
HE
Helga
1 year ago
I'm a bit confused on this one. What exactly is the "web rewrite" method and how does it work with the virtual gateway?
NI
Nickole
1 year ago
Okay, I think I've got this. The default behavior is that the FCS is verified and kept, but the VLAN tag is removed for transport over the network. So the answer should be option D.
KR
Krissy
1 year ago
I'm feeling a bit report-ish about this question. Time to put on my thinking cap and make a choice that's not a total export-astrophe.
CO
Corinne
1 year ago
C) I think using SAML federated Authentication and treating SAML Sessions as High Assurance could be the way to go.
LE
Lemuel
1 year ago
B) That sounds like a good idea. Use SAML Federated Authentication and Custom SAML JIT Provisioning to dynamically add or remove a permission set.
CO
Coral
1 year ago
A) Use SAML Federated Authentication and block access to reports when accessed through a Standard Assurance session.
MA
Marge
1 year ago
Hmm, exporting reports, huh? Sounds like someone's trying to sneak a peek at the secret recipe for Salesforce's world-famous unicorn frappuccinos.
CH
Cherrie
1 year ago
Ah, the age-old battle of security vs. convenience. Option A sounds like the classic 'block everything' approach. I'll pass on that one.
CH
Chandra
1 year ago
User 4: True, that could provide an extra layer of security without completely blocking access.
OL
Olive
1 year ago
User 3: Option C could also work by raising the session level required for exporting reports.
KE
Kerrie
1 year ago
User 2: I agree, it allows for flexibility while still maintaining control over report exports.
MI
Ming
1 year ago
User 1: Option B sounds like a good compromise between security and convenience.
AN
Annita
2 years ago
Option B looks good, but I'm not sure about the dynamic provisioning aspect. Seems like it could get messy if not implemented properly.
AU
Audry
1 year ago
Hoa: Agreed, let's go with Option D for a simpler solution.
GL
Glenn
1 year ago
User 3: That could be a more straightforward approach to manage permissions for exporting reports.
HO
Hoa
1 year ago
User 2: Maybe we should consider Option D with the Login Flow instead.
AL
Alline
2 years ago
User 1: Option B does sound a bit complex with the dynamic provisioning.
PA
Pamella
2 years ago
I'm leaning towards option D. Using a login flow to manage the permission set seems more flexible than the other options.
AN
Anjelica
2 years ago
Option C seems like the way to go. Treating SAML sessions as high assurance and raising the session level for exporting reports is a neat way to control access without disrupting normal login.
RO
Roy
2 years ago
I'm not sure about option B. I think option D might be a better choice since it involves using a Login Flow to manage permissions.
LO
Loreta
2 years ago
I agree with Michel. Option B seems like the most efficient way to control access to exporting reports based on the user's login method.
MI
Michel
2 years ago
I think option B sounds like a good solution. It allows for dynamic permission management based on the user's credentials.