Skip to content

All certifications

XK0-006 practice question on Firewalls, 2026-11-08

Archived question for 2026-11-08. Domain: Security. Objective 3.2: Firewalls. Original SecLern question, written for practice.

A host runs Docker on an Ubuntu server with ufw enabled. ``` $ sudo ufw status Status: active To Action From -- ------ ---- 22/tcp ALLOW Anywhere $ docker run -d -p 8080:80 nginx $ curl -sI http://203.0.113.10:8080 | head -1 # run from another host HTTP/1.1 200 OK ``` Why is port 8080 reachable although ufw has no rule for it?

Show the explanation

Published container ports are handled in the forwarding path that ufw's input rules do not cover.

Each option

  • A (correct). Correct: Published container ports are handled in the forwarding path that ufw's input rules do not cover.
  • B. ufw has no such default. It would be right for no ufw policy.
  • C. Images cannot change host rules. It would be right for no container behavior.
  • D. curl options do not change firewall decisions. It would be right for no tool.

What this question tests

It maps to XK0-006 objective 3.2, Firewalls: Firewalls Related ideas: docker, ufw, port publishing.

The published topics under this objective, so you can check what you have covered:

  • Zones and services
  • Rich rules
  • nftables and iptables

More from the archive

Start a daily session

Several questions at a time, aimed at your gaps.