New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Okta Certified Professional Exam - Topic 9 Question 76 Discussion

Actual exam question for Okta's Okta Certified Professional exam
Question #: 76
Topic #: 9
[All Okta Certified Professional Questions]

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.

Show Suggested Answer Hide Answer
Suggested Answer: A

by Charlesetta at Aug 22, 2024, 02:57 PM

Limited Time Offer

25%

Off

Get Premium Okta Certified Professional Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Simona
3 months ago
No way, that can't be the only reason!
upvoted 0 times
...
Domonique
3 months ago
Seems odd, but I guess it makes sense for security.
upvoted 0 times
...
Goldie
4 months ago
Yup, only distribution groups get imported.
upvoted 0 times
...
Chaya
4 months ago
Wait, really? I thought they would!
upvoted 0 times
...
Lili
4 months ago
Security groups don't sync to Okta, that's correct.
upvoted 0 times
...
Norah
4 months ago
I’m leaning towards "Yes" because I recall reading that only distribution groups are imported by default.
upvoted 0 times
...
Blondell
5 months ago
I feel like there could be other factors too, like permissions or sync settings, but security groups definitely sound familiar.
upvoted 0 times
...
Raina
5 months ago
I remember a practice question where a similar issue came up, and it was about group types affecting imports.
upvoted 0 times
...
Sina
5 months ago
I think security groups might not get imported, but I’m not entirely sure if that’s the only reason.
upvoted 0 times
...
Zachary
5 months 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.
upvoted 0 times
...
Alethea
5 months 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.
upvoted 0 times
...
Rocco
5 months 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.
upvoted 0 times
...
Oliva
5 months 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.
upvoted 0 times
...
Xuan
5 months 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.
upvoted 0 times
...
Lettie
5 months 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.
upvoted 0 times
...
Quentin
10 months 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)
upvoted 0 times
Dominga
9 months ago
Solution: The groups was NOT imported because it is a security group in Active Directory.
upvoted 0 times
...
Jules
9 months ago
B) No
upvoted 0 times
...
Beckie
9 months ago
A) Yes
upvoted 0 times
...
...
Jenise
10 months ago
Ah, the old 'security group' excuse. That's like the IT version of 'my dog ate my homework'.
upvoted 0 times
Alton
9 months ago
Yes
upvoted 0 times
...
Jeannetta
9 months ago
No
upvoted 0 times
...
Caprice
9 months ago
Yes
upvoted 0 times
...
...
Narcisa
11 months 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.
upvoted 0 times
Alita
9 months ago
User 4: Could it be a permissions issue?
upvoted 0 times
...
Skye
9 months ago
User 3: Maybe there's another reason why the group wasn't imported
upvoted 0 times
...
Kasandra
9 months ago
User 2: No
upvoted 0 times
...
Ashleigh
9 months ago
User 1: Yes
upvoted 0 times
...
...
Lai
11 months 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.
upvoted 0 times
Tiffiny
9 months ago
Solution: The group was NOT imported because it is a security group in Active Directory.
upvoted 0 times
...
Shonda
9 months ago
No
upvoted 0 times
...
Sherell
10 months ago
Yes
upvoted 0 times
...
...
Anthony
11 months ago
No, I don't think that's the reason.
upvoted 0 times
...
Vashti
11 months ago
I think the group was not imported because it is a security group in Active Directory.
upvoted 0 times
...
Keneth
11 months ago
Yes, that could be the reason.
upvoted 0 times
...

Save Cancel