MENU
An Okta Administrator ran a full import from Active Directory An expected group was NOT imported into OKt
a. Is this a reason why the group was NOT imported into Okta?
Solution: The organizational unit (OU) containing the group was NOT selected for Import
Suggested Answer: B
Get Premium Okta Certified Professional Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
15 comments · newest first
KA
Katheryn
1 month ago
Yeah, A is logical. OUs control visibility.
FR
Freeman
2 months ago
A is definitely the right choice. Can't import without selection.
FA
Fallon
2 months ago
I still lean towards A. Selection matters.
AU
Audry
2 months ago
But what if the group was empty? That could be B.
TR
Trinidad
2 months ago
Agreed, A makes sense. OUs are crucial.
AV
Avery
2 months ago
I think it's A. The OU wasn't selected.
MA
Maira
3 months ago
I thought all groups would auto-import, that's surprising!
PE
Peggie
3 months ago
Nah, I think there could be other reasons too.
SA
Salina
3 months ago
Wait, how do you even select OUs for import?
KR
Kristal
3 months ago
Definitely a reason, forgot to check that once.
RO
Rosendo
3 months ago
That makes sense, OUs can be tricky!
ER
Erasmo
3 months ago
I feel like I read that sometimes groups can be excluded for other reasons, but this OU thing seems pretty straightforward.
TR
Truman
4 months ago
This reminds me of a practice question where the OU was also the issue. I think it’s likely the correct answer.
MY
Myong
4 months ago
I'm not entirely sure, but I think there might be other factors too, like permissions or group types.
DE
Delsie
4 months ago
I remember something about OUs being crucial for imports, so this could definitely be a reason.