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 24

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.

Question 231

During a tenant protection and compliance review, A company deploys an internal AI assistant that reads approved files and wants a distinct policy and audit trail from its employee's interactive account. What is the most appropriate next decision?

  1. 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.
  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. 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. Choose cloud-only authentication or a supported hybrid password hash, pass-through or federation approach based on business and dependency constraints.

Explanation

Correct Answer

C:

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. An automated service principal or agent identity has a different accountability and token lifecycle from an interactive workforce member or external guest. To verify, examine a sample employee sign-in, workload service principal access and registered agent identity, verifying each uses the intended tenant permissions.

Incorrect Answers

A:

This alternative focuses on “identify a Microsoft entra tenant as cloud identity directory” instead of the required outcome. An automated service principal or agent identity has a different accountability and token lifecycle from an interactive workforce member or external guest.

B:

That choice concerns “use system-assigned managed identities for a single Azure resource”, not the immediate requirement. An automated service principal or agent identity has a different accountability and token lifecycle from an interactive workforce member or external guest.

D:

“distinguish cloud-only and hybrid identity sign-in choices” is related to another task, not the failure shown here. An automated service principal or agent identity has a different accountability and token lifecycle from an interactive workforce member or external guest.

Question 232

A company deploys an internal AI assistant that reads approved files and wants a distinct policy and audit trail from its employee's interactive account. Why does the recommended approach address this particular concern?

  1. B2B collaboration represents external identities in a resource tenant while their home organization may remain responsible for primary authentication.
  2. An app registration describes application identity while a service principal represents its concrete presence and authorization in a tenant.
  3. Different hybrid sign-in patterns change where credentials are validated and which on-prem services remain necessary when connectivity fails.
  4. An automated service principal or agent identity has a different accountability and token lifecycle from an interactive workforce member or external guest.

Explanation

Correct Answer

D:

An automated service principal or agent identity has a different accountability and token lifecycle from an interactive workforce member or external guest. This supports the decision to 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.

Incorrect Answers

A:

“separate member and guest identities in collaboration” explains a different mechanism. Here, an automated service principal or agent identity has a different accountability and token lifecycle from an interactive workforce member or external guest.

B:

That statement concerns “use an app registration and service principal for application access” rather than the cause in this case. Here, an automated service principal or agent identity has a different accountability and token lifecycle from an interactive workforce member or external guest.

C:

The principle behind “distinguish cloud-only and hybrid identity sign-in choices” is not the one being tested. Here, an automated service principal or agent identity has a different accountability and token lifecycle from an interactive workforce member or external guest.

Question 233

A company deploys an internal AI assistant that reads approved files and wants a distinct policy and audit trail from its employee's interactive account. 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. 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.
  3. Check application object and enterprise application representation in a sandbox tenant and verify a token has only approved resource permissions.
  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

A:

Examine a sample employee sign-in, workload service principal access and registered agent identity, verifying each uses the intended tenant permissions. It is the relevant test because an automated service principal or agent identity has a different accountability and token lifecycle from an interactive workforce member or external guest.

Incorrect Answers

B:

This evidence addresses “identify a Microsoft entra tenant as cloud identity directory” instead of confirming the repair. To check this result, examine a sample employee sign-in, workload service principal access and registered agent identity, verifying each uses the intended tenant permissions.

C:

“use an app registration and service principal for application access” would verify a different part of the system. To check this result, examine a sample employee sign-in, workload service principal access and registered agent identity, verifying each uses the intended tenant permissions.

D:

That test concerns “distinguish cloud-only and hybrid identity sign-in choices”, not the requested outcome. To check this result, examine a sample employee sign-in, workload service principal access and registered agent identity, verifying each uses the intended tenant permissions.

Question 234

Consider this situation: A company deploys an internal AI assistant that reads approved files and wants a distinct policy and audit trail from its employee's interactive account. A team member suggests: "Give a nonhuman AI assistant an employee's unrestricted password and assume automated agent activities are indistinguishable from normal user work." What is the main risk?

  1. Leaked long-lived credentials may grant unintended privileges while resource deletion fails to remove the separately embedded secret.
  2. Automated tasks can gain broad untraceable access and weaken the ability to revoke or audit a particular workload or agent.
  3. Partner credentials may outlive the contract and expose unrelated company resources because lifecycle and privileges were never scoped.
  4. The app can inherit excessive tenant powers and may stop when the human password or MFA policy changes unexpectedly.

Explanation

Correct Answer

B:

Automated tasks can gain broad untraceable access and weaken the ability to revoke or audit a particular workload or agent. The shortcut is unsafe because an automated service principal or agent identity has a different accountability and token lifecycle from an interactive workforce member or external guest.

Incorrect Answers

A:

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, automated tasks can gain broad untraceable access and weaken the ability to revoke or audit a particular workload or agent.

C:

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, automated tasks can gain broad untraceable access and weaken the ability to revoke or audit a particular workload or agent.

D:

“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, automated tasks can gain broad untraceable access and weaken the ability to revoke or audit a particular workload or agent.

Question 235

A security and compliance reviewer considers: A company deploys an internal AI assistant that reads approved files and wants a distinct policy and audit trail from its employee's interactive account. Which response and evidence should be linked?

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

Explanation

Correct Answer

C:

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. The action and test belong together because an automated service principal or agent identity has a different accountability and token lifecycle from an interactive workforce member or external guest.

Incorrect Answers

A:

The linked action and check for “separate member and guest identities in collaboration” would not resolve this case. The appropriate action is to 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. To confirm, examine a sample employee sign-in, workload service principal access and registered agent identity, verifying each uses the intended tenant permissions.

B:

That action-and-evidence pair concerns “use system-assigned managed identities for a single Azure resource”, not this decision. The appropriate action is to 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. To confirm, examine a sample employee sign-in, workload service principal access and registered agent identity, verifying each uses the intended tenant permissions.

D:

“distinguish cloud-only and hybrid identity sign-in choices” evaluates a different intervention. The appropriate action is to 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. To confirm, examine a sample employee sign-in, workload service principal access and registered agent identity, verifying each uses the intended tenant permissions.

Question 236

A background service and a human operator appear under the same sign-in identity, preventing investigators from isolating who performed a privileged task. Which action best addresses this requirement?

  1. Use supported Microsoft Entra Connect Sync or Cloud Sync where appropriate to synchronize intended on-prem directory accounts and monitor synchronization scope and health.
  2. 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.
  3. Register an application in Entra and grant its service principal explicitly approved permissions with a supported certificate or federated credential when appropriate.
  4. 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.

Explanation

Correct Answer

D:

The situation is that a background service and a human operator appear under the same sign-in identity, preventing investigators from isolating who performed a privileged task. 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. An automated service principal or agent identity has a different accountability and token lifecycle from an interactive workforce member or external guest. To verify, examine a sample employee sign-in, workload service principal access and registered agent identity, verifying each uses the intended tenant permissions.

Incorrect Answers

A:

That choice concerns “synchronize hybrid identities with explicit scope and health checks”, not the immediate requirement. An automated service principal or agent identity has a different accountability and token lifecycle from an interactive workforce member or external guest.

B:

The proposed action addresses “identify a Microsoft entra tenant as cloud identity directory” rather than the problem described. An automated service principal or agent identity has a different accountability and token lifecycle from an interactive workforce member or external guest.

C:

“use an app registration and service principal for application access” is related to another task, not the failure shown here. An automated service principal or agent identity has a different accountability and token lifecycle from an interactive workforce member or external guest.

Question 237

A cloud security learner considers: A background service and a human operator appear under the same sign-in identity, preventing investigators from isolating who performed a privileged task. 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. 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. A system-assigned managed identity is tied to its Azure resource lifecycle and avoids hard-coded long-lived application secrets for supported token requests.
  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

A:

The situation is that a background service and a human operator appear under the same sign-in identity, preventing investigators from isolating who performed a privileged task. An automated service principal or agent identity has a different accountability and token lifecycle from an interactive workforce member or external guest. This supports the decision to 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.

Incorrect Answers

B:

The principle behind “synchronize hybrid identities with explicit scope and health checks” is not the one being tested. Here, an automated service principal or agent identity has a different accountability and token lifecycle from an interactive workforce member or external guest.

C:

“use system-assigned managed identities for a single Azure resource” describes another technical distinction. Here, an automated service principal or agent identity has a different accountability and token lifecycle from an interactive workforce member or external guest.

D:

“prefer workload identity federation over stored CI secrets” explains a different mechanism. Here, an automated service principal or agent identity has a different accountability and token lifecycle from an interactive workforce member or external guest.

Question 238

A background service and a human operator appear under the same sign-in identity, preventing investigators from isolating who performed a privileged task. What should the team examine before accepting the result?

  1. 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.
  2. Examine a sample employee sign-in, workload service principal access and registered agent identity, verifying each uses the intended tenant permissions.
  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

B:

The situation is that a background service and a human operator appear under the same sign-in identity, preventing investigators from isolating who performed a privileged task. Examine a sample employee sign-in, workload service principal access and registered agent identity, verifying each uses the intended tenant permissions. It is the relevant test because an automated service principal or agent identity has a different accountability and token lifecycle from an interactive workforce member or external guest.

Incorrect Answers

A:

This evidence addresses “use system-assigned managed identities for a single Azure resource” instead of confirming the repair. To check this result, examine a sample employee sign-in, workload service principal access and registered agent identity, verifying each uses the intended tenant permissions.

C:

That test concerns “reuse user-assigned managed identity deliberately”, not the requested outcome. To check this result, examine a sample employee sign-in, workload service principal access and registered agent identity, verifying each uses the intended tenant permissions.

D:

The proposed check is relevant to “distinguish cloud-only and hybrid identity sign-in choices”, but not sufficient here. To check this result, examine a sample employee sign-in, workload service principal access and registered agent identity, verifying each uses the intended tenant permissions.

Question 239

A background service and a human operator appear under the same sign-in identity, preventing investigators from isolating who performed a privileged task. The proposed shortcut is: "Give a nonhuman AI assistant an employee's unrestricted password and assume automated agent activities are indistinguishable from normal user work." Which failure is most likely?

  1. The app can inherit excessive tenant powers and may stop when the human password or MFA policy changes unexpectedly.
  2. Workloads may lose access or administrators may broaden permissions unnecessarily when distinct managed identity lifecycles are misunderstood.
  3. Automated tasks can gain broad untraceable access and weaken the ability to revoke or audit a particular workload or agent.
  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

C:

The situation is that a background service and a human operator appear under the same sign-in identity, preventing investigators from isolating who performed a privileged task. Automated tasks can gain broad untraceable access and weaken the ability to revoke or audit a particular workload or agent. The shortcut is unsafe because an automated service principal or agent identity has a different accountability and token lifecycle from an interactive workforce member or external guest.

Incorrect Answers

A:

“The app can inherit excessive tenant powers and may stop when the human password or MFA…” can arise elsewhere, but it is not the most direct risk here. Here, automated tasks can gain broad untraceable access and weaken the ability to revoke or audit a particular workload or agent.

B:

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, automated tasks can gain broad untraceable access and weaken the ability to revoke or audit a particular workload or agent.

D:

The alternative risk relates to “A failure of an on-prem authentication endpoint can cause unexpected outage when the organization selected a…”, not the stated mistake. Here, automated tasks can gain broad untraceable access and weaken the ability to revoke or audit a particular workload or agent.

Question 240

For this case—A background service and a human operator appear under the same sign-in identity, preventing investigators from isolating who performed a privileged task.—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: Use Microsoft Entra entitlement management access packages to define approved bundles of applications, groups or sites with requester and expiration policies. Validation: Have a synthetic contractor request a test package, approve it, inspect granted group access and confirm expiration removes access according to policy.
  3. 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.
  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

D:

The situation is that a background service and a human operator appear under the same sign-in identity, preventing investigators from isolating who performed a privileged task. 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. The action and test belong together because an automated service principal or agent identity has a different accountability and token lifecycle from an interactive workforce member or external guest.

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 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. To confirm, examine a sample employee sign-in, workload service principal access and registered agent identity, verifying each uses the intended tenant permissions.

B:

The proposed pair focuses on “provision time-bound entitlement management access packages” instead. The appropriate action is to 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. To confirm, examine a sample employee sign-in, workload service principal access and registered agent identity, verifying each uses the intended tenant permissions.

C:

“identify a Microsoft entra tenant as cloud identity directory” evaluates a different intervention. The appropriate action is to 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. To confirm, examine a sample employee sign-in, workload service principal access and registered agent identity, verifying each uses the intended tenant permissions.

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