Concept and mechanism
An active daemon does not demonstrate its consumer contract. In Apache, IP and port narrow candidates and hostname helps select the virtual host. A request by IP can receive the default site and hide failure on the business name. A useful check uses expected name, path, and response. Active chronyd can also remain unsynchronized; tracking and sources provide evidence different from process state. Avoid correcting time with an immediate step without assessing impact. In relayed DHCP, correlate giaddr and subnet selection before extending incorrect leases.
Guided application
For SMTP and proxy services, test permitted and denied access: TLS or HTTP 200 does not demonstrate correct authorization. For an outdated DNS secondary, check serial, transfer, and authorization rather than manually editing data without correcting the mechanism. Logs have another contract: delivery and durability. A disk-assisted rsyslog queue can retain messages in memory. SaveOnShutdown acts during orderly shutdown and does not guarantee persistence of that portion after a kill or power loss. In a fictional case, the collector returns but events are missing after the sender crashes. Define tolerable loss and rehearse persistence, limits, and recovery, including synchronization cost. More RAM can postpone saturation but does not demonstrate durability.
The health check receives 200 from the wrong site and declares healthy a service it never tested.
Common pitfalls
Open port as authorization; active process as synchronization; TCP as disk persistence.
Related topics: Automate with evidence · Operate and recover systems · Identity, PAM, and SSH
Write the expected contract and choose a test that actually observes it.
Reference: Apache 2.4 virtual hosts · Historical LFCE V3.18 (2018-06-12); exam retired 2022-05-01; technical references inspected 2026-09-30