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 23

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.

Question 221

A company wants cloud application sign-in during an on-prem network outage and compares supported synchronization and federation options. Which action best addresses this requirement?

  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. Attach a user-assigned managed identity to multiple supported Azure resources when a shared, separately managed identity lifecycle is required.
  4. Register an application in Entra and grant its service principal explicitly approved permissions with a supported certificate or federated credential when appropriate.

Explanation

Correct Answer

A:

Choose cloud-only authentication or a supported hybrid password hash, pass-through or federation approach based on business and dependency constraints. Different hybrid sign-in patterns change where credentials are validated and which on-prem services remain necessary when connectivity fails. To verify, perform documented test sign-ins during a controlled laboratory loss of on-prem connectivity and record expected sign-in differences for the chosen model.

Incorrect Answers

B:

“distinguish workforce workload and agent identities at a conceptual level” is related to another task, not the failure shown here. Different hybrid sign-in patterns change where credentials are validated and which on-prem services remain necessary when connectivity fails.

C:

This alternative focuses on “reuse user-assigned managed identity deliberately” instead of the required outcome. Different hybrid sign-in patterns change where credentials are validated and which on-prem services remain necessary when connectivity fails.

D:

That choice concerns “use an app registration and service principal for application access”, not the immediate requirement. Different hybrid sign-in patterns change where credentials are validated and which on-prem services remain necessary when connectivity fails.

Question 222

A cloud security learner considers: A company wants cloud application sign-in during an on-prem network outage and compares supported synchronization and federation options. Which underlying principle applies?

  1. An automated service principal or agent identity has a different accountability and token lifecycle from an interactive workforce member or external guest.
  2. Different hybrid sign-in patterns change where credentials are validated and which on-prem services remain necessary when connectivity fails.
  3. A Microsoft Entra tenant defines a cloud identity boundary and issues access tokens for supported applications, unlike a classic on-prem AD DS domain controller.
  4. B2B collaboration represents external identities in a resource tenant while their home organization may remain responsible for primary authentication.

Explanation

Correct Answer

B:

Different hybrid sign-in patterns change where credentials are validated and which on-prem services remain necessary when connectivity fails. This supports the decision to choose cloud-only authentication or a supported hybrid password hash, pass-through or federation approach based on business and dependency constraints.

Incorrect Answers

A:

The principle behind “distinguish workforce workload and agent identities at a conceptual level” is not the one being tested. Here, different hybrid sign-in patterns change where credentials are validated and which on-prem services remain necessary when connectivity fails.

C:

“identify a Microsoft entra tenant as cloud identity directory” explains a different mechanism. Here, different hybrid sign-in patterns change where credentials are validated and which on-prem services remain necessary when connectivity fails.

D:

That statement concerns “separate member and guest identities in collaboration” rather than the cause in this case. Here, different hybrid sign-in patterns change where credentials are validated and which on-prem services remain necessary when connectivity fails.

Question 223

A company wants cloud application sign-in during an on-prem network outage and compares supported synchronization and federation options. What should the team examine before accepting the result?

  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. Perform documented test sign-ins during a controlled laboratory loss of on-prem connectivity and record expected sign-in differences for the chosen model.
  4. 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

C:

Perform documented test sign-ins during a controlled laboratory loss of on-prem connectivity and record expected sign-in differences for the chosen model. It is the relevant test because different hybrid sign-in patterns change where credentials are validated and which on-prem services remain necessary when connectivity fails.

Incorrect Answers

A:

“synchronize hybrid identities with explicit scope and health checks” would verify a different part of the system. To check this result, perform documented test sign-ins during a controlled laboratory loss of on-prem connectivity and record expected sign-in differences for the chosen model.

B:

That test concerns “prefer workload identity federation over stored CI secrets”, not the requested outcome. To check this result, perform documented test sign-ins during a controlled laboratory loss of on-prem connectivity and record expected sign-in differences for the chosen model.

D:

This evidence addresses “identify a Microsoft entra tenant as cloud identity directory” instead of confirming the repair. To check this result, perform documented test sign-ins during a controlled laboratory loss of on-prem connectivity and record expected sign-in differences for the chosen model.

Question 224

A company wants cloud application sign-in during an on-prem network outage and compares supported synchronization and federation options. The proposed shortcut is: "Describe password hash synchronization and federation as identical services with identical on-prem runtime dependencies." Which failure is most likely?

  1. Workloads may lose access or administrators may broaden permissions unnecessarily when distinct managed identity lifecycles are misunderstood.
  2. The app can inherit excessive tenant powers and may stop when the human password or MFA policy changes unexpectedly.
  3. Anyone who obtains the static secret may impersonate the deployment application beyond the intended build run or repository boundary.
  4. A failure of an on-prem authentication endpoint can cause unexpected outage when the organization selected a dependency-heavy sign-in architecture.

Explanation

Correct Answer

D:

A failure of an on-prem authentication endpoint can cause unexpected outage when the organization selected a dependency-heavy sign-in architecture. The shortcut is unsafe because different hybrid sign-in patterns change where credentials are validated and which on-prem services remain necessary when connectivity fails.

Incorrect Answers

A:

That consequence concerns “Workloads may lose access or administrators may broaden permissions unnecessarily when distinct managed identity lifecycles are…”, which is a different failure. Here, a failure of an on-prem authentication endpoint can cause unexpected outage when the organization selected a dependency-heavy sign-in architecture.

B:

“The app can inherit excessive tenant powers and may stop when the human password or MFA…” does not describe the result of this shortcut. Here, a failure of an on-prem authentication endpoint can cause unexpected outage when the organization selected a dependency-heavy sign-in architecture.

C:

The alternative risk relates to “Anyone who obtains the static secret may impersonate the deployment application beyond the intended build run…”, not the stated mistake. Here, a failure of an on-prem authentication endpoint can cause unexpected outage when the organization selected a dependency-heavy sign-in architecture.

Question 225

For this case—A company wants cloud application sign-in during an on-prem network outage and compares supported synchronization and federation options.—which implementation and acceptance check are correctly paired?

  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: 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.
  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: Register an application in Entra and grant its service principal explicitly approved permissions with a supported certificate or federated credential when appropriate. Validation: Check application object and enterprise application representation in a sandbox tenant and verify a token has only approved resource permissions.

Explanation

Correct Answer

A:

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. The action and test belong together because different hybrid sign-in patterns change where credentials are validated and which on-prem services remain necessary when connectivity fails.

Incorrect Answers

B:

“use system-assigned managed identities for a single Azure resource” evaluates a different intervention. The appropriate action is to choose cloud-only authentication or a supported hybrid password hash, pass-through or federation approach based on business and dependency constraints. To confirm, perform documented test sign-ins during a controlled laboratory loss of on-prem connectivity and record expected sign-in differences for the chosen model.

C:

The linked action and check for “synchronize hybrid identities with explicit scope and health checks” would not resolve this case. The appropriate action is to choose cloud-only authentication or a supported hybrid password hash, pass-through or federation approach based on business and dependency constraints. To confirm, perform documented test sign-ins during a controlled laboratory loss of on-prem connectivity and record expected sign-in differences for the chosen model.

D:

That action-and-evidence pair concerns “use an app registration and service principal for application access”, not this decision. The appropriate action is to choose cloud-only authentication or a supported hybrid password hash, pass-through or federation approach based on business and dependency constraints. To confirm, perform documented test sign-ins during a controlled laboratory loss of on-prem connectivity and record expected sign-in differences for the chosen model.

Question 226

An architect assumes an app federated directly to an on-prem identity provider stays available when that provider's network becomes unreachable. 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. Choose cloud-only authentication or a supported hybrid password hash, pass-through or federation approach based on business and dependency constraints.
  3. 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.
  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

B:

The situation is that an architect assumes an app federated directly to an on-prem identity provider stays available when that provider's network becomes unreachable. Choose cloud-only authentication or a supported hybrid password hash, pass-through or federation approach based on business and dependency constraints. Different hybrid sign-in patterns change where credentials are validated and which on-prem services remain necessary when connectivity fails. To verify, perform documented test sign-ins during a controlled laboratory loss of on-prem connectivity and record expected sign-in differences for the chosen model.

Incorrect Answers

A:

“use an app registration and service principal for application access” is related to another task, not the failure shown here. Different hybrid sign-in patterns change where credentials are validated and which on-prem services remain necessary when connectivity fails.

C:

That choice concerns “distinguish workforce workload and agent identities at a conceptual level”, not the immediate requirement. Different hybrid sign-in patterns change where credentials are validated and which on-prem services remain necessary when connectivity fails.

D:

The proposed action addresses “synchronize hybrid identities with explicit scope and health checks” rather than the problem described. Different hybrid sign-in patterns change where credentials are validated and which on-prem services remain necessary when connectivity fails.

Question 227

An architect assumes an app federated directly to an on-prem identity provider stays available when that provider's network becomes unreachable. Which technical explanation most directly supports the right approach?

  1. Authentication methods availability is governed by tenant policy and user targeting, not merely by a user installing an authenticator app.
  2. 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.
  3. Different hybrid sign-in patterns change where credentials are validated and which on-prem services remain necessary when connectivity fails.
  4. Federated workload credentials exchange verified short-lived tokens based on issuer, audience and subject, avoiding stored long-lived cloud secrets in CI.

Explanation

Correct Answer

C:

The situation is that an architect assumes an app federated directly to an on-prem identity provider stays available when that provider's network becomes unreachable. Different hybrid sign-in patterns change where credentials are validated and which on-prem services remain necessary when connectivity fails. This supports the decision to choose cloud-only authentication or a supported hybrid password hash, pass-through or federation approach based on business and dependency constraints.

Incorrect Answers

A:

“set authentication method policies for approved factors” describes another technical distinction. Here, different hybrid sign-in patterns change where credentials are validated and which on-prem services remain necessary when connectivity fails.

B:

“synchronize hybrid identities with explicit scope and health checks” explains a different mechanism. Here, different hybrid sign-in patterns change where credentials are validated and which on-prem services remain necessary when connectivity fails.

D:

The principle behind “prefer workload identity federation over stored CI secrets” is not the one being tested. Here, different hybrid sign-in patterns change where credentials are validated and which on-prem services remain necessary when connectivity fails.

Question 228

For this situation—An architect assumes an app federated directly to an on-prem identity provider stays available when that provider's network becomes unreachable.—which check provides the strongest verification?

  1. Examine a sample employee sign-in, workload service principal access and registered agent identity, verifying each uses the intended tenant permissions.
  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. Attach one test user-assigned identity to two authorized services, prove restricted token access and remove one host without deleting the identity itself.
  4. Perform documented test sign-ins during a controlled laboratory loss of on-prem connectivity and record expected sign-in differences for the chosen model.

Explanation

Correct Answer

D:

The situation is that an architect assumes an app federated directly to an on-prem identity provider stays available when that provider's network becomes unreachable. Perform documented test sign-ins during a controlled laboratory loss of on-prem connectivity and record expected sign-in differences for the chosen model. It is the relevant test because different hybrid sign-in patterns change where credentials are validated and which on-prem services remain necessary when connectivity fails.

Incorrect Answers

A:

That test concerns “distinguish workforce workload and agent identities at a conceptual level”, not the requested outcome. To check this result, perform documented test sign-ins during a controlled laboratory loss of on-prem connectivity and record expected sign-in differences for the chosen model.

B:

The proposed check is relevant to “prefer workload identity federation over stored CI secrets”, but not sufficient here. To check this result, perform documented test sign-ins during a controlled laboratory loss of on-prem connectivity and record expected sign-in differences for the chosen model.

C:

This evidence addresses “reuse user-assigned managed identity deliberately” instead of confirming the repair. To check this result, perform documented test sign-ins during a controlled laboratory loss of on-prem connectivity and record expected sign-in differences for the chosen model.

Question 229

An architect assumes an app federated directly to an on-prem identity provider stays available when that provider's network becomes unreachable. If the team does the following—"Describe password hash synchronization and federation as identical services with identical on-prem runtime dependencies."—what could go wrong?

  1. A failure of an on-prem authentication endpoint can cause unexpected outage when the organization selected a dependency-heavy sign-in architecture.
  2. Leaked long-lived credentials may grant unintended privileges while resource deletion fails to remove the separately embedded secret.
  3. Automated tasks can gain broad untraceable access and weaken the ability to revoke or audit a particular workload or agent.
  4. Partner credentials may outlive the contract and expose unrelated company resources because lifecycle and privileges were never scoped.

Explanation

Correct Answer

A:

The situation is that an architect assumes an app federated directly to an on-prem identity provider stays available when that provider's network becomes unreachable. A failure of an on-prem authentication endpoint can cause unexpected outage when the organization selected a dependency-heavy sign-in architecture. The shortcut is unsafe because different hybrid sign-in patterns change where credentials are validated and which on-prem services remain necessary when connectivity fails.

Incorrect Answers

B:

The alternative risk relates to “Leaked long-lived credentials may grant unintended privileges while resource deletion fails to remove the separately embedded…”, not the stated mistake. Here, a failure of an on-prem authentication endpoint can cause unexpected outage when the organization selected a dependency-heavy sign-in architecture.

C:

“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, a failure of an on-prem authentication endpoint can cause unexpected outage when the organization selected a dependency-heavy sign-in architecture.

D:

That consequence concerns “Partner credentials may outlive the contract and expose unrelated company resources because lifecycle and privileges were…”, which is a different failure. Here, a failure of an on-prem authentication endpoint can cause unexpected outage when the organization selected a dependency-heavy sign-in architecture.

Question 230

An architect assumes an app federated directly to an on-prem identity provider stays available when that provider's network becomes unreachable. Which action and validation evidence belong together?

  1. 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.
  2. 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.
  3. 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.
  4. 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.

Explanation

Correct Answer

B:

The situation is that an architect assumes an app federated directly to an on-prem identity provider stays available when that provider's network becomes unreachable. 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. The action and test belong together because different hybrid sign-in patterns change where credentials are validated and which on-prem services remain necessary when connectivity fails.

Incorrect Answers

A:

“reuse user-assigned managed identity deliberately” evaluates a different intervention. The appropriate action is to choose cloud-only authentication or a supported hybrid password hash, pass-through or federation approach based on business and dependency constraints. To confirm, perform documented test sign-ins during a controlled laboratory loss of on-prem connectivity and record expected sign-in differences for the chosen model.

C:

That action-and-evidence pair concerns “distinguish workforce workload and agent identities at a conceptual level”, not this decision. The appropriate action is to choose cloud-only authentication or a supported hybrid password hash, pass-through or federation approach based on business and dependency constraints. To confirm, perform documented test sign-ins during a controlled laboratory loss of on-prem connectivity and record expected sign-in differences for the chosen model.

D:

The proposed pair focuses on “use system-assigned managed identities for a single Azure resource” instead. The appropriate action is to choose cloud-only authentication or a supported hybrid password hash, pass-through or federation approach based on business and dependency constraints. To confirm, perform documented test sign-ins during a controlled laboratory loss of on-prem connectivity and record expected sign-in differences for the chosen model.

Microsoft Security, Compliance, and Identity Fundamentals (SC-900) Practice Tests