An administrator is validating the health of a BIG-IP DNS sync group. The sync group has two devices. The administrator wants to ensure that both devices are in sync and that the configuration is consistent. Which action should the administrator take?

Restart the bigd service on both devices.

Run a DNS query against both devices and compare the responses.

Check the sync status in the Configuration utility and verify that the configuration is synchronized.

Review the SNMP traps for any sync-related alerts.

A BIG-IP DNS administrator notices that a pool member is marked down. What is the first step in a systematic troubleshooting approach?

Disable the monitor to force the member up

Delete and recreate the pool member

Check the health monitor configuration and the member's response to the monitor

When viewing the status of a pool in BIG-IP DNS, what does a 'green' status for a pool member indicate?

The member is up and available to receive traffic

The member is down and will not receive traffic

The member is being tested for the first time

The member is disabled by an administrator

A BIG-IP DNS administrator notices that a pool member is marked down, but the member is actually up and responding to DNS queries. The monitor is a simple TCP monitor on port 53. What is the most likely cause of the false down status?

The monitor's interval is set too high.

The BIG-IP DNS device is not in the same network as the pool member.

The monitor is not appropriate for the service; a DNS monitor should be used.

The pool member's IP address is incorrect.

An administrator has just added a new data center to the BIG-IP DNS configuration. To validate that the data center is properly configured and operational, which action should the administrator take?

Check the SNMP community string on the data center's servers.

Run a packet capture on the BIG-IP DNS to see DNS queries.

Verify that the data center appears in the Configuration utility and that its associated servers are reporting health.

Review the DNS zone file for the data center's domain.

F5Certified Technology Specialist, BIG-IP DNS

Domain 2Objective 14

Objective 2.14 Given a Scenario Explain How to Validate System Health for Proper Operation 302 Practice Questions (Page 1)

Part of the Section 2: Deployment domain, which makes up ~30% of our current practice bank.

19questions here

4free pages

4concepts

Questions 1–5

1expert · medium
An administrator is validating the health of a BIG-IP DNS sync group. The sync group has two devices. The administrator wants to ensure that both devices are in sync and that the configuration is consistent. Which action should the administrator take?
Select an answer first
2foundation · easy
A BIG-IP DNS administrator notices that a pool member is marked down. What is the first step in a systematic troubleshooting approach?
Select an answer first
3foundation · easy
When viewing the status of a pool in BIG-IP DNS, what does a 'green' status for a pool member indicate?
Select an answer first
4application · medium
A BIG-IP DNS administrator notices that a pool member is marked down, but the member is actually up and responding to DNS queries. The monitor is a simple TCP monitor on port 53. What is the most likely cause of the false down status?
Select an answer first
5application · medium
An administrator has just added a new data center to the BIG-IP DNS configuration. To validate that the data center is properly configured and operational, which action should the administrator take?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to 302

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by F5. “302” is a trademark of its owner, used for identification only.