easyMultiple Choice
300-410 Practice Question: Which IPv6 FHS feature uses a 'device tracking'…
Which IPv6 FHS feature uses a 'device tracking' database to maintain reachability information for hosts?
⚠ Common exam trap
Cisco often tests the distinction between features that maintain the database (Device Tracking) versus features that use the database (e.g., DHCPv6 Guard, RA Guard), so the trap here is assuming that any FHS feature that interacts with host information must be the one that maintains the tracking database.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Device Tracking
Device Tracking is the correct answer because it is the IPv6 First Hop Security (FHS) feature that maintains a 'device tracking' database to monitor and store reachability information for hosts. This database tracks the IPv6 address, MAC address, and binding state of each host, enabling features like ND Inspection and DHCPv6 Guard to verify host reachability before forwarding traffic.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
RA Guard
Why it's wrong here
RA Guard filters inbound IPv6 Router Advertisement messages on access ports to block rogue routers; it inspects RA packets, not host reachability, and maintains no device tracking database. It is tempting because it is an FHS feature tied to IPv6 first-hop security, but its function is RA filtering, not host tracking.
- ✗
DHCPv6 Guard
Why it's wrong here
DHCPv6 Guard filters DHCPv6 server and client messages on access ports to prevent rogue DHCPv6 servers; it does not build a device tracking database of host reachability. It is tempting as a first-hop security feature, but its mechanism is DHCPv6 message filtering, not host tracking.
- ✓
Device Tracking
Why this is correct
IPv6 First Hop Security's device tracking feature builds and maintains a binding database of host reachability by snooping ND and DHCPv6 traffic, feeding that state to other FHS components such as IPv6 snooping and ND inspection to validate legitimate hosts.
- ✗
PACL
Why it's wrong here
PACL is a port-based access control list applied to Layer 2 switch ports to filter traffic; it performs stateless packet filtering and maintains no device tracking database. It is tempting because it is an FHS access-control feature, but its mechanism is ACL filtering, not host reachability tracking.
Quick reference
Access Control Model Comparison
| Model | Acronym | Who Controls Access? | Best For |
|---|---|---|---|
| Discretionary Access Control | DAC | Resource owner | Small teams, file shares |
| Mandatory Access Control | MAC | System / security labels | Classified govt / military |
| Role-Based Access Control | RBAC | Administrator (via roles) | Enterprise environments |
| Attribute-Based Access Control | ABAC | Policy engine (user + resource attributes) | Fine-grained, dynamic policies |
| Rule-Based Access Control | RuBAC | System rules / ACLs | Firewall rules, network ACLs |
Go deeper
Related to this question
About these practice questions
This 300-410 question is part of Courseiva's 1,401-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This 300-410 practice question is part of Courseiva's free Cisco certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 300-410 exam.