A transceiver is the correct answer because it is the Layer 1 (Physical Layer) component that physically terminates and converts fiber-optic signals on an SFP-capable switch. In CompTIA Network+ N10-009 objectives, transceivers-such as SFP, SFP+, QSFP, and QSFP+ modules-are explicitly identified as physical interface components that handle signal transmission and reception. These modules convert electrical signals from the switch into optical signals for fiber cabling (and vice versa), enabling communication over different media types and distances.
A modem is also a Layer 1 device, but its purpose is to modulate and demodulate signals for WAN technologies such as DSL or cable-it does not terminate fiber connections on switches. An Ethernet NIC provides network access for end devices like computers and servers and typically terminates copper Ethernet, not modular fiber interfaces on switches. A repeater regenerates and amplifies signals to extend cable distances but does not provide fiber termination or media conversion at a switch port.
According to Network+ standards, SFP transceivers are essential for flexible network design, allowing administrators to select appropriate fiber types (single-mode or multi-mode), wavelengths, and distances while remaining compliant with physical layer requirements.

Site-to-Site VPN: A site-to-site VPN is used to securely connect two networks, such as a company's headquarters and a branch location, over the internet. This type of VPN creates a secure tunnel for data transmission, ensuring confidentiality and integrity.
Split-tunnel VPN (A): Allows some traffic to bypass the VPN tunnel, which may not secure all communications.
Clientless VPN (B): Used for individual users to access the network without VPN client software.
Full-tunnel VPN (C): Typically used for individual user traffic rather than connecting two networks.
Reference: CompTIA Network+ Official Study Guide, Domain 1.3 (Secure Network Connections).

Availability refers to ensuring that data is accessible when needed. If a customer's data is accidentally deleted, it impacts availability, as the data can no longer be accessed.

Comprehensive and Detailed Explanation (paraphrased, aligned to N10-009):
In a spine-leaf architecture, endpoints (including servers, firewalls, and WAN/edge routers) connect to leaf switches. Leaf switches then uplink to spine switches; spine switches do not have endpoints connected directly to them. Therefore, a WAN router (an external/edge device) should connect to the leaf layer-often specifically to a "border leaf" that handles external connectivity.
Why not B. Core or D. Spine? In spine-leaf, "core" isn't a formal layer, and spines are designed only to interconnect leafs, not to terminate endpoints.
Why not A. Access? "Access" is a term from the traditional three-tier model (access-distribution-core). In modern spine-leaf language, the analogous layer for endpoint attachment is the leaf.
References (CompTIA Network+ N10-009):
Domain: Network Infrastructure - Data center and campus architectures (spine-leaf vs. three-tier), roles of leaf/spine, WAN/edge connectivity points.

SSO (Single Sign-On) allows an organization to use an identity provider (IdP) to centrally manage authentication and access across multiple SaaS applications. In the Network+ (N10-009) objectives, identity and access management concepts include federated authentication, centralized account control, and reducing password sprawl. With SSO, users authenticate once to the IdP, and the IdP then provides assertions/tokens to SaaS services (commonly using federation standards such as SAML or OIDC in real environments). This improves security (fewer reused passwords, easier MFA enforcement), streamlines user experience, and simplifies administration (provisioning/deprovisioning from one place).
PKI supports certificates and encryption/signing, but it is not the core mechanism for managing access across many SaaS apps via an IdP. TACACS+ is typically used for device administration (AAA) on network equipment, and RADIUS commonly supports network access (802.1X, VPN) AAA-both are important AAA protocols but do not describe the SaaS-wide "one login across many apps" capability. Therefore, SSO is the best answer.