A core Kanban concept is managing flow by limiting work in progress (WIP). Kanban uses visual workflow boards and explicit WIP limits to prevent overloading the system, expose bottlenecks, and improve throughput and predictability. By limiting how many items can be “in progress” at once, teams finish work faster, reduce context switching, and stabilize cycle time—key goals of flow-based delivery. CompTIA Project+ includes Agile and adaptive concepts, and Kanban is commonly distinguished by its focus on continuous flow and WIP limits rather than timeboxed iterations.

Option A describes iteration-based alignment (more associated with Scrum’s sprint cadence). Option B (color-coding tasks) can be a visual technique but is not a defining Kanban principle. Option C (allocating resources to high-priority tasks) is a general management practice; Kanban does include prioritization, but its hallmark control is WIP limitation to optimize flow.

Therefore, the correct Kanban concept is limiting WIP to manage flow—a fundamental mechanism used to improve delivery efficiency and quality while keeping the system from becoming congested.