A 311 supervisor sees mail-access failures clustered on unmanaged personal phones. Where should the EUC operator look first?
Select an answer to reveal the explanation.
Short Explanation
If only unmanaged phones cannot pick up city mail, the bouncer is the mail policy, not the PDF locker. Check EAS or managed-mail rules first.
Full Explanation
Mail-access failures clustered on unmanaged personal phones point first to email-management policies such as EAS or managed-mail rules that exclude unmanaged devices. In municipal EUC terms, treat the endpoint as a window into city systems when the architecture says so, not as the system of record for the files or apps in the stem. Distractor concept: Content locker catalog issues would affect documents, not Exchange sync for unmanaged phones as a class. Distractor concept: Horizon Help Desk metrics address VDI sessions, not mobile mail policy. Distractor concept: NSX Distributed Firewall is data-center microsegmentation, not the first stop for unmanaged phone mail denials. Exam caveat: Pattern "unmanaged phones cannot get mail" → check email/MEM/EAS policy before Content, Horizon, or NSX. Operational check: Compare one unmanaged test phone versus one managed phone against EAS/managed-mail allow lists and align policy to the 311 supervisor's intent. Record the chosen control and the rejected failure modes in the civic change ticket or runbook so on-call staff and auditors share the same rationale after the next maintenance window. Re-validate after personnel or image changes that the same control still meets the city's continuity, security, and support expectations for this service.