Which objects does the operator expect on the Content Dashboard when a new council agenda pack is pushed?
Select an answer to reveal the explanation.
Short Explanation
Content Dashboard is the library card catalog: repositories, who got the pack, how many installs, and which version. BLAST counts and clone disks are VDI furniture; jailbreak-plus-mail is a different dashboard mash-up.
Full Explanation
On the Content Dashboard after a new council agenda pack is pushed, the operator should expect content repositories, assignments, install counts, and the published pack version. Those objects confirm the pack exists, who should receive it, how many devices installed it, and which version is current. BLAST gateway connection counts belong to Unified Access Gateway or Horizon edge monitoring. Instant-clone replica disk chains belong to Horizon image operations. Compliance jailbreak flags for unmanaged mail clients belong to compliance or Mail views, not Content Dashboard pack publish verification. Exam caveat: version mismatches between "published" and "installed" are normal until devices sync—do not delete the repository on first glance. Operational check: open Content Dashboard, confirm the new repository/pack version, verify assignments to council iPads, read install counts, and spot-check one iPad after a Hub sync. In municipal EUC operations, record the console path and the rejected alternatives in the change ticket so the next on-call technician repeats the same evidence-first workflow for city staff. Re-validate after the next maintenance window that the same control still holds for the civic tenant.