Which IPv4 issue relates to the exhaustion of 32-bit addresses?

Which IPv4 issue relates to the exhaustion of 32-bit addresses?

• A. 32-bit address exhaustion
• B. IPv6 header length
• C. Hop Limit
• D. Payload Length

Answer: (A)

IPv4 relies on a 32-bit address space, which provides about 4.29 billion unique addresses. As the internet grew, that finite space began to run out, a situation known as 32-bit address exhaustion. This scarcity drove solutions like NAT to share a single public address among many devices and the transition to IPv6, which uses 128-bit addresses to vastly expand capacity. The other options refer to packet or header fields (such as how long the header is, how many hops a packet can take, or the payload size) and do not describe the limitation caused by the finite IPv4 address space.

IPv4 relies on a 32-bit address space, which provides about 4.29 billion unique addresses. As the internet grew, that finite space began to run out, a situation known as 32-bit address exhaustion. This scarcity drove solutions like NAT to share a single public address among many devices and the transition to IPv6, which uses 128-bit addresses to vastly expand capacity. The other options refer to packet or header fields (such as how long the header is, how many hops a packet can take, or the payload size) and do not describe the limitation caused by the finite IPv4 address space.