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 17

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.

Question 161

A manufacturer invites a supplier into a confidential Teams channel and needs an identity that can be removed when the project closes. Which action best addresses this requirement?

  1. Invite external collaborators using supported Microsoft Entra B2B guest collaboration and give them scoped resource access rather than treating partners as tenant administrators.
  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

A:

Invite external collaborators using supported Microsoft Entra B2B guest collaboration and give them scoped resource access rather than treating partners as tenant administrators. B2B collaboration represents external identities in a resource tenant while their home organization may remain responsible for primary authentication. To verify, verify a sample guest appears with the expected external identity type, accesses only one approved Teams workspace and cannot manage directory roles.

Incorrect Answers

B:

“distinguish cloud-only and hybrid identity sign-in choices” is related to another task, not the failure shown here. B2B collaboration represents external identities in a resource tenant while their home organization may remain responsible for primary authentication.

C:

This alternative focuses on “use system-assigned managed identities for a single Azure resource” instead of the required outcome. B2B collaboration represents external identities in a resource tenant while their home organization may remain responsible for primary authentication.

D:

That choice concerns “identify a Microsoft entra tenant as cloud identity directory”, not the immediate requirement. B2B collaboration represents external identities in a resource tenant while their home organization may remain responsible for primary authentication.

Question 162

A cloud security learner considers: A manufacturer invites a supplier into a confidential Teams channel and needs an identity that can be removed when the project closes. Which underlying principle applies?

  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. B2B collaboration represents external identities in a resource tenant while their home organization may remain responsible for primary authentication.
  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. Different hybrid sign-in patterns change where credentials are validated and which on-prem services remain necessary when connectivity fails.

Explanation

Correct Answer

B:

B2B collaboration represents external identities in a resource tenant while their home organization may remain responsible for primary authentication. This supports the decision to invite external collaborators using supported Microsoft Entra B2B guest collaboration and give them scoped resource access rather than treating partners as tenant administrators.

Incorrect Answers

A:

The principle behind “use system-assigned managed identities for a single Azure resource” is not the one being tested. Here, b2B collaboration represents external identities in a resource tenant while their home organization may remain responsible for primary authentication.

C:

“identify a Microsoft entra tenant as cloud identity directory” explains a different mechanism. Here, b2B collaboration represents external identities in a resource tenant while their home organization may remain responsible for primary authentication.

D:

That statement concerns “distinguish cloud-only and hybrid identity sign-in choices” rather than the cause in this case. Here, b2B collaboration represents external identities in a resource tenant while their home organization may remain responsible for primary authentication.

Question 163

A manufacturer invites a supplier into a confidential Teams channel and needs an identity that can be removed when the project closes. What should the team examine before accepting the result?

  1. Attach one test user-assigned identity to two authorized services, prove restricted token access and remove one host without deleting the identity itself.
  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. Verify a sample guest appears with the expected external identity type, accesses only one approved Teams workspace and cannot manage directory roles.
  4. Check application object and enterprise application representation in a sandbox tenant and verify a token has only approved resource permissions.

Explanation

Correct Answer

C:

Verify a sample guest appears with the expected external identity type, accesses only one approved Teams workspace and cannot manage directory roles. It is the relevant test because b2B collaboration represents external identities in a resource tenant while their home organization may remain responsible for primary authentication.

Incorrect Answers

A:

“reuse user-assigned managed identity deliberately” would verify a different part of the system. To check this result, verify a sample guest appears with the expected external identity type, accesses only one approved Teams workspace and cannot manage directory roles.

B:

That test concerns “synchronize hybrid identities with explicit scope and health checks”, not the requested outcome. To check this result, verify a sample guest appears with the expected external identity type, accesses only one approved Teams workspace and cannot manage directory roles.

D:

This evidence addresses “use an app registration and service principal for application access” instead of confirming the repair. To check this result, verify a sample guest appears with the expected external identity type, accesses only one approved Teams workspace and cannot manage directory roles.

Question 164

A manufacturer invites a supplier into a confidential Teams channel and needs an identity that can be removed when the project closes. The proposed shortcut is: "Create permanent internal employee accounts with global privileges for every outside consultant to simplify a short partner project." Which failure is most likely?

  1. Anyone who obtains the static secret may impersonate the deployment application beyond the intended build run or repository boundary.
  2. A failure of an on-prem authentication endpoint can cause unexpected outage when the organization selected a dependency-heavy sign-in architecture.
  3. Workloads may lose access or administrators may broaden permissions unnecessarily when distinct managed identity lifecycles are misunderstood.
  4. Partner credentials may outlive the contract and expose unrelated company resources because lifecycle and privileges were never scoped.

Explanation

Correct Answer

D:

Partner credentials may outlive the contract and expose unrelated company resources because lifecycle and privileges were never scoped. The shortcut is unsafe because b2B collaboration represents external identities in a resource tenant while their home organization may remain responsible for primary authentication.

Incorrect Answers

A:

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, partner credentials may outlive the contract and expose unrelated company resources because lifecycle and privileges were never scoped.

B:

“A failure of an on-prem authentication endpoint can cause unexpected outage when the organization selected a…” does not describe the result of this shortcut. Here, partner credentials may outlive the contract and expose unrelated company resources because lifecycle and privileges were never scoped.

C:

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, partner credentials may outlive the contract and expose unrelated company resources because lifecycle and privileges were never scoped.

Question 165

For this case—A manufacturer invites a supplier into a confidential Teams channel and needs an identity that can be removed when the project closes.—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: 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.
  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: 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:

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. The action and test belong together because b2B collaboration represents external identities in a resource tenant while their home organization may remain responsible for primary authentication.

Incorrect Answers

B:

“reuse user-assigned managed identity deliberately” evaluates a different intervention. The appropriate action is to invite external collaborators using supported Microsoft Entra B2B guest collaboration and give them scoped resource access rather than treating partners as tenant administrators. To confirm, verify a sample guest appears with the expected external identity type, accesses only one approved Teams workspace and cannot manage directory roles.

C:

The linked action and check for “use system-assigned managed identities for a single Azure resource” would not resolve this case. The appropriate action is to invite external collaborators using supported Microsoft Entra B2B guest collaboration and give them scoped resource access rather than treating partners as tenant administrators. To confirm, verify a sample guest appears with the expected external identity type, accesses only one approved Teams workspace and cannot manage directory roles.

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 invite external collaborators using supported Microsoft Entra B2B guest collaboration and give them scoped resource access rather than treating partners as tenant administrators. To confirm, verify a sample guest appears with the expected external identity type, accesses only one approved Teams workspace and cannot manage directory roles.

Question 166

A university shares a project site with visiting researchers but accidentally gives outside participants tenant-wide administrative capabilities. Which implementation or design choice most directly mitigates the stated issue?

  1. Enable a system-assigned managed identity for a supported Azure-hosted workload and grant its service principal only required access to a target service.
  2. Invite external collaborators using supported Microsoft Entra B2B guest collaboration and give them scoped resource access rather than treating partners as tenant administrators.
  3. Register an application in Entra and grant its service principal explicitly approved permissions with a supported certificate or federated credential when appropriate.
  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

B:

The situation is that a university shares a project site with visiting researchers but accidentally gives outside participants tenant-wide administrative capabilities. Invite external collaborators using supported Microsoft Entra B2B guest collaboration and give them scoped resource access rather than treating partners as tenant administrators. B2B collaboration represents external identities in a resource tenant while their home organization may remain responsible for primary authentication. To verify, verify a sample guest appears with the expected external identity type, accesses only one approved Teams workspace and cannot manage directory roles.

Incorrect Answers

A:

“use system-assigned managed identities for a single Azure resource” is related to another task, not the failure shown here. B2B collaboration represents external identities in a resource tenant while their home organization may remain responsible for primary authentication.

C:

That choice concerns “use an app registration and service principal for application access”, not the immediate requirement. B2B collaboration represents external identities in a resource tenant while their home organization may remain responsible for primary authentication.

D:

The proposed action addresses “distinguish cloud-only and hybrid identity sign-in choices” rather than the problem described. B2B collaboration represents external identities in a resource tenant while their home organization may remain responsible for primary authentication.

Question 167

A university shares a project site with visiting researchers but accidentally gives outside participants tenant-wide administrative capabilities. 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. An app registration describes application identity while a service principal represents its concrete presence and authorization in a tenant.
  3. B2B collaboration represents external identities in a resource tenant while their home organization may remain responsible for primary authentication.
  4. A user-assigned managed identity exists independently of any one associated resource, unlike system-assigned identities deleted with their host resources.

Explanation

Correct Answer

C:

The situation is that a university shares a project site with visiting researchers but accidentally gives outside participants tenant-wide administrative capabilities. B2B collaboration represents external identities in a resource tenant while their home organization may remain responsible for primary authentication. This supports the decision to invite external collaborators using supported Microsoft Entra B2B guest collaboration and give them scoped resource access rather than treating partners as tenant administrators.

Incorrect Answers

A:

“use system-assigned managed identities for a single Azure resource” describes another technical distinction. Here, b2B collaboration represents external identities in a resource tenant while their home organization may remain responsible for primary authentication.

B:

“use an app registration and service principal for application access” explains a different mechanism. Here, b2B collaboration represents external identities in a resource tenant while their home organization may remain responsible for primary authentication.

D:

The principle behind “reuse user-assigned managed identity deliberately” is not the one being tested. Here, b2B collaboration represents external identities in a resource tenant while their home organization may remain responsible for primary authentication.

Question 168

For this situation—A university shares a project site with visiting researchers but accidentally gives outside participants tenant-wide administrative capabilities.—which check provides the strongest verification?

  1. Check application object and enterprise application representation in a sandbox tenant and verify a token has only approved resource permissions.
  2. Attach one test user-assigned identity to two authorized services, prove restricted token access and remove one host without deleting the identity itself.
  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. Verify a sample guest appears with the expected external identity type, accesses only one approved Teams workspace and cannot manage directory roles.

Explanation

Correct Answer

D:

The situation is that a university shares a project site with visiting researchers but accidentally gives outside participants tenant-wide administrative capabilities. Verify a sample guest appears with the expected external identity type, accesses only one approved Teams workspace and cannot manage directory roles. It is the relevant test because b2B collaboration represents external identities in a resource tenant while their home organization may remain responsible for primary authentication.

Incorrect Answers

A:

That test concerns “use an app registration and service principal for application access”, not the requested outcome. To check this result, verify a sample guest appears with the expected external identity type, accesses only one approved Teams workspace and cannot manage directory roles.

B:

The proposed check is relevant to “reuse user-assigned managed identity deliberately”, but not sufficient here. To check this result, verify a sample guest appears with the expected external identity type, accesses only one approved Teams workspace and cannot manage directory roles.

C:

This evidence addresses “identify a Microsoft entra tenant as cloud identity directory” instead of confirming the repair. To check this result, verify a sample guest appears with the expected external identity type, accesses only one approved Teams workspace and cannot manage directory roles.

Question 169

A university shares a project site with visiting researchers but accidentally gives outside participants tenant-wide administrative capabilities. If the team does the following—"Create permanent internal employee accounts with global privileges for every outside consultant to simplify a short partner project."—what could go wrong?

  1. Partner credentials may outlive the contract and expose unrelated company resources because lifecycle and privileges were never scoped.
  2. Workloads may lose access or administrators may broaden permissions unnecessarily when distinct managed identity lifecycles are misunderstood.
  3. Former employee access may persist in cloud apps because directory changes did not propagate through an unhealthy synchronization service.
  4. Leaked long-lived credentials may grant unintended privileges while resource deletion fails to remove the separately embedded secret.

Explanation

Correct Answer

A:

The situation is that a university shares a project site with visiting researchers but accidentally gives outside participants tenant-wide administrative capabilities. Partner credentials may outlive the contract and expose unrelated company resources because lifecycle and privileges were never scoped. The shortcut is unsafe because b2B collaboration represents external identities in a resource tenant while their home organization may remain responsible for primary authentication.

Incorrect Answers

B:

The situation is that a university shares a project site with visiting researchers but accidentally gives outside participants tenant-wide administrative capabilities. 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, partner credentials may outlive the contract and expose unrelated company resources because lifecycle and privileges were never scoped.

C:

“Former employee access may persist in cloud apps because directory changes did not propagate through an…” can arise elsewhere, but it is not the most direct risk here. Here, partner credentials may outlive the contract and expose unrelated company resources because lifecycle and privileges were never scoped.

D:

That consequence concerns “Leaked long-lived credentials may grant unintended privileges while resource deletion fails to remove the separately embedded…”, which is a different failure. Here, partner credentials may outlive the contract and expose unrelated company resources because lifecycle and privileges were never scoped.

Question 170

A university shares a project site with visiting researchers but accidentally gives outside participants tenant-wide administrative capabilities. Which action and validation evidence belong together?

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

B:

The situation is that a university shares a project site with visiting researchers but accidentally gives outside participants tenant-wide administrative capabilities. 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. The action and test belong together because b2B collaboration represents external identities in a resource tenant while their home organization may remain responsible for primary authentication.

Incorrect Answers

A:

“identify a Microsoft entra tenant as cloud identity directory” evaluates a different intervention. The appropriate action is to invite external collaborators using supported Microsoft Entra B2B guest collaboration and give them scoped resource access rather than treating partners as tenant administrators. To confirm, verify a sample guest appears with the expected external identity type, accesses only one approved Teams workspace and cannot manage directory roles.

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 invite external collaborators using supported Microsoft Entra B2B guest collaboration and give them scoped resource access rather than treating partners as tenant administrators. To confirm, verify a sample guest appears with the expected external identity type, accesses only one approved Teams workspace and cannot manage directory roles.

D:

The proposed pair focuses on “synchronize hybrid identities with explicit scope and health checks” instead. The appropriate action is to invite external collaborators using supported Microsoft Entra B2B guest collaboration and give them scoped resource access rather than treating partners as tenant administrators. To confirm, verify a sample guest appears with the expected external identity type, accesses only one approved Teams workspace and cannot manage directory roles.

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