Q: 3
DRAG DROP Drag and drop the packet types from the left onto the correct descriptions on the right. 
Drag & Drop
Discussion
data plane packets → always forwarded user packets, control plane → network creation, management plane → operate/admin, services plane → high-priority user flows. Had something like this in a mock and that was the Cisco mapping. Pretty sure it's right but open to other takes.
data plane packets → always forwarded user traffic, control plane packets → network creation, management plane packets → operate/admin, services plane packets → high-priority user flows. Cisco loves making this confusing in some of the practice banks, but this matches how they define planes in their blueprints.
All good here: data plane-always forwarded, control plane-creation, management plane-operate/admin, services plane-high-priority user traffic.
Yeah, mapping goes like this: data plane to always forwarded, control plane for network creation, management plane for operation/admin stuff, services plane hits high-priority user traffic. Pretty sure that's what Cisco expects here.
data plane packets → always forwarded, control plane packets → creation of the network, management plane packets → operate the network, services plane packets → higher priority user traffic. Service vs management is a common trap here, I think these match Cisco docs.
data plane packets to always forwarded, control plane to network creation, management plane to operate/admin, services plane to high-priority. Solid Cisco mapping.
Not quite, I think services plane goes with the high-priority user flows, not management. Some exam questions try to trip you up and swap management/services, but here Cisco usually sticks to services = special/priority traffic. Anyone see it phrased differently in other practice sets?
data plane packets → user-generated always forwarded, control plane packets → used for network creation, management plane packets → operate/admin, services plane packets → high-priority user traffic. This lines up with Cisco's docs and what I saw in official practice. If anyone's got a different mapping let me know but this fits ENARSI objectives.
Cisco official guide clarifies this split: data is regular user traffic, control builds routes, management is admin functions (SSH/SNMP), services plane handles user flows needing extra priority. Practice labs help nail this mapping.
data plane packets → always forwarded, control plane packets → creation, management plane packets → operate the network, services plane packets → higher priority user traffic.
I don't think management plane should go with "high priority user traffic". That's usually service plane like VoIP. Easy to mix up since management sounds important, but it's more about device admin (SSH, SNMP). Common trap question, Cisco docs back this order. Disagree?
I don't think management plane should go with "high priority user traffic". That's usually service plane like VoIP. Easy to mix up since management sounds important, but it's more about device admin (SSH, SNMP). Common trap question, Cisco docs back this order. Disagree?
Be respectful. No spam.
