Question 480
While designing controls for this requirement—A company has cloud-hosted Microsoft Entra ID but plans a redundant on-prem LDAP proxy only to obtain cloud user groups—what limitation should the project not overlook?
Explanation
Correct Answer
The controlling risk is that a cloud identity source does not always need a custom on-prem synchronization hop. In the reported setting—a company has cloud-hosted Microsoft Entra ID but plans a redundant on-prem LDAP proxy only to obtain cloud user groups—the team needs to compare available cloud directory and supported CIE sync options with tenancy permissions and then use supported CIE cloud-directory integration for the cloud identity provider where applicable. The expected safe result is that test identity and group updates appear without a newly introduced on-prem LDAP relay.
Incorrect Answers
The distinct use case for this response is “A legacy directory is reachable only from a private datacenter, while cloud enforcement requires current employee groups”. The design should document the corresponding investigation and practical acceptance evidence. The present case instead calls for “A cloud identity source does not always need a custom on-prem synchronization hop”.
This can be appropriate when a firm integrates Okta groups with cloud security services and sees duplicate identities after directory sync, but it does not isolate the distinguishing requirement here: A company has cloud-hosted Microsoft Entra ID but plans a redundant on-prem LDAP proxy only to obtain cloud user groups. The correct risk decision is a cloud identity source does not always need a custom on-prem synchronization hop.
This would be appropriate for “A multinational's HR system removes access groups, but the Cloud Identity Engine connector runs only once per month”. Confirm the relevant evidence—review expected synchronization frequency, sync health alerts and security offboarding SLO—before selecting architect an appropriately frequent and monitored identity synchronization cycle. Here the decisive requirement is “A cloud identity source does not always need a custom on-prem synchronization hop”.