What this test measures
This test checks namespace discovery, exact query context, cache timing, record-chain dependencies, and application-selected destinations. Each difficulty has 25 questions; complete all three for 75. Easy emphasizes direct application, Medium combines evidence, and Hard asks you to choose among plausible diagnoses or evaluate what a result actually proves.
These are independent instructional questions, not released College Board items or a replica of Bluebook. The difficulty labels are local teaching choices; a score here does not predict an AP score.
For explanation before testing, use the dns resolution guide. Return to AP Networking Practice Tests by Topic to compare results across topics instead of repeating only your strongest subject.
For the prerequisite decision, review the related earlier topic test. This test adds its own focused scenarios and explanations.
Take the 25-question test for your selected level
Choose one answer to receive immediate feedback. Your first selection is scored; read the explanation before moving on. Use keyboard Tab to reach controls and arrow keys within the answer group. You can use these as untimed diagnostic practice, pausing to write your reasoning.
Changing difficulty or restarting clears the current attempt. Download your log first if you want to keep it.
Read the boundary before naming the fault
Representative reasoning
A resolver receives an address answer at 14:00 with a 900-second TTL. At 14:06, 360 seconds have elapsed, so ordinary unrefreshed cache freshness has 540 seconds left. Editing the authoritative record at 14:06 does not retroactively replace that cached answer. Keep the old service available for the applicable overlap and check the destination actually used by clients.
Record the exact absolute name, requested type, resolver, source context, response code, returned data and time. Trace authority discovery and every alias needed to reach terminal data. Then separate successful discovery from a successful connection to the discovered service.
Track each cached result
14:00 A answer received, TTL 900 seconds 14:06 Elapsed 360 seconds; remaining 540 seconds 14:06 Authoritative edit does not rewrite the old cache Verify Actual selected resolver, chain and destination
A tempting shortcut to avoid
A direct query to a new authoritative server can succeed while ordinary recursion follows a stale or wrong parent delegation. A working A lookup also does not prove an AAAA, MX or SRV query has the intended result. Match the query and application path before editing records.
A worked decision
A negative response is cached at 09:10 with 600 seconds remaining. A missing record is added at 09:12. The cache can still expire at 09:20 under ordinary unrefreshed handling. Verify current authoritative data, identify the negative cache and its lifetime, and retest through the intended resolver rather than repeatedly changing a correct new record.
For a second representation of the same skill, review the related topic explanation. Compare its evidence with your calculation or packet-path sketch rather than memorizing the answer letter.
How to read the explained question library
All 75 items are available below as ordinary HTML. Open a question to view its choices, answer, and explanation. For retrieval practice, read the prompt, write a decision without opening it, then compare your reasoning. This library also gives teachers a stable question ID for discussion.
The six groups contain two halves of each difficulty, with 12 and 13 questions respectively. The interactive version uses the same questions and answer keys.
Easy explained questions · 1–12
Start by identifying the function or applying one explicit rule. These 12 questions are 1–12 of the easy set.
dns-easy-1 · The zone school.example contains a host named lab. Which complete name identifies that host without relying on a search suffix?
- school.lab.example.
- lab.example.school.
- lab.school.example.
- example.school.lab.
Correct answer: C. lab.school.example.
DNS labels run from the most specific name toward the root. The trailing dot explicitly marks an absolute name.
dns-easy-2 · An administrator needs to identify which servers hold a zone's published data. Which record set is relevant?
- MX records for the zone alone
- NS records for that zone
- PTR records for every client
- The client's configured recursive server option alone
Correct answer: B. NS records for that zone
NS records identify the zone's name servers. Their reachability and authoritative contents still need checking.
dns-easy-3 · A DNS resolver obtains answers on a client's behalf and can reuse earlier answers. Which role does this describe?
- Ethernet MAC learning bridge
- DHCP relay
- Recursive caching resolver
- Authoritative server for every queried Internet zone
Correct answer: C. Recursive caching resolver
Recursion and caching are resolver functions. A server is authoritative only for zones it actually serves.
dns-easy-4 · A name server answers from its own configured zone data. What property identifies that role?
- Ownership of the client's DHCP assignment
- Authority for the zone concerned
- Permission to recurse for every client
- Authority for all names the server has ever cached
Correct answer: B. Authority for the zone concerned
Authority has a zone boundary. It does not mean the server knows or controls every name in the hierarchy.
dns-easy-5 · Which record points a mail domain toward its mail exchanger?
- AAAA
- MX
- NS alone
- PTR
Correct answer: B. MX
An MX record names a mail exchanger and includes preference. The exchanger's address and the mail service's reachability are separate requirements.
dns-easy-6 · Two MX records have preferences 10 and 30. Which is ordinarily preferred, assuming both are otherwise eligible?
- The record with preference 10
- The record with the larger numeric address
- The record with the longer hostname
- The record with preference 30
Correct answer: A. The record with preference 10
Lower MX preference values are preferred. Delivery behavior also depends on reachable exchangers and the mail system's implementation.
dns-easy-7 · Which DNS record is commonly queried to map an IPv4 address back to a name?
- CNAME at the gateway
- PTR in the appropriate reverse zone
- MX in the forward zone
- TXT in the DHCP scope
Correct answer: B. PTR in the appropriate reverse zone
Reverse resolution uses PTR data under the reverse namespace. It is maintained separately from the forward address record.
dns-easy-8 · What does the SOA record help describe?
- Every active transport connection
- Every client-side cached answer
- Every current client lease
- A zone's administrative and version-related information
Correct answer: D. A zone's administrative and version-related information
SOA data includes a serial and other zone parameters. It is not a substitute for client routing or transport-state information.
dns-easy-9 · A CNAME points camera.school.example to media.school.example. What kind of target is media.school.example?
- Another domain name
- A transport port number
- An IPv4 address stored in the alias field
- A DHCP client identifier
Correct answer: A. Another domain name
A CNAME target is a name, whose relevant record data must then be resolved. It is not an address stored in the alias field.
dns-easy-10 · A server responds REFUSED to a query. What does that response indicate?
- The name is proven nonexistent
- The zone is necessarily absent
- The server declined that query under its policy
- No DNS response arrived
Correct answer: C. The server declined that query under its policy
REFUSED is a received DNS result about processing policy. It differs from NXDOMAIN, SERVFAIL, and an unanswered query.
dns-easy-11 · A recursive lookup returns SERVFAIL. What is the careful first interpretation?
- The client definitely has no valid address
- Resolution failed at that resolver; the specific cause needs investigation
- The queried name definitely does not exist
- The server definitely rejected the query by policy
Correct answer: B. Resolution failed at that resolver; the specific cause needs investigation
SERVFAIL can have several causes, including upstream or validation problems. The response code alone does not locate the cause.
dns-easy-12 · NXDOMAIN and a timeout are observed in two separate tests. What is the main distinction?
- Both prove authoritative nonexistence
- NXDOMAIN proves the responder was unreachable
- Timeout proves a received negative answer
- NXDOMAIN is a name-error response; timeout means no usable reply arrived within the test interval
Correct answer: D. NXDOMAIN is a name-error response; timeout means no usable reply arrived within the test interval
A received answer and missing answer require different investigations. Keep resolver, name, type, and time with each result.
Easy explained questions · 13–25
Start by identifying the function or applying one explicit rule. These 13 questions are 13–25 of the easy set.
dns-easy-13 · A name exists but has no AAAA record; the response is NOERROR with no requested answer. What result is this commonly called?
- A recursive referral
- NODATA for that queried type
- A completed IPv6 service connection
- NXDOMAIN for the whole owner name
Correct answer: B. NODATA for that queried type
NODATA means the queried type is absent for the relevant existing name. It is distinct from a statement that the name does not exist.
dns-easy-14 · Which part of a DNS question distinguishes an address lookup from a mail-exchanger lookup?
- The query type
- The transaction ID alone
- The response's record order
- The resolver address alone
Correct answer: A. The query type
Name, type, and class define the question. Identical names queried for different types need not return equivalent answers.
dns-easy-15 · A record has 120 seconds of remaining TTL when received by a cache. Under ordinary caching with no refresh, how long may that entry remain fresh there?
- Until every application connection ends
- Until the lease expires
- 120 minutes
- Up to those remaining 120 seconds
Correct answer: D. Up to those remaining 120 seconds
TTL is a cache lifetime in seconds for DNS data. It does not govern leases or the duration of established application connections.
dns-easy-16 · A zone transfer is intended to copy zone data between authorized servers. Which restriction should be considered?
- Remove authoritative records to limit transfer access
- Allow any querying client to copy every zone
- Treat recursive-client permission as transfer permission
- Limit transfers to the intended recipients
Correct answer: D. Limit transfers to the intended recipients
Zone transfer access is a server-side administrative policy. A public lookup service need not expose full zone transfers to everyone.
dns-easy-17 · A host needs a service's protocol and port as well as its target name. Which record type can describe that information?
- PTR
- SRV
- A alone
- AAAA alone
Correct answer: B. SRV
SRV data includes service location information such as target and port. The service and its addresses still require separate validation.
dns-easy-18 · What does an ordinary DNS TXT record contain?
- An automatic endpoint firewall rule
- A replacement for every service port
- Text data associated with its owner name
- A command automatically executed by all resolvers
Correct answer: C. Text data associated with its owner name
Applications can give TXT content specific meaning. DNS storage alone does not make arbitrary text an executable network configuration.
dns-easy-19 · Why is a PTR answer insufficient as proof of a sender's identity?
- PTR permanently identifies one human
- PTR assigns an application role
- Reverse names are DNS data, not user authentication
- PTR alone verifies user identity
Correct answer: C. Reverse names are DNS data, not user authentication
A reverse name may help operations, but identity claims need the relevant authentication and trust checks.
dns-easy-20 · A client's hosts file supplies an address for a name. What must be considered when investigating application resolution?
- The local entry publishes a public record
- The entry updates the SOA serial automatically
- Every application must use only DNS
- Local name sources may override or differ from DNS results
Correct answer: D. Local name sources may override or differ from DNS results
Determine the name-resolution path the application actually uses. An explicit DNS test may not match a local override.
dns-easy-21 · A local resolver forwards certain queries to another resolver. What should be documented?
- Only the cached answer for an unrelated name
- Only the client-facing resolver address without forwarding scope
- Only whether the server process runs
- Which names or query classes use that forwarding path
Correct answer: D. Which names or query classes use that forwarding path
Forwarding policy introduces another dependency. Its scope matters when only some namespaces fail.
dns-easy-22 · Why use a complete hostname in a reproducible DNS test?
- It bypasses transport policy
- It removes ambiguity from search-list expansion
- It clears every resolver cache
- It guarantees the listener is running
Correct answer: B. It removes ambiguity from search-list expansion
An absolute name helps ensure different clients ask the same question. It does not validate the resulting address's service path.
dns-easy-23 · A DNS response includes several address records for one name. What should a service test identify?
- Which returned address the application actually selected
- Only the longest TTL
- Only that one returned address responds
- Only the first printed address regardless of selection
Correct answer: A. Which returned address the application actually selected
The selected destination determines the actual connection path. One successful returned address does not validate every alternative.
dns-easy-24 · What information should accompany a copied DNS answer in a troubleshooting note?
- Only a statement that DNS worked
- Exact name, type, resolver, response, and timestamp
- Only the name without resolver or type
- Only the returned address
Correct answer: B. Exact name, type, resolver, response, and timestamp
These fields make the lookup reviewable and distinguish answers from different views, caches, and times.
dns-easy-25 · A DNS answer is cryptographically validated by DNSSEC. What does that primarily support?
- Authenticity and integrity of the validated DNS data chain
- Confidentiality of every query
- Correct application permissions
- Unlimited service availability
Correct answer: A. Authenticity and integrity of the validated DNS data chain
DNSSEC validation concerns DNS data. It does not encrypt queries or prove that an application endpoint will accept the user.
Medium explained questions · 1–12
Combine the configuration with the symptom before selecting a decision. These 12 questions are 1–12 of the medium set.
dns-medium-1 · A fresh cache stores a TTL of 900 seconds at 14:00. No refresh or stale-serving behavior is used. At 14:06, what TTL remains?
- 1440 seconds
- 540 seconds
- 900 seconds
- 360 seconds
Correct answer: B. 540 seconds
Six minutes consume 360 seconds. The ordinary remaining lifetime is 900 minus 360, or 540 seconds.
dns-medium-2 · Resolver A returns an address for print.school.example, while resolver B returns REFUSED for the same type. What should be compared?
- Only the printer's transport listener
- Resolver query policy and client/source scope
- Only whether the name exists in any zone
- Only whether resolver A answered quickly
Correct answer: B. Resolver query policy and client/source scope
The received refusal identifies policy at B rather than proving the name is absent. Compare authorized recursion, views, and query scope.
dns-medium-3 · A forward record maps build.school.example to 192.0.2.70, but its reverse record names archive.school.example. What needs review?
- Whether forward and reverse data reflect the intended host identity
- Whether DHCP always controls both zones
- Whether the mismatch necessarily breaks TCP
- Whether PTR automatically rewrites A
Correct answer: A. Whether forward and reverse data reflect the intended host identity
Forward and reverse namespaces are maintained independently. The mismatch may affect operational checks without proving transport failure.
dns-medium-4 · A new MX points to mx.school.example, but that target has no usable address record. Which dependency is missing?
- A higher MX preference
- Address resolution for the exchanger target
- A PTR for every sender
- A CNAME at the mail domain instead of usable target data
Correct answer: B. Address resolution for the exchanger target
The MX names a host; delivery then needs its address and reachable mail service. A correct MX owner alone is insufficient.
dns-medium-5 · A CNAME for help.school.example points to retired.school.example, whose address was removed. What should be corrected?
- The intended alias target and its address data
- Only the alias label while retaining the retired target
- Only the resolver's reverse record
- Only the terminal record's TTL without repairing the chain
Correct answer: A. The intended alias target and its address data
The alias chain ends at a missing dependency. Restore the intended target relationship rather than infer that all resolution is unavailable.
dns-medium-6 · An internal resolver has a conditional forward for lab.school.example to an unreachable server. Public names still resolve. What should be investigated?
- The namespace-specific forwarding dependency
- Only the client's search list regardless of queried namespace
- A universal failure of all resolution
- Every public authoritative copy
Correct answer: A. The namespace-specific forwarding dependency
Selective namespace failure fits the forwarding rule's scope. Check the chosen upstream and policy/path for that set of names.
dns-medium-7 · Two authoritative servers return different SOA serials and different addresses for the same zone. What is the useful next check?
- Whether disagreement alone proves compromise
- Zone update distribution and the intended current data
- Whether one client has a faster link
- Whether serial values numerically equal host addresses
Correct answer: B. Zone update distribution and the intended current data
Inconsistent authoritative copies can create varying answers. Compare update/transfer state and intended data without inferring malicious activity from disagreement alone.
dns-medium-8 · A client queries short name files and sends files.west.school.example, but the intended host is files.east.school.example. Which setting explains the question mismatch?
- The MX preference
- The reverse lookup suffix
- The application's transport receive window
- Its effective search suffix/list
Correct answer: D. Its effective search suffix/list
The expanded question differs from the intended name. Confirm the application's actual expansion and use an absolute-name control test.
dns-medium-9 · An external authoritative server is reachable, but its parent delegates to obsolete name servers. What may fail?
- The reachable server's local data necessarily
- Only reverse resolution
- Discovery of the intended authority through the delegation path
- Every direct query to the reachable server
Correct answer: C. Discovery of the intended authority through the delegation path
A direct query can work while normal recursive discovery follows stale delegation. Inspect parent and child records separately.
dns-medium-10 · A name has A data but intentionally no AAAA. A diagnostic treats empty AAAA as the whole name being absent. What correction is needed?
- Treat every NOERROR as a requested address answer
- Delete the working A data
- Distinguish missing queried type from NXDOMAIN
- Create an unrelated PTR as a substitute
Correct answer: C. Distinguish missing queried type from NXDOMAIN
The query type determines what is missing. An existing IPv4-only name can legitimately lack an IPv6 address record.
dns-medium-11 · A resolver sends repeated upstream queries but receives no replies for one zone. What observation separates discovery from server reachability?
- Only a successful gateway ping
- Only the count of aliases
- Only the client's configured resolver address
- The selected authority addresses and traffic to/from those addresses
Correct answer: D. The selected authority addresses and traffic to/from those addresses
Trace which servers were selected and their request/reply paths. A lookup failure can arise after correct delegation discovery.
dns-medium-12 · An application retains an old destination after a fresh explicit DNS query returns the new one. What should be inspected?
- Only the authoritative record already checked
- Only the reverse namespace
- Only the resolver's process status
- Application caching, local overrides, connection reuse, and the effective resolver
Correct answer: D. Application caching, local overrides, connection reuse, and the effective resolver
The application's state can differ from a new diagnostic lookup. Determine its selected address before treating the fresh answer as proof of its behavior.
Medium explained questions · 13–25
Combine the configuration with the symptom before selecting a decision. These 13 questions are 13–25 of the medium set.
dns-medium-13 · A DNS reply's transaction ID does not match the outstanding query on that socket. Why may the client ignore it?
- The owner name must be absent
- All UDP replies require a TCP handshake
- The SOA serial is too high
- It does not match the request context
Correct answer: D. It does not match the request context
Clients associate replies with outstanding queries using request context. Receiving a DNS-shaped packet does not prove it is the usable response to this request.
dns-medium-14 · A local server answers queries for its hosted zone but refuses public-name recursion. Is that necessarily a fault?
- No; its intended role may be authoritative-only for those clients
- Yes, authoritative service proves recursive service
- Yes, every server must recurse for every source
- Only if reverse records exist
Correct answer: A. No; its intended role may be authoritative-only for those clients
Server role and access policy determine expected behavior. Verify the stated service rather than impose open recursion on an authoritative server.
dns-medium-15 · A record is scheduled to move tomorrow. Existing caches have a long TTL today. What makes a planned TTL reduction useful?
- Set TTL from the application's source port
- Reducing it early enough for old longer-lived entries to age before the move
- Lower TTL only after the old host shuts down
- Expect all stored lifetimes to change immediately
Correct answer: B. Reducing it early enough for old longer-lived entries to age before the move
A new lower TTL affects later cache refreshes, not the remaining lifetime already stored elsewhere. Plan overlap and verify the clients' actual destinations.
dns-medium-16 · A DNSSEC-validating resolver returns failure while a nonvalidating resolver returns the record. What should be checked before disabling validation?
- Only server process status
- Signature/delegation validation evidence and the intended trust chain
- Only a passing small UDP query
- Only the convenient nonvalidating result
Correct answer: B. Signature/delegation validation evidence and the intended trust chain
The difference may identify a validation problem. Investigate chain, signatures, timing, and authoritative data instead of removing assurance as the first repair.
dns-medium-17 · An internal-only service name is accidentally forwarded to a public resolver. What policy should be reviewed?
- The intended resolution path for that namespace
- Only a successful unrelated public lookup
- Only the web listener
- Only the server's public reverse name
Correct answer: A. The intended resolution path for that namespace
The application may be asking a server without the intended internal view. Correct scope and permitted dependencies rather than publish private data automatically.
dns-medium-18 · A change updates A data but leaves an old AAAA address serving the same name. What complete verification is needed?
- Only a working IPv4 connection
- Only a local resolver ping
- Test the intended service through each enabled returned family/address
- Only a successful A lookup
Correct answer: C. Test the intended service through each enabled returned family/address
Clients may select either supported family. Confirm that every retained service address is intended and usable, or correct the publication plan.
dns-medium-19 · A service's name resolves to three nodes, but one returns application errors. What should the DNS/task test record?
- The selected node address and its task outcome
- Only one healthy node's result
- Only the largest TTL
- Only that some A data exists
Correct answer: A. The selected node address and its task outcome
A pooled answer can hide a failing member. Correlate each chosen destination with service correctness before diagnosing the pool as uniformly healthy.
dns-medium-20 · A query succeeds only when using an absolute trailing-dot name; a resolver tool appends a suffix otherwise. What does the control establish?
- Both tests asked the identical owner name
- Question expansion changes the queried owner name
- The dot fixes a physical link
- The dot bypasses DNSSEC
Correct answer: B. Question expansion changes the queried owner name
The comparison isolates name construction. Read the actual question and search behavior rather than attributing the result to transport speed.
dns-medium-21 · An SOA serial advances on the primary, but a secondary still serves old records. Which administrative path needs inspection?
- Notification/transfer/update behavior between the authorized servers
- Only the secondary's process status
- Only the primary's edit screen
- Every client hosts file before authority comparison
Correct answer: A. Notification/transfer/update behavior between the authorized servers
The authoritative copies have diverged. Check the supported distribution mechanism and permissions rather than rely only on the primary's edit success.
dns-medium-22 · An NXDOMAIN reply for absent.school.example includes negative-caching SOA information. Why retain it in the case record?
- It changes client routing
- It prevents new records permanently
- It proves every name and type is absent
- It helps explain the duration and scope of cached nonexistence
Correct answer: D. It helps explain the duration and scope of cached nonexistence
Negative responses can be cached under defined rules. Record the name and TTL evidence so later differences can be interpreted without assuming immediate global refresh.
dns-medium-23 · A DNS client receives a response with a referral rather than the requested answer. What must happen for a nonrecursive resolution path?
- Assume NXDOMAIN
- Treat the referral as terminal address data
- Follow the relevant delegation toward an authority
- Assume recursion has already completed
Correct answer: C. Follow the relevant delegation toward an authority
A referral identifies a next authority to consult. It is not by itself the requested record set or an application success result.
dns-medium-24 · A DNS response has AA set for the answer concerned. What does that bit mean?
- Automatic confidentiality
- The responding server claims authority for the relevant answer
- Automatic application authorization
- Automatic DNSSEC validation
Correct answer: B. The responding server claims authority for the relevant answer
The authoritative-answer flag identifies a DNS role assertion. It should not be confused with cryptographic validation or user permission.
dns-medium-25 · An administrator flushes one laptop's DNS cache after a record correction. What remains possible?
- The recursive resolver or application still retains relevant state
- All caches worldwide were cleared
- All authoritative copies updated
- All established connections closed
Correct answer: A. The recursive resolver or application still retains relevant state
Cache layers and connection reuse have separate lifecycles. A local action affects only the state it actually clears.
Hard explained questions · 1–12
State what the evidence proves and reject conclusions that reach beyond it. These 12 questions are 1–12 of the hard set.
dns-hard-1 · A parent delegates a zone to ns.old.example, while the child zone lists ns.new.example. Direct queries to the new server succeed; ordinary recursion fails. Which comparison best addresses the discrepancy?
- Only the website's TCP listener
- Only every client's local suffix, regardless of the absolute query
- Only the new server's successful direct answer
- Parent delegation, needed name-server addresses, and actual selected authority path
Correct answer: D. Parent delegation, needed name-server addresses, and actual selected authority path
Normal discovery begins from the delegation path, which can differ from a manually selected direct target. Reconcile the intended parent/child information and verify recursive use.
dns-hard-2 · Two CNAMEs form a cycle: alpha.school.example points to beta.school.example, which points back to alpha. What repair is justified?
- Raise both TTLs so recursion can finish
- Allow broader client TCP access without changing the aliases
- Add PTR data while retaining the cycle
- Replace the loop with the intended finite chain to usable terminal data
Correct answer: D. Replace the loop with the intended finite chain to usable terminal data
A cyclic alias relationship cannot yield the intended terminal address. Correct the name relationships, then verify both fresh and cached client behavior.
dns-hard-3 · A validating resolver logs an expired zone signature; authoritative addresses are reachable and nonvalidating queries return data. What is the focused repair?
- Treat the returned unsigned view as equivalent assurance
- Change the client's subnet because authority is unreachable
- Disable all DNSSEC validation permanently as proof of success
- Correct signature/publication timing and verify the validation chain
Correct answer: D. Correct signature/publication timing and verify the validation chain
The validation evidence narrows the problem beyond basic reachability. Restore valid signed data and verify the intended trust path instead of simply bypassing the failed check.
dns-hard-4 · A negative answer cached at 09:10 has a stated 600-second remaining negative TTL. A record is added at 09:12. Under ordinary caching, when does that entry expire if not refreshed?
- 09:22
- 09:20
- 09:12 immediately
- 19:10
Correct answer: B. 09:20
The stored interval runs from receipt at 09:10. Creating authoritative data at 09:12 does not retroactively remove this cache entry; the stated expiry remains 09:20.
dns-hard-5 · During a hostname migration, the old A entry was cached for 3600 seconds just before the TTL was lowered to 60. What must the cutover plan allow for?
- Every cache expiring 60 seconds after the edit
- The already cached long lifetime, independent of the new lower TTL
- The SOA serial directly erasing each application's connections
- DHCP renewal instantly rewriting all resolver caches
Correct answer: B. The already cached long lifetime, independent of the new lower TTL
Lowering authoritative TTL changes later answers. Existing caches may retain their previous lifetime, so preserve a suitable overlap and verify real client destinations.
dns-hard-6 · A resolver serves expired DNS data under its documented serve-stale feature when upstream authority is unreachable. Does a past TTL expiry alone prove this response violates its design?
- No; stale-serving guarantees the endpoint is still correct
- Yes; the application must have forged the DNS response
- Yes; all implementations must discard every expired record immediately
- No; examine the supported stale-serving policy and outage context
Correct answer: D. No; examine the supported stale-serving policy and outage context
Some resolvers support defined stale-serving behavior. Determine its scope and status; it improves continuity but does not prove the old endpoint remains suitable.
dns-hard-7 · A recursive server listens on UDP and TCP 53. UDP answers work, but an ACL blocks TCP fallback after truncation on the actual client path. What should verification include?
- Only the presence of an A record in the zone file
- Only another small UDP query
- Only a successful server loopback TCP test
- The large-answer query's complete fallback exchange through the required path
Correct answer: D. The large-answer query's complete fallback exchange through the required path
The failing query requires more than a small-answer test. Verify protocol-specific policy, transport opening, and the actual response under the relevant client context.
dns-hard-8 · A name's A record is correct, but its CNAME alias is cached to a retired target with a longer remaining TTL. Which state should be traced?
- Only the terminal A record's current TTL
- Only the gateway's MAC aging timer
- Each alias-chain record and the application's selected terminal destination
- Only the client's PTR record
Correct answer: C. Each alias-chain record and the application's selected terminal destination
Alias and address records can have separate cache lifetimes. Trace the chain used by the application instead of treating one corrected terminal answer as complete migration.
dns-hard-9 · A company resolver forwards a child namespace to an internal authority. That authority's hostname is itself resolvable only through the failed child path under this design. What is the design problem?
- A guaranteed physical-layer loop
- A need to increase every client's lease length
- A circular discovery dependency for reaching the forwarding target
- A harmless mismatch between MX preferences
Correct answer: C. A circular discovery dependency for reaching the forwarding target
The resolver needs a usable way to locate the upstream before querying it. Remove the circular dependency through the supported resolution/addressing design and test cold-start behavior.
dns-hard-10 · Two clients ask the same absolute name and type at the same time, but policy selects different source-dependent views. Which conclusion is sound?
- Different intended answers can be legitimate; compare effective view and required service
- Equal query names require globally identical responses
- The shorter response always has the correct identity
- Any answer difference proves poisoning
Correct answer: A. Different intended answers can be legitimate; compare effective view and required service
Split views are intentional in some designs. Verify source context and desired answer/task behavior before classifying a difference as a fault.
dns-hard-11 · A browser uses an encrypted external resolver while the OS uses an internal conditional-forwarding resolver. Both return technically valid but different destinations. What should be established before editing public DNS?
- That encrypted transport guarantees the right internal endpoint
- The intended browser resolution policy and actual namespace/service path
- That an OS lookup proves the browser chose its address
- That the external answer must override the internal view
Correct answer: B. The intended browser resolution policy and actual namespace/service path
Resolution policy and application context differ. Confirm the permitted path and selected destination rather than changing zone data based on an unrelated resolver test.
dns-hard-12 · A mail domain has working MX and address data, but all referenced exchangers reject the transport connection. What has DNS established?
- A complete inbound mail policy repair
- Server discovery, not mail delivery readiness
- That the mail user has the right password
- Successful message acceptance
Correct answer: B. Server discovery, not mail delivery readiness
Name data can be correct while the service is unavailable. Follow transport and application evidence after discovering the intended exchangers.
Hard explained questions · 13–25
State what the evidence proves and reject conclusions that reach beyond it. These 13 questions are 13–25 of the hard set.
dns-hard-13 · After a zone transfer restriction changes, one authorized secondary stops updating but continues answering old data. What does complete remediation require?
- Change all MX preferences to hide the stale copy
- Restore intended update access and verify consistent current authoritative answers
- Flush one client cache without checking the secondary
- Permit transfers to every Internet source and test only the primary
Correct answer: B. Restore intended update access and verify consistent current authoritative answers
The secondary is an active serving dependency. Repair the authorized distribution path and validate current data on each relevant authoritative endpoint.
dns-hard-14 · A DNS tool reports an answer for api.school.example, but the application actually requests api2.school.example from its configuration. What should be corrected in the investigation?
- Flush every cache before examining the application's configuration
- Use the application's exact requested name and type as the test target
- Treat the similar-name answer as proof of application resolution
- Change the returned address at api.school.example without confirming intent
Correct answer: B. Use the application's exact requested name and type as the test target
Similar hostnames are different questions. Evidence for one cannot establish the other's resolution; reproduce the exact request before changing infrastructure.
dns-hard-15 · A recursive resolver can answer a popular cached domain but fails uncached queries because its upstream path is down. What test reveals the hidden dependency?
- Repeatedly querying only the same warm record
- A permitted fresh query with trace/log evidence of upstream discovery and reply
- Using the cached answer's low latency as universal health proof
- Checking only that the resolver's process is running
Correct answer: B. A permitted fresh query with trace/log evidence of upstream discovery and reply
Warm-cache success can hide an upstream outage. A safe uncached test and path evidence validate resolution beyond local reuse.
dns-hard-16 · A successful SRV query names service.school.example on port 8443. Testing the owner's name on 443 fails. What mismatch should be addressed?
- Treat the failed unrelated endpoint as proof of no SRV answer
- Delete the SRV record because all services use 443
- Raise the query TTL to install a listener
- Use the discovered target and port for the intended service test
Correct answer: D. Use the discovered target and port for the intended service test
Service discovery gives a specific target/port under the application's protocol. Test that advertised endpoint rather than substitute a different owner/port combination.
dns-hard-17 · An authoritative server incorrectly returns NXDOMAIN for an existing name with no queried MX type. What response distinction matters?
- Whether every MX target has a reverse record
- Whether the LAN uses a /24 prefix
- Nonexistence of the name versus absence of MX data at an existing name
- Whether the client uses a high source port
Correct answer: C. Nonexistence of the name versus absence of MX data at an existing name
NXDOMAIN can negatively affect name use more broadly than NODATA for one type. Correct the authoritative response/data behavior and examine cached consequences.
dns-hard-18 · A changed zone shows the new record on both authorities, but a resolver follows an old cached delegation to a retired server. What state is different?
- The server's TCP receive window
- The endpoint's Ethernet source address
- The delegation path cache, rather than only the host-record cache
- The new record's character encoding
Correct answer: C. The delegation path cache, rather than only the host-record cache
DNS resolution depends on cached discovery information as well as answer data. Track the authority selection and lifetime before claiming all caches see the new zone.
dns-hard-19 · An internal DNS failover test uses a warm client and passes. New clients fail because the alternate resolver has no configured forwarding path for the private zone. What did the test omit?
- Cold-resolution behavior through the alternate resolver's dependencies
- Whether a local cached address could connect
- Whether the original client had any DNS data
- Whether the backup resolver had an IP address
Correct answer: A. Cold-resolution behavior through the alternate resolver's dependencies
Warm state can bypass required resolution stages. Test both representative cached use and fresh discovery under the actual alternate configuration.
dns-hard-20 · A response's DNSSEC status is secure, but the published address belongs to the wrong application deployment due to an authorized editing mistake. What follows?
- Authenticated DNS data can still be operationally wrong; verify publication intent and task identity
- The client must ignore all validated data
- Encryption of the query would correct the address automatically
- DNSSEC guarantees the application deployment is correct
Correct answer: A. Authenticated DNS data can still be operationally wrong; verify publication intent and task identity
Validation protects provenance/integrity under the chain. It does not establish that an administrator chose the intended operational endpoint.
dns-hard-21 · A load-balanced name has four addresses; three work and one fails TLS hostname validation. What should the incident record identify?
- Only the resolver's total query count
- The selected failing address, requested identity, certificate result, and pool publication
- Only a claim that DNS is down
- Only a successful test against the first address
Correct answer: B. The selected failing address, requested identity, certificate result, and pool publication
A record set can resolve correctly while one endpoint serves a wrong identity. Correlate node-specific task results and repair the relevant publication or endpoint configuration.
dns-hard-22 · A query is forwarded between resolver A and resolver B, and each forwards that namespace back to the other. What should be repaired?
- Only the client's DHCP lease
- Only the website's return route
- Only the zone's reverse records
- The forwarding loop and intended authority path
Correct answer: D. The forwarding loop and intended authority path
Cyclic forwarding can prevent resolution despite reachable resolvers. Replace the loop with a supported path to authority and test a fresh question.
dns-hard-23 · A secondary's SOA serial matches the primary, but its returned host data differs. Can serial equality alone prove correct synchronization?
- Yes; equal serials authenticate identical contents cryptographically
- Yes; client caches must contain both copies
- No; compare actual data, view, and serving state as well
- Only if the answer contains IPv4
Correct answer: C. No; compare actual data, view, and serving state as well
A serial is operational version information, not a hash of all data. Configuration/views or incorrect publication can produce disagreement that the numeric comparison misses.
dns-hard-24 · A public lookup returns a private address accidentally published for an externally required service. What should a narrow repair verify?
- Unrestricted publication of every private host
- Correct external publication and external task access while preserving the intended internal view
- Only a direct LAN connection to the private address
- Only a public PTR record for the client
Correct answer: B. Correct external publication and external task access while preserving the intended internal view
The required external path needs a suitable intended endpoint. Preserve view boundaries and test both audiences instead of globally exposing internal names.
dns-hard-25 · Which evidence best supports closing a DNS migration case?
- Only one warm-cache lookup returning any address
- Only the primary zone editor reporting saved
- Consistent intended authority/delegation data, relevant cache-state checks, and task tests from required client views
- Only a successful ping to one name server
Correct answer: C. Consistent intended authority/delegation data, relevant cache-state checks, and task tests from required client views
Completion must cover publication, discovery, cache transition, and user task under the required views. Record specific outcomes and remaining planned overlap rather than a blanket DNS-is-fixed claim.
Use the result to choose your next study step
Draw the exact query path for one missed item. Put each cached record or delegation on its own row with the observation time and remaining lifetime. Add the selected service target and port; mark which lookup and which application operation have actually passed.
Record whether each miss concerned record and delegation paths, cache timelines, resolution policy. Copy one decisive observation and one rejected inference into your error log. Then review the focused supporting resource, explain a missed item without its options, and retry the relevant level after a separate study session.
For course-level transfer, move to Unit 1 practice, Unit 2 practice, Unit 4 practice. When the topic labels no longer guide your answer, use full practice exams and artifact analysis to combine selection, evidence, and explanation.
Teacher use
Assign one level as a diagnostic, collect explanations for two missed items, and group students by the missing step rather than total score alone. Ask pairs to compare a correct conclusion with a tempting overclaim. Do not treat repeated exposure to the same answer as independent evidence of mastery.