A housing authority separates enrichment automation from containment automation in architecture diagrams. What layering practice is that?
Select an answer to reveal the explanation.
Short Explanation
Enrichment looks; containment acts—draw them as separate floors. You'll miss it if you pick automation roles since it's types that tell you what just adds context versus what changes state. Housing IT diagrams should show which automation only adds context and which changes state.
Full Explanation
A housing authority that separates enrichment automation from containment automation in architecture diagrams is layering automation types as distinct civic architecture layers. Enrichment gathers context; containment changes system state (isolate host, disable account, block indicator). Drawing them apart makes blast radius, approval gates, and failure modes visible to leadership. Layering automation roles so enrichment and containment appear as distinct civic architecture layers misses the point because it swaps types for roles and hides the functional difference between reversible context jobs and high-impact municipal actions.
Why the other options fail by concept: Layering automation roles so enrichment and containment appear as distinct civic architecture layers prevents proper risk review because it frames the separation as organizational roles rather than automation types, leaving the different blast radius and approval needs of containment undefined. Layering automation types so enrichment and containment appear as distinct civic operational layers misplaces the separation because operational layers describe run-time procedures and staffing, not civic architecture layers where blast radius and approval controls for containment are enforced. Layering automation types so enrichment and containment appear as distinct civic data residency layers mislabels the architecture domain because data residency describes where civic data must be stored and governed, not civic architecture layers where blast radius and approval controls for containment are enforced.
Exam caveat: Layering in diagrams must match runtime enforcement—separate boxes with a shared service account that can still isolate hosts are theater. Operational check: review the housing authority architecture for distinct enrichment versus containment components, verify different approval or allowlist controls on containment, and test that an enrichment-only playbook cannot trigger host isolation.
Prefer to study offline? Printable PDF study book + test engine ($7.50, unofficial). These questions stay free here.