Explanation:
Compliance Manager tracks only customer-managed controls. No
Compliance Manager provides predefined templates for creating assessments. Yes Compliance Manager can help you assess whether data adheres to specific data protection standards. No Microsoft Purview Compliance Manager is described as a feature that "helps you manage your organization's compliance requirements" by giving you assessments, improvement actions, and a compliance score that
"measures your progress in completing recommended actions" aligned to regulations and standards. The service does not track only customer-managed controls; Microsoft's documentation clarifies that Compliance Manager includes "Microsoft-managed controls and customer-managed controls," and it tracks both within each assessment to show overall posture. It also provides prebuilt (predefined) assessment templates for common regulations and industry standards so organizations can "create assessments from templates" such as GDPR, ISO/IEC 27001, and the Data Protection Baseline.
Importantly, Compliance Manager evaluates control implementation and improvement actions mapped to requirements; it does not scan or classify individual data to determine whether specific data items "adhere" to a standard. Instead, it helps you assess organizational compliance posture by tracking the status of controls, assigning actions, and recording evidence. Thus:
"Tracks only customer-managed controls" # No (it tracks Microsoft-managed and customer-managed).
"Provides predefined templates for creating assessments" # Yes (prebuilt templates are a core feature).
"Helps you assess whether data adheres to specific data protection standards" # No (it measures control
/compliance posture, not data-level adherence).
Box 1: No
Compliance Manager tracks Microsoft managed controls, customer-managed controls, and shared controls.
Box 2: Yes
Box 3: Yes
Reference:
https://docs.microsoft.com/en-us/microsoft-365/compliance/compliance-manager?view=o365-worldwide

Explanation:

In Microsoft identity architecture, federation establishes trust between different identity providers to enable single sign-on (SSO) across organizational and platform boundaries. Microsoft Learn explains that federation uses standards such as SAML, WS-Federation, and OpenID Connect/OAuth 2.0 so a user can authenticate with their home identity provider and obtain tokens that are accepted by a relying party (the application or service). This trust relationship lets organizations share identities securely without copying passwords or synchronizing credentials, providing a seamless sign-in experience across multiple systems and clouds.
By contrast, Active Directory Domain Services (AD DS) and a domain controller provide on-premises directory and authentication services primarily within a single Windows domain/forest using Kerberos
/NTLM, not cross-provider SSO on their own. Microsoft Entra Privileged Identity Management (PIM) manages just-in-time, approval-based elevation for roles and does not deliver SSO capabilities. Therefore, the technology explicitly intended to provide SSO across multiple identity providers is federation.

Explanation:
In Microsoft Sentinel, playbooks are the feature that integrates with Azure Logic Apps to automate response.
Microsoft's documentation describes them as "collections of procedures that can be run from Microsoft Sentinel in response to an alert" and clarifies that "playbooks are built on Azure Logic Apps" providing a workflow engine and a gallery of connectors to other Microsoft and third-party services. Playbooks can be triggered automatically from analytics rules or manually from incidents and alerts, enabling orchestration such as assigning owners, creating tickets, disabling accounts, blocking IPs, or posting to collaboration channels.
The platform emphasizes that the Logic Apps foundation gives security teams a visual designer, managed connectors, and run history to track execution and outcomes. In short, Sentinel uses playbooks to "automate and orchestrate responses to alerts and incidents", reducing mean-time-to-respond and standardizing actions across your SOC. Other Sentinel components serve different purposes: analytic rules detect threats, hunting queries aid proactive investigation, and workbooks provide dashboards and visualizations. Therefore, the correct completion is: Microsoft Sentinel playbooks use Azure Logic Apps to automate and orchestrate responses to alerts.

In Microsoft Purview, Sensitivity labels are the feature designed to let users identify and classify content that should be protected. Microsoft's guidance explains that sensitivity labels "enable you to classify and protect your organization's data while ensuring that user productivity and collaboration aren't hindered." Users can manually choose a label in Office apps and services to indicate the data's sensitivity; as Microsoft notes, labels "can be applied by users or automatically," and the label "persists with the content in its metadata." Once identified with a label, protection settings can be enforced, including "encryption, content marking (headers, footers, watermarks), and access restrictions based on the label." By comparison, Data Loss Prevention (DLP) focuses on "monitoring and blocking the unintentional sharing of sensitive information" based on policy-DLP enforces handling rules after data is identified, rather than providing the user-centric classification mechanism. Insider Risk addresses "risky user activities and insider data security scenarios," and eDiscovery is used to "find, preserve, collect, and review content for investigations or litigation." Therefore, the feature that explicitly allows users to identify content that should be protected-by selecting and applying a classification that then drives protection-is Sensitivity labels.

Microsoft's SCI documentation explains that Information Barriers (part of Microsoft Purview and enforced across Microsoft Teams, SharePoint, OneDrive, and Exchange) are used to "restrict communication and collaboration between specific groups of users to avoid conflicts of interest or to comply with regulatory obligations." Policies define which segments can communicate and which must be blocked, and they control chat, channel conversations, meetings, file sharing, and e-discovery visibility between the defined segments.
Typical scenarios include preventing communication between investment banking and research, or between merger deal teams and the rest of the organization. This is fundamentally different from other features:
Sensitivity label policies classify and protect content but do not block who can talk to whom; Customer Lockbox manages Microsoft engineer access to customer data during support; and Privileged Access Management (PAM) limits admin task approvals and elevated operations, not end-user communication. When the requirement is to "restrict communication and the sharing of information between members of two departments," Microsoft prescribes Information Barriers as the purpose-built capability to enforce those restrictions across collaboration workloads.