Skip to main content
  1. Public practice questions
  2. AB-900 Practice Exams | Copilot and Agent Administration Fundamentals
  3. AB-900 Practice Exam 6

Question 8 — AB-900 Practice Exam 6

For each Microsoft 365 Copilot data access and governance component, drag it to the appropriate boxes in the Correct Match column to match it against its description in the Option Column.

Each item may be used once, more than once, or not at all.

Option Correct Match
The centralized API layer Copilot uses to retrieve Microsoft 365 data while enforcing user permissions [Gap 1]
The token used to query data “on behalf of” the signed-in user and enforce authorization scope [Gap 2]
The Microsoft 365 governance and compliance boundary that Copilot stays within to prevent tenant data from being sent outside [Gap 3]
A policy category that can restrict Copilot from surfacing sensitive data in responses [Gap 4]
A security control that can block Copilot data processing from unmanaged devices or specific IP ranges [Gap 5]
  1. Personal email permissions
  2. Static firewall rules
  3. OAuth token
  4. Data Loss Prevention (DLP) rules
  5. Microsoft Purview compliance boundaries
  6. Microsoft Graph
  7. Conditional Access

Correct answers

  1. Gap 1: Microsoft Graph
  2. Gap 2: OAuth token
  3. Gap 3: Microsoft Purview compliance boundaries
  4. Gap 4: Data Loss Prevention (DLP) rules
  5. Gap 5: Conditional Access

Explanations

Correct Matches

Microsoft Graph – Copilot retrieves content from Microsoft 365 services through Graph, which enforces access checks so Copilot can only return what the user is allowed to access.
OAuth token – Graph queries are executed using the signed-in user’s token so requests are authorized under that user identity and scope rather than granting Copilot extra access.
Microsoft Purview compliance boundaries – Copilot stays within tenant and Microsoft governance boundaries so organizational data is not transmitted to non-Microsoft services or outside the tenant.
Data Loss Prevention (DLP) rules – DLP policies can prevent Copilot from extracting or presenting sensitive data when policy conditions indicate the content must be restricted.
Conditional Access – Conditional Access can restrict access based on conditions like device compliance or location; when access is blocked, Copilot cannot process data from those sources on that device.

Unused Item(s)

Static firewall rules – Copilot security in this context is based on identity, permissions, and governance policies, not static perimeter firewall rules.
Personal email permissions – Copilot data access is governed by Microsoft 365 identity and permissions, not personal mailbox permission settings.