Practice Exams:

Microsoft SC-900 Dumps

EXAM: Microsoft Security, Compliance, and Identity Fundamentals
Verified By Experts
Premium Bundle
$40.00
$59.97 $99.97

SC-900 Premium Bundle


  • Premium File 259 Questions & Answers
  • Training Course 147 Lectures
  • Study Guide 413 Pages

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?

  1. Action: Invite external collaborators using supported Microsoft Entra B2B guest collaboration and give them scoped resource access rather than treating partners as tenant administrators. Validation: Verify a sample guest appears with the expected external identity type, accesses only one approved Teams workspace and cannot manage directory roles.
  2. Action: 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.
  3. Action: Enable a system-assigned managed identity for a supported Azure-hosted workload and grant its service principal only required access to a target service. Validation: From a test workload obtain an Entra token and access its permitted Key Vault secret, then delete the resource in a lab and inspect identity lifecycle.
  4. Action: Use Microsoft Entra ID as the tenant's cloud directory for registered users, groups, applications and sign-in policy without assuming it is a physical domain controller. Validation: List synthetic tenant users, registered applications and sign-in events, then verify a separate legacy AD DS Group Policy test remains outside Entra-only functions.

Explanation

Correct Answer

B:

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

A:

“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.

C:

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.

D:

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?

  1. Register an application in Entra and grant its service principal explicitly approved permissions with a supported certificate or federated credential when appropriate.
  2. Enable a system-assigned managed identity for a supported Azure-hosted workload and grant its service principal only required access to a target service.
  3. Use supported Microsoft Entra Connect Sync or Cloud Sync where appropriate to synchronize intended on-prem directory accounts and monitor synchronization scope and health.
  4. Use Entra workload identity federation to validate trusted external OIDC assertions from a supported build service before issuing an app access token.

Explanation

Correct Answer

C:

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

A:

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.

B:

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.

D:

“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?

  1. A system-assigned managed identity is tied to its Azure resource lifecycle and avoids hard-coded long-lived application secrets for supported token requests.
  2. Different hybrid sign-in patterns change where credentials are validated and which on-prem services remain necessary when connectivity fails.
  3. A user-assigned managed identity exists independently of any one associated resource, unlike system-assigned identities deleted with their host resources.
  4. 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.

Explanation

Correct Answer

D:

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

A:

“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.

B:

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.

C:

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?

  1. Create a synthetic on-prem identity update in a lab and verify intended user attributes and deactivation propagate while excluded accounts remain outside scope.
  2. Run a sandbox pipeline with an approved issuer and branch-bound subject, then show an unexpected branch or audience cannot obtain the cloud token.
  3. List synthetic tenant users, registered applications and sign-in events, then verify a separate legacy AD DS Group Policy test remains outside Entra-only functions.
  4. Examine a sample employee sign-in, workload service principal access and registered agent identity, verifying each uses the intended tenant permissions.

Explanation

Correct Answer

A:

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

B:

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.

C:

“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.

D:

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?

  1. The app can inherit excessive tenant powers and may stop when the human password or MFA policy changes unexpectedly.
  2. Former employee access may persist in cloud apps because directory changes did not propagate through an unhealthy synchronization service.
  3. A failure of an on-prem authentication endpoint can cause unexpected outage when the organization selected a dependency-heavy sign-in architecture.
  4. Leaked long-lived credentials may grant unintended privileges while resource deletion fails to remove the separately embedded secret.

Explanation

Correct Answer

B:

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

A:

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.

C:

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.

D:

“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?

  1. Action: Choose cloud-only authentication or a supported hybrid password hash, pass-through or federation approach based on business and dependency constraints. Validation: Perform documented test sign-ins during a controlled laboratory loss of on-prem connectivity and record expected sign-in differences for the chosen model.
  2. Action: Invite external collaborators using supported Microsoft Entra B2B guest collaboration and give them scoped resource access rather than treating partners as tenant administrators. Validation: Verify a sample guest appears with the expected external identity type, accesses only one approved Teams workspace and cannot manage directory roles.
  3. Action: 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.
  4. Action: Classify identities by the actor performing work and apply supported human, service or agent access controls instead of assuming all principals are employee user accounts. Validation: Examine a sample employee sign-in, workload service principal access and registered agent identity, verifying each uses the intended tenant permissions.

Explanation

Correct Answer

C:

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

A:

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.

B:

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.

D:

“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?

  1. Choose cloud-only authentication or a supported hybrid password hash, pass-through or federation approach based on business and dependency constraints.
  2. Classify identities by the actor performing work and apply supported human, service or agent access controls instead of assuming all principals are employee user accounts.
  3. Use Microsoft Entra ID as the tenant's cloud directory for registered users, groups, applications and sign-in policy without assuming it is a physical domain controller.
  4. Use supported Microsoft Entra Connect Sync or Cloud Sync where appropriate to synchronize intended on-prem directory accounts and monitor synchronization scope and health.

Explanation

Correct Answer

D:

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

A:

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.

B:

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.

C:

“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?

  1. 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.
  2. An automated service principal or agent identity has a different accountability and token lifecycle from an interactive workforce member or external guest.
  3. Different hybrid sign-in patterns change where credentials are validated and which on-prem services remain necessary when connectivity fails.
  4. An app registration describes application identity while a service principal represents its concrete presence and authorization in a tenant.

Explanation

Correct Answer

A:

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

B:

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.

C:

“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.

D:

“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?

  1. Examine a sample employee sign-in, workload service principal access and registered agent identity, verifying each uses the intended tenant permissions.
  2. Create a synthetic on-prem identity update in a lab and verify intended user attributes and deactivation propagate while excluded accounts remain outside scope.
  3. Attach one test user-assigned identity to two authorized services, prove restricted token access and remove one host without deleting the identity itself.
  4. From a test workload obtain an Entra token and access its permitted Key Vault secret, then delete the resource in a lab and inspect identity lifecycle.

Explanation

Correct Answer

B:

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

A:

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.

C:

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.

D:

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?

  1. Automated tasks can gain broad untraceable access and weaken the ability to revoke or audit a particular workload or agent.
  2. Anyone who obtains the static secret may impersonate the deployment application beyond the intended build run or repository boundary.
  3. Former employee access may persist in cloud apps because directory changes did not propagate through an unhealthy synchronization service.
  4. A migration may break old device policies or application authentication because the architecture confused a cloud tenant with an AD DS forest.

Explanation

Correct Answer

C:

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

A:

“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.

B:

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.

D:

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?

  1. Action: Choose cloud-only authentication or a supported hybrid password hash, pass-through or federation approach based on business and dependency constraints. Validation: Perform documented test sign-ins during a controlled laboratory loss of on-prem connectivity and record expected sign-in differences for the chosen model.
  2. Action: 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.
  3. Action: Attach a user-assigned managed identity to multiple supported Azure resources when a shared, separately managed identity lifecycle is required. Validation: Attach one test user-assigned identity to two authorized services, prove restricted token access and remove one host without deleting the identity itself.
  4. Action: 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.

Explanation

Correct Answer

D:

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

A:

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.

B:

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.

C:

“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