AZ-802 Practice Question: Implement and Manage On-Prem and Hybrid Networking
You are troubleshooting a Windows Server DNS environment where stale resource records are not being removed, leading to name resolution errors. Which THREE conditions must be met for DNS scavenging to successfully delete a stale record?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Scavenging must be enabled at the DNS server level.
DNS scavenging is a multi-step process that requires specific configurations at both the server and zone levels. If any of these components are misconfigured, the scavenging engine will not process the records, leading to an accumulation of outdated data that can interfere with network operations and IP management.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Scavenging must be enabled at the DNS server level.
Why this is correct
Even if individual zones are configured for scavenging, the master switch at the DNS server level must be turned on. This setting tells the DNS service to periodically run the scavenging algorithm and check all hosted zones for records that have exceeded their aging and refresh intervals.
- ✓
Scavenging and aging must be enabled at the specific zone level.
Why this is correct
Each DNS zone must be explicitly configured to allow aging and scavenging. This provides granular control, allowing administrators to protect static zones from accidental record deletion while ensuring that dynamic zones, which often contain temporary DHCP-assigned records, are regularly cleaned of obsolete entries that are no longer valid.
- ✗
The record must be a static record with a zero timestamp.
Why it's wrong here
Static records with a timestamp of zero are actually protected from scavenging. Scavenging only applies to dynamic records that have a non-zero timestamp, which indicates when the record was last refreshed. This prevents critical manually-created infrastructure records from being deleted by the automated cleanup process.
- ✓
The record must have existed past the sum of the No-refresh and Refresh intervals.
Why this is correct
A record is only considered stale after the No-refresh interval and the Refresh interval have both lapsed without the client updating its record. This combined duration ensures that the client has had ample opportunity to renew its lease and update its DNS information before the server deletes it.
- ✗
The DNS server must be a member of the Schema Admins group.
Why it's wrong here
DNS scavenging is a local service operation and does not require high-level Active Directory permissions like Schema Admins. The DNS service runs under the computer account or a service account which already has the necessary permissions to manage records within the Active Directory-integrated DNS zones it hosts.
Visual reference
About these practice questions
This AZ-802 question is part of Courseiva's 116-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Microsoft exam blueprint
This AZ-802 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-802 exam.