When a host fails to obtain an IP address from a DHCP server, it assigns itself an APIPA (Automatic Private IP Addressing) address in the 169.254.x.x range, commonly described as a "self-assigned IP." This prevents communication outside the local link, including reaching the default gateway.
B). RFC1918 addresses are private ranges (10.x.x.x, 172.16-31.x.x, 192.168.x.x), but these are not self- assigned.
C). If the TCP/IP stack were disabled, the host wouldn't have any IP at all.
D). If a static IP were assigned, it would show a configured value, not self-assigned.
References (CompTIA Network+ N10-009):
Domain: Network Troubleshooting - IP addressing issues, DHCP failures, APIPA behavior.

The correct answer is D. Link aggregation. Link aggregation combines multiple physical switch links into one logical connection. This increases available bandwidth and can also add redundancy, all without replacing the switch hardware itself. If users are experiencing slow throughput and the goal is to improve capacity using existing equipment, bundling links is a common and effective solution.
The other options do not directly increase throughput. SVI configuration provides Layer 3 interfaces for VLANs, but it does not add link capacity. VLAN trunking allows multiple VLANs to traverse one connection, but that does not increase bandwidth by itself. 802.1Q tagging identifies VLAN membership on tagged frames; it is related to trunking, not throughput expansion.
In many enterprise environments, link aggregation is implemented through standards such as LACP. This lets several ports act together as one logical channel, which can help distribute traffic more efficiently across the bundled interfaces. For Network+ exam scenarios, when the requirement is to improve throughput using the current switch hardware rather than buying faster switches, link aggregation is the most appropriate answer.

When configuring a firewall, the first step is identifying which ports, protocols, and services are required for normal business operations. This ensures only legitimate traffic is allowed. After establishing the required rules, a default deny rule is added for security.
B). Deny all rule is important, but it should come after defining required rules.
C). VPN access is a service to configure, but only after determining baseline needs.
D). Outbound traffic policies are part of refinement, not the first consideration.
References (CompTIA Network+ N10-009):
Domain: Network Security - Firewall configuration, rule order, least privilege.

The correct answer is Modify the CNAME record because a CNAME (Canonical Name) record maps one domain name (alias) to another domain name. If a user enters www.abc.com but is redirected to www.cba.
com, it is likely that the DNS configuration includes an incorrect CNAME entry pointing abc.com to cba.com.
Updating or correcting the CNAME record ensures the alias resolves to the intended host.
According to CompTIA Network+ (N10-009) objectives covering DNS record types, a CNAME record is used to alias one domain name to another, commonly for load balancing, CDN services, or website redirection.
A PTR record (Option B) is used for reverse DNS lookups (IP address to hostname) and does not control forward name resolution for websites. NTP settings (Option C) are used for time synchronization and have no impact on DNS resolution. A TXT record (Option D) stores descriptive text information (such as SPF, DKIM, or domain verification data) and does not affect website redirection.
Therefore, correcting the CNAME record resolves the issue and ensures users reach the correct website.

The correct answer is C. Address pool exhaustion. The client has an address in the 169.254.x.x range, which is an APIPA address automatically assigned when a system cannot get a valid IP lease from DHCP. The absence of both a default gateway and a DHCP server entry confirms that the laptop did not receive proper network settings from the DHCP service.
Among the choices, the most likely cause is that the DHCP server has no addresses left in its scope. When the address pool is exhausted, new or renewing clients cannot obtain a lease and must self-assign an APIPA address instead. A client with that kind of address cannot normally reach internal resources such as an intranet site because it lacks the correct network configuration.
The other options do not align with the evidence shown. A short DHCP lease duration could create frequent renewals, but it does not directly explain this output. An IIS malfunction would affect the web server, not the client's IP assignment. An IDS misconfiguration would not normally cause a host to self-assign a 169.254 address.
This is a DHCP-related problem, and from the available answers, address pool exhaustion is the best explanation.