SC-900 domain - 13% of the exam

Security, Compliance, and Identity Concepts

Security, Compliance, and Identity Concepts is 13% of the SC-900 exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

39
Practice questions
2
Objectives
21
Easy
18
Medium

Where people go wrong

  • Moving customer-owned layers onto Microsoft

    The wrong answers hand the customer's layers to Microsoft or treat the physical layers as the customer's. Data and identities stay with the customer in every deployment type, and the operating system is the customer's in IaaS but Microsoft's in PaaS and SaaS. The physical datacenter, network and hosts belong to Microsoft once a workload is in the cloud. Applications are the shared area, with the split moving between IaaS, PaaS and SaaS.

    See it in a sample question
  • Swapping the three Zero Trust principles

    The wrong answers describe a different Zero Trust principle from the one named. Authenticating and authorising every request with all available signals is verify explicitly. Granting each identity minimal access for the shortest time is least privilege. Designing controls on the expectation that attackers may already be inside, to limit impact and speed detection, is assume breach. Trusting requests because they come from inside the corporate network is the perimeter model Zero Trust replaces.

    See it in a sample question
  • Confusing authentication, authorization, MFA and single sign-on

    Four neighbouring terms get exchanged. Authentication proves who a person or device is. Authorization then decides what that verified party can access and do. Multifactor authentication adds another factor to the proof of identity and grants no permissions. Single sign-on lets one sign-in reach many apps that share a directory, which is a different job from adding a verification factor.

    See it in a sample question
  • Applying the wrong protection to a data state

    Data at rest, in transit and in use each need a different control, and the wrong answers borrow one from another state. Storage Service Encryption and Transparent Data Encryption protect stored data. Transport Layer Security protects data travelling between a client and a service, while MACsec and SSTP are also transit mechanisms. Data loaded into memory is decrypted, so only confidential computing in a protected execution environment covers it.

    See it in a sample question
  • Mixing up hashing, symmetric and asymmetric encryption

    Hashing, symmetric encryption and asymmetric encryption are given each other's properties. Symmetric encryption uses one key to encrypt and decrypt. Asymmetric encryption uses a public and private key pair, so a sender can encrypt to a recipient without sharing a secret key first. Hashing has no key and cannot be reversed, so it verifies data but never returns the original value.

    See it in a sample question

Objectives in this domain

Sample questions from this domain

Free sampleSecurity, Compliance, and Identity Conceptseasy

An instructor is explaining the cloud shared responsibility model. Which responsibility area stays with the customer across on-premises, IaaS, PaaS, and SaaS deployments alike?

  • AData and identities, which the customer is responsible for protecting in every deployment type. Correct
  • BThe physical hosts, which the customer is responsible for maintaining in every deployment type.
  • CThe physical datacenter, which the customer is responsible for securing in every deployment type.
  • DThe hypervisor layer, which the customer is responsible for managing in every deployment type.
The customer always retains responsibility for their data and identities, no matter the cloud deployment type. The grounding states that for all cloud deployment types you own your data and identities, and that data and accounts and access management are responsibilities you always retain regardless of the deployment type.

Why A is correct: Correct. The grounding states that for all cloud deployment types you own your data and identities, and that data and accounts and access management are responsibilities you always retain regardless of the deployment type.

Why B is wrong: Physical hosts are a Microsoft responsibility in IaaS, PaaS, and SaaS; only on-premises leaves them with the customer, so they are not always retained.

Why C is wrong: Securing the physical datacenter shifts to Microsoft once you move to any cloud model, so it is not a responsibility the customer always retains.

Why D is wrong: The grounding lists the hypervisor as a Microsoft responsibility for the virtualization layer, so the customer does not retain it.

Free sampleSecurity, Compliance, and Identity Conceptsmedium

A workload owner is applying the Zero Trust assume breach principle. Which design approach best reflects what assume breach means?

  • ADesign controls so a failed primary defence still limits damage and speeds detection. Correct
  • BAuthenticate and authorise each access request using all of the available signals at sign-in.
  • CGive each identity only the access that it needs, and only for the shortest time required.
  • DTreat requests that come from inside the corporate network as already trusted and let them pass.
Assume breach designs controls expecting attackers may already be inside, to limit impact and enable rapid detection and response. The grounding states assume breach means security controls are designed with the expectation that attackers might be operating inside the environment, with controls focused on limiting breach impact and enabling rapid threat detection and response.

Why A is correct: Correct. The grounding states assume breach means security controls are designed with the expectation that attackers might be operating inside the environment, with controls focused on limiting breach impact and enabling rapid threat detection and response.

Why B is wrong: Authenticating with all available signals describes the verify explicitly principle, not assume breach.

Why C is wrong: Granting minimal access for the shortest time describes the use least privilege access principle, not assume breach.

Why D is wrong: Trusting internal requests contradicts Zero Trust entirely; assume breach expects attackers may already be inside, so internal requests are not trusted by default.

Free sampleSecurity, Compliance, and Identity Conceptseasy

A new administrator is learning the difference between authentication and authorization. Which statement best describes what authentication does?

  • AIt grants an already-verified party permission to perform a specific action on data.
  • BIt proves you are who you say you are by verifying the identity of a person or device. Correct
  • CIt synchronises on-premises user accounts into a central cloud directory on a schedule.
  • DIt detects risky sign-in behaviour and then requires a forced password change.
Authentication is the process of proving who you are by verifying the identity of a person or device. The grounding defines authentication as the process of proving that you are who you say you are, achieved by verifying the identity of a person or device, and notes it is sometimes shortened to AuthN.

Why A is wrong: Granting an already-verified party permission to act on data describes authorization, which decides what you can do after your identity is confirmed.

Why B is correct: Correct. The grounding defines authentication as the process of proving that you are who you say you are, achieved by verifying the identity of a person or device, and notes it is sometimes shortened to AuthN.

Why C is wrong: Synchronising on-premises accounts into a cloud directory is a directory synchronisation task, not the act of verifying who a user is.

Why D is wrong: Detecting risky behaviour and forcing remediation describes Identity Protection, not the basic act of proving an identity.

Free sampleSecurity, Compliance, and Identity Conceptseasy

A storage administrator is protecting information that resides in persistent storage on physical media. Which encryption strength does Azure Storage Service Encryption use to automatically encrypt this data at rest?

  • A256-bit AES encryption, one of the strongest block ciphers available. Correct
  • BThe IEEE 802.1AE MACsec standard applied across the network hardware.
  • CThe Transport Layer Security protocol negotiated with the client system.
  • DThe Secure Socket Tunneling Protocol used to build a point-to-site tunnel.
Azure Storage Service Encryption protects data at rest automatically using 256-bit AES, one of the strongest block ciphers available. The grounding states Azure Storage Service Encryption automatically encrypts data before it is stored and decrypts it on retrieval, using 256-bit AES encryption, one of the strongest block ciphers available, and that AES 256 protects data at rest across the cloud models.

Why A is correct: Correct. The grounding states Azure Storage Service Encryption automatically encrypts data before it is stored and decrypts it on retrieval, using 256-bit AES encryption, one of the strongest block ciphers available, and that AES 256 protects data at rest across the cloud models.

Why B is wrong: MACsec is a data-link layer method for traffic moving between datacenters, which is data in transit, not the at-rest encryption Storage Service Encryption applies.

Why C is wrong: TLS protects data in transit between cloud services and clients, not data at rest in storage, so it is the wrong protection for this scenario.

Why D is wrong: SSTP builds the VPN tunnel for a point-to-site VPN, a transit mechanism, and has nothing to do with encrypting stored data.

Free sampleSecurity, Compliance, and Identity Conceptsmedium

An architect wants a method where anyone can encrypt a message to a recipient, but only that recipient can read it, without first sharing a secret key over the network. Which encryption type meets this need?

  • ASymmetric encryption, where both parties must first agree on and securely share a single secret key.
  • BAsymmetric encryption, where a public key encrypts and the matching private key decrypts. Correct
  • CHashing, where an algorithm turns the message into a fixed-length value with no key.
  • DSalting, where a random value is added to the message before it is processed.
Asymmetric encryption uses a freely shared public key to encrypt and a private key to decrypt, solving symmetric encryption's key-distribution problem. The grounding states asymmetric encryption uses a public and private key pair, data encrypted with the public key can only be decrypted with the corresponding private key, and because the public key can be freely shared it solves the key-distribution problem of symmetric encryption.

Why A is wrong: Symmetric encryption needs both parties to hold the same secret key, which reintroduces the key-distribution problem the scenario wants to avoid.

Why B is correct: Correct. The grounding states asymmetric encryption uses a public and private key pair, data encrypted with the public key can only be decrypted with the corresponding private key, and because the public key can be freely shared it solves the key-distribution problem of symmetric encryption.

Why C is wrong: Hashing produces a one-way value with no key and cannot be reversed, so the recipient could never recover the original message.

Why D is wrong: Salting adds a random value before hashing to defend stored passwords; it is not an encryption method that lets a recipient decrypt a message.

Other domains in this exam

See also the SC-900 cert hub, the study guide, and the cheat sheet.

Examworthy is not affiliated with or endorsed by Microsoft. Original, blueprint-aligned practice material only.