In Microsoft 365 compliance, sensitivity labels (Microsoft Purview Information Protection) are the feature designed to classify and automatically protect data. Microsoft states that sensitivity labels "let you classify and protect your organization's data" and that a label "can apply protection settings such as encryption" to files and emails. Labels can be deployed so that protection is applied without user action: Microsoft explains that labels "can be applied automatically, recommended, or by users," and that administrators can "auto-apply a sensitivity label to content in SharePoint, OneDrive, and Exchange based on conditions such as sensitive info types, keywords, or trainable classifiers." When a label with protection is applied, "encryption settings travel with the content" and enforce usage rights like who can open, print, or forward, even outside the organization.
By contrast, Content Search and eDiscovery are discovery/investigative tools and do not enforce protection.
Retention policies manage how long content is kept or deleted, but they don't encrypt content. Therefore, the Microsoft 365 compliance capability that encrypts content automatically based on specific conditions is sensitivity labels with auto-labeling policies in Microsoft Purview.

Explanation:
Microsoft's security and compliance learning content explains that digital signatures are built on public key (asymmetric) cryptography. In this model, each identity has a key pair: a private key that is kept secret and a public key that can be shared. The signing operation is performed with the private key to produce a signature bound to the content and the signer's identity. Verification is then performed by anyone who has access to the corresponding public key, which mathematically validates the signature and confirms both integrity (the content wasn't altered) and authenticity (it was signed by the holder of the private key). SCI materials (covering Microsoft Purview Information Protection, Azure Key Vault/PKI concepts, and identity fundamentals) emphasize that the private key must never be disclosed or required for verification; only the public key is used to validate signatures and certificates. This is the same principle used across Microsoft 365 for certificate-based trust, code signing, and document signing: sign with the private key; verify with the public key. Therefore, statements one and two are true, and the statement claiming verification requires the private key is false.

The recommended way to enable and use Azure AD Multi-Factor Authentication is with Conditional Access policies. Conditional Access lets you create and define policies that react to sign-in events and that request additional actions before a user is granted access to an application or service.

Explanation:

In Microsoft Entra Conditional Access, policy evaluation occurs after the user successfully completes first- factor authentication (for example, username + password or Windows Hello for Business key). Microsoft Learn explains that Conditional Access "is the tool used by Azure AD to bring signals together, make decisions, and enforce organizational policies" and that it's applied "after the first-factor authentication is completed." Once primary authentication succeeds, Conditional Access evaluates signals like user, device state, location, risk (from Identity Protection), and application, and then enforces controls such as requiring MFA, blocking access, or applying session controls.
This design ensures Conditional Access does not replace primary authentication and is not enforced before or during the initial credential verification. Instead, it adds a second policy decision point that can demand stronger proof (e.g., MFA), restrict access paths, or limit sessions. Therefore, "after" is correct, while
"before," "during," or "instead of" first-factor authentication are incorrect because Conditional Access relies on the initial sign-in to collect the necessary signals and then applies the configured access decisions and protections.

Explanation:
authorization
In the context of Microsoft identity and access management, when users attempt to access an application or a service, authorization is what controls their level of access. This concept is clearly defined in Microsoft's Security, Compliance, and Identity (SCI) learning paths, particularly in SC-900 and SC-300 certifications.
From Microsoft SCI training materials:
"Authentication is the process of verifying the identity of a user, while authorization is the process of determining what resources a user can access and what actions they are permitted to perform." In more detail:
Authentication confirms who you are (e.g., verifying credentials through Azure AD, MFA).
Authorization decides what you can do (e.g., access to files, roles, permissions in an app or service).
SCI documentation explains:
"Once authentication is successful, authorization policies are applied to determine whether the authenticated user is allowed to access the requested resource and at what level." This principle is implemented using role-based access control (RBAC) in Microsoft Azure and Microsoft 365 environments. For example, even if a user successfully logs into the Microsoft 365 portal (authentication), their ability to manage Exchange Online settings or view compliance data depends on their assigned roles (authorization).