CompTIA Security+ SY0-701 Practice Test 15
Question 140
A serverless function accepts partner webhooks, queries an internal database, and imports a third-party package. Developers say that because the provider manages servers, there is no application infrastructure security work left. What review is most appropriate?
- Verify webhook signatures while keeping the function's database role unrestricted
- Reduce database permissions but assume every imported package is safe
- Evaluate event authenticity and replay defense, execution privileges, and dependency risks
- Assume automatic function teardown makes repeated malicious webhooks harmless
Explanation
Correct Answer
C:Managed runtimes shift responsibility for underlying host operation to the provider, but developers still control function code, events, identities, secrets, and dependency choices. The team should authenticate incoming webhooks, protect against replay where relevant, validate payloads, restrict database and network permissions, and track third-party library vulnerabilities and integrity. Logging and monitoring should identify unexpected executions and privilege use. Automatic scaling and teardown do not validate that an event is authorized. The security design must therefore cover the application-level trust boundaries left in customer control rather than assuming provider management eliminates all risk.
Incorrect Answers
A:Validating webhook signatures helps establish that an event came from an authorized sender, but an unrestricted execution role still grants more database access than the function needs. An attacker who compromises the function through another input or dependency could misuse those privileges. Authentication of one input does not replace least-privilege execution. The team should review both event entry and downstream access boundaries.
B:A narrowly scoped database role limits damage if the function is abused, which is valuable. However, third-party packages execute within the function's environment and may contain vulnerabilities or compromised code. Trusting all dependencies without review leaves another significant entry path. Securing serverless workloads involves software supply-chain management in addition to service permissions.
D:A short-lived runtime can reduce some persistence opportunities but does not stop a forged or replayed webhook from invoking a function repeatedly. Each invocation could still read, modify, or export data using the function's permissions. Replay prevention may require event identifiers, nonces, timestamps, or idempotency checks suited to the integration. Lifecycle management is not equivalent to input authentication and authorization.
Question 141
Three microservices run on a shared cluster and use one privileged API key to call each other over unrestricted internal networking. A compromise in one service could therefore access resources belonging to the others. What architectural risk should be prioritized?
- Require mutual TLS between microservices while retaining the same overprivileged API key and broad internal reachability
- Excessive east-west trust and shared service credentials
- Failure to install a second Internet ingress firewall while allowing all internal service calls
- A single secrets store that intentionally assigns one identity and role to every service
Explanation
Correct Answer
B:East-west traffic describes communications between services inside a data center or cluster rather than traffic entering from the Internet. Shared privileged credentials and unrestricted internal calls make compromise of one workload useful for reaching the others. Each service should have a distinct identity, minimum necessary permissions, and authenticated encrypted communication where appropriate, with network policies limiting allowed service pairs. Centralized key management can support this design if it issues scoped credentials rather than one shared secret. The central lesson is that an internal network is not automatically a trusted authorization boundary. The risk is lateral movement and privilege reuse across otherwise separate application components.
Incorrect Answers
A:Mutual TLS authenticates the communicating workload endpoints and encrypts service-to-service traffic, which is an important improvement in a microservices cluster. It does not provide least-privilege authorization when every workload still shares one key granting access to unrelated services. A compromised microservice can continue making authorized-looking requests using that common identity. The architectural weakness is excessive east-west trust and shared privilege; separate workload identities, narrowly scoped permissions, and network restrictions are needed in addition to protected transport.
C:An ingress firewall controls traffic entering the environment, but compromised code already inside one service can communicate laterally over permitted cluster paths. Adding another perimeter appliance without governing east-west calls may not reduce this trust gap. Internal service identity and segmentation are the missing safeguards. The ability to move between services should not depend solely on having passed the outside boundary once.
D:A shared secrets vault can be useful infrastructure, but issuing one identical privileged identity to every workload defeats least privilege and individual service attribution. The vault's centralized location is not inherently the problem; the overly broad shared authorization model is. The team should use per-service identities and scoped retrieval, not abandon secret management while leaving common privileges intact.
Question 142
A container cluster runs several production workloads on the same host kernel. One application image has vulnerable old packages, and another runs with unnecessary kernel capabilities. What should the security review include?
- Review image packages but assume default runtime privileges cannot affect the host
- Harden the host while ignoring vulnerabilities in packaged application dependencies
- Apply network policies between containers without reviewing vulnerable image packages or unnecessary kernel capabilities
- Examine image supply and patch state, container privileges, and shared-kernel boundaries together
Explanation
Correct Answer
D:Container security spans the full workload lifecycle. Reviewers should assess base-image provenance, known vulnerable libraries, update cadence, effective Linux capabilities, privilege escalation settings, host filesystem mounts, network policies, and the shared host kernel. Unlike virtual machines with separate guest kernels, ordinary containers rely heavily on kernel-level isolation, so excessive capabilities can enlarge the consequences of a compromise. Security controls must align with responsibility for host operation and image maintenance. The case deliberately combines an old image and an overprivileged runtime to show why auditing only one layer is incomplete. Restricting workload access reduces blast radius while patching reduces initial exploitability.
Incorrect Answers
A:Scanning images identifies outdated packages, but containers share a host kernel and may have runtime privileges that weaken isolation. Ignoring capabilities or host mounts can let a compromised workload reach resources beyond its intended scope. Even a fully patched image may create risk if launched privileged. The review must include both software contents and execution settings to capture the complete container boundary.
B:Kernel hardening and patching protect a shared foundation, but a vulnerable library inside an image may still allow attackers to gain code execution within a container. That foothold can then be used against other resources depending on privileges and network policy. Skipping image vulnerabilities leaves a separate attack path unaddressed. Defense requires responsibility for both host and workload code.
C:Container network policies can limit east-west and external communication, reducing the reachability of compromised services. They do not remove vulnerable libraries already present in an application image or the host-impacting privileges granted to a container. Because the workloads share a kernel, unnecessary capabilities may enable damage even when network connectivity is constrained. A complete review must assess image provenance, patch levels, privilege and namespace boundaries, and host protections together rather than treating network isolation as a substitute for runtime hardening.
Question 143
A hosting provider manages the physical servers and hypervisors used by several customers. Each customer administers the operating system inside its own guest VM. A hypervisor security bulletin is released. Who typically patches the relevant layers?
- Each customer applies the hypervisor patch inside its guest operating system
- Require the IaaS operator to maintain every customer's guest operating system as well as the hypervisor
- The infrastructure operator updates the hypervisor while guest owners maintain their operating systems
- Virtualization makes both host and guest patching unnecessary
Explanation
Correct Answer
C:The infrastructure operator controls the host virtualization stack and therefore usually installs or coordinates hypervisor security updates. Customers maintain operating systems and applications within guest VMs, subject to the agreed service model. A host bulletin may require coordinated maintenance windows because patched hypervisors can involve node restarts or migrations that affect tenant availability. Both layers need lifecycle management; one does not replace the other. The shared-responsibility distinction is critical when assessing whether a hypervisor escape weakness has been addressed, because a patched guest alone may still run on a vulnerable host. Clear ownership and evidence of updates reduce gaps between teams.
Incorrect Answers
A:A tenant inside a normal VM generally cannot patch the underlying host hypervisor merely by running operating-system updates in the guest. The guest and hypervisor are distinct software layers under different administrative controls. Tenant patching is still necessary for guest vulnerabilities, but it does not remediate a host-level isolation flaw. The party controlling the infrastructure must address that layer.
B:An infrastructure provider generally manages the physical hosts and virtualization layer in a traditional IaaS model. Some optional managed services can alter this boundary, but the question specifically says customers administer their own guest operating systems. Asking the provider to patch all guest kernels would overlook that customer responsibility and leave the host-guest maintenance plan unclear. The operator patches the hypervisor, while each VM owner manages its guest operating system and applications under the agreed service model.
D:Virtualization isolates workloads only to the extent that the hypervisor and guest software enforce their intended boundaries. Vulnerabilities exist in both layers, and a host flaw can affect multiple tenants. Assuming isolation removes patching needs ignores the very hypervisor advisory in the stem. The correct response is coordinated infrastructure and guest maintenance, not deferral of all updates.
Question 144
A production controller runs a millisecond-critical process over a dedicated wired fieldbus. Years ago the vendor installed a separate cellular maintenance modem, whose carrier tunnel bypasses the plant's enterprise firewalls. An exploitable management service remains reachable only through that modem, and the controller cannot be safely patched or restarted until a scheduled shutdown. The plant no longer requires any remote vendor work; a physically controlled local console supports emergency maintenance. Which immediate compensating isolation decision is most appropriate?
- Deactivate the legacy cellular SIM and remote tunnel, verify the wired process path remains operational, and use approved local-console maintenance until patching
- Add another firewall VLAN between office IT and OT but leave the modem carrier tunnel active outside those firewalls
- Require multifactor authentication on the corporate VPN while leaving the independent cellular maintenance path exposed
- Increase remote modem intrusion alerts while keeping its vulnerable management service reachable until the normal patch window
Explanation
Correct Answer
A:The vulnerable management service is exposed through a separate cellular tunnel that bypasses the enterprise firewall, not through the wired process-control link. Disabling the obsolete SIM and carrier-side session removes that unintended remote attack path while allowing the deterministic fieldbus traffic to continue. Engineers still have an approved, physically controlled local console for exceptional work before the safe shutdown. They should verify that carrier deactivation does not affect critical telemetry, record the temporary control and residual risks, and prepare the eventual vendor fix. This tests out-of-band carrier-path isolation, not a general engineering jump-host exception or a guest-network firewall rule.
Incorrect Answers
B:Additional IT/OT firewall zones can restrict ordinary office-to-controller traffic and are useful for long-term plant security. The scenario's vulnerable service is reachable through a separate cellular tunnel that bypasses all those enterprise firewalls. Changing VLAN membership on the office side therefore does not close the actual route attackers could use. The production wired fieldbus is already dedicated and must remain operational. The immediate compensating step is to deactivate the unnecessary cellular maintenance connectivity, then confirm that local console access remains available for controlled emergencies.
C:Multifactor authentication on the corporate VPN can strengthen access for legitimate enterprise remote administrators. The obsolete cellular modem uses a separate carrier route that does not traverse that VPN or the plant firewalls. Adding a factor to the wrong access path leaves the vulnerable management daemon exposed to remote requests. The vendor service cannot be patched while production is running, and no remote work is required. Disabling the carrier tunnel addresses the reachable exploit interface; VPN hardening may still be appropriate elsewhere as defense in depth.
D:Alerting on suspicious modem sessions could provide some warning before a known network exploit succeeds, and preserved carrier telemetry may help an investigation. Alert-only monitoring does not stop malicious requests from reaching the vulnerable maintenance service. Because remote maintenance is unnecessary and approved physical console access exists, the modem can be taken out of service now without disrupting the separate control link. The chosen isolation action removes the attack route rather than merely detecting future misuse while waiting for the scheduled patch window.
Question 145
A medical monitoring sensor has a very small battery, limited CPU, and a physically accessible technician port. Engineers propose installing a full desktop EDR suite despite evidence it will exhaust processing capacity. Which assessment is most appropriate?
- Require the desktop agent even if it prevents the sensor from collecting readings
- Use only cloud transport encryption and leave the local service port unrestricted
- Design controls for constrained resources and the risk of local physical access
- Rely on the sensor enclosure alone while leaving its technician service port unauthenticated and usable when physically reached
Explanation
Correct Answer
C:Embedded medical sensors require controls compatible with their processing, energy, and safety constraints. The team should restrict and authenticate the service port, protect firmware integrity where supported, minimize exposed interfaces, secure communication, and provide monitoring at a gateway when a full local agent is impractical. Physical proximity matters because a technician-accessible port can bypass assumptions based only on Internet reachability. Controls must be validated not to degrade critical sampling or alerting functions. This is a contextual architectural assessment balancing safety, resource limitations, and attack paths rather than assuming desktop-scale security software can simply be transferred to a tiny device.
Incorrect Answers
A:Heavy endpoint agents may be unsuitable for embedded devices with strict CPU, memory, and battery budgets. If security software interrupts medical readings, the protection can create a serious availability or safety failure. Device-appropriate hardening and compensating controls should be tested against actual operational limits. The goal is an effective risk reduction, not deployment of a familiar desktop product at any cost.
B:Encryption in transit can protect sensor reports as they travel to an authorized service, but it does not prevent an attacker with physical access from manipulating a maintenance port or extracting local secrets. The scenario specifically raises a nearby service interface and constrained hardware. Both communication security and physical maintenance restrictions are needed, with clear responsibility for technician access and device recovery.
D:A sealed or tamper-evident enclosure can make opportunistic physical interference harder and provide useful evidence during scheduled inspections. It does not eliminate attacks through an accessible local service port, especially if a legitimate technician or intruder can open the case. The sensor's limited CPU and battery also rule out assuming that a heavyweight desktop agent is safe. Appropriate controls must combine feasible service-port authentication, local access protection, monitored maintenance, and resource-aware software safeguards.
Question 146
An industrial safety controller must respond to inputs within a strict millisecond deadline. Engineers propose inserting deep packet inspection that may add variable processing delay to every control message. What principle should guide selection of security controls?
- Maximize inspection depth regardless of control-loop response time
- Approve the inspection appliance based on average throughput tests without measuring worst-case control-message delay
- Preserve validated deterministic behavior while applying suitable security restrictions
- Assume every encrypted inspection path adds no latency
Explanation
Correct Answer
C:Real-time industrial systems often require predictable worst-case response latency rather than merely good average throughput. Security controls should therefore be selected and tested against deterministic timing constraints, with plant engineering involvement and an approved safe failure mode. Possible measures include segmentation, authenticated maintenance access, bounded inspection at appropriate network points, and passive telemetry that does not delay the control loop. Encryption and inspection can consume resources, so capacity and timing must be measured. The principle is to reduce cyber exposure without invalidating essential safety behavior; a control that unpredictably delays critical messages can be unsuitable even if it is effective in ordinary IT environments.
Incorrect Answers
A:Deep inspection may detect some threats but can introduce variable processing time and dropped or delayed control messages. A safety system with a strict response deadline cannot accept unbounded latency merely to maximize inspection. Security requirements must include the operational timing and failover limits of the process. Controls should be evaluated in a test environment that reflects real load and safety conditions.
B:An inspection product may perform well in ordinary throughput benchmarks and still introduce occasional latency spikes during unusual packets, overload, or failover. Industrial control deadlines are set by worst-case timing and validated safety behavior, not merely the average throughput of an appliance. Approving an inline scanner without measuring bounded response time could cause late or missed control actions. The security design should preserve deterministic operation and place inspection or segmentation controls where validated timing and fail-safe requirements remain satisfied.
D:Encryption, key negotiation, and traffic inspection all have computational and operational costs, even when hardware acceleration keeps them small. Treating their latency as zero would be an unsafe design assumption for a controller with millisecond deadlines. The team must measure actual worst-case behavior and failure handling. Cryptographic protection can still be used, but only with validated timing and resource requirements.
Question 147
At a manufacturing plant, office workstations and programmable controllers share unrestricted routed connectivity. Accredited controls engineers occasionally must perform authorized diagnostics on a few PLCs, but the plant manager prohibits everyday corporate endpoints from reaching industrial control ports. Maintenance must have individual accountability and a defined time window. Which IT/OT security architecture meets that need?
- Separate IT and OT zones with an industrial DMZ and monitored jump gateway that permits approved engineers' time-bound, protocol-scoped PLC maintenance sessions
- Create distinct IT and OT VLAN numbers but leave unrestricted inter-VLAN routing in place to keep all maintenance tools reachable
- Authenticate engineers to the corporate wireless network and then let their laptops connect directly to every PLC without an industrial access gateway
- Keep PLCs on the same office subnet and rely on endpoint detection on corporate laptops to prevent every unauthorized control command
Explanation
Correct Answer
A:The plant needs occasional legitimate control access, so its boundary must govern inbound engineering sessions rather than merely export measurements. An industrial DMZ and hardened jump gateway can enforce named engineer authentication, authorized change windows, approved protocols and target PLCs, and session recording without opening direct office-to-controller routes. Firewalls should deny everything else and maintenance privileges should be removed when work ends. Industrial reliability and safety requirements govern the allowed diagnostic commands, and the team must test recovery behavior rather than treat segmentation as a universal guarantee. This is distinct from a one-direction historian reporting bridge, which would not satisfy authorized maintenance requirements. The core decision is a tightly governed, attributable IT-to-OT conduit for rare control-system administration.
Incorrect Answers
B:Virtual LANs can reduce broadcast exposure and simplify traffic policy, but assigning separate VLAN numbers is not equivalent to restricting communication. If inter-VLAN routing still allows arbitrary office connections to PLC ports, the same lateral movement and unauthorized control opportunities remain. The scenario requires individual approvals, limited maintenance windows and recorded diagnostic sessions. Those safeguards need enforceable gateways and policy, not merely different network labels. VLAN separation is useful as part of the design but cannot satisfy the stated trust boundary without corresponding route and access restrictions.
C:Corporate wireless authentication can help determine which staff or devices are connected to the enterprise network, but it does not authorize arbitrary modifications to safety-sensitive controllers. A compromised engineer laptop could still issue dangerous PLC requests if the corporate network has an unrestricted direct route. The plant must explicitly restrict maintenance identities, control protocols, destination devices and allowed operating times. A monitored industrial access gateway provides those checks and audit evidence; joining an office SSID does not replace the separate OT authorization and safety process.
D:Endpoint detection on office laptops may identify malicious tools or suspicious lateral traffic, which provides useful defense in depth. It cannot guarantee that all unauthorized commands will be blocked, especially when a valid engineer account or permitted application is misused. Leaving the industrial controllers on an unrestricted office subnet preserves the exposure highlighted by the scenario. The controls need enforced network separation and a monitored maintenance conduit so even compromised corporate endpoints cannot freely address PLC management ports. Endpoint monitoring should supplement, not substitute for, the OT trust boundary.
Question 148
A research laboratory has no routine Internet connection. External contractors occasionally transfer approved software updates to lab equipment using removable drives during maintenance. Which residual attack path deserves focused controls?
- Scan contractor removable drives with antivirus and treat a clean result as sufficient approval for every update transferred into the laboratory
- Removable media and authorized maintenance procedures can bridge the disconnected boundary
- Tighten Internet firewall policy around the rest of the campus while leaving laboratory update media and contractor handling unchanged
- Require visitors to pass through physical access checks but accept any digitally unsigned update brought by an escorted technician
Explanation
Correct Answer
B:An air gap removes routine network connectivity but does not prevent bytes crossing the boundary on authorized removable drives. Contractor update workflows create a legitimate transfer path that can introduce compromised installation packages, malicious files or modified firmware. Security must therefore govern supplier authenticity, media provenance, scanning or sandboxing, explicit change authorization, least-privilege update accounts and custody of the drives. The lab should validate update signatures and operational compatibility, retain logs and plan for recovery if a package behaves unexpectedly. Physical isolation is valuable but does not eliminate attack paths created by necessary maintenance activity. The actual residual risk is the controlled media bridge, not a hypothetical Internet connection.
Incorrect Answers
A:Antivirus scanning reduces some malicious-content risk and should be part of media intake, but detection may miss previously unseen or deliberately concealed payloads. The question concerns a laboratory whose only routine introduction path is supervised transfer media, making source authorization, cryptographic update verification and device-use control especially important. A clean scanner result does not authenticate the software supplier or establish that the removable drive remained trustworthy throughout handling. Layered media controls are necessary instead of treating antivirus as a universal approval token.
C:Campus firewall policy can reduce external exposure for connected systems, but the laboratory is described as having no routine Internet path. The update mechanism under review is removable media carried by contractors into a disconnected room. Hardening a separate network perimeter does not establish that an installation package on a drive is authentic or free of malicious components. Network controls remain relevant to the broader organization, while this residual laboratory risk requires controls at the physical media and software-update handoff.
D:Physical access controls help ensure only authorized visitors enter the laboratory, yet an escorted technician can still bring a compromised or counterfeit update package. The fact that staff are present does not verify the software's origin or detect manipulated binary content. In a disconnected environment, accepted update media need provenance checks, approved transfer procedures and appropriate integrity validation. Visitor screening and logging are important complementary safeguards but cannot substitute for an authorized, authenticated software-supply path.
Question 149
A software-defined network relies on one central controller to install forwarding policy on dozens of switches. Attackers obtain administrator-level control of the SDN controller. What distinctive architectural risk does this create?
- Only the switch nearest the controller can be affected
- Hardening leaf-switch ACLs makes controller access security unnecessary
- Encrypting application traffic eliminates the need to authorize controller changes
- Compromise of the central control plane can propagate malicious policy to many network devices
Explanation
Correct Answer
D:Centralized SDN management improves consistency and simplifies automation, but it concentrates authority over forwarding state. An attacker with high privilege on the controller may alter routes, bypass segmentation, or disrupt many switches through one set of commands. The security design should protect controller identities and APIs, separate duties, validate policy changes, maintain logs, and plan safe controller recovery. The important distinction is a central control-plane blast radius versus isolated compromise of one network device. Network encryption helps protect some data but does not neutralize unauthorized controller programming, so strong control-plane security is a core architecture requirement.
Incorrect Answers
A:A central SDN controller may program many forwarding devices across the fabric, not merely the physically nearest switch. Distance in cabling does not define its management authority. The scenario explicitly says it installs rules across dozens of devices. A single compromised controller credential can therefore have a broad blast radius depending on role scope and network policy.
B:Switch ACLs may provide defense in depth, but if the controller is authorized to overwrite or distribute forwarding policies, compromised control access can change those protections. Controller administration needs strong authentication, least privilege, protected APIs, and auditable change procedures. Hardening individual switches is not a substitute for securing the central authority that manages them.
C:Encrypted application traffic protects contents in transit but does not stop a malicious network controller from rerouting, dropping, or selectively diverting packets. It also cannot guarantee that forwarding policy remains correct. Control-plane authorization is essential even when endpoints use strong cryptography, because network availability and metadata exposure still depend on safe routing. The architecture risks are related but distinct.
Question 150
Twenty regional offices manage network access rules independently. A new corporate standard is interpreted differently at each office, leaving some locations with overly broad permissions. Which downside of the governance architecture is visible?
- Decentralized rule ownership has allowed local interpretation and configuration drift from the common security baseline
- A centralized rule-design team would automatically eliminate all differences even if branches continued to maintain unreviewed local exceptions
- Standardizing the same firewall product across every branch would by itself resolve conflicting local definitions of who may access protected systems
- Deploying a common management dashboard without assigning baseline ownership or exception review would ensure enforcement consistency
Explanation
Correct Answer
A:When many offices independently interpret a corporate access standard, the same business requirement can result in inconsistent firewall objects, permissions, and exceptions. That is decentralized policy administration and configuration drift, which can create unpredictable exposure between locations. The organization should define a clear authoritative baseline, designate owners for exceptions, version controlled configurations, and reconcile actual deployed rules against approved intent. Centralized tooling or a shared vendor may make that work easier but does not replace decision governance. The decisive facts are independent rule ownership and differences in enforcement, not a demonstrated failure of the network's cryptographic channels.
Incorrect Answers
B:Centralized design can reduce divergent policy interpretation, but it does not guarantee consistent enforcement if branch operators retain undocumented override privileges or local exceptions. The scenario is about independent rule decisions that produced broad access, not a simple absence of one central team. A central reference policy would still need version control, distribution, reconciliation and compliance checks. Without those elements, central writing alone may coexist with local configuration drift and leave the actual branch filtering inconsistent with the intended standard.
C:Common firewall software can simplify training, policy deployment and reporting, but identical vendors do not make authorization decisions automatically consistent. Different branches can still configure different rules, or apply the same rule to incompatible network objects. The security gap arises from who defines, approves and verifies policy intent across offices. Standardizing platforms may be helpful operationally, yet it is neither sufficient nor the primary architectural issue described by the audit.
D:A shared dashboard improves visibility and may help detect differences across branches, but it cannot enforce one approved policy without clear ownership, controlled configuration changes, and routine exception review. A branch could retain broad permissions and still appear as a normal device in the dashboard. Real consistency requires defined baseline rules, delegated authority boundaries, monitored distribution and drift remediation. The question asks for the governance disadvantage revealed by independent decisions, not simply whether management has one interface.