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 18

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.

Question 171

During a tenant protection and compliance review, An Azure Function needs to read one protected configuration secret without maintaining a developer-owned password in source control. What is the most appropriate next decision?

  1. Use Entra workload identity federation to validate trusted external OIDC assertions from a supported build service before issuing an app access token.
  2. Register an application in Entra and grant its service principal explicitly approved permissions with a supported certificate or federated credential when appropriate.
  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. 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:

Enable a system-assigned managed identity for a supported Azure-hosted workload and grant its service principal only required access to a target service. A system-assigned managed identity is tied to its Azure resource lifecycle and avoids hard-coded long-lived application secrets for supported token requests. To verify, 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.

Incorrect Answers

A:

This alternative focuses on “prefer workload identity federation over stored CI secrets” instead of the required outcome. A system-assigned managed identity is tied to its Azure resource lifecycle and avoids hard-coded long-lived application secrets for supported token requests.

B:

That choice concerns “use an app registration and service principal for application access”, not the immediate requirement. A system-assigned managed identity is tied to its Azure resource lifecycle and avoids hard-coded long-lived application secrets for supported token requests.

D:

“distinguish cloud-only and hybrid identity sign-in choices” is related to another task, not the failure shown here. A system-assigned managed identity is tied to its Azure resource lifecycle and avoids hard-coded long-lived application secrets for supported token requests.

Question 172

An Azure Function needs to read one protected configuration secret without maintaining a developer-owned password in source control. 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. A user-assigned managed identity exists independently of any one associated resource, unlike system-assigned identities deleted with their host resources.
  3. Different hybrid sign-in patterns change where credentials are validated and which on-prem services remain necessary when connectivity fails.
  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

D:

A system-assigned managed identity is tied to its Azure resource lifecycle and avoids hard-coded long-lived application secrets for supported token requests. This supports the decision to enable a system-assigned managed identity for a supported Azure-hosted workload and grant its service principal only required access to a target service.

Incorrect Answers

A:

“identify a Microsoft entra tenant as cloud identity directory” explains a different mechanism. Here, a system-assigned managed identity is tied to its Azure resource lifecycle and avoids hard-coded long-lived application secrets for supported token requests.

B:

That statement concerns “reuse user-assigned managed identity deliberately” rather than the cause in this case. Here, a system-assigned managed identity is tied to its Azure resource lifecycle and avoids hard-coded long-lived application secrets for supported token requests.

C:

The principle behind “distinguish cloud-only and hybrid identity sign-in choices” is not the one being tested. Here, a system-assigned managed identity is tied to its Azure resource lifecycle and avoids hard-coded long-lived application secrets for supported token requests.

Question 173

An Azure Function needs to read one protected configuration secret without maintaining a developer-owned password in source control. 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. 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. Examine a sample employee sign-in, workload service principal access and registered agent identity, verifying each uses the intended tenant permissions.
  4. Check application object and enterprise application representation in a sandbox tenant and verify a token has only approved resource permissions.

Explanation

Correct Answer

A:

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. It is the relevant test because a system-assigned managed identity is tied to its Azure resource lifecycle and avoids hard-coded long-lived application secrets for supported token requests.

Incorrect Answers

B:

This evidence addresses “synchronize hybrid identities with explicit scope and health checks” instead of confirming the repair. To check this result, 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.

C:

“distinguish workforce workload and agent identities at a conceptual level” would verify a different part of the system. To check this result, 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.

D:

That test concerns “use an app registration and service principal for application access”, not the requested outcome. To check this result, 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.

Question 174

Consider this situation: An Azure Function needs to read one protected configuration secret without maintaining a developer-owned password in source control. A team member suggests: "Embed an Azure administrator client secret in application code instead of using the platform-managed resource identity." What is the main risk?

  1. A migration may break old device policies or application authentication because the architecture confused a cloud tenant with an AD DS forest.
  2. Leaked long-lived credentials may grant unintended privileges while resource deletion fails to remove the separately embedded secret.
  3. Former employee access may persist in cloud apps because directory changes did not propagate through an unhealthy synchronization service.
  4. Anyone who obtains the static secret may impersonate the deployment application beyond the intended build run or repository boundary.

Explanation

Correct Answer

B:

Leaked long-lived credentials may grant unintended privileges while resource deletion fails to remove the separately embedded secret. The shortcut is unsafe because a system-assigned managed identity is tied to its Azure resource lifecycle and avoids hard-coded long-lived application secrets for supported token requests.

Incorrect Answers

A:

The alternative risk relates to “A migration may break old device policies or application authentication because the architecture confused a cloud…”, not the stated mistake. Here, leaked long-lived credentials may grant unintended privileges while resource deletion fails to remove the separately embedded secret.

C:

That consequence concerns “Former employee access may persist in cloud apps because directory changes did not propagate through an…”, which is a different failure. Here, leaked long-lived credentials may grant unintended privileges while resource deletion fails to remove the separately embedded secret.

D:

“Anyone who obtains the static secret may impersonate the deployment application beyond the intended build run…” does not describe the result of this shortcut. Here, leaked long-lived credentials may grant unintended privileges while resource deletion fails to remove the separately embedded secret.

Question 175

A security and compliance reviewer considers: An Azure Function needs to read one protected configuration secret without maintaining a developer-owned password in source control. Which response and evidence should be linked?

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

Explanation

Correct Answer

C:

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. The action and test belong together because a system-assigned managed identity is tied to its Azure resource lifecycle and avoids hard-coded long-lived application secrets for supported token requests.

Incorrect Answers

A:

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

B:

That action-and-evidence pair concerns “separate member and guest identities in collaboration”, not this decision. The appropriate action is to enable a system-assigned managed identity for a supported Azure-hosted workload and grant its service principal only required access to a target service. To confirm, 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.

D:

“prefer workload identity federation over stored CI secrets” evaluates a different intervention. The appropriate action is to enable a system-assigned managed identity for a supported Azure-hosted workload and grant its service principal only required access to a target service. To confirm, 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.

Question 176

A managed application hosted on an Azure VM uses a service credential copied into five scripts instead of using its available system identity. Which action best addresses this requirement?

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

Explanation

Correct Answer

D:

The situation is that a managed application hosted on an Azure VM uses a service credential copied into five scripts instead of using its available system identity. Enable a system-assigned managed identity for a supported Azure-hosted workload and grant its service principal only required access to a target service. A system-assigned managed identity is tied to its Azure resource lifecycle and avoids hard-coded long-lived application secrets for supported token requests. To verify, 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.

Incorrect Answers

A:

The situation is that a managed application hosted on an Azure VM uses a service credential copied into five scripts instead of using its available system identity. That choice concerns “use an app registration and service principal for application access”, not the immediate requirement. A system-assigned managed identity is tied to its Azure resource lifecycle and avoids hard-coded long-lived application secrets for supported token requests.

B:

The proposed action addresses “identify a Microsoft entra tenant as cloud identity directory” rather than the problem described. A system-assigned managed identity is tied to its Azure resource lifecycle and avoids hard-coded long-lived application secrets for supported token requests.

C:

“reuse user-assigned managed identity deliberately” is related to another task, not the failure shown here. A system-assigned managed identity is tied to its Azure resource lifecycle and avoids hard-coded long-lived application secrets for supported token requests.

Question 177

A cloud security learner considers: A managed application hosted on an Azure VM uses a service credential copied into five scripts instead of using its available system identity. 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. Different hybrid sign-in patterns change where credentials are validated and which on-prem services remain necessary when connectivity fails.
  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

A:

The situation is that a managed application hosted on an Azure VM uses a service credential copied into five scripts instead of using its available system identity. A system-assigned managed identity is tied to its Azure resource lifecycle and avoids hard-coded long-lived application secrets for supported token requests. This supports the decision to enable a system-assigned managed identity for a supported Azure-hosted workload and grant its service principal only required access to a target service.

Incorrect Answers

B:

The situation is that a managed application hosted on an Azure VM uses a service credential copied into five scripts instead of using its available system identity. The principle behind “distinguish cloud-only and hybrid identity sign-in choices” is not the one being tested. Here, a system-assigned managed identity is tied to its Azure resource lifecycle and avoids hard-coded long-lived application secrets for supported token requests.

C:

“use an app registration and service principal for application access” describes another technical distinction. Here, a system-assigned managed identity is tied to its Azure resource lifecycle and avoids hard-coded long-lived application secrets for supported token requests.

D:

The situation is that a managed application hosted on an Azure VM uses a service credential copied into five scripts instead of using its available system identity. “identify a Microsoft entra tenant as cloud identity directory” explains a different mechanism. Here, a system-assigned managed identity is tied to its Azure resource lifecycle and avoids hard-coded long-lived application secrets for supported token requests.

Question 178

A managed application hosted on an Azure VM uses a service credential copied into five scripts instead of using its available system identity. What should the team examine before accepting the result?

  1. Check application object and enterprise application representation in a sandbox tenant and verify a token has only approved resource permissions.
  2. 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. 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

B:

The situation is that a managed application hosted on an Azure VM uses a service credential copied into five scripts instead of using its available system identity. 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. It is the relevant test because a system-assigned managed identity is tied to its Azure resource lifecycle and avoids hard-coded long-lived application secrets for supported token requests.

Incorrect Answers

A:

This evidence addresses “use an app registration and service principal for application access” instead of confirming the repair. To check this result, 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.

C:

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

D:

The proposed check is relevant to “identify a Microsoft entra tenant as cloud identity directory”, but not sufficient here. To check this result, 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.

Question 179

A managed application hosted on an Azure VM uses a service credential copied into five scripts instead of using its available system identity. The proposed shortcut is: "Embed an Azure administrator client secret in application code instead of using the platform-managed resource identity." Which failure is most likely?

  1. A failure of an on-prem authentication endpoint can cause unexpected outage when the organization selected a dependency-heavy sign-in architecture.
  2. Partner credentials may outlive the contract and expose unrelated company resources because lifecycle and privileges were never scoped.
  3. Leaked long-lived credentials may grant unintended privileges while resource deletion fails to remove the separately embedded secret.
  4. Former employee access may persist in cloud apps because directory changes did not propagate through an unhealthy synchronization service.

Explanation

Correct Answer

C:

The situation is that a managed application hosted on an Azure VM uses a service credential copied into five scripts instead of using its available system identity. Leaked long-lived credentials may grant unintended privileges while resource deletion fails to remove the separately embedded secret. The shortcut is unsafe because a system-assigned managed identity is tied to its Azure resource lifecycle and avoids hard-coded long-lived application secrets for supported token requests.

Incorrect Answers

A:

“A failure of an on-prem authentication endpoint can cause unexpected outage when the organization selected a…” can arise elsewhere, but it is not the most direct risk here. Here, leaked long-lived credentials may grant unintended privileges while resource deletion fails to remove the separately embedded secret.

B:

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, leaked long-lived credentials may grant unintended privileges while resource deletion fails to remove the separately embedded secret.

D:

The alternative risk relates to “Former employee access may persist in cloud apps because directory changes did not propagate through an…”, not the stated mistake. Here, leaked long-lived credentials may grant unintended privileges while resource deletion fails to remove the separately embedded secret.

Question 180

For this case—A managed application hosted on an Azure VM uses a service credential copied into five scripts instead of using its available system identity.—which implementation and acceptance check are correctly paired?

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

D:

The situation is that a managed application hosted on an Azure VM uses a service credential copied into five scripts instead of using its available system identity. 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. The action and test belong together because a system-assigned managed identity is tied to its Azure resource lifecycle and avoids hard-coded long-lived application secrets for supported token requests.

Incorrect Answers

A:

That action-and-evidence pair concerns “distinguish workforce workload and agent identities at a conceptual level”, not this decision. The appropriate action is to enable a system-assigned managed identity for a supported Azure-hosted workload and grant its service principal only required access to a target service. To confirm, 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.

B:

The proposed pair focuses on “identify a Microsoft entra tenant as cloud identity directory” instead. The appropriate action is to enable a system-assigned managed identity for a supported Azure-hosted workload and grant its service principal only required access to a target service. To confirm, 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.

C:

“synchronize hybrid identities with explicit scope and health checks” evaluates a different intervention. The appropriate action is to enable a system-assigned managed identity for a supported Azure-hosted workload and grant its service principal only required access to a target service. To confirm, 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.

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