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 20

Question 190

A security and compliance reviewer considers: A developer removes a VM then expects its former system-assigned identity to be automatically available to another new VM. Which response and evidence should be linked?

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

B:

The situation is that a developer removes a VM then expects its former system-assigned identity to be automatically available to another new VM. 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. The action and test belong together because a user-assigned managed identity exists independently of any one associated resource, unlike system-assigned identities deleted with their host resources.

Incorrect Answers

A:

“use an app registration and service principal for application access” evaluates a different intervention. The appropriate action is to attach a user-assigned managed identity to multiple supported Azure resources when a shared, separately managed identity lifecycle is required. To confirm, attach one test user-assigned identity to two authorized services, prove restricted token access and remove one host without deleting the identity itself.

C:

That action-and-evidence pair concerns “prefer workload identity federation over stored CI secrets”, not this decision. The appropriate action is to attach a user-assigned managed identity to multiple supported Azure resources when a shared, separately managed identity lifecycle is required. To confirm, attach one test user-assigned identity to two authorized services, prove restricted token access and remove one host without deleting the identity itself.

D:

The proposed pair focuses on “distinguish workforce workload and agent identities at a conceptual level” instead. The appropriate action is to attach a user-assigned managed identity to multiple supported Azure resources when a shared, separately managed identity lifecycle is required. To confirm, attach one test user-assigned identity to two authorized services, prove restricted token access and remove one host without deleting the identity itself.

Question 191

A third-party reporting connector needs machine authentication to one Microsoft API and must be granted narrowly approved application permissions. Which action best addresses this requirement?

  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. Use supported Microsoft Entra Connect Sync or Cloud Sync where appropriate to synchronize intended on-prem directory accounts and monitor synchronization scope and health.
  3. Register an application in Entra and grant its service principal explicitly approved permissions with a supported certificate or federated credential when appropriate.
  4. Use Entra workload identity federation to validate trusted external OIDC assertions from a supported build service before issuing an app access token.

Explanation

Correct Answer

C:

Register an application in Entra and grant its service principal explicitly approved permissions with a supported certificate or federated credential when appropriate. An app registration describes application identity while a service principal represents its concrete presence and authorization in a tenant. To verify, check application object and enterprise application representation in a sandbox tenant and verify a token has only approved resource permissions.

Incorrect Answers

A:

This alternative focuses on “identify a Microsoft entra tenant as cloud identity directory” instead of the required outcome. An app registration describes application identity while a service principal represents its concrete presence and authorization in a tenant.

B:

That choice concerns “synchronize hybrid identities with explicit scope and health checks”, not the immediate requirement. An app registration describes application identity while a service principal represents its concrete presence and authorization in a tenant.

D:

“prefer workload identity federation over stored CI secrets” is related to another task, not the failure shown here. An app registration describes application identity while a service principal represents its concrete presence and authorization in a tenant.

Question 192

A cloud security learner considers: A third-party reporting connector needs machine authentication to one Microsoft API and must be granted narrowly approved application permissions. Which underlying principle applies?

  1. FIDO2 public-key authentication binds cryptographic proof to the legitimate relying party origin, reducing phishing and password replay exposure.
  2. An automated service principal or agent identity has a different accountability and token lifecycle from an interactive workforce member or external guest.
  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. An app registration describes application identity while a service principal represents its concrete presence and authorization in a tenant.

Explanation

Correct Answer

D:

An app registration describes application identity while a service principal represents its concrete presence and authorization in a tenant. This supports the decision to register an application in Entra and grant its service principal explicitly approved permissions with a supported certificate or federated credential when appropriate.

Incorrect Answers

A:

“choose phishing-resistant authentication methods where required” explains a different mechanism. Here, an app registration describes application identity while a service principal represents its concrete presence and authorization in a tenant.

B:

That statement concerns “distinguish workforce workload and agent identities at a conceptual level” rather than the cause in this case. Here, an app registration describes application identity while a service principal represents its concrete presence and authorization in a tenant.

C:

The principle behind “identify a Microsoft entra tenant as cloud identity directory” is not the one being tested. Here, an app registration describes application identity while a service principal represents its concrete presence and authorization in a tenant.

Question 193

A third-party reporting connector needs machine authentication to one Microsoft API and must be granted narrowly approved application permissions. 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. Examine a sample employee sign-in, workload service principal access and registered agent identity, verifying each uses the intended tenant permissions.
  3. Verify a sample guest appears with the expected external identity type, accesses only one approved Teams workspace and cannot manage directory roles.
  4. 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

A:

Check application object and enterprise application representation in a sandbox tenant and verify a token has only approved resource permissions. It is the relevant test because an app registration describes application identity while a service principal represents its concrete presence and authorization in a tenant.

Incorrect Answers

B:

This evidence addresses “distinguish workforce workload and agent identities at a conceptual level” instead of confirming the repair. To check this result, check application object and enterprise application representation in a sandbox tenant and verify a token has only approved resource permissions.

C:

“separate member and guest identities in collaboration” would verify a different part of the system. To check this result, check application object and enterprise application representation in a sandbox tenant and verify a token has only approved resource permissions.

D:

That test concerns “prefer workload identity federation over stored CI secrets”, not the requested outcome. To check this result, check application object and enterprise application representation in a sandbox tenant and verify a token has only approved resource permissions.

Question 194

A third-party reporting connector needs machine authentication to one Microsoft API and must be granted narrowly approved application permissions. The proposed shortcut is: "Give an unattended integration a human Global Administrator account because it avoids learning how applications authenticate." Which failure is most likely?

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

B:

The app can inherit excessive tenant powers and may stop when the human password or MFA policy changes unexpectedly. The shortcut is unsafe because an app registration describes application identity while a service principal represents its concrete presence and authorization in a tenant.

Incorrect Answers

A:

The alternative risk relates to “Partner credentials may outlive the contract and expose unrelated company resources because lifecycle and privileges were…”, not the stated mistake. Here, the app can inherit excessive tenant powers and may stop when the human password or MFA policy changes unexpectedly.

C:

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

D:

“Workloads may lose access or administrators may broaden permissions unnecessarily when distinct managed identity lifecycles are…” does not describe the result of this shortcut. Here, the app can inherit excessive tenant powers and may stop when the human password or MFA policy changes unexpectedly.

Question 195

For this case—A third-party reporting connector needs machine authentication to one Microsoft API and must be granted narrowly approved application permissions.—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 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: 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.
  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

C:

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. The action and test belong together because an app registration describes application identity while a service principal represents its concrete presence and authorization in a tenant.

Incorrect Answers

A:

The linked action and check for “distinguish cloud-only and hybrid identity sign-in choices” would not resolve this case. The appropriate action is to register an application in Entra and grant its service principal explicitly approved permissions with a supported certificate or federated credential when appropriate. To confirm, check application object and enterprise application representation in a sandbox tenant and verify a token has only approved resource permissions.

B:

That action-and-evidence pair concerns “identify a Microsoft entra tenant as cloud identity directory”, not this decision. The appropriate action is to register an application in Entra and grant its service principal explicitly approved permissions with a supported certificate or federated credential when appropriate. To confirm, check application object and enterprise application representation in a sandbox tenant and verify a token has only approved resource permissions.

D:

“use system-assigned managed identities for a single Azure resource” evaluates a different intervention. The appropriate action is to register an application in Entra and grant its service principal explicitly approved permissions with a supported certificate or federated credential when appropriate. To confirm, check application object and enterprise application representation in a sandbox tenant and verify a token has only approved resource permissions.

Question 196

A business app works in its publisher tenant but the customer cannot locate the corresponding enterprise application permissions locally. Which implementation or design choice most directly mitigates the stated issue?

  1. Attach a user-assigned managed identity to multiple supported Azure resources when a shared, separately managed identity lifecycle is required.
  2. Choose cloud-only authentication or a supported hybrid password hash, pass-through or federation approach based on business and dependency constraints.
  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

D:

The situation is that a business app works in its publisher tenant but the customer cannot locate the corresponding enterprise application permissions locally. Register an application in Entra and grant its service principal explicitly approved permissions with a supported certificate or federated credential when appropriate. An app registration describes application identity while a service principal represents its concrete presence and authorization in a tenant. To verify, check application object and enterprise application representation in a sandbox tenant and verify a token has only approved resource permissions.

Incorrect Answers

A:

That choice concerns “reuse user-assigned managed identity deliberately”, not the immediate requirement. An app registration describes application identity while a service principal represents its concrete presence and authorization in a tenant.

B:

The proposed action addresses “distinguish cloud-only and hybrid identity sign-in choices” rather than the problem described. An app registration describes application identity while a service principal represents its concrete presence and authorization in a tenant.

C:

“identify a Microsoft entra tenant as cloud identity directory” is related to another task, not the failure shown here. An app registration describes application identity while a service principal represents its concrete presence and authorization in a tenant.

Question 197

A business app works in its publisher tenant but the customer cannot locate the corresponding enterprise application permissions locally. Which technical explanation most directly supports the right approach?

  1. An app registration describes application identity while a service principal represents its concrete presence and authorization in a tenant.
  2. 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.
  3. 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.
  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

A:

The situation is that a business app works in its publisher tenant but the customer cannot locate the corresponding enterprise application permissions locally. An app registration describes application identity while a service principal represents its concrete presence and authorization in a tenant. This supports the decision to register an application in Entra and grant its service principal explicitly approved permissions with a supported certificate or federated credential when appropriate.

Incorrect Answers

B:

The situation is that a business app works in its publisher tenant but the customer cannot locate the corresponding enterprise application permissions locally. The principle behind “identify a Microsoft entra tenant as cloud identity directory” is not the one being tested. Here, an app registration describes application identity while a service principal represents its concrete presence and authorization in a tenant.

C:

“synchronize hybrid identities with explicit scope and health checks” describes another technical distinction. Here, an app registration describes application identity while a service principal represents its concrete presence and authorization in a tenant.

D:

“distinguish workforce workload and agent identities at a conceptual level” explains a different mechanism. Here, an app registration describes application identity while a service principal represents its concrete presence and authorization in a tenant.

Question 198

For this situation—A business app works in its publisher tenant but the customer cannot locate the corresponding enterprise application permissions locally.—which check provides the strongest verification?

  1. Verify a sample guest appears with the expected external identity type, accesses only one approved Teams workspace and cannot manage directory roles.
  2. Check application object and enterprise application representation in a sandbox tenant and verify a token has only approved resource 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. 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 a business app works in its publisher tenant but the customer cannot locate the corresponding enterprise application permissions locally. Check application object and enterprise application representation in a sandbox tenant and verify a token has only approved resource permissions. It is the relevant test because an app registration describes application identity while a service principal represents its concrete presence and authorization in a tenant.

Incorrect Answers

A:

This evidence addresses “separate member and guest identities in collaboration” instead of confirming the repair. To check this result, check application object and enterprise application representation in a sandbox tenant and verify a token has only approved resource permissions.

C:

That test concerns “reuse user-assigned managed identity deliberately”, not the requested outcome. To check this result, check application object and enterprise application representation in a sandbox tenant and verify a token has only approved resource permissions.

D:

The proposed check is relevant to “use system-assigned managed identities for a single Azure resource”, but not sufficient here. To check this result, check application object and enterprise application representation in a sandbox tenant and verify a token has only approved resource permissions.

Question 199

A business app works in its publisher tenant but the customer cannot locate the corresponding enterprise application permissions locally. If the team does the following—"Give an unattended integration a human Global Administrator account because it avoids learning how applications authenticate."—what could go wrong?

  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. The app can inherit excessive tenant powers and may stop when the human password or MFA policy changes unexpectedly.
  4. Partner credentials may outlive the contract and expose unrelated company resources because lifecycle and privileges were never scoped.

Explanation

Correct Answer

C:

The situation is that a business app works in its publisher tenant but the customer cannot locate the corresponding enterprise application permissions locally. The app can inherit excessive tenant powers and may stop when the human password or MFA policy changes unexpectedly. The shortcut is unsafe because an app registration describes application identity while a service principal represents its concrete presence and authorization in a tenant.

Incorrect Answers

A:

“A migration may break old device policies or application authentication because the architecture confused a cloud…” can arise elsewhere, but it is not the most direct risk here. Here, the app can inherit excessive tenant powers and may stop when the human password or MFA policy changes unexpectedly.

B:

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, the app can inherit excessive tenant powers and may stop when the human password or MFA policy changes unexpectedly.

D:

The situation is that a business app works in its publisher tenant but the customer cannot locate the corresponding enterprise application permissions locally. The alternative risk relates to “Partner credentials may outlive the contract and expose unrelated company resources because lifecycle and privileges were…”, not the stated mistake. Here, the app can inherit excessive tenant powers and may stop when the human password or MFA policy changes unexpectedly.

Question 200

A business app works in its publisher tenant but the customer cannot locate the corresponding enterprise application permissions locally. Which action and validation evidence belong together?

  1. Action: Grant Entra directory administration through Entra roles and Azure subscription or resource access through Azure RBAC, each within its intended management plane. Validation: Use a test helpdesk identity to reset an eligible Entra account, then verify it cannot change an unrelated Azure storage account without Azure role assignment.
  2. Action: Use Entra workload identity federation to validate trusted external OIDC assertions from a supported build service before issuing an app access token. Validation: Run a sandbox pipeline with an approved issuer and branch-bound subject, then show an unexpected branch or audience cannot obtain the cloud token.
  3. Action: Use supported Microsoft Entra Connect Sync or Cloud Sync where appropriate to synchronize intended on-prem directory accounts and monitor synchronization scope and health. Validation: Create a synthetic on-prem identity update in a lab and verify intended user attributes and deactivation propagate while excluded accounts remain outside scope.
  4. Action: Register an application in Entra and grant its service principal explicitly approved permissions with a supported certificate or federated credential when appropriate. Validation: Check application object and enterprise application representation in a sandbox tenant and verify a token has only approved resource permissions.

Explanation

Correct Answer

D:

The situation is that a business app works in its publisher tenant but the customer cannot locate the corresponding enterprise application permissions locally. 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. The action and test belong together because an app registration describes application identity while a service principal represents its concrete presence and authorization in a tenant.

Incorrect Answers

A:

That action-and-evidence pair concerns “separate Microsoft entra directory roles from Azure resource RBAC”, not this decision. The appropriate action is to register an application in Entra and grant its service principal explicitly approved permissions with a supported certificate or federated credential when appropriate. To confirm, check application object and enterprise application representation in a sandbox tenant and verify a token has only approved resource permissions.

B:

The proposed pair focuses on “prefer workload identity federation over stored CI secrets” instead. The appropriate action is to register an application in Entra and grant its service principal explicitly approved permissions with a supported certificate or federated credential when appropriate. To confirm, check application object and enterprise application representation in a sandbox tenant and verify a token has only approved resource permissions.

C:

“synchronize hybrid identities with explicit scope and health checks” evaluates a different intervention. The appropriate action is to register an application in Entra and grant its service principal explicitly approved permissions with a supported certificate or federated credential when appropriate. To confirm, check application object and enterprise application representation in a sandbox tenant and verify a token has only approved resource permissions.

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