Free 302 Practice Test Questions and Answers (2026)

In high-availability (HA) network architecture and F5 incident severity management, a "site at risk" condition occurs when system fault tolerance is compromised. When one unit in an HA pair fails, redundant failover capability is lost entirely. Although traffic may currently be processing normally through the active unit, any secondary hardware fault, power loss, or software crash on the surviving BIG-IP device will immediately cause an uncontrolled, complete site outage. Therefore, a failure of a redundant unit explicitly signals that the site is operating without redundancy and is at elevated risk of severe operational downtime.

B. An employee departure is an administrative or human resources matter that does not directly indicate an active technical fault or redundancy loss on the network infrastructure.

1. F5 Networks Official Documentation: K1633: Overview of F5 technical support case severity levels. F5 Knowledge Base.

2. F5 Networks Official Documentation: BIG-IP Device Service Clustering: Administration, Chapter: High Availability and Failover Options.

When BIG-IP Global Traffic Manager (GTM) processes a DNS resolution request, it initially attempts to select an available pool member using the configured Preferred load balancing method. If the Preferred method fails to yield an available virtual server—due to resource exhaustion, failed monitor health checks, or restrictive ratio conditions—the BIG-IP GTM system automatically transitions to the Alternate load balancing method configured on the pool. This built-in multi-tier evaluation ensures continuous application delivery by attempting a secondary algorithm before resorting to fallback modes or returning a BIND/No Answer response to the querying client.

B: The load balancing evaluation is performed directly by the local BIG-IP GTM system itself, not by any third-party system.

1. F5 Networks Official Documentation, "BIG-IP DNS: Load Balancing Overview," Section: Alternate Load Balancing Method Selection Logic.

2. F5 Networks Technical Knowledge Base, "K7032: The order of preference for GTM load balancing methods," Paragraph 2: Preferred and Alternate Failover Logic.

The process of querying the Domain Name System to determine the IP address associated with a given Fully Qualified Domain Name (FQDN) is formally defined as name resolution or a DNS lookup. During this operation, a client resolver issues a DNS query to a recursive DNS server, which iterates through root, top-level domain (TLD), and authoritative name servers until it locates the matching resource record (such as an A or AAAA record). In an F5 BIG-IP DNS deployment, name resolution is intercepted or handled by listener objects, allowing the BIG-IP system to return dynamically evaluated IP addresses to client queries based on real-time health monitors, load balancing algorithms, and geolocation policies.

B. Routing is the Layer 3 process of forwarding IP packets across network boundaries towards their destination network, independent of domain name queries.
C. Switching is the Layer 2 network operation of forwarding data frames between hardware devices on a local area network using MAC address tables.
D. MAC lookup refers to inspecting a device's hardware address table within network switches, which operates exclusively at Layer 2 for frame delivery.
E. Nslookup is a specific command-line administration tool used to query DNS servers, not the generic architectural term for the resolution process.

- F5 Networks. "BIG-IP DNS Concepts." Official Vendor Documentation, Section: Understanding DNS Query Processing.

- RFC 1034: Domain Names - Concepts and Facilities, Section 5 "Resolvers", Internet Engineering Task Force (IETF), 1987. https://doi.org/10.17487/RFC1034

- Comer, D. E. "Internetworking with TCP/IP Vol 1: Principles, Protocols, and Architecture." Pearson, Chapter on Name Resolution.

In DNS hierarchy and administration, a lame delegation occurs when a parent domain's NS records delegate a zone to a specific name server, but that server is incapable of providing authoritative answers for the delegated domain. This happens when the designated responder is not configured as authoritative for the zone, responds with errors like REFUSED, experiences severe latency, or fails to respond altogether. Lame delegations degrade DNS performance, cause delays, and lead to resolution failures across the Internet. BIG-IP DNS monitors and detects lame delegations during health checks and recursive queries to ensure efficient path selection and accurate traffic distribution.

Option B: This describes standard iterative referral processing rather than a configuration error or failure condition known as a lame delegation.

1. IETF RFC 1912: Common DNS Operational and Configuration Errors, Section 2.8 "Lame delegations".

2. F5 BIG-IP DNS Manual: "Managing DNS Zones and Delegation Health Monitoring".

Within the topology record configuration of BIG-IP DNS (GTM), the Request Source builder component represents the specific matching criteria used to identify where an incoming DNS query originated. Administrators configure the Request Source by selecting parameters such as IP address subnets, local DNS (LDNS) IP ranges, geographic countries, states, continents, or specific ISP networks. When a client's LDNS server sends a resolution request, BIG-IP DNS compares the query's source IP address against these configured Request Source criteria. Once a match is confirmed, BIG-IP DNS applies the corresponding topology rule to direct the client to the designated destination resource, ensuring precise location-aware traffic steering.

B: FIFO (First In, First Out) is a queue scheduling method, not a Request Source builder component or location identification criterion in topology records.

1. F5 Networks Official Documentation: "BIG-IP DNS Configuration Guide", Section: Defining Request Sources for Topology Records, v16.1.x.

2. F5 Support KB Article K13412: "Overview of BIG-IP DNS topology load balancing", F5 Support Portal.

According to RFC 1035 and RFC 7766, DNS resolution for any DNS record type (A, AAAA, MX, SOA, TXT, etc.) can be performed over a TCP connection. While UDP port 53 is the traditional transport mechanism for speed and low overhead, TCP port 53 is an integral part of the standard DNS specification used for fallback, large responses, zone transfers, and enhanced transport reliability.

The option "False" is incorrect because TCP is a fully recognized and standardized transport protocol for standard DNS resolution operations, not limited solely to zone transfers or specific record types.

1. RFC 7766 - DNS Transport over TCP - Implementation Requirements, Section 4 "Requirement on DNS Clients and Servers".

2. F5 Networks Official Documentation - BIG-IP LTM/DNS Profile Reference: TCP Profile and DNS Profile interaction.

3. RFC 1035 - Domain Names - Implementation and Specification, Section 4.2 "Transport".

The BIG-IP product license file (/config/bigip.license) is included by default inside the UCS archive file. This ensures that system re-licensing information is preserved alongside configuration data when restoring a device backup.

Selecting [False] is incorrect because the system license (bigip.license) is a standard, default constituent of the UCS file archive set.

1. F5 Support Knowledge Base, K4423: Overview of UCS archives, F5, Inc., Section: "Files included in a UCS archive".

2. F5 Support Knowledge Base, K13132: Backing up and restoring BIG-IP configuration files using tmsh, F5, Inc., Section: "UCS Archive Details".

3. F5 BIG-IP System: Administration Guide, Version 15.x/16.x/17.x, F5, Inc., Chapter: "Licensing and Configuration Archives".

An SRV (Service) resource record in DNS (as defined in RFC 2782 and supported in BIG-IP DNS) specifies the following parameters: Service name, Protocol (e.g., TCP or UDP), Domain Name, TTL, Class, Priority, Weight, Port, and Target host. "Alias Service name" is not a defined parameter of an SRV record. Furthermore, RFC 2782 explicitly specifies that the Target field must point to a canonical hostname with valid A or AAAA records, rather than an alias.

Marking this statement as True is incorrect because "Alias Service name" is not a standard attribute or field in the DNS SRV record structure.

1. RFC 2782 - A DNS RR for specifying the location of services (DNS SRV), Section "Format of the SRV RR". https://doi.org/10.17487/RFC2782

2. F5 Networks Official Documentation: BIG-IP DNS Concepts and Configuration Guides, Chapter: "Managing Resource Records and Zone Files".

While DNS queries typically use UDP, the DNS protocol specification (RFC 1035 / RFC 7766) explicitly allows DNS queries—including SOA record lookups—to be transmitted over a standard TCP connection (port 53). Clients resort to TCP DNS lookups when responses exceed the maximum allowable UDP payload size, when truncation (TC bit) occurs, or when network/security policies enforce TCP transport.

The option "False" is incorrect because TCP is a fully standard and supported transport protocol for all types of DNS record queries, including SOA lookups.

1. RFC 1035 - Domain Names - Implementation and Specification, Section 4.2.2 "TCP usage".

2. RFC 7766 - DNS Transport over TCP - Implementation Requirements, Section 5 "Transport Selection".

3. F5 Networks Official Documentation - BIG-IP DNS Services / Manual Chapter: Configuring DNS Profiles.

In standard BIG-IP SSL/TLS administration workflow, after a Certificate Authority issues the signed digital certificate, the administrator must receive and store the certificate file in a specific local directory location (or stage it via the web interface) prior to executing the installation/import step into the BIG-IP system database.

Selecting "False" is incorrect because the installation action in BIG-IP relies on referencing the received certificate file stored in a accessible file system directory before it can be applied to SSL profiles.

1. F5 Knowledge Base Solution K13454: Importing SSL certificates and keys using the Configuration Utility or tmsh. F5 Official Technical Support Documentation.

2. F5 BIG-IP System: SSL Certificates Management Guide, F5 Official Documentation.