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 groups was NOT imported because it is a security group in Active Directory.
Suggested Answer: A
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
35 comments · newest first
SI
Simona
11 months ago
No way, that can't be the only reason!
DO
Domonique
11 months ago
Seems odd, but I guess it makes sense for security.
GO
Goldie
11 months ago
Yup, only distribution groups get imported.
CH
Chaya
12 months ago
Wait, really? I thought they would!
LI
Lili
12 months ago
Security groups don't sync to Okta, that's correct.
NO
Norah
12 months ago
I’m leaning towards "Yes" because I recall reading that only distribution groups are imported by default.
BL
Blondell
1 year ago
I feel like there could be other factors too, like permissions or sync settings, but security groups definitely sound familiar.
RA
Raina
1 year ago
I remember a practice question where a similar issue came up, and it was about group types affecting imports.
SI
Sina
1 year ago
I think security groups might not get imported, but I’m not entirely sure if that’s the only reason.
ZA
Zachary
1 year ago
Got it, this is a good reminder that we need to be aware of the different group types in Active Directory and how they might behave during an Okta import. I'll make sure to double-check that in the future.
AL
Alethea
1 year ago
Ah, I see. The solution states that security groups are the reason the group wasn't imported. That makes sense - Okta must have some specific handling for those types of groups during the import process.
RO
Rocco
1 year ago
Okay, so the key here is that the group was not imported because it's a security group. I think I understand that - security groups have some special properties that might cause issues during the import process.
OL
Oliva
1 year ago
Hmm, this seems like a tricky one. I'll need to think carefully about the difference between security groups and other types of groups in Active Directory.
XU
Xuan
1 year ago
I'm a bit confused on this one. Is there a specific reason why security groups wouldn't get imported? I'll need to review the details on how Okta handles different group types from Active Directory.
LE
Lettie
1 year ago
Hmm, this seems like a tricky one. I'll need to think through the different arbitration factors and how they relate to the problem scenario.
QU
Quentin
1 year ago
Well, at least the group didn't get imported into Okta... it would have been a real 'security breach' if it had! (Wink, wink)
DO
Dominga
1 year ago
Solution: The groups was NOT imported because it is a security group in Active Directory.
JU
Jules
1 year ago
B) No
BE
Beckie
1 year ago
A) Yes
JE
Jenise
1 year ago
Ah, the old 'security group' excuse. That's like the IT version of 'my dog ate my homework'.
AL
Alton
1 year ago
Yes
JE
Jeannetta
1 year ago
No
CA
Caprice
1 year ago
Yes
NA
Narcisa
2 years ago
Hmm, I'm not sure about that. I've seen security groups get imported into Okta before. Maybe there's something else going on here that we're missing.
AL
Alita
1 year ago
User 4: Could it be a permissions issue?
SK
Skye
1 year ago
User 3: Maybe there's another reason why the group wasn't imported
KA
Kasandra
1 year ago
User 2: No
AS
Ashleigh
1 year ago
User 1: Yes
LA
Lai
2 years ago
I think the group was not imported because it's a security group in Active Directory. That makes sense, as Okta may not be able to handle those types of groups.
TI
Tiffiny
1 year ago
Solution: The group was NOT imported because it is a security group in Active Directory.
SH
Shonda
1 year ago
No
SH
Sherell
1 year ago
Yes
AN
Anthony
2 years ago
No, I don't think that's the reason.
VA
Vashti
2 years ago
I think the group was not imported because it is a security group in Active Directory.
KE
Keneth
2 years ago
Yes, that could be the reason.