MENU
The system administrator at Get Cloudy Consulting is trying to import Customer Portal users to the newly created Experience Cloud. However, the import failed.
What could be two reasons for this failure?
Choose 2 answers
Suggested Answer: A, D
Get Premium Salesforce Certified Experience Cloud Consultant (EX-Con-101) Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
Two reasons for the import failure are A and D. To import Customer Portal users to the Experience Cloud, you need to have a portal role record and a contact record for each user. A portal role record is a record that defines the role of a portal user in the portal hierarchy. A contact record is a record that contains the personal information of a portal user, such as name, email, phone, etc. If these records are missing, the import will fail.
24 comments · newest first
GR
Graham
10 months ago
Yeah, I agree with A and B, those are common pitfalls.
PA
Patrick
10 months ago
A and B seem right, but I’m surprised no one mentioned permissions issues!
TI
Tiffiny
11 months ago
Definitely A and B, those roles and profiles are crucial!
MA
Maurine
11 months ago
I think C could also be a reason, missing user records can mess things up.
JU
Julianna
11 months ago
Wait, are you sure about D? I thought contacts weren't necessary for portal access.
NI
Nikita
11 months ago
I vaguely recall something about contact records needing to be in place for user imports. D might be a possibility, but I need to double-check that.
JO
Joye
12 months ago
I feel like user records being missing could be a factor, but I’m not sure if that’s the same as the portal role. Maybe C is relevant?
MO
Mona
12 months ago
I’m not entirely sure, but I think if the portal profile isn’t created, that might also cause issues. So, B seems plausible too.
SO
Sol
1 year ago
I remember we discussed the importance of having the right portal role set up before importing users. So, A could definitely be a reason.
CH
Cherry
1 year ago
I've got a good strategy here. I'll methodically go through each option, considering the potential issues with the portal setup and user data. I think I can nail this one.
GI
Gilberto
1 year ago
I'm a bit unsure about the "Penal & Pep ore" part in option C. That doesn't sound right to me, so I'll probably rule that one out.
PA
Paz
1 year ago
User records and contact records - those are key pieces of data that need to be in place. I'll make sure to review those as well.
SH
Shanda
1 year ago
Okay, let's see. The portal role and profile records need to be set up properly, so that's definitely something I'll check.
DI
Dick
1 year ago
Hmm, this seems like a tricky one. I'll need to think carefully about the potential reasons for the import failure.
CH
Charlena
1 year ago
I love how option C just throws in some random words. Sounds like a coding error to me!
RE
Rene
1 year ago
C is just weird, 'Penal & Pep ore'? What is that even supposed to mean? Clearly the wrong answer.
MI
Mitsue
1 year ago
D is also important, the contact records need to exist before you can create the portal users. This is a common issue I've seen.
MA
Marcos
10 months ago
True! Missing contact records can really mess things up.
AL
Alayna
10 months ago
I agree, but D is crucial too. Contacts must be there first.
EL
Elizabeth
10 months ago
Definitely! Without those roles and profiles, it won't work.
KR
Kristel
11 months ago
I think A and B are the main reasons.
RA
Rachael
1 year ago
A and B for sure, you need the role and profile records set up for the portal users to be imported properly.
EM
Emelda
1 year ago
A) The portal role record has not been created.
AR
Armando
1 year ago
I think the import failed because the portal role record has not been created.