On Core-SW01, the ports are configured with LACP (mode active) for link aggregation. On Core-SW02, the ports are configured as independent trunks, not as part of an LACP group. Because of this mismatch, LACP cannot form the bundle, and the aggregated ports on SW01 will go into a suspended state.
A). CRC errors suggest cabling or signal integrity issues, not config mismatch.
B). Error disabled occurs when a violation (like BPDU guard or port security) disables the port, not LACP mismatch.
C). Administratively down indicates a shutdown command, not the case here.
References (CompTIA Network+ N10-009):
Domain: Network Troubleshooting - Port-channel/LACP configuration issues, interface states.

To redirect a network resource that has moved from a local network to a Software-as-a-Service (SaaS) solution, the network administrator needs to configure a DNS record that maps an alias to the new canonical name (hostname) of the SaaS provider's server. The CNAME (Canonical Name) record is used to alias one domain name to another, effectively redirecting requests to the new hostname without needing to update the IP address directly. This is ideal for SaaS solutions, where the provider's server hostname is used, and the IP address may change dynamically.
Why not TXT? A TXT record is used to store arbitrary text data, such as SPF records for email authentication or verification strings, not for redirecting resources.
Why not AAA? There is no such thing as an "AAA" record in DNS. This might be a typo for AAAA (IPv6 address record), but AAAA maps a hostname to an IPv6 address, not an alias.
Why not PTR? A PTR record is used for reverse DNS lookups (mapping an IP address to a hostname), not for redirecting a resource to a new hostname.
Reference:CompTIA Network+ N10-009 Objective 1.5: Compare and contrast common network services and ports. The CNAME record is discussed under DNS configuration in the CompTIA Network+ Certification Study Guide (e.g., Mike Meyers' CompTIA Network+ Guide, Chapter 7: TCP/IP Applications). The guide explains that CNAME records are used to create aliases for hostnames, particularly useful for redirecting services to external providers like SaaS solutions.

The answer is D. BGP . When a company wants a redundant internet connection , especially across more than one external path or provider, Border Gateway Protocol (BGP) is the routing technology most commonly associated with that design. BGP is used between autonomous systems and is the standard protocol for making routing decisions across the internet or between an organization and one or more ISPs.
The other options are interior routing protocols. EIGRP , RIPv2 , and OSPF are generally used inside an organization to exchange routes within a private network environment. They are not the normal answer when the question specifically says internet connection redundancy . That wording points outward, beyond the internal LAN or campus routing domain.
In practical terms, BGP gives administrators a way to influence path selection, advertise network prefixes, and maintain reachability if one outside connection fails. That is why it appears in questions involving multihoming, ISP failover, or resilient edge connectivity. Since the scenario mentions redundant firewalls and a need for a redundant internet connection, the best match is the routing technology designed for external route exchange. For Network+, that technology is BGP .

An IP Helper (IP Helper Address) allows DHCP requests to pass through routers and reach a DHCP server on another network.
* DHCP broadcasts are not forwarded across routers by default, so an IP Helper Address is needed to relay the request.
* This is crucial for large networks where a single DHCP server serves multiple subnets.
* Option B (Reservation): Ensures a specific IP address is assigned to a MAC address but does not relay DHCP across networks.
* Option C (Exclusion): Prevents specific IP addresses from being assigned, but does not help with DHCP relay.
* Option D (Scope): Defines the range of IP addresses available for DHCP clients but does not assist in cross-network communication.
? Reference: CompTIA Network+ (N10-009) Official Study Guide - Section: DHCP and IP Addressing

The correct answer is SNMP (Simple Network Management Protocol) because it is specifically designed to collect and transmit network management and status information between managed devices and management systems. According to CompTIA Network+ (N10-009) objectives, SNMP is used for monitoring and managing network devices such as routers, switches, servers, and printers.
SNMP operates using a manager-agent model. The SNMP manager (such as a network monitoring server) communicates with SNMP agents installed on network devices. Agents send traps and inform messages, which are unsolicited status alerts indicating events such as device failures, high CPU usage, or link outages.
The manager can also poll agents to retrieve performance metrics and configuration details stored in the Management Information Base (MIB).
SSH (Option A) is used for secure remote administration. DHCP (Option B) dynamically assigns IP addresses. NTP (Option C) synchronizes time between devices. None of these protocols are designed for network status monitoring and alert messaging.
Therefore, SNMP is the correct protocol for sending networking status messages between devices and management systems.
Bottom of Form