352-001 · Question #215
As part of the network design, ACME Corporation requires the ability to export IPv6 information to better manage its network. Which version of NetFlow records is required to export this information?
The correct answer is E. 9. NetFlow version 9 is the first version to support IPv6 export because it uses a flexible template-based record format that accommodates variable-length fields including 128-bit IPv6 addresses.
Question
As part of the network design, ACME Corporation requires the ability to export IPv6 information to better manage its network. Which version of NetFlow records is required to export this information?
Options
- A5
- B6
- C7
- D8
- E9
How the community answered
(53 responses)- A6% (3)
- B4% (2)
- C2% (1)
- D2% (1)
- E87% (46)
Why each option
NetFlow version 9 is the first version to support IPv6 export because it uses a flexible template-based record format that accommodates variable-length fields including 128-bit IPv6 addresses.
NetFlow v5 uses a fixed 48-byte record format designed exclusively for IPv4 with hardcoded 32-bit address fields that cannot represent IPv6 addresses.
NetFlow v6 is also a fixed-format version supporting only IPv4 and was never widely deployed; it has no mechanism for IPv6 address fields.
NetFlow v7 was developed specifically for Catalyst switches with dedicated NetFlow hardware and is an IPv4-only fixed-format version.
NetFlow v8 added aggregation schemes to reduce export volume but retained the IPv4-only fixed record structure and cannot export IPv6 flow data.
NetFlow v9 introduced a template-based flexible record format standardized in RFC 3954, where templates define field types and lengths dynamically, allowing it to represent IPv6 source and destination addresses. All earlier versions (v5, v6, v7, v8) use fixed record formats with hardcoded 32-bit IPv4 address fields that cannot encode 128-bit IPv6 addresses.
Concept tested: NetFlow version 9 template-based IPv6 export
Source: https://datatracker.ietf.org/doc/html/rfc3954
Topics
Community Discussion
No community discussion yet for this question.