An employee experience lead pilots Viva-style intranet and engage experiences for city culture posts and staff community updates. What should they expect Viva to support at describe depth?
Select an answer to reveal the explanation.
Short Explanation
Culture posts and staff communities sit in Viva’s employee experience playground. Think communications and engagement, not mail transport or Autopilot tokens. That is the describe-level lane for city culture updates.
Full Explanation
An employee experience lead piloting Viva-style intranet and engage experiences for city culture posts and staff community updates should expect Viva to support communications and engagement experiences for employee communities at describe depth. That is Viva’s lane in the Microsoft 365 story: helping staff feel informed and connected through employee-experience communications and related engagement patterns—not taking over SMTP or device enrollment.
Claiming Viva exclusively replaces Exchange Online as the city’s SMTP mail transport fails because Viva is not the mail transport replacement narrative. Claiming Viva is only a Windows Autopilot enrollment token with no communications features fails because that confuses employee experience with device provisioning. Claiming Viva disables SharePoint pages whenever culture posts are published fails because engagement experiences are not designed to break intranet pages.
Exam caveat: describe-depth answers emphasize communications and engagement. You do not need every Viva module SKU memorized, but you must keep Viva out of Autopilot and Exchange-transport distractors.
Operational check: pilot culture posts and community updates on the appropriate employee-experience surfaces, keep Exchange for email transport, keep Autopilot for provisioning, confirm SharePoint intranet pages remain available as needed, and measure pilot success on staff reach and clarity—not on mail-routing metrics.