Question 110
After a lab configuration change, verify: An IPv6-only lab application cannot listen because the host connection has no configured static IPv6 address. Which result most directly proves the desired system state?
Explanation
Correct Answer
`ip -6 addr show` lists the address and a local IPv6 connectivity test succeeds. This check confirms the expected effect of: Use `nmcli con mod lablan ipv6.method manual ipv6.addresses 2001:db8:1::10/64` with the documented lab gateway if required. It distinguishes the intended result from the original failure mechanism: IPv4 and IPv6 address families require their own connection settings.
Incorrect Answers
`hostnamectl` and `hostname -f` show the intended identity after the name is resolvable and after reboot. That verifies a separate lab task: A hostname change is applied only with the `hostname` runtime command and resets after restart. It does not validate the implementation required here: Use `nmcli con mod lablan ipv6.method manual ipv6.addresses 2001:db8:1::10/64` with the documented lab gateway if required.
`firewall-cmd --zone=public --list-services` contains SSH and firewalld remains running and enabled. That verifies a separate lab task: A firewall service was accidentally removed from the active zone, and an operator proposes disabling firewalld entirely. It does not validate the implementation required here: Use `nmcli con mod lablan ipv6.method manual ipv6.addresses 2001:db8:1::10/64` with the documented lab gateway if required.
A test from the management subnet succeeds and an unauthorized source is denied. That verifies a separate lab task: The server needs HTTPS only from one lab management subnet instead of from every source in the public zone. It does not validate the implementation required here: Use `nmcli con mod lablan ipv6.method manual ipv6.addresses 2001:db8:1::10/64` with the documented lab gateway if required.