XK0-006 practice question on Authentication, 2026-11-05
Archived question for 2026-11-05. Domain: Security. Objective 3.1: Authentication. Original SecLern question, written for practice.
A TLS query to a directory server fails. ``` $ ldapsearch -x -H ldaps://10.0.0.8 -b dc=example,dc=com uid=alice TLS: hostname does not match CN in peer certificate ldap_sasl_bind(SIMPLE): Can't contact LDAP server (-1) ``` The server's certificate names ldap.example.com. Which change fixes it while keeping validation on?
Show the explanation
The URI host must match a name in the certificate.
Each option
- A. That turns off certificate validation and hides the problem. It would be right for a test that tolerates risk.
- B. That sends data without encryption. It would be right for no secure case.
- C. Port 636 is already used by ldaps. It would be right for a different port number.
- D (correct). Correct: The URI host must match a name in the certificate.
What this question tests
It maps to XK0-006 objective 3.1, Authentication: Authentication and authorisation Related ideas: ldap, tls, hostname.
The published topics under this objective, so you can check what you have covered:
- PAM stacks
- LDAP and Kerberos
- SSSD
More from the archive
- 2026-11-03: Firewall rules set on a Debian-family server are gone after a reboot. ``` $ sudo iptables -S INPUT -P INPUT ACCEPT ``` Which step makes iptables rules persistent on that server?
- 2026-11-04: A server with this ruleset can be reached by ssh, but its own DNS lookups time out. ``` table inet filter { chain input { type filter hook input priority filter; policy drop; tcp dport 22 accept } } ``` Which rule fixes the lookups?
- 2026-11-06: Which nftables feature lets one rule match a whole list of addresses?
- 2026-11-07: A scheduled script on web01 needs a Kerberos ticket without a person typing a password. A keytab exists at /etc/app.keytab for the principal app/web01.example.com. Which command obtains the ticket?
- 2026-11-08: 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?
- 2026-11-09: An administrator must allow ssh in the public zone only from 192.0.2.0/24 using a firewalld rich rule. Which rule text does this?
Start a daily session
Several questions at a time, aimed at your gaps.