Your network contains an Active Directory domain named contoso.com. The domain contains a domain controller named DC1. DC1 has the DNS Server server role installed and hosts an Active Directory-integrated zone for contoso.com. The no-refresh interval and the refresh interval are both set to three days.
The Advanced DNS settings of DC1 are shown in the Advanced DNS Settings exhibit. (Click the Exhibit button.)
You open the properties of a static record named Server1 as shown in the Server1 Record exhibit.
(Click the Exhibit button.)
You discover that the scavenging process ran today, but the record for Server1 was not deleted.
You run dnscmd.exe and specify the ageallrecords parameter.
You need to identify when the record for Server1 will be deleted from the zone.
In how many days will the record be deleted?
A.
13
B.
10
C.
23
D.
7
Explanation:
Automatic scavenging. Automatic scavenging specifies that aging and scavenging of stale records is to be performed automatically by the server for any eligible zones at a recurring interval that is specified as the scavenging period. When you use automatic scavenging, the default scavenging period is one day, and the minimum allowed value that you can use for the scavenging period is one hour.
I still didn’t understand from the explanation. I’ve done some reading though – the TTL of 10 days really threw me. TTL does NOT have any effect on aging and scavenging; it’s how long the record is cached for. The reason the reoord was not scavenged today was that it is static, and static records are not scavenged. The dnscmd /ageallrecords gave it a time stamp and therefore removed its static status.
0
0