Skip to main content
  1. Public practice questions
  2. AB-650 Practice Exams | Microsoft 365 and AI Services Administrator Associate
  3. AB-650 Practice Exam 6

Question 44 — AB-650 Practice Exam 6

A compliance system contains rapidly changing investigation records. The records must remain in the system of record and must not be copied into Microsoft 365. Each employee must authenticate individually, the compliance system must evaluate that employee's current permissions whenever a query occurs, and Copilot only needs to read the records. Which connector implementation meets these requirements? (Select one answer)

  1. Use a synced connector with organization-level authentication and periodically refresh its Microsoft Graph index.

  2. Use a synced connector that copies source ACLs into Microsoft Graph and performs full crawls when records change.

  3. Use a synced connector built through the Microsoft Graph connectors API and increase its synchronization frequency.

  4. Use a federated connector that retrieves records live through per-user authentication and source-enforced access.

Correct answers

  1. Use a federated connector that retrieves records live through per-user authentication and source-enforced access.

Explanations

Correct:

Use a federated connector that retrieves records live through per-user authentication and source-enforced access.
A federated connector leaves the information in its system of record and retrieves it only when the user queries it. OAuth 2.0 authentication occurs per user, the source evaluates permissions in real time, and the connection is read-only. These characteristics satisfy the data-residency and rapidly changing permission requirements.

Wrong:

Use a synced connector with organization-level authentication and periodically refresh its Microsoft Graph index.
A synced connector copies and indexes content into Microsoft Graph. That conflicts with the requirement that the investigation records remain exclusively in their source system.

Use a synced connector that copies source ACLs into Microsoft Graph and performs full crawls when records change.
Source ACL preservation can protect indexed content, but this approach still requires the records to be indexed into Microsoft Graph rather than remain solely in the compliance system.

Use a synced connector built through the Microsoft Graph connectors API and increase its synchronization frequency.
Increasing synchronization frequency does not satisfy a requirement prohibiting source data from being copied into Microsoft 365. The synced model still creates an indexed representation in Microsoft Graph.