Microsoft SC-900 Dumps
Microsoft SC-900 Practice Test 22
Question 210
For this case—A deployment system accepts OIDC assertions from any repository subject and accidentally allows forked builds to assume production identity.—which implementation and acceptance check are correctly paired?
Explanation
Correct Answer
The situation is that a deployment system accepts OIDC assertions from any repository subject and accidentally allows forked builds to assume production identity. Use Entra workload identity federation to validate trusted external OIDC assertions from a supported build service before issuing an app access token. Validation: Run a sandbox pipeline with an approved issuer and branch-bound subject, then show an unexpected branch or audience cannot obtain the cloud token. The action and test belong together because federated workload credentials exchange verified short-lived tokens based on issuer, audience and subject, avoiding stored long-lived cloud secrets in CI.
Incorrect Answers
“separate member and guest identities in collaboration” evaluates a different intervention. The appropriate action is to use Entra workload identity federation to validate trusted external OIDC assertions from a supported build service before issuing an app access token. To confirm, run a sandbox pipeline with an approved issuer and branch-bound subject, then show an unexpected branch or audience cannot obtain the cloud token.
That action-and-evidence pair concerns “use system-assigned managed identities for a single Azure resource”, not this decision. The appropriate action is to use Entra workload identity federation to validate trusted external OIDC assertions from a supported build service before issuing an app access token. To confirm, run a sandbox pipeline with an approved issuer and branch-bound subject, then show an unexpected branch or audience cannot obtain the cloud token.
The proposed pair focuses on “identify a Microsoft entra tenant as cloud identity directory” instead. The appropriate action is to use Entra workload identity federation to validate trusted external OIDC assertions from a supported build service before issuing an app access token. To confirm, run a sandbox pipeline with an approved issuer and branch-bound subject, then show an unexpected branch or audience cannot obtain the cloud token.
Question 211
An organization keeps its factory AD DS but wants staff sign-in accounts to appear centrally in Microsoft Entra for cloud applications. Which implementation or design choice most directly mitigates the stated issue?
Explanation
Correct Answer
Use supported Microsoft Entra Connect Sync or Cloud Sync where appropriate to synchronize intended on-prem directory accounts and monitor synchronization scope and health. Hybrid identity depends on matching and synchronizing attributes between directories, and on-prem account changes are not automatically visible in the cloud without the configured path. To verify, create a synthetic on-prem identity update in a lab and verify intended user attributes and deactivation propagate while excluded accounts remain outside scope.
Incorrect Answers
This alternative focuses on “use an app registration and service principal for application access” instead of the required outcome. Hybrid identity depends on matching and synchronizing attributes between directories, and on-prem account changes are not automatically visible in the cloud without the configured path.
That choice concerns “use system-assigned managed identities for a single Azure resource”, not the immediate requirement. Hybrid identity depends on matching and synchronizing attributes between directories, and on-prem account changes are not automatically visible in the cloud without the configured path.
“prefer workload identity federation over stored CI secrets” is related to another task, not the failure shown here. Hybrid identity depends on matching and synchronizing attributes between directories, and on-prem account changes are not automatically visible in the cloud without the configured path.
Question 212
An organization keeps its factory AD DS but wants staff sign-in accounts to appear centrally in Microsoft Entra for cloud applications. Which technical explanation most directly supports the right approach?
Explanation
Correct Answer
Hybrid identity depends on matching and synchronizing attributes between directories, and on-prem account changes are not automatically visible in the cloud without the configured path. This supports the decision to use supported Microsoft Entra Connect Sync or Cloud Sync where appropriate to synchronize intended on-prem directory accounts and monitor synchronization scope and health.
Incorrect Answers
“use system-assigned managed identities for a single Azure resource” explains a different mechanism. Here, hybrid identity depends on matching and synchronizing attributes between directories, and on-prem account changes are not automatically visible in the cloud without the configured path.
That statement concerns “distinguish cloud-only and hybrid identity sign-in choices” rather than the cause in this case. Here, hybrid identity depends on matching and synchronizing attributes between directories, and on-prem account changes are not automatically visible in the cloud without the configured path.
The principle behind “reuse user-assigned managed identity deliberately” is not the one being tested. Here, hybrid identity depends on matching and synchronizing attributes between directories, and on-prem account changes are not automatically visible in the cloud without the configured path.
Question 213
For this situation—An organization keeps its factory AD DS but wants staff sign-in accounts to appear centrally in Microsoft Entra for cloud applications.—which check provides the strongest verification?
Explanation
Correct Answer
Create a synthetic on-prem identity update in a lab and verify intended user attributes and deactivation propagate while excluded accounts remain outside scope. It is the relevant test because hybrid identity depends on matching and synchronizing attributes between directories, and on-prem account changes are not automatically visible in the cloud without the configured path.
Incorrect Answers
This evidence addresses “prefer workload identity federation over stored CI secrets” instead of confirming the repair. To check this result, create a synthetic on-prem identity update in a lab and verify intended user attributes and deactivation propagate while excluded accounts remain outside scope.
“identify a Microsoft entra tenant as cloud identity directory” would verify a different part of the system. To check this result, create a synthetic on-prem identity update in a lab and verify intended user attributes and deactivation propagate while excluded accounts remain outside scope.
That test concerns “distinguish workforce workload and agent identities at a conceptual level”, not the requested outcome. To check this result, create a synthetic on-prem identity update in a lab and verify intended user attributes and deactivation propagate while excluded accounts remain outside scope.
Question 214
An organization keeps its factory AD DS but wants staff sign-in accounts to appear centrally in Microsoft Entra for cloud applications. If the team does the following—"Assume disabling an AD DS user immediately disables every cloud session even when identity synchronization has stopped for several days."—what could go wrong?
Explanation
Correct Answer
Former employee access may persist in cloud apps because directory changes did not propagate through an unhealthy synchronization service. The shortcut is unsafe because hybrid identity depends on matching and synchronizing attributes between directories, and on-prem account changes are not automatically visible in the cloud without the configured path.
Incorrect Answers
The alternative risk relates to “The app can inherit excessive tenant powers and may stop when the human password or MFA…”, not the stated mistake. Here, former employee access may persist in cloud apps because directory changes did not propagate through an unhealthy synchronization service.
That consequence concerns “A failure of an on-prem authentication endpoint can cause unexpected outage when the organization selected a…”, which is a different failure. Here, former employee access may persist in cloud apps because directory changes did not propagate through an unhealthy synchronization service.
“Leaked long-lived credentials may grant unintended privileges while resource deletion fails to remove the separately embedded…” does not describe the result of this shortcut. Here, former employee access may persist in cloud apps because directory changes did not propagate through an unhealthy synchronization service.
Question 215
An organization keeps its factory AD DS but wants staff sign-in accounts to appear centrally in Microsoft Entra for cloud applications. Which action and validation evidence belong together?
Explanation
Correct Answer
Use supported Microsoft Entra Connect Sync or Cloud Sync where appropriate to synchronize intended on-prem directory accounts and monitor synchronization scope and health. Validation: Create a synthetic on-prem identity update in a lab and verify intended user attributes and deactivation propagate while excluded accounts remain outside scope. The action and test belong together because hybrid identity depends on matching and synchronizing attributes between directories, and on-prem account changes are not automatically visible in the cloud without the configured path.
Incorrect Answers
The linked action and check for “distinguish cloud-only and hybrid identity sign-in choices” would not resolve this case. The appropriate action is to use supported Microsoft Entra Connect Sync or Cloud Sync where appropriate to synchronize intended on-prem directory accounts and monitor synchronization scope and health. To confirm, create a synthetic on-prem identity update in a lab and verify intended user attributes and deactivation propagate while excluded accounts remain outside scope.
That action-and-evidence pair concerns “separate member and guest identities in collaboration”, not this decision. The appropriate action is to use supported Microsoft Entra Connect Sync or Cloud Sync where appropriate to synchronize intended on-prem directory accounts and monitor synchronization scope and health. To confirm, create a synthetic on-prem identity update in a lab and verify intended user attributes and deactivation propagate while excluded accounts remain outside scope.
“distinguish workforce workload and agent identities at a conceptual level” evaluates a different intervention. The appropriate action is to use supported Microsoft Entra Connect Sync or Cloud Sync where appropriate to synchronize intended on-prem directory accounts and monitor synchronization scope and health. To confirm, create a synthetic on-prem identity update in a lab and verify intended user attributes and deactivation propagate while excluded accounts remain outside scope.
Question 216
During a Microsoft security fundamentals review, A hybrid tenant's new employees are missing from cloud applications after the identity synchronization scheduler failed silently. What is the most appropriate next decision?
Explanation
Correct Answer
The situation is that a hybrid tenant's new employees are missing from cloud applications after the identity synchronization scheduler failed silently. Use supported Microsoft Entra Connect Sync or Cloud Sync where appropriate to synchronize intended on-prem directory accounts and monitor synchronization scope and health. Hybrid identity depends on matching and synchronizing attributes between directories, and on-prem account changes are not automatically visible in the cloud without the configured path. To verify, create a synthetic on-prem identity update in a lab and verify intended user attributes and deactivation propagate while excluded accounts remain outside scope.
Incorrect Answers
That choice concerns “distinguish cloud-only and hybrid identity sign-in choices”, not the immediate requirement. Hybrid identity depends on matching and synchronizing attributes between directories, and on-prem account changes are not automatically visible in the cloud without the configured path.
The proposed action addresses “distinguish workforce workload and agent identities at a conceptual level” rather than the problem described. Hybrid identity depends on matching and synchronizing attributes between directories, and on-prem account changes are not automatically visible in the cloud without the configured path.
“identify a Microsoft entra tenant as cloud identity directory” is related to another task, not the failure shown here. Hybrid identity depends on matching and synchronizing attributes between directories, and on-prem account changes are not automatically visible in the cloud without the configured path.
Question 217
A hybrid tenant's new employees are missing from cloud applications after the identity synchronization scheduler failed silently. Why does the recommended approach address this particular concern?
Explanation
Correct Answer
The situation is that a hybrid tenant's new employees are missing from cloud applications after the identity synchronization scheduler failed silently. Hybrid identity depends on matching and synchronizing attributes between directories, and on-prem account changes are not automatically visible in the cloud without the configured path. This supports the decision to use supported Microsoft Entra Connect Sync or Cloud Sync where appropriate to synchronize intended on-prem directory accounts and monitor synchronization scope and health.
Incorrect Answers
The principle behind “distinguish workforce workload and agent identities at a conceptual level” is not the one being tested. Here, hybrid identity depends on matching and synchronizing attributes between directories, and on-prem account changes are not automatically visible in the cloud without the configured path.
“distinguish cloud-only and hybrid identity sign-in choices” describes another technical distinction. Here, hybrid identity depends on matching and synchronizing attributes between directories, and on-prem account changes are not automatically visible in the cloud without the configured path.
“use an app registration and service principal for application access” explains a different mechanism. Here, hybrid identity depends on matching and synchronizing attributes between directories, and on-prem account changes are not automatically visible in the cloud without the configured path.
Question 218
A hybrid tenant's new employees are missing from cloud applications after the identity synchronization scheduler failed silently. Which evidence best validates the proposed outcome?
Explanation
Correct Answer
The situation is that a hybrid tenant's new employees are missing from cloud applications after the identity synchronization scheduler failed silently. Create a synthetic on-prem identity update in a lab and verify intended user attributes and deactivation propagate while excluded accounts remain outside scope. It is the relevant test because hybrid identity depends on matching and synchronizing attributes between directories, and on-prem account changes are not automatically visible in the cloud without the configured path.
Incorrect Answers
This evidence addresses “distinguish workforce workload and agent identities at a conceptual level” instead of confirming the repair. To check this result, create a synthetic on-prem identity update in a lab and verify intended user attributes and deactivation propagate while excluded accounts remain outside scope.
That test concerns “reuse user-assigned managed identity deliberately”, not the requested outcome. To check this result, create a synthetic on-prem identity update in a lab and verify intended user attributes and deactivation propagate while excluded accounts remain outside scope.
The proposed check is relevant to “use system-assigned managed identities for a single Azure resource”, but not sufficient here. To check this result, create a synthetic on-prem identity update in a lab and verify intended user attributes and deactivation propagate while excluded accounts remain outside scope.
Question 219
Consider this situation: A hybrid tenant's new employees are missing from cloud applications after the identity synchronization scheduler failed silently. A team member suggests: "Assume disabling an AD DS user immediately disables every cloud session even when identity synchronization has stopped for several days." What is the main risk?
Explanation
Correct Answer
The situation is that a hybrid tenant's new employees are missing from cloud applications after the identity synchronization scheduler failed silently. Former employee access may persist in cloud apps because directory changes did not propagate through an unhealthy synchronization service. The shortcut is unsafe because hybrid identity depends on matching and synchronizing attributes between directories, and on-prem account changes are not automatically visible in the cloud without the configured path.
Incorrect Answers
“Automated tasks can gain broad untraceable access and weaken the ability to revoke or audit a…” can arise elsewhere, but it is not the most direct risk here. Here, former employee access may persist in cloud apps because directory changes did not propagate through an unhealthy synchronization service.
That consequence concerns “Anyone who obtains the static secret may impersonate the deployment application beyond the intended build run…”, which is a different failure. Here, former employee access may persist in cloud apps because directory changes did not propagate through an unhealthy synchronization service.
The alternative risk relates to “A migration may break old device policies or application authentication because the architecture confused a cloud…”, not the stated mistake. Here, former employee access may persist in cloud apps because directory changes did not propagate through an unhealthy synchronization service.
Question 220
A security and compliance reviewer considers: A hybrid tenant's new employees are missing from cloud applications after the identity synchronization scheduler failed silently. Which response and evidence should be linked?
Explanation
Correct Answer
The situation is that a hybrid tenant's new employees are missing from cloud applications after the identity synchronization scheduler failed silently. Use supported Microsoft Entra Connect Sync or Cloud Sync where appropriate to synchronize intended on-prem directory accounts and monitor synchronization scope and health. Validation: Create a synthetic on-prem identity update in a lab and verify intended user attributes and deactivation propagate while excluded accounts remain outside scope. The action and test belong together because hybrid identity depends on matching and synchronizing attributes between directories, and on-prem account changes are not automatically visible in the cloud without the configured path.
Incorrect Answers
That action-and-evidence pair concerns “distinguish cloud-only and hybrid identity sign-in choices”, not this decision. The appropriate action is to use supported Microsoft Entra Connect Sync or Cloud Sync where appropriate to synchronize intended on-prem directory accounts and monitor synchronization scope and health. To confirm, create a synthetic on-prem identity update in a lab and verify intended user attributes and deactivation propagate while excluded accounts remain outside scope.
The proposed pair focuses on “prefer workload identity federation over stored CI secrets” instead. The appropriate action is to use supported Microsoft Entra Connect Sync or Cloud Sync where appropriate to synchronize intended on-prem directory accounts and monitor synchronization scope and health. To confirm, create a synthetic on-prem identity update in a lab and verify intended user attributes and deactivation propagate while excluded accounts remain outside scope.
“reuse user-assigned managed identity deliberately” evaluates a different intervention. The appropriate action is to use supported Microsoft Entra Connect Sync or Cloud Sync where appropriate to synchronize intended on-prem directory accounts and monitor synchronization scope and health. To confirm, create a synthetic on-prem identity update in a lab and verify intended user attributes and deactivation propagate while excluded accounts remain outside scope.
Microsoft Security, Compliance, and Identity Fundamentals (SC-900) Practice Tests
- Microsoft SC-900 Practice Test 20 - 10 Questions (Last Reviewed 01-Nov-2026)
- Microsoft SC-900 Practice Test 21 - 10 Questions (Last Reviewed 31-Oct-2026)
- Microsoft SC-900 Practice Test 22 - 10 Questions (Last Reviewed 30-Oct-2026)
- Microsoft SC-900 Practice Test 23 - 10 Questions (Last Reviewed 29-Oct-2026)
- Microsoft SC-900 Practice Test 24 - 10 Questions (Last Reviewed 28-Oct-2026)