What is a key characteristic of an ACI policy model?

Question

Options

• ALogical and concrete domains are separated.
• BAll configuration is carried out against concrete entities.
• CIt allows communications with newly connected devices.
• DNetwork administrators configure logical and physical system resources directly.

• A
  93% (13)
• C
  7% (1)

Explanation

ACI's policy model is fundamentally built on the separation of logical (abstract policy objects like tenants, EPGs, and contracts) from concrete domains (physical infrastructure like switches and interfaces). Administrators define intent in the logical layer, and the APIC automatically resolves and pushes that configuration to the concrete layer - this decoupling is the model's defining characteristic.

Why the distractors are wrong:

• B is incorrect because ACI administrators configure logical entities, not concrete ones directly - the whole point is to abstract away physical complexity.
• C describes a generic network capability, not something specific to ACI's policy model architecture.
• D contradicts ACI's design: admins configure the logical layer only, and ACI handles the mapping to physical resources automatically.

Memory tip: Think of ACI's policy model as a two-layer cake - the logical layer (your recipe/policy) sits on top of the concrete layer (the actual ingredients/hardware). You work with the recipe; ACI handles the kitchen. The separation is the model.

No community discussion yet for this question.