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 16

Question 150

For this case—A business analyst receives a privileged directory role so they can view a reporting dashboard and later accidentally changes tenant authentication controls.—which implementation and acceptance check are correctly paired?

  1. Action: Use a supported federated sign-in relationship when an application trusts an external identity provider's signed assertion rather than directly storing every user's password. Validation: Complete a controlled sign-in using a trusted federated identity and verify an assertion from an untrusted issuer or wrong audience is refused.
  2. Action: Grant a verified identity only the directory and resource actions required for its job, and separate tenant administration from ordinary data viewing. Validation: Sign in as a test helpdesk operator and show successful password assistance but rejection of a separate tenant-wide security policy modification.
  3. Action: Assign a supported workload or service identity to an unattended automation and a human account to interactive employees, limiting permissions according to function. Validation: Review test sign-in logs to distinguish service-principal token use from an employee sign-in and confirm permissions match each identity's role.
  4. Action: Authenticate a requesting principal first and then separately authorize only the actions it is allowed to perform on the target resource. Validation: Sign in a test employee successfully and confirm they can open their department site but are denied an unrelated payroll administration operation.

Explanation

Correct Answer

B:

The situation is that a business analyst receives a privileged directory role so they can view a reporting dashboard and later accidentally changes tenant authentication controls. Grant a verified identity only the directory and resource actions required for its job, and separate tenant administration from ordinary data viewing. Validation: Sign in as a test helpdesk operator and show successful password assistance but rejection of a separate tenant-wide security policy modification. The action and test belong together because a single globally privileged account greatly increases attack impact and auditing difficulty compared with scoped roles limited to a particular service.

Incorrect Answers

A:

“understand federation trust” evaluates a different intervention. The appropriate action is to grant a verified identity only the directory and resource actions required for its job, and separate tenant administration from ordinary data viewing. To confirm, sign in as a test helpdesk operator and show successful password assistance but rejection of a separate tenant-wide security policy modification.

C:

That action-and-evidence pair concerns “distinguish human and application identities”, not this decision. The appropriate action is to grant a verified identity only the directory and resource actions required for its job, and separate tenant administration from ordinary data viewing. To confirm, sign in as a test helpdesk operator and show successful password assistance but rejection of a separate tenant-wide security policy modification.

D:

The proposed pair focuses on “distinguish proof of identity from resource permission” instead. The appropriate action is to grant a verified identity only the directory and resource actions required for its job, and separate tenant administration from ordinary data viewing. To confirm, sign in as a test helpdesk operator and show successful password assistance but rejection of a separate tenant-wide security policy modification.

Question 151

A new company activates Microsoft 365 and wants to identify which directory represents its employees and application identities in the cloud. Which implementation or design choice most directly mitigates the stated issue?

  1. Use Entra workload identity federation to validate trusted external OIDC assertions from a supported build service before issuing an app access token.
  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. 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

C:

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. 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. To verify, 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.

Incorrect Answers

A:

This alternative focuses on “prefer workload identity federation over stored CI secrets” instead of the required outcome. 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.

B:

That choice concerns “distinguish workforce workload and agent identities at a conceptual level”, not the immediate requirement. 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.

D:

“use an app registration and service principal for application access” is related to another task, not the failure shown here. 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.

Question 152

A new company activates Microsoft 365 and wants to identify which directory represents its employees and application identities in the cloud. Which technical explanation most directly supports the right approach?

  1. B2B collaboration represents external identities in a resource tenant while their home organization may remain responsible for primary authentication.
  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. An app registration describes application identity while a service principal represents its concrete presence and authorization in a tenant.
  4. 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.

Explanation

Correct Answer

D:

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. This supports the decision to 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.

Incorrect Answers

A:

“separate member and guest identities in collaboration” explains a different mechanism. Here, 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.

B:

That statement concerns “synchronize hybrid identities with explicit scope and health checks” rather than the cause in this case. Here, 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.

C:

The principle behind “use an app registration and service principal for application access” is not the one being tested. Here, 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.

Question 153

For this situation—A new company activates Microsoft 365 and wants to identify which directory represents its employees and application identities in the cloud.—which check provides the strongest verification?

  1. 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.
  2. Verify a sample guest appears with the expected external identity type, accesses only one approved Teams workspace and cannot manage directory roles.
  3. 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. 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

A:

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. It is the relevant test because 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.

Incorrect Answers

B:

This evidence addresses “separate member and guest identities in collaboration” instead of confirming the repair. To check this result, 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.

C:

“synchronize hybrid identities with explicit scope and health checks” would verify a different part of the system. To check this result, 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.

D:

That test concerns “use system-assigned managed identities for a single Azure resource”, not the requested outcome. To check this result, 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.

Question 154

A new company activates Microsoft 365 and wants to identify which directory represents its employees and application identities in the cloud. If the team does the following—"Assume every Entra tenant can directly process classic LDAP binds and Windows Group Policy for old computers without any hybrid component."—what could go wrong?

  1. Workloads may lose access or administrators may broaden permissions unnecessarily when distinct managed identity lifecycles are misunderstood.
  2. A migration may break old device policies or application authentication because the architecture confused a cloud tenant with an AD DS forest.
  3. A failure of an on-prem authentication endpoint can cause unexpected outage when the organization selected a dependency-heavy sign-in architecture.
  4. Former employee access may persist in cloud apps because directory changes did not propagate through an unhealthy synchronization service.

Explanation

Correct Answer

B:

A migration may break old device policies or application authentication because the architecture confused a cloud tenant with an AD DS forest. The shortcut is unsafe because 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.

Incorrect Answers

A:

The alternative risk relates to “Workloads may lose access or administrators may broaden permissions unnecessarily when distinct managed identity lifecycles are…”, not the stated mistake. Here, a migration may break old device policies or application authentication because the architecture confused a cloud tenant with an AD DS forest.

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, a migration may break old device policies or application authentication because the architecture confused a cloud tenant with an AD DS forest.

D:

“Former employee access may persist in cloud apps because directory changes did not propagate through an…” does not describe the result of this shortcut. Here, a migration may break old device policies or application authentication because the architecture confused a cloud tenant with an AD DS forest.

Question 155

A new company activates Microsoft 365 and wants to identify which directory represents its employees and application identities in the cloud. Which action and validation evidence belong together?

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

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. The action and test belong together because 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.

Incorrect Answers

A:

The linked action and check for “distinguish workforce workload and agent identities at a conceptual level” would not resolve this case. The appropriate action is to 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. To confirm, 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.

B:

That action-and-evidence pair concerns “use an app registration and service principal for application access”, not this decision. The appropriate action is to 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. To confirm, 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.

D:

“distinguish cloud-only and hybrid identity sign-in choices” evaluates a different intervention. The appropriate action is to 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. To confirm, 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.

Question 156

During a Microsoft security fundamentals review, A systems engineer attempts to point an ancient LDAP-only application at a basic Entra tenant and expects domain-controller behavior. What is the most appropriate next decision?

  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. Enable a system-assigned managed identity for a supported Azure-hosted workload and grant its service principal only required access to a target service.
  4. 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.

Explanation

Correct Answer

D:

The situation is that a systems engineer attempts to point an ancient LDAP-only application at a basic Entra tenant and expects domain-controller behavior. 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. 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. To verify, 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.

Incorrect Answers

A:

That choice concerns “use an app registration and service principal for application access”, not the immediate requirement. 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.

B:

The proposed action addresses “distinguish cloud-only and hybrid identity sign-in choices” rather than the problem described. 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.

C:

“use system-assigned managed identities for a single Azure resource” is related to another task, not the failure shown here. 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.

Question 157

A systems engineer attempts to point an ancient LDAP-only application at a basic Entra tenant and expects domain-controller behavior. Why does the recommended approach address this particular concern?

  1. 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.
  2. Federated workload credentials exchange verified short-lived tokens based on issuer, audience and subject, avoiding stored long-lived cloud secrets in CI.
  3. A user-assigned managed identity exists independently of any one associated resource, unlike system-assigned identities deleted with their host resources.
  4. A system-assigned managed identity is tied to its Azure resource lifecycle and avoids hard-coded long-lived application secrets for supported token requests.

Explanation

Correct Answer

A:

The situation is that a systems engineer attempts to point an ancient LDAP-only application at a basic Entra tenant and expects domain-controller behavior. 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. This supports the decision to 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.

Incorrect Answers

B:

The principle behind “prefer workload identity federation over stored CI secrets” is not the one being tested. Here, 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.

C:

“reuse user-assigned managed identity deliberately” describes another technical distinction. Here, 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.

D:

“use system-assigned managed identities for a single Azure resource” explains a different mechanism. Here, 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.

Question 158

A systems engineer attempts to point an ancient LDAP-only application at a basic Entra tenant and expects domain-controller behavior. Which evidence best validates the proposed outcome?

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

B:

The situation is that a systems engineer attempts to point an ancient LDAP-only application at a basic Entra tenant and expects domain-controller behavior. 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. It is the relevant test because 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.

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

C:

That test concerns “distinguish cloud-only and hybrid identity sign-in choices”, not the requested outcome. To check this result, 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.

D:

The proposed check is relevant to “synchronize hybrid identities with explicit scope and health checks”, but not sufficient here. To check this result, 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.

Question 159

Consider this situation: A systems engineer attempts to point an ancient LDAP-only application at a basic Entra tenant and expects domain-controller behavior. A team member suggests: "Assume every Entra tenant can directly process classic LDAP binds and Windows Group Policy for old computers without any hybrid component." 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. The app can inherit excessive tenant powers and may stop when the human password or MFA policy changes unexpectedly.
  3. A migration may break old device policies or application authentication because the architecture confused a cloud tenant with an AD DS forest.
  4. Workloads may lose access or administrators may broaden permissions unnecessarily when distinct managed identity lifecycles are misunderstood.

Explanation

Correct Answer

C:

The situation is that a systems engineer attempts to point an ancient LDAP-only application at a basic Entra tenant and expects domain-controller behavior. A migration may break old device policies or application authentication because the architecture confused a cloud tenant with an AD DS forest. The shortcut is unsafe because 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.

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, a migration may break old device policies or application authentication because the architecture confused a cloud tenant with an AD DS forest.

B:

That consequence concerns “The app can inherit excessive tenant powers and may stop when the human password or MFA…”, which is a different failure. Here, a migration may break old device policies or application authentication because the architecture confused a cloud tenant with an AD DS forest.

D:

The situation is that a systems engineer attempts to point an ancient LDAP-only application at a basic Entra tenant and expects domain-controller behavior. The alternative risk relates to “Workloads may lose access or administrators may broaden permissions unnecessarily when distinct managed identity lifecycles are…”, not the stated mistake. Here, a migration may break old device policies or application authentication because the architecture confused a cloud tenant with an AD DS forest.

Question 160

A security and compliance reviewer considers: A systems engineer attempts to point an ancient LDAP-only application at a basic Entra tenant and expects domain-controller behavior. Which response and evidence should be linked?

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

D:

The situation is that a systems engineer attempts to point an ancient LDAP-only application at a basic Entra tenant and expects domain-controller behavior. 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. The action and test belong together because 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.

Incorrect Answers

A:

That action-and-evidence pair concerns “prefer workload identity federation over stored CI secrets”, not this decision. The appropriate action is to 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. To confirm, 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.

B:

The proposed pair focuses on “use an app registration and service principal for application access” instead. The appropriate action is to 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. To confirm, 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.

C:

“reuse user-assigned managed identity deliberately” evaluates a different intervention. The appropriate action is to 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. To confirm, 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.

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