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

Question 1 — AB-650 Case Study Set

Paideffort Exchange Online Mailbox Lifecycle Modernization
 

Business Context

Paideffort operates a Microsoft 365 environment in which Exchange Online supports approximately 4,800 licensed employees and several operational mailboxes used by customer service, billing, training, and executive teams. Administrators manage mailbox objects through the Microsoft 365 admin center, the Exchange admin center, and Exchange Online PowerShell. Paideffort requires administrators to use the simplest management surface for isolated changes while using automation for tenant-wide reporting and bulk operations.

The operations team must minimize unnecessary licensing cost without interrupting mail delivery. Departing-user content that is subject to legal preservation must remain discoverable, and customer-facing addresses must continue receiving mail during staff transitions. Shared operational mailboxes must also remain reliable during periods of heavy concurrent access.

Current Mailbox Estate

support@paideffort.com is a shared mailbox containing 84 GB of data. Eighteen support specialists use it regularly. Its anchor account currently has no Exchange Online license because the operations team previously standardized on removing licenses from shared mailboxes.

billing@paideffort.com is a 37 GB shared mailbox used by twelve billing specialists. It has no in-place archive or litigation hold and currently operates without a dedicated mailbox license.

escalations@paideffort.com is a 28 GB shared mailbox used by 34 service specialists who frequently keep the mailbox open simultaneously in Outlook throughout their shifts.

Departing-User Workflow

Nadia Mensah is leaving Paideffort. Her licensed user mailbox contains 43 GB. Legal requires all existing, deleted, and subsequently modified mailbox content to remain preserved indefinitely. The operations team also wants future messages sent to Nadia to be forwarded to operationslead@paideffort.com while Nadia's historical mailbox remains available to an authorized team. The service desk intends to convert the mailbox to a shared mailbox as part of offboarding.

Paideffort's current offboarding checklist tells technicians to reclaim a departing employee's Microsoft 365 license as soon as the employment status changes, and conversion work is performed later in the same workflow.

Automation Artifacts

A Python validation function is being introduced before license reclamation:

def requires_exchange_license(mailbox):
    return (
        mailbox["type"] == "Shared"
        and mailbox["sizeGB"] > 50
    )

Nadia's proposed offboarding configuration is stored as YAML:

mailbox: nadia@paideffort.com
targetType: Shared
forwarding:
  enabled: true
litigationHold: true
preservation: indefinite

The mailbox inventory consumed by the reporting process includes:

[
  {
    "identity": "support@paideffort.com",
    "type": "Shared",
    "sizeGB": 84,
    "license": "None",
    "concurrentUsers": 18
  },
  {
    "identity": "billing@paideffort.com",
    "type": "Shared",
    "sizeGB": 37,
    "license": "None",
    "concurrentUsers": 12
  },
  {
    "identity": "escalations@paideffort.com",
    "type": "Shared",
    "sizeGB": 28,
    "license": "None",
    "concurrentUsers": 34
  }
]

Exchange administrators also use the following commands during mailbox investigations and transitions:

Get-Mailbox -Identity "nadia@paideffort.com" |
    Select-Object DisplayName, ProhibitSendReceiveQuota

Set-Mailbox -Identity "nadia@paideffort.com" `
    -ForwardingAddress "operationslead@paideffort.com"

Future Requirements

Paideffort expects the service organization to grow to more than 60 specialists. Administrators want automated reporting that identifies mailbox storage and licensing risks before delivery is affected, while legal preservation decisions must prevent premature license removal. The architecture team also wants collaboration patterns selected according to scale instead of automatically creating shared mailboxes for every common address. Single-user changes should remain easy to perform, while tenant-wide mailbox analysis must support filtering and bulk remediation.