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 21

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.

Question 201

For this cloud security and identity case, A GitHub Actions workflow needs to deploy an Azure test resource without keeping an Azure client secret in repository settings. 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. Invite external collaborators using supported Microsoft Entra B2B guest collaboration and give them scoped resource access rather than treating partners as tenant administrators.
  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:

Use Entra workload identity federation to validate trusted external OIDC assertions from a supported build service before issuing an app access token. Federated workload credentials exchange verified short-lived tokens based on issuer, audience and subject, avoiding stored long-lived cloud secrets in CI. To verify, run a sandbox pipeline with an approved issuer and branch-bound subject, then show an unexpected branch or audience cannot obtain the cloud token.

Incorrect Answers

B:

“separate member and guest identities in collaboration” is related to another task, not the failure shown here. Federated workload credentials exchange verified short-lived tokens based on issuer, audience and subject, avoiding stored long-lived cloud secrets in CI.

C:

This alternative focuses on “use system-assigned managed identities for a single Azure resource” instead of the required outcome. Federated workload credentials exchange verified short-lived tokens based on issuer, audience and subject, avoiding stored long-lived cloud secrets in CI.

D:

That choice concerns “identify a Microsoft entra tenant as cloud identity directory”, not the immediate requirement. Federated workload credentials exchange verified short-lived tokens based on issuer, audience and subject, avoiding stored long-lived cloud secrets in CI.

Question 202

A GitHub Actions workflow needs to deploy an Azure test resource without keeping an Azure client secret in repository settings. Why does the recommended approach address this particular concern?

  1. Different hybrid sign-in patterns change where credentials are validated and which on-prem services remain necessary when connectivity fails.
  2. Federated workload credentials exchange verified short-lived tokens based on issuer, audience and subject, avoiding stored long-lived cloud secrets in CI.
  3. An automated service principal or agent identity has a different accountability and token lifecycle from an interactive workforce member or external guest.
  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

B:

Federated workload credentials exchange verified short-lived tokens based on issuer, audience and subject, avoiding stored long-lived cloud secrets in CI. This supports the decision to use Entra workload identity federation to validate trusted external OIDC assertions from a supported build service before issuing an app access token.

Incorrect Answers

A:

The principle behind “distinguish cloud-only and hybrid identity sign-in choices” is not the one being tested. Here, federated workload credentials exchange verified short-lived tokens based on issuer, audience and subject, avoiding stored long-lived cloud secrets in CI.

C:

“distinguish workforce workload and agent identities at a conceptual level” explains a different mechanism. Here, federated workload credentials exchange verified short-lived tokens based on issuer, audience and subject, avoiding stored long-lived cloud secrets in CI.

D:

That statement concerns “reuse user-assigned managed identity deliberately” rather than the cause in this case. Here, federated workload credentials exchange verified short-lived tokens based on issuer, audience and subject, avoiding stored long-lived cloud secrets in CI.

Question 203

A GitHub Actions workflow needs to deploy an Azure test resource without keeping an Azure client secret in repository settings. Which evidence best validates the proposed outcome?

  1. Verify a sample guest appears with the expected external identity type, accesses only one approved Teams workspace and cannot manage directory roles.
  2. Perform documented test sign-ins during a controlled laboratory loss of on-prem connectivity and record expected sign-in differences for the chosen model.
  3. 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. 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

C:

Run a sandbox pipeline with an approved issuer and branch-bound subject, then show an unexpected branch or audience cannot obtain the cloud token. It is the relevant test because federated workload credentials exchange verified short-lived tokens based on issuer, audience and subject, avoiding stored long-lived cloud secrets in CI.

Incorrect Answers

A:

“separate member and guest identities in collaboration” would verify a different part of the system. To check this result, run a sandbox pipeline with an approved issuer and branch-bound subject, then show an unexpected branch or audience cannot obtain the cloud token.

B:

That test concerns “distinguish cloud-only and hybrid identity sign-in choices”, not the requested outcome. To check this result, run a sandbox pipeline with an approved issuer and branch-bound subject, then show an unexpected branch or audience cannot obtain the cloud token.

D:

This evidence addresses “synchronize hybrid identities with explicit scope and health checks” instead of confirming the repair. To check this result, run a sandbox pipeline with an approved issuer and branch-bound subject, then show an unexpected branch or audience cannot obtain the cloud token.

Question 204

Consider this situation: A GitHub Actions workflow needs to deploy an Azure test resource without keeping an Azure client secret in repository settings. A team member suggests: "Store a nonexpiring service-principal password in a public CI variable because it is easier than configuring OIDC trust conditions." 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. The app can inherit excessive tenant powers and may stop when the human password or MFA policy changes unexpectedly.
  4. Anyone who obtains the static secret may impersonate the deployment application beyond the intended build run or repository boundary.

Explanation

Correct Answer

D:

Anyone who obtains the static secret may impersonate the deployment application beyond the intended build run or repository boundary. The shortcut is unsafe because federated workload credentials exchange verified short-lived tokens based on issuer, audience and subject, avoiding stored long-lived cloud secrets in CI.

Incorrect Answers

A:

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, anyone who obtains the static secret may impersonate the deployment application beyond the intended build run or repository boundary.

B:

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

C:

The alternative risk relates to “The app can inherit excessive tenant powers and may stop when the human password or MFA…”, not the stated mistake. Here, anyone who obtains the static secret may impersonate the deployment application beyond the intended build run or repository boundary.

Question 205

A security and compliance reviewer considers: A GitHub Actions workflow needs to deploy an Azure test resource without keeping an Azure client secret in repository settings. 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: 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.
  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:

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. The action and test belong together because federated workload credentials exchange verified short-lived tokens based on issuer, audience and subject, avoiding stored long-lived cloud secrets in CI.

Incorrect Answers

B:

“separate Microsoft entra directory roles from Azure resource RBAC” evaluates a different intervention. The appropriate action is to use Entra workload identity federation to validate trusted external OIDC assertions from a supported build service before issuing an app access token. To confirm, run a sandbox pipeline with an approved issuer and branch-bound subject, then show an unexpected branch or audience cannot obtain the cloud token.

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 use Entra workload identity federation to validate trusted external OIDC assertions from a supported build service before issuing an app access token. To confirm, run a sandbox pipeline with an approved issuer and branch-bound subject, then show an unexpected branch or audience cannot obtain the cloud token.

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 use Entra workload identity federation to validate trusted external OIDC assertions from a supported build service before issuing an app access token. To confirm, run a sandbox pipeline with an approved issuer and branch-bound subject, then show an unexpected branch or audience cannot obtain the cloud token.

Question 206

A deployment system accepts OIDC assertions from any repository subject and accidentally allows forked builds to assume production identity. Which action best addresses this requirement?

  1. 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.
  2. Use Entra workload identity federation to validate trusted external OIDC assertions from a supported build service before issuing an app access token.
  3. Choose cloud-only authentication or a supported hybrid password hash, pass-through or federation approach based on business and dependency constraints.
  4. Invite external collaborators using supported Microsoft Entra B2B guest collaboration and give them scoped resource access rather than treating partners as tenant administrators.

Explanation

Correct Answer

B:

The situation is that a deployment system accepts OIDC assertions from any repository subject and accidentally allows forked builds to assume production identity. Use Entra workload identity federation to validate trusted external OIDC assertions from a supported build service before issuing an app access token. Federated workload credentials exchange verified short-lived tokens based on issuer, audience and subject, avoiding stored long-lived cloud secrets in CI. To verify, run a sandbox pipeline with an approved issuer and branch-bound subject, then show an unexpected branch or audience cannot obtain the cloud token.

Incorrect Answers

A:

“distinguish workforce workload and agent identities at a conceptual level” is related to another task, not the failure shown here. Federated workload credentials exchange verified short-lived tokens based on issuer, audience and subject, avoiding stored long-lived cloud secrets in CI.

C:

That choice concerns “distinguish cloud-only and hybrid identity sign-in choices”, not the immediate requirement. Federated workload credentials exchange verified short-lived tokens based on issuer, audience and subject, avoiding stored long-lived cloud secrets in CI.

D:

The proposed action addresses “separate member and guest identities in collaboration” rather than the problem described. Federated workload credentials exchange verified short-lived tokens based on issuer, audience and subject, avoiding stored long-lived cloud secrets in CI.

Question 207

A cloud security learner considers: A deployment system accepts OIDC assertions from any repository subject and accidentally allows forked builds to assume production identity. Which underlying principle applies?

  1. B2B collaboration represents external identities in a resource tenant while their home organization may remain responsible for primary authentication.
  2. An app registration describes application identity while a service principal represents its concrete presence and authorization in a tenant.
  3. Federated workload credentials exchange verified short-lived tokens based on issuer, audience and subject, avoiding stored long-lived cloud secrets in CI.
  4. 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.

Explanation

Correct Answer

C:

The situation is that a deployment system accepts OIDC assertions from any repository subject and accidentally allows forked builds to assume production identity. Federated workload credentials exchange verified short-lived tokens based on issuer, audience and subject, avoiding stored long-lived cloud secrets in CI. This supports the decision to use Entra workload identity federation to validate trusted external OIDC assertions from a supported build service before issuing an app access token.

Incorrect Answers

A:

“separate member and guest identities in collaboration” describes another technical distinction. Here, federated workload credentials exchange verified short-lived tokens based on issuer, audience and subject, avoiding stored long-lived cloud secrets in CI.

B:

“use an app registration and service principal for application access” explains a different mechanism. Here, federated workload credentials exchange verified short-lived tokens based on issuer, audience and subject, avoiding stored long-lived cloud secrets in CI.

D:

The principle behind “synchronize hybrid identities with explicit scope and health checks” is not the one being tested. Here, federated workload credentials exchange verified short-lived tokens based on issuer, audience and subject, avoiding stored long-lived cloud secrets in CI.

Question 208

A deployment system accepts OIDC assertions from any repository subject and accidentally allows forked builds to assume production identity. 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. Verify a sample guest appears with the expected external identity type, accesses only one approved Teams workspace and cannot manage directory roles.
  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. 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

D:

The situation is that a deployment system accepts OIDC assertions from any repository subject and accidentally allows forked builds to assume production identity. Run a sandbox pipeline with an approved issuer and branch-bound subject, then show an unexpected branch or audience cannot obtain the cloud token. It is the relevant test because federated workload credentials exchange verified short-lived tokens based on issuer, audience and subject, avoiding stored long-lived cloud secrets in CI.

Incorrect Answers

A:

That test concerns “reuse user-assigned managed identity deliberately”, not the requested outcome. To check this result, run a sandbox pipeline with an approved issuer and branch-bound subject, then show an unexpected branch or audience cannot obtain the cloud token.

B:

The proposed check is relevant to “separate member and guest identities in collaboration”, but not sufficient here. To check this result, run a sandbox pipeline with an approved issuer and branch-bound subject, then show an unexpected branch or audience cannot obtain the cloud token.

C:

This evidence addresses “identify a Microsoft entra tenant as cloud identity directory” instead of confirming the repair. To check this result, run a sandbox pipeline with an approved issuer and branch-bound subject, then show an unexpected branch or audience cannot obtain the cloud token.

Question 209

A deployment system accepts OIDC assertions from any repository subject and accidentally allows forked builds to assume production identity. The proposed shortcut is: "Store a nonexpiring service-principal password in a public CI variable because it is easier than configuring OIDC trust conditions." 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. Former employee access may persist in cloud apps because directory changes did not propagate through an unhealthy synchronization service.
  4. The app can inherit excessive tenant powers and may stop when the human password or MFA policy changes unexpectedly.

Explanation

Correct Answer

A:

The situation is that a deployment system accepts OIDC assertions from any repository subject and accidentally allows forked builds to assume production identity. Anyone who obtains the static secret may impersonate the deployment application beyond the intended build run or repository boundary. The shortcut is unsafe because federated workload credentials exchange verified short-lived tokens based on issuer, audience and subject, avoiding stored long-lived cloud secrets in CI.

Incorrect Answers

B:

The alternative risk relates to “A failure of an on-prem authentication endpoint can cause unexpected outage when the organization selected a…”, not the stated mistake. Here, anyone who obtains the static secret may impersonate the deployment application beyond the intended build run or repository boundary.

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, anyone who obtains the static secret may impersonate the deployment application beyond the intended build run or repository boundary.

D:

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, anyone who obtains the static secret may impersonate the deployment application beyond the intended build run or repository boundary.

Question 210

For this case—A deployment system accepts OIDC assertions from any repository subject and accidentally allows forked builds to assume production identity.—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: 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: 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 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

B:

The situation is that a deployment system accepts OIDC assertions from any repository subject and accidentally allows forked builds to assume production identity. 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. The action and test belong together because federated workload credentials exchange verified short-lived tokens based on issuer, audience and subject, avoiding stored long-lived cloud secrets in CI.

Incorrect Answers

A:

“separate member and guest identities in collaboration” evaluates a different intervention. The appropriate action is to use Entra workload identity federation to validate trusted external OIDC assertions from a supported build service before issuing an app access token. To confirm, run a sandbox pipeline with an approved issuer and branch-bound subject, then show an unexpected branch or audience cannot obtain the cloud token.

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 use Entra workload identity federation to validate trusted external OIDC assertions from a supported build service before issuing an app access token. To confirm, run a sandbox pipeline with an approved issuer and branch-bound subject, then show an unexpected branch or audience cannot obtain the cloud token.

D:

The proposed pair focuses on “identify a Microsoft entra tenant as cloud identity directory” instead. The appropriate action is to use Entra workload identity federation to validate trusted external OIDC assertions from a supported build service before issuing an app access token. To confirm, run a sandbox pipeline with an approved issuer and branch-bound subject, then show an unexpected branch or audience cannot obtain the cloud token.

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