McAfee Secured

Microsoft SC-900 Bundle

Exam Code: SC-900

Exam Name Microsoft Security, Compliance, and Identity Fundamentals

Certification Provider: Microsoft

Corresponding Certification: Microsoft Certified: Security, Compliance, and Identity Fundamentals

Microsoft SC-900 Bundle $44.99

Pass Microsoft SC-900 with Real Questions From Testking

Download Web's Best SC-900 Exam Preparation Materials Today

  • Questions & Answers

    SC-900 Questions & Answers

    259 Questions & Answers

    Questions & Answers Testing Engine software allows you to practice questions and answers in real SC-900 exam environment.

  • SC-900 Video Course

    SC-900 Video Course

    147 Video Lectures

    SC-900 Video Course is developed by Microsoft Professionals to help you pass SC-900 exam.

    Description

    This course will improve your knowledge and skills required to pass Microsoft Security, Compliance, and Identity Fundamentals exam.
  • Study Guide

    SC-900 Study Guide

    413 PDF Pages

    Study Guide will give you a practical experience regarding the subject and provide an academic background. SC-900 Study Guide is available in PDF format.

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

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Total Cost: $194.97
Bundle Price: $149.98

Purchase Individually

  • Questions & Answers

    Questions & Answers

    259 Questions

    $124.99
  • SC-900 Video Course

    Video Course

    147 Video Lectures

    $39.99
  • Study Guide

    Study Guide

    413 PDF Pages

    $29.99

Microsoft SC-900 Practice Test 17

Question 160

An enterprise creates a new Azure subscription and assumes its subscription owner is automatically the same principal as the Microsoft Entra tenant Global Administrator. Which governance action most directly addresses the recurring risk?

  1. Prohibit user passwords in unattended jobs and audit nonhuman app identities.
  2. Enforce application consent reviews and least-privilege service principal grants.
  3. Review directory roles and subscription RBAC in separate privileged-access processes.
  4. Review external-user access separately from identity invitations.

Explanation

Correct Answer

C:

Review directory roles and subscription RBAC in separate privileged-access processes. Maintaining this control reduces recurrence because: Directory administration and Azure resource permissions are separate authorization planes. The immediate response remains: Distinguish Entra directory roles from Azure resource RBAC assignments.

Other Answers

A:

Workload identities authenticate software and automation independently from a human user's lifecycle. Reducing this risk requires a practice to review directory roles and subscription RBAC in separate privileged-access processes.

B:

Application permissions are distinct from tenant-wide administration, and consent scope determines what the app can do. The stronger recurring control is to review directory roles and subscription RBAC in separate privileged-access processes.

D:

Entra B2B directory presence and resource authorization are separate trust decisions. The stronger recurring control is to review directory roles and subscription RBAC in separate privileged-access processes.

Question 161

A bank wants an app to perform directory-level automation but its engineers assign a human's interactive login instead of an application identity. Which action most directly resolves the security or identity requirement?

  1. Grant only delegated Microsoft Graph permissions to a shared employee account while leaving the unattended job without an app identity.
  2. Assign an Azure VM resource role to the human login while keeping Microsoft Graph directory automation under that shared identity.
  3. Create a dedicated app registration and service principal with approved Microsoft Graph permissions.
  4. Inventory app registrations and service principals, assign accountable owners, and disable unused credentials.

Explanation

Correct Answer

C:

An application principal represents software rather than an employee signing in interactively. To confirm, observe client-credential token issuance and deny access when the app permission is removed.

Other Answers

A:

Grant only delegated Microsoft Graph permissions to a shared employee account while leaving the unattended job without an app identity. Delegated human permissions do not establish the requested dedicated nonhuman automation principal. The relevant mechanism is: An application principal represents software rather than an employee signing in interactively. The uniquely targeted response is: Create a dedicated app registration and service principal with approved Microsoft Graph permissions.

B:

Assign an Azure VM resource role to the human login while keeping Microsoft Graph directory automation under that shared identity. An Azure resource role on a human account is not the dedicated app principal and Microsoft Graph authorization required here. The relevant mechanism is: An application principal represents software rather than an employee signing in interactively. The uniquely targeted response is: Create a dedicated app registration and service principal with approved Microsoft Graph permissions.

D:

Applications and their service principals create identity attack surface even without interactive employees. A more relevant action is to create a dedicated app registration and service principal with approved Microsoft Graph permissions.

Question 162

A bank wants an app to perform directory-level automation but its engineers assign a human's interactive login instead of an application identity. Which technical distinction is decisive in this case?

  1. Workload identities authenticate software and automation independently from a human user's lifecycle.
  2. Applications and their service principals create identity attack surface even without interactive employees.
  3. Application permissions are distinct from tenant-wide administration, and consent scope determines what the app can do.
  4. An application principal represents software rather than an employee signing in interactively.

Explanation

Correct Answer

D:

An application principal represents software rather than an employee signing in interactively. This is the principle behind: Create a dedicated app registration and service principal with approved Microsoft Graph permissions. The evidence to inspect is: Observe client-credential token issuance and deny access when the app permission is removed.

Other Answers

A:

Workload identities authenticate software and automation independently from a human user's lifecycle. By contrast, an application principal represents software rather than an employee signing in interactively.

B:

Applications and their service principals create identity attack surface even without interactive employees. In the stated system, an application principal represents software rather than an employee signing in interactively.

C:

Application permissions are distinct from tenant-wide administration, and consent scope determines what the app can do. By contrast, an application principal represents software rather than an employee signing in interactively.

Question 163

A bank wants an app to perform directory-level automation but its engineers assign a human's interactive login instead of an application identity. Which observation best validates the chosen approach?

  1. Observe client-credential token issuance and deny access when the app permission is removed.
  2. Inspect granted API scopes and verify an unrelated API remains inaccessible.
  3. Disable the employee account and confirm the automated job still authenticates as its own principal.
  4. Identify an orphaned application and verify its old credential can no longer request tokens.

Explanation

Correct Answer

A:

Observe client-credential token issuance and deny access when the app permission is removed. This test checks the expected result of: Create a dedicated app registration and service principal with approved Microsoft Graph permissions. It matters because: An application principal represents software rather than an employee signing in interactively.

Other Answers

B:

Application permissions are distinct from tenant-wide administration, and consent scope determines what the app can do. Proving this correction calls for a check to observe client-credential token issuance and deny access when the app permission is removed.

C:

Workload identities authenticate software and automation independently from a human user's lifecycle. A more meaningful verification is to observe client-credential token issuance and deny access when the app permission is removed.

D:

Applications and their service principals create identity attack surface even without interactive employees. The failure is checked more directly by a test to observe client-credential token issuance and deny access when the app permission is removed.

Question 164

A bank wants an app to perform directory-level automation but its engineers assign a human's interactive login instead of an application identity. Which governance action most directly addresses the recurring risk?

  1. Require expiration, ownership and lifecycle review for registered applications.
  2. Enforce application consent reviews and least-privilege service principal grants.
  3. Use application permission governance and service principal credential rotation.
  4. Prohibit user passwords in unattended jobs and audit nonhuman app identities.

Explanation

Correct Answer

C:

Use application permission governance and service principal credential rotation. Maintaining this control reduces recurrence because: An application principal represents software rather than an employee signing in interactively. The immediate response remains: Create a dedicated app registration and service principal with approved Microsoft Graph permissions.

Other Answers

A:

Applications and their service principals create identity attack surface even without interactive employees. The lasting safeguard is to use application permission governance and service principal credential rotation.

B:

Application permissions are distinct from tenant-wide administration, and consent scope determines what the app can do. The stronger recurring control is to use application permission governance and service principal credential rotation.

D:

Workload identities authenticate software and automation independently from a human user's lifecycle. Reducing this risk requires a practice to use application permission governance and service principal credential rotation.

Question 165

A school wants a temporary project team to access a shared app and manually grants each student a direct individual assignment. Which action most directly resolves the security or identity requirement?

  1. Assign the app through a governed Microsoft Entra group for the student project cohort.
  2. Use Microsoft Entra B2B collaboration identities with scoped resource invitations.
  3. Register the application and grant only the requested Microsoft Entra app permissions through a controlled consent process.
  4. Distinguish Entra directory roles from Azure resource RBAC assignments.

Explanation

Correct Answer

A:

Group-based resource assignment separates membership administration from per-app authorization changes. To confirm, add and remove a test member and confirm app access follows current group membership.

Other Answers

B:

External guest identities support collaboration without turning every invited partner into a normal internal employee identity. This failure calls for a decision to assign the app through a governed Microsoft Entra group for the student project cohort.

C:

Application permissions are distinct from tenant-wide administration, and consent scope determines what the app can do. The required change instead is to assign the app through a governed Microsoft Entra group for the student project cohort.

D:

Directory administration and Azure resource permissions are separate authorization planes. The corrective action for this requirement is to assign the app through a governed Microsoft Entra group for the student project cohort.

Question 166

A school wants a temporary project team to access a shared app and manually grants each student a direct individual assignment. Which technical distinction is decisive in this case?

  1. Group-based resource assignment separates membership administration from per-app authorization changes.
  2. Application permissions are distinct from tenant-wide administration, and consent scope determines what the app can do.
  3. External guest identities support collaboration without turning every invited partner into a normal internal employee identity.
  4. Directory administration and Azure resource permissions are separate authorization planes.

Explanation

Correct Answer

A:

Group-based resource assignment separates membership administration from per-app authorization changes. This is the principle behind: Assign the app through a governed Microsoft Entra group for the student project cohort. The evidence to inspect is: Add and remove a test member and confirm app access follows current group membership.

Other Answers

B:

Application permissions are distinct from tenant-wide administration, and consent scope determines what the app can do. By contrast, group-based resource assignment separates membership administration from per-app authorization changes.

C:

External guest identities support collaboration without turning every invited partner into a normal internal employee identity. By contrast, group-based resource assignment separates membership administration from per-app authorization changes.

D:

Directory administration and Azure resource permissions are separate authorization planes. In the stated system, group-based resource assignment separates membership administration from per-app authorization changes.

Question 167

A school wants a temporary project team to access a shared app and manually grants each student a direct individual assignment. Which observation best validates the chosen approach?

  1. Add and remove a test member and confirm app access follows current group membership.
  2. Invite a test partner and confirm its directory user type and limited access to an approved team.
  3. Compare a test user's directory-role capabilities with its subscription-resource access.
  4. Inspect granted API scopes and verify an unrelated API remains inaccessible.

Explanation

Correct Answer

A:

Add and remove a test member and confirm app access follows current group membership. This test checks the expected result of: Assign the app through a governed Microsoft Entra group for the student project cohort. It matters because: Group-based resource assignment separates membership administration from per-app authorization changes.

Other Answers

B:

External guest identities support collaboration without turning every invited partner into a normal internal employee identity. The failure is checked more directly by a test to add and remove a test member and confirm app access follows current group membership.

C:

Directory administration and Azure resource permissions are separate authorization planes. The relevant acceptance check is to add and remove a test member and confirm app access follows current group membership.

D:

Application permissions are distinct from tenant-wide administration, and consent scope determines what the app can do. Proving this correction calls for a check to add and remove a test member and confirm app access follows current group membership.

Question 168

A school wants a temporary project team to access a shared app and manually grants each student a direct individual assignment. Which governance action most directly addresses the recurring risk?

  1. Apply guest access reviews and automatic expiration at project completion.
  2. Review directory roles and subscription RBAC in separate privileged-access processes.
  3. Enforce application consent reviews and least-privilege service principal grants.
  4. Require group owners, access reviews, and enrollment expiration.

Explanation

Correct Answer

D:

Require group owners, access reviews, and enrollment expiration. Maintaining this control reduces recurrence because: Group-based resource assignment separates membership administration from per-app authorization changes. The immediate response remains: Assign the app through a governed Microsoft Entra group for the student project cohort.

Other Answers

A:

External guest identities support collaboration without turning every invited partner into a normal internal employee identity. The stronger recurring control is to require group owners, access reviews, and enrollment expiration.

B:

Directory administration and Azure resource permissions are separate authorization planes. The lasting safeguard is to require group owners, access reviews, and enrollment expiration.

C:

Application permissions are distinct from tenant-wide administration, and consent scope determines what the app can do. Reducing this risk requires a practice to require group owners, access reviews, and enrollment expiration.

Question 169

An acquired company has duplicate usernames across forests and proposes mapping accounts solely by display name during hybrid identity consolidation. Which action most directly resolves the security or identity requirement?

  1. Select the documented hybrid Entra/AD DS integration suitable to domain and cloud sign-in requirements.
  2. Monitor the supported hybrid identity synchronization and sign-in configuration.
  3. Design a supported unique identity matching and synchronization strategy using stable identifiers.
  4. Verify the group is included and correctly synchronized or provisioned before using it in cloud access assignments.

Explanation

Correct Answer

C:

Names are mutable and nonunique; hybrid identity synchronization needs correct object association. To confirm, match a test user with a duplicate display name and verify its cloud object is not merged with another person.

Other Answers

A:

Traditional AD DS domain control and Entra cloud identity are related but distinct services with different capabilities. The required change instead is to design a supported unique identity matching and synchronization strategy using stable identifiers.

B:

Hybrid identity depends on a functioning synchronization or federation path between on-premises identity and cloud services. The corrective action for this requirement is to design a supported unique identity matching and synchronization strategy using stable identifiers.

D:

Hybrid cloud authorization needs the relevant user and group representation in the target directory. A more relevant action is to design a supported unique identity matching and synchronization strategy using stable identifiers.

Question 170

An acquired company has duplicate usernames across forests and proposes mapping accounts solely by display name during hybrid identity consolidation. Which technical distinction is decisive in this case?

  1. Traditional AD DS domain control and Entra cloud identity are related but distinct services with different capabilities.
  2. Hybrid cloud authorization needs the relevant user and group representation in the target directory.
  3. Names are mutable and nonunique; hybrid identity synchronization needs correct object association.
  4. Hybrid identity depends on a functioning synchronization or federation path between on-premises identity and cloud services.

Explanation

Correct Answer

C:

Names are mutable and nonunique; hybrid identity synchronization needs correct object association. This is the principle behind: Design a supported unique identity matching and synchronization strategy using stable identifiers. The evidence to inspect is: Match a test user with a duplicate display name and verify its cloud object is not merged with another person.

Other Answers

A:

Traditional AD DS domain control and Entra cloud identity are related but distinct services with different capabilities. By contrast, names are mutable and nonunique; hybrid identity synchronization needs correct object association.

B:

Hybrid cloud authorization needs the relevant user and group representation in the target directory. In the stated system, names are mutable and nonunique; hybrid identity synchronization needs correct object association.

D:

Hybrid identity depends on a functioning synchronization or federation path between on-premises identity and cloud services. In the stated system, names are mutable and nonunique; hybrid identity synchronization needs correct object association.