CompTIA Security+ SY0-701 Practice Test 17
Question 160
The security team has installed an MFA-protected jump server in an isolated management zone for production database administration. However, network testing shows that ordinary office laptops can still SSH directly to database hosts, bypassing the jump server and its session recorder. Which rule design makes the hardened management path mandatory rather than merely optional?
- Retain the broad office-to-database SSH route because users can voluntarily choose the more secure jump server
- Deny management traffic from ordinary office subnets and allow it to database hosts only from the authenticated, monitored jump server
- Allow the new management VLAN to reach every application and storage service, since access through it has already passed MFA
- Publish the jump server's SSH listener directly to the Internet while keeping the old office-to-database route for convenience
Explanation
Correct Answer
B:The security boundary must restrict database-host management ports to the hardened jump server's controlled management-zone address or identity, rejecting direct office-subnet SSH connections. Administrators authenticate individually through the existing MFA gateway, with session recording, authorization and time-bounded privileges before reaching a permitted database target. Engineers should verify the negative test from ordinary laptops and the positive test from the bastion, including return traffic and emergency procedures. The precise decision is about enforcing the one allowed route after the jump server already exists, not simply choosing to deploy a jump server. The gateway remains a highly privileged asset requiring monitoring and patching.
Incorrect Answers
A:Providing a bastion as an option does not eliminate a direct path that attackers or administrators can continue using from higher-risk workstations. An employee laptop may be compromised through routine browsing or email, and network reachability to privileged database ports enables attempts that evade the bastion's recording controls. The organization must enforce the approved traffic path through firewall or host-based rules rather than rely on users to choose it. Optional use is appropriate only when direct access has been assessed as separately authorized, which is not the case here.
C:A management network can contain privileged access tools, but its existence does not authorize its hosts to reach every workload or service. Broad route permissions risk lateral movement from a compromised jump server into systems unrelated to database administration. The requested configuration should enumerate only necessary database management destinations and ports, and should log permitted and denied attempts. MFA authenticates administrators to the gateway; it does not replace network least privilege for subsequent connections.
D:A publicly exposed bastion can sometimes be protected through carefully designed gateways, but direct publication of its SSH listener increases attack surface and is unnecessary when a private management network is available. Keeping the office-to-database bypass also defeats the centralized session recorder. The scenario specifies an isolated administration zone and demands mandatory use of that path. A safer design limits access to the bastion through approved private or authenticated remote channels and denies direct management from everyday office endpoints.
Question 161
A network security sensor receives copies of switch traffic through a mirror port. It detects a suspicious packet sequence and sends an alert, but the packet continues to the destination because the sensor is not in the forwarding path. Which description is accurate?
- An inline IPS that automatically blocks the original packet
- A passive network IDS providing detection and alerts without inline prevention
- A layer-two access-control device that replaces switch forwarding decisions
- A transparent proxy that terminates the clients' TCP sessions
Explanation
Correct Answer
B:A passive IDS analyzes a copy of network packets and raises alerts when signatures or behavioral rules indicate suspicious activity. Because it receives mirrored traffic rather than forwarding the actual packets, its default action is detection, not direct blocking. Security teams can use IDS alerts to investigate or to initiate actions on firewalls and switches, but those downstream integrations must be designed and verified separately. The mirrored-port configuration explains why the suspicious packet was delivered even though detection succeeded. Sensor coverage, packet loss, encrypted payload visibility, and alert tuning can limit effectiveness. The correct classification depends on placement and enforcement capability rather than whether the device recognizes malicious patterns.
Incorrect Answers
A:An inline IPS must be placed in a position where it can enforce a drop, reject, or other active response on the original traffic path. A sensor observing mirrored copies normally cannot stop packets already forwarded by the switch. It may trigger a separate containment workflow using other equipment, but that is distinct from inline prevention. Calling it an IPS here would overstate the direct enforcement capability described.
C:A switch makes forwarding decisions using its own tables and configured security features. A passive sensor on a mirror port does not replace those decisions or necessarily participate in access control. A separate network access-control system could enforce port admission, but the described sensor is not exercising that function. The distinction matters because detection on copies of traffic does not prevent the initial frame from arriving.
D:A transparent proxy is normally placed in a path where it can receive, relay, or terminate sessions on behalf of endpoints. A passive mirror-port listener merely sees copies and cannot reliably interpose itself in existing TCP exchanges. The scenario provides no evidence of proxying or termination. The sensor may log session metadata, but that observation does not make it a traffic-intercepting proxy.
Question 162
A payment processor has already placed its transaction database in a separate security VLAN, but the interzone firewall still permits TCP 5432 from every internal subnet. Only two named application servers should issue SQL queries, and database administrators use a dedicated management jump host. Which policy change actually enforces the intended payment-zone trust boundary?
- Keep broad internal TCP 5432 access and rely on database passwords to compensate for unnecessary network paths
- Allow SQL traffic from employee and printer VLANs whenever the clients complete a TLS handshake
- Default-deny database-zone ingress, allow SQL only from the two named application servers, and separately limit administrative access to the jump host
- Require all database nodes to accept SQL from any Internet source so vendor troubleshooting remains straightforward
Explanation
Correct Answer
C:A default-deny rule set with explicit SQL permits for the two approved application servers removes unnecessary east-west reachability into the payment database. Administrative flows can be separately restricted to the hardened jump host, with authentication, logging, and established change controls. Stateful return traffic should be allowed only as needed for established sessions, and the exact allowed ports and identities should be validated against the running application. The crucial distinction is that the VLAN boundary has already been built; security now depends on enforcing a least-privilege rule set at that boundary. This tests the actual permitted source/port relationship, not merely whether a flat network should be segmented someday.
Incorrect Answers
A:Database authentication is important for verifying application and administrator identities, but a broadly reachable service exposes the database protocol to many unnecessary hosts. A compromised workstation can still attempt credential attacks or exploit protocol weaknesses even if the SQL account password is strong. The question describes a separate VLAN that already exists but is undermined by its permissive firewall rules. Therefore the missing control is a narrow cross-zone permitlist, not merely trusting users to authenticate correctly to a widely accessible listener.
B:TLS can protect confidentiality and server identity for permitted SQL sessions, but it does not establish that an arbitrary employee or printer workstation is an authorized database application client. The two named application servers are the only approved transaction sources. Letting entire user VLANs connect after negotiating TLS would preserve unnecessary attack paths into the payment zone. Transport protection must accompany, not replace, source-specific network access rules that constrain which hosts may initiate the database workflow.
D:Publishing the database listener to the Internet would substantially expand the attack surface and violate the stated business dependency on only two internal application servers. Remote vendors can receive constrained, authenticated administrative access through a managed path without direct public SQL connectivity. Externally visible database services attract credential attacks and vulnerability scanning even when encryption is enabled. The interzone firewall should eliminate unnecessary sources rather than add more.
Question 163
An inline inspection appliance protects a hospital network that carries time-sensitive patient-monitoring messages. The appliance might fail, and the service owner explicitly prioritizes continued telemetry delivery over blocking traffic during that single-device failure. What failure behavior fits this documented requirement?
- Fail closed by dropping all traffic whenever the appliance is unavailable
- Fail open to preserve traffic forwarding while alerting operators and invoking a monitored replacement path
- Disable all network logging so device failures are invisible
- Leave the forwarding behavior undefined until the first real outage
Explanation
Correct Answer
B:Fail-open behavior allows forwarding to continue when the inline inspector is unavailable, favoring availability over immediate inspection enforcement. In this patient-monitoring scenario, leadership has explicitly prioritized telemetry delivery during this defined failure, making fail open the aligned design. The bypass condition should be monitored, logged, and alarmed so operators restore protection promptly; redundancy and health-checked failover can further reduce uninspected exposure. Fail open creates residual security risk because malicious traffic may pass unchecked during bypass. That risk must be acknowledged and bounded by other controls, not hidden behind an availability claim. The architectural decision is determined by this service's safety-critical continuity requirement, not by assuming all inline devices should behave alike.
Incorrect Answers
A:Fail-closed behavior blocks traffic when enforcement cannot be guaranteed. That can be appropriate for highly sensitive data paths where unauthorized traffic is unacceptable, but it contradicts this service owner's explicit requirement that life-critical telemetry continue during an appliance failure. A closed response might create an immediate availability or safety problem. The decision must follow documented business and clinical risk priorities rather than a universal rule that blocking is always best.
C:Suppressing logging does not improve the fundamental continuity decision and removes evidence of a degraded security state. Operators need timely notification that inspection is bypassed, particularly because malicious traffic may transit during fail-open operation. Telemetry and response procedures are complementary safeguards. Silence would make it harder to determine how long the hospital operated without inline security inspection.
D:Undefined behavior is not an acceptable design for a time-sensitive clinical service. The team should test power loss, link failure, recovery, and failover in controlled conditions and document expected forwarding behavior. A surprise fail-closed or unstable link could interrupt monitoring messages. The choice must be explicit and validated before production, with known security consequences and escalation paths.
Question 164
Contractors can plug unmanaged laptops into available Ethernet wall ports at a factory office. The network team wants the switch to withhold ordinary network access until the attached user or device has authenticated, with limited exceptions for approved equipment. Which control best addresses this requirement?
- Allow devices based only on having an IP address from DHCP
- Deploy port-based IEEE 802.1X network access control with an approved authentication service and tightly managed exceptions
- Configure static switchport MAC allowlists instead of requiring an authenticated 802.1X session
- Assign every unused wall port to a restricted contractor VLAN but grant that VLAN access without authenticating the attached device
Explanation
Correct Answer
B:IEEE 802.1X allows a switch acting as an authenticator to control port admission using an authentication service such as RADIUS. A contractor laptop must present acceptable user or device credentials before receiving normal connectivity, after which policy can assign an appropriate restricted network or role. The deployment should account for supplicants, certificates, guest access, and equipment that cannot speak 802.1X; exceptions should be carefully scoped and monitored rather than turned into unrestricted bypasses. Port authentication reduces unauthorized physical network attachment but does not replace endpoint security or ongoing authorization. It directly matches the stated requirement to decide access at a wired switch port before ordinary traffic is permitted.
Incorrect Answers
A:Receiving a DHCP address does not prove that a device or person is authorized to enter the enterprise network. DHCP is an address-configuration mechanism, and an attacker may also use a static address. Relying solely on that exchange allows network attachment before identity or posture is evaluated. The access decision must occur at the port or authenticated session boundary, with policy-driven authorization.
C:Static MAC rules may deter casual connections from unknown devices and can be operationally useful for narrowly managed equipment. A MAC address, however, is not a cryptographic device or user identity and can be observed and spoofed by a determined visitor. Maintaining large contractor allowlists is also error-prone as laptops change. The stated requirement is authentication before normal network admission, with limited authorized exceptions. An 802.1X supplicant and authentication service provide a stronger access decision than a port-level address match.
D:A restricted VLAN limits what an unauthenticated laptop can reach and may be appropriate for a temporary guest or remediation state. But the requirement is that normal network service be withheld until user or device credentials are validated. A permanently open contractor VLAN does not establish who is attached and cannot automatically authorize approved exceptions. Pair restrictive unauthenticated treatment with a genuine authenticated admission decision, such as 802.1X with centrally managed policy, rather than relying only on static port placement.
Question 165
Employees use managed laptops on home and hotel networks to access several private internal web applications. The company needs an encrypted, centrally authenticated remote-access connection without maintaining a permanent branch-to-branch link. Which option is the best fit?
- Use a centrally managed TLS-based remote-access VPN with strong user authentication and scoped access
- Rely on hotel Wi-Fi passwords as protection for enterprise sessions
- Deploy a site-to-site tunnel between every employee's residential router and the data center
- Expose every internal application directly to the Internet using its management port
Explanation
Correct Answer
A:A TLS-based remote-access VPN can create an encrypted session between a managed endpoint and a controlled enterprise gateway across an untrusted network. Central authentication, MFA, device requirements, and least-privilege resource policies limit who receives internal access. Because employees connect from changing locations, a per-user remote-access design is more practical than permanently establishing network-to-network tunnels to home routers. The service must still enforce access boundaries after tunnel establishment, monitor sessions, and protect the client. TLS secures the transport but does not by itself validate endpoint health or prevent abuse of a legitimately authenticated account. This architecture matches the stated temporary, centrally controlled workforce access need.
Incorrect Answers
B:A hotel wireless password only controls access to the local Wi-Fi and can be shared with many untrusted guests. It does not authenticate a user to internal company applications or necessarily provide end-to-end confidentiality. Even protected public Wi-Fi can carry traffic toward malicious local infrastructure or other hostile networks. Enterprise access needs a separate authenticated and encrypted security boundary independent of the hotel.
C:Permanent site-to-site tunnels are usually managed between fixed enterprise networks or trusted gateways. Asking every employee to configure a home-router tunnel introduces support burden, incompatible consumer equipment, and an unnecessarily broad link between private household networks and company resources. A remote-access VPN terminates at the managed laptop and can enforce per-user policies. The proposed network-to-network approach does not fit a mobile workforce.
D:Publishing internal applications and their administrative ports makes them reachable to unsolicited Internet traffic. Even when application login is enabled, unnecessary public exposure increases probing and vulnerability risks. Private remote access reduces reachability while adding controlled identity checks. The goal is encrypted employee access from untrusted networks, not direct exposure of every internal service to those networks.
Question 166
Two retail branches need to exchange internal application traffic over the public Internet, including protocols that do not natively use HTTPS. Each branch has an administratively controlled gateway. Which mechanism best protects the entire link at the network layer?
- Enable HTTPS only on each branch's employee portal
- Replace the Internet connection with an unauthenticated GRE tunnel
- Use NAT on both branch gateways and assume translated addresses are secret
- Establish an authenticated IPsec site-to-site tunnel between the branch gateways
Explanation
Correct Answer
D:An IPsec site-to-site tunnel can authenticate the branch gateways and protect IP traffic with cryptographic integrity and encryption over the public Internet. Tunnel mode can carry diverse internal protocols without requiring each application to implement HTTPS, while policies define which branch subnets use the protected path. The team should configure appropriate IKE authentication, strong algorithms, key lifetimes, routing, and monitoring, and prevent cleartext fallback for sensitive traffic. IPsec does not automatically authorize every application connection or cure compromised branch hosts, so local segmentation and endpoint controls remain necessary. It is the most direct network-layer mechanism for the gateway-to-gateway trust relationship in this scenario.
Incorrect Answers
A:HTTPS protects application sessions that actually use TLS, but the requirement includes several internal protocols that may not offer their own encryption. Protecting one web portal would not secure all branch-to-branch traffic. Application TLS remains useful as defense in depth, yet it cannot substitute for an authenticated network-layer tunnel when broad routed traffic requires confidentiality and integrity across the untrusted path.
B:Generic GRE encapsulation can carry routed protocols but does not inherently provide encryption, integrity verification, or peer authentication. Encapsulated packets may still be observed or modified on an untrusted Internet route. GRE can be combined with IPsec in some designs, but an unauthenticated GRE tunnel alone does not meet this security requirement. The difference is cryptographic protection rather than the mere existence of a tunnel.
C:NAT changes address representations at a gateway but is not an encryption or peer-authentication mechanism. Attackers on the transport path may still inspect or alter traffic if other protocols do not protect it. Internal private addresses becoming less obvious does not secure payloads. A site-to-site requirement should be met with negotiated cryptographic protection, keys, and authenticated endpoints, not address translation.
Question 167
A company operates several private application servers but wants clients to connect through one public endpoint. The endpoint must terminate HTTPS, apply inbound request policies, and relay permitted requests to the appropriate internal server without allowing clients to address those servers directly. Which architecture fits?
- Place a reverse proxy at the application ingress boundary with controlled back-end reachability
- Place an unrestricted forward proxy on every employee workstation
- Publish the private servers individually and rely on DNS obscurity
- Use a DHCP relay to rewrite incoming web requests
Explanation
Correct Answer
A:A reverse proxy sits in front of the application servers and accepts inbound client requests on their behalf. It can terminate HTTPS, enforce authentication or request policies where configured, route traffic to selected back ends, and log access while limiting direct exposure of origin hosts. The back-end network should permit only the proxy's necessary connections; otherwise clients might bypass the centralized controls. Certificates, forwarded identity headers, and trust between proxy and application need careful configuration. A reverse proxy does not automatically provide WAF-quality inspection unless corresponding features are enabled, but it supplies the desired centralized ingress and relay pattern. The key relationship is external client to controlled intermediary to private application.
Incorrect Answers
B:A forward proxy generally mediates outbound requests made by internal clients to destinations beyond their network. Installing one on employee workstations would not create the required public ingress point for external application users. Proxy technologies can have multiple functions, but the intended traffic direction and ownership of back-end servers distinguish the architecture. The proposed solution should protect inbound origin servers rather than employee browsing.
C:Giving each private application server its own public endpoint increases the exposed surface and allows clients to bypass a single centralized request-control point. DNS naming conventions do not create a security boundary; public addresses and open ports can be discovered by scanning. Separate public origins may be valid in other designs, but not when the explicit requirement is one controlled entry point and private back ends.
D:A DHCP relay forwards address-assignment messages between clients and DHCP servers across routed boundaries. It does not terminate HTTPS sessions, authenticate web users, inspect HTTP requests, or proxy requests to origin applications. It solves a different network configuration problem. The proposed central web entry point requires an application ingress intermediary, not an address-management service.
Question 168
An API service uses a load balancer that checks whether application instances respond to health probes. The security lead worries that a healthy instance might still accept a malicious request. Which assessment is correct?
- Successful health probes prove that all API requests are safe
- Load balancing supports availability and routing, but separate application-aware controls are needed to inspect malicious requests
- A health-check failure necessarily means data has been stolen
- Turning off HTTPS is required for a load balancer to distribute traffic
Explanation
Correct Answer
B:Load balancers direct traffic among service instances and can stop sending requests to an unhealthy node, improving availability and fault management. Their health probes do not, by themselves, analyze every incoming API field for malicious semantics or verify per-user authorization. An API gateway, WAF, robust application validation, and access controls can handle those requirements according to the actual threat model. Some load balancers offer optional security features, but those capabilities must be explicitly enabled and evaluated. The situation distinguishes application health and distribution from security inspection: one can function correctly while the other remains absent. Security owners should inventory which layer enforces which policy.
Incorrect Answers
A:A health check may verify that an endpoint responds within an expected time or returns a particular status. That says little about whether each API request contains malicious input or whether authorization logic is sound. A healthy application can still be vulnerable to injection or broken access control. Security inspection must be established through appropriately configured gateway, WAF, application validation, and logging controls rather than inferred from uptime.
C:A node can fail health checks due to overload, software error, expired certificate, or network partition without any security breach. Failure is a service-state indicator that merits investigation, not proof of exfiltration. Likewise, a compromised application can continue returning healthy responses. Incident decisions need corroborating logs and behavioral evidence rather than treating a probe result as a definitive security conclusion.
D:Many load balancers can handle HTTPS using TLS pass-through or controlled termination and re-encryption. Disabling TLS would expose API credentials and data on untrusted links and is not a prerequisite for distribution. Choosing a termination point affects where request-inspection controls can observe plaintext. The team should preserve encrypted transport while designing visibility and key management intentionally.
Question 169
A chain of branches uses SD-WAN with both public broadband and cellular uplinks. The provider offers dynamic route selection, but the organization also requires confidential interbranch traffic and consistent access policy regardless of which transport is selected. What should be verified?
- Select routes by observed bandwidth and latency, assuming transport performance also ensures confidentiality
- Treat successful provider BGP reachability on both circuits as sufficient verification of branch peer identity
- That the SD-WAN overlay encrypts and authenticates traffic and applies centrally governed policies across both transports
- That routing logs are permanently disabled to reduce bandwidth
Explanation
Correct Answer
C:SD-WAN dynamically selects underlying paths while an overlay may provide encrypted, authenticated tunnels and centrally distributed security policies. The team should verify that protection is applied to the relevant subnets and applications on both broadband and cellular paths, that peer onboarding uses secure credentials or certificates, and that route changes do not bypass access restrictions. Consistent segmentation, key rotation, audit logs, and failover testing help maintain security when transport conditions change. SD-WAN is a connectivity architecture, not a guarantee of encryption by name; feature configuration and actual packet paths matter. The precise assurance required here is protection and policy continuity regardless of which untrusted underlay carries the traffic.
Incorrect Answers
A:Link measurements can improve SD-WAN path selection and application quality, especially when broadband and cellular performance vary. However, bandwidth and latency say nothing about whether interbranch packets are encrypted or whether endpoints authenticate each other. An untrusted carrier can still observe traffic on a fast route. Confidentiality and branch authorization must be enforced through the overlay and policy plane separately from performance routing.
B:BGP reachability can establish available paths and help recover from an uplink failure, but an advertised route is not an authenticated endpoint for a confidential SD-WAN overlay. Misrouting or unauthorized branch enrollment could still expose interbranch traffic. The design needs explicit peer identity and tunnel protection regardless of which underlay route carries packets. Routing availability is a prerequisite, not proof that all access policies have been enforced.
D:Routing logs help operators diagnose tunnel failures, identify unexpected paths, and confirm which policies were applied. Disabling them would weaken troubleshooting and incident investigation without addressing confidentiality. Telemetry volume can be managed through retention and filtering, but removing essential records is not an authentication control. The goal is consistent secure behavior across transports, including observable failover decisions.
Question 170
A financial services firm employs 1,200 people who work from home and regional offices. Employees access SaaS applications directly, but the existing security design backhauls all Internet traffic to a headquarters firewall, causing long delays and frequent capacity problems. The security team must retain consistent identity-aware browsing and data protection without trusting each home network. What architectural direction best addresses the placement problem?
- Remove web inspection from remote sessions to eliminate headquarters latency
- Deliver centrally governed security functions through distributed SASE points of presence near the users
- Publish the firm's database administration interfaces so remote employees connect without backhaul
- Retain mandatory headquarters backhaul and simply add a faster firewall appliance
Explanation
Correct Answer
B:Secure Access Service Edge integrates distributed connectivity and cloud-delivered security capabilities under centrally managed policies. Instead of requiring each remote SaaS request to transit the headquarters data center, users can reach a nearby enforcement point where identity, device posture, web threats and data policies are evaluated as supported by the service. This reduces dependence on a single backhaul and can improve performance. The team must verify provider coverage, policy parity for on-premises applications, encrypted transport, logging and failover rather than assuming a product label provides complete protection. The architectural benefit is moving enforcement toward the traffic while retaining governance, not removing controls.
Incorrect Answers
A:Removing inspection reduces latency, but it also discards the required policy enforcement for traffic leaving remote devices. The company still needs access authorization, threat filtering and appropriate data controls for SaaS use. Internet access from home is not inherently trustworthy just because it avoids an internal choke point. A distributed control design may solve both security and performance needs without abandoning inspection.
C:Exposing database management ports would create new privileged Internet attack surfaces unrelated to the users' cloud application access. A database listener requires tightly scoped administrative reachability, strong authentication, and monitoring; it should not become a convenience route around remote-access design. It also provides no replacement for SaaS browsing inspection or data-loss controls. The proposed solution would worsen exposure while leaving the original policy-placement problem unanswered.
D:A larger headquarters firewall might address appliance throughput, but all remote traffic would still depend on headquarters connectivity and the same geographically distant route. The design retains a single operational choke point and may still impose latency on direct SaaS sessions. Central appliances are appropriate for some private application traffic, but this firm needs distributed enforcement for users everywhere. Expanding one box is not equivalent to changing the placement of controls.