You have a domain controller that hosts an Active Directory-integrated zone.
On the domain controller, you run the following cmdlet:
PS C:\\> Get-DnsServerScavenging
NoRefreshInterval:2.00:00:00
RefreshInterval:3.00:00:00
ScavengingInterval:4.00:00:00
ScavengingState:True
LastScavengeTime:1/30/2014 9:10:36 AM
Use the drop-down menus to select the answer choice that completes each statement.
Hot Area:
Answer: 
Explanation:
First answer
* -NoRefreshInterval<TimeSpan>
Specifies a length of time as a TimeSpan object. NoRefreshInterval sets a period of time in which no refreshes are accepted for dynamically updated records.
Zones on the server inherit this value automatically.
This value is the interval between the last update of a timestamp for a record and the earliest time when the timestamp can be refreshed. The minimum value is 0.
The maximum value is 8760 hours (seven days).
* Here it is set to 2 days: NoRefreshInterval:2.00:00:00
Second answer
-ScavengingState<Boolean> (In this question it is set to true)
Enables or disables automatic scavenging of stale records. ScavengingState determines whether the DNS scavenging feature is enabled by default on newly
created zones. The acceptable values for this parameter are:
— $False. Disables scavenging. This is the default setting.
— $True. Enables scavenging
I believe the answer is correct, but the explanation is not exactly accurate.
Please see:
https://technet.microsoft.com/en-us/itpro/powershell/windows/dnsserver/set-dnsserverscavenging
i think asnwer is wrong
its 2 days for both
Answers are correct, however explanation of #2 is not relevant to the question.
From: https://technet.microsoft.com/en-us/library/cc771677(v=ws.11).aspx
When registering the record, the DNS server places a time stamp on this record based on current server time.
After the record time stamp is written, the DNS server does not accept refreshes for this record for the duration of the zone no-refresh interval. It can, however, accept updates before that time. For example, if the IP address for “host-a.example.microsoft.com” changes, the DNS server can accept the update. In this case, the server also updates (resets) the record time stamp.