Northern Trail Outfitters (NTO) is planning to implement a community for its customers using Salesforce Experience Cloud . Customers are not able to self-register. NTO would like to have customers set their own passwords when provided access to the community.
Which two recommendations should an identity architect make to fulfill this requirement?
Choose 2 answers
Suggested Answer: D
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
33 comments · newest first
IL
Ilene
11 months ago
Option C could work too, but it sounds a bit complicated.
TY
Tyisha
11 months ago
A and D seem like the best choices here.
CO
Cory
12 months ago
Wait, can they really set their own passwords if they can't self-register?
NO
Noah
12 months ago
I disagree, I feel like option D is more effective for password resets.
NE
Nelida
1 year ago
I think option B is a must for sending welcome emails!
CI
Ciara
1 year ago
I practiced a similar question about password resets, and I think allowing API access could be crucial for managing user accounts effectively.
SH
Sharen
1 year ago
Adding customers as contacts seems like a straightforward approach, but I feel like there might be more to it regarding password management.
IL
Ilene
1 year ago
I think using Login Flows could be a good way to let users reset their passwords, but I need to double-check how that works in Experience Cloud.
VE
Vernice
1 year ago
I remember something about enabling welcome emails, but I'm not sure if that's the best option for allowing password setup.
SK
Skye
1 year ago
I feel pretty confident that options A and D are the way to go here. Adding customers as contacts and using login flows to allow password reset seems like the best approach.
KE
Kenny
1 year ago
I think the welcome email in option B could be a good way to provide initial access, but it doesn't seem to address the password reset requirement. I'll need to weigh that one carefully.
NA
Nakita
1 year ago
I'm a bit confused on the difference between options C and D. Both seem to involve password reset, but I'm not sure how they differ in the context of this question.
TA
Tawny
1 year ago
Okay, let's see. The key is that customers can't self-register, but they need to set their own passwords. I'm leaning towards options A and D.
AB
Abel
1 year ago
Hmm, this seems like a tricky one. I'll need to think carefully about the options and how they address the requirements.
MA
Malcom
1 year ago
Hmm, this is a tricky one. I'm not totally sure about the differences between the organizational structures, but I think the matrix structure is the one that combines functional and project elements. I'll have to think this through carefully.
NA
Nada
1 year ago
Okay, let me see. I remember that Business Units are a key part of the reporting structure, but I'm not sure if they're the highest level or not. And I think they can be assigned to multiple companies, but I'm not 100% certain. I'll have to review my notes on this.
RA
Raina
1 year ago
I'm not totally confident, but I think the answer is D. Forward schema evolution seems to fit the description best out of the options given.
CL
Clorinda
1 year ago
Ah, this is a good one. The key here is "primary method" - that points to templates as the best answer. Audits, administration, and patching are all important, but templates are the foundation for consistent configurations across IT systems.
GA
Gail
1 year ago
Okay, I've got this. Distributive fairness is about the customer's perception of the benefits versus the costs, so that's the right answer. I'm confident I can apply this concept to similar questions.
AR
Arletta
2 years ago
As an identity architect, I'd have to recommend C and D. Giving customers the ability to reset their own passwords is key, and the API or login flows seem like the best way to do that.
HO
Hoa
1 year ago
That sounds like a solid plan. Customers being able to reset their own passwords will definitely improve their experience.
MI
Milly
1 year ago
D) Use Login Flows to allow users to reset password in Experience Cloud site.
ZO
Zona
1 year ago
C) Allow Password reset using the API to update Experience Cloud site membership.
MI
Michell
2 years ago
I agree with Kimbery. C and D are the way to go. Adding customers as contacts and using welcome emails just doesn't seem like it would meet the requirement properly.
JU
Juliann
2 years ago
Haha, can you imagine if they just emailed everyone their passwords? That's a security nightmare waiting to happen. Definitely go with the options that give customers control over their passwords.
NI
Niesha
2 years ago
I also think option D is important as it allows users to reset their passwords easily.
ST
Stefanie
2 years ago
I agree with Lenny. Option B will make customers feel more engaged.
KI
Kimbery
2 years ago
The requirement to have customers set their own passwords is a crucial one, and I think options C and D are the way to go. Letting them reset passwords through the API or using login flows seems like the most secure and user-friendly approach.
NY
Nydia
1 year ago
Customers being able to set their own passwords will definitely enhance their overall experience with the community.
LA
Lashawn
1 year ago
It's important to prioritize security and user experience when implementing a community for customers.
ST
Stephaine
1 year ago
Using the API for password reset and login flows for resetting passwords in the community site would give customers control over their passwords.
MA
Malcom
1 year ago
I agree, options C and D seem like the best choices for allowing customers to set their own passwords.
LE
Lenny
2 years ago
I think option B is a good idea because customers will feel welcomed.