Question 24 — AB-900 Practice Exam 8
For each Microsoft Graph capability, drag it to the appropriate box in the Correct Match column to match it against what that capability enables.
Each item may be used once, more than once, or not at all.
| Option | Correct Match |
|---|---|
| Makes emails, calendars, documents, chat transcripts, and meeting notes accessible through a single API layer across Microsoft 365 services | [Gap 1] |
| Models how people, content, and activities are connected so questions about contributors and discussions can be answered | [Gap 2] |
| Surfaces information based on what the user is doing right now and what they are permitted to access | [Gap 3] |
| Applies enterprise protections so restricted content cannot be retrieved or exposed to unauthorized users | [Gap 4] |
- Security and compliance
- Data aggregation
- Relationship mapping
- Public indexing without permissions
- Static keyword-only search
- Dynamic context
Correct answers
- Gap 1: Data aggregation
- Gap 2: Relationship mapping
- Gap 3: Dynamic context
- Gap 4: Security and compliance
Explanations
Correct Matches
Data aggregation – This capability brings together content from multiple Microsoft 365 services so different content types can be accessed through one consistent layer rather than separate app-by-app retrieval.
Relationship mapping – This capability connects people and artifacts (such as who co-authored a document, where it was discussed, and what it relates to), enabling answers that depend on understanding “who did what” and “where it was discussed.”
Dynamic context – This capability adjusts what is retrieved based on the user’s current activity and their permitted scope, preventing generic responses by focusing on what is most relevant at the moment.
Security and compliance – This capability enforces enterprise protections so Copilot cannot retrieve or reveal content the user is not authorized to access, keeping outputs within compliance boundaries.
Unused Item(s)
Public indexing without permissions – The described system enforces permission boundaries; retrieval is not open or permissionless.
Static keyword-only search – The described behavior emphasizes context and relationships rather than only fixed keyword matching.