CompTIA Security+ SY0-701 Practice Test 26
Question 250
During a suspected data leak, a firewall exporter shows that one payroll server sent far more bytes than usual to a new public address after business hours. Analysts want to find the talking hosts, protocol and time window before requesting deeper packet inspection. Which data source matches this objective?
- Use a daily firewall summary that counts blocked requests but omits source-destination tuples and byte volumes
- Review DNS query logs for the server without collecting connection-level protocol, byte or duration metadata
- NetFlow or IPFIX records showing source, destination, ports, timestamps and transferred byte counts
- A packet payload transcript claimed to be automatically included inside every flow record
Explanation
Correct Answer
C:Flow telemetry summarizes conversations using IP endpoints, transport ports, timestamps, protocol and counters such as bytes and packets. It can confirm whether the payroll server communicated with the new public destination, when the transfer occurred, and which other hosts share the same pattern. Analysts should understand sampling, NAT translations and the exporter's observation point before attributing traffic to an endpoint. Because these records normally lack application payloads, the next step may be proxy logs, TLS metadata or authorized packet capture for deeper detail. This is the appropriate first source for identifying high-volume talkers without overclaiming content visibility.
Incorrect Answers
A:A firewall dashboard can show broad security trends and alert volume, but totals of denied requests do not identify which server transferred data to a specific destination. The suspected event requires a time-bounded conversation record with source, destination, protocol and byte counters. NetFlow or IPFIX data can supply that detail before deeper packet inspection. Aggregate counts alone would hide the unusual payroll server among unrelated network activity.
B:DNS requests can help identify unfamiliar destination names and are a valuable enrichment source for investigating the public address. They do not prove that the payroll server established a data transfer, how many bytes it sent or which transport port carried it. Cached lookups and encrypted resolution can further limit visibility. Flow records are better for first identifying traffic talkers and transfer windows, after which DNS can add attribution context.
D:NetFlow and IPFIX records generally describe traffic metadata, not the full application bytes transmitted in a session. Claiming they provide a packet payload transcript would lead to false assumptions about whether confidential salary documents were sent. Full packet capture or another application-aware source is required to inspect content, and encryption may limit what that evidence reveals. Flow telemetry remains valuable precisely because it identifies suspect communications with lower storage demands than pervasive packet capture.
Question 251
An employee laptop triggers a behavioral alert: a previously unseen executable spawns a scripting interpreter, creates a scheduled task and changes an autorun registry value. Network firewall logs show only ordinary HTTPS traffic. Which collection should the responder prioritize to reconstruct the local sequence?
- Edge NetFlow data alone because it records every local process and registry operation
- Endpoint detection and response telemetry with process ancestry, persistence events and file changes
- Compare the laptop’s current installed-software inventory with last month’s inventory without collecting execution timelines
- Inspect only firewall proxy logs for external HTTPS destinations and infer the local scheduled-task creator from the connections
Explanation
Correct Answer
B:Endpoint detection and response can correlate parent-child processes, command-line arguments, new binaries, scheduled-task registration and registry persistence changes on the affected laptop. Those events let the responder determine whether the interpreter was launched by the suspicious executable, what it wrote and which identity performed the action. Preserve event timestamps, hashes and relevant artifacts under the incident process; EDR alerts alone are not proof of malicious intent. Comparing behavior to approved software and baselines reduces false positives. Network logs can supplement the timeline, but endpoint instrumentation directly observes the actions that made the case suspicious.
Incorrect Answers
A:NetFlow identifies traffic endpoints, timing and volumes, not the creation of scheduled tasks or individual registry writes inside a computer. The ordinary HTTPS connections may still be relevant if a process later contacts an attacker, but flow records cannot reconstruct the immediate local persistence chain. The responder needs host-level process and system-event visibility, then can pivot to network evidence after the executing components are identified.
C:An inventory difference may reveal a newly installed product or changed file package, making it a useful supporting artifact. Malware can use existing interpreters or run without a durable installation, and a static inventory does not show which parent process created a scheduled task or autorun value. The responder needs timestamped host activity with process ancestry and persistence changes. EDR or equivalent endpoint event collection offers that sequence; inventory comparison alone cannot.
D:Proxy data can identify some destinations, timings and network identity associated with the workstation, which is valuable after a suspicious process is identified. It does not directly record the registry modification, task-creation API or parent-child execution relationship on the laptop. Several programs could share the same outbound address. Endpoint telemetry is the appropriate primary evidence for reconstructing the local persistence chain; network records should be correlated afterward.
Question 252
A finance employee attempts to upload a spreadsheet containing customer account numbers to a personally owned cloud-storage tenant. The organization already classifies the spreadsheet as confidential and wants to prevent unauthorized transfers while retaining useful evidence for review. What should it deploy or tune?
- Enable endpoint antivirus scanning of uploaded files without evaluating their confidentiality classification or recipient tenant
- Block the personal cloud provider’s DNS name across every network but allow equivalent uploads through other storage tenants
- A data loss prevention policy that recognizes sensitive content, evaluates destinations and blocks or justifies the transfer
- Collect cloud access audit logs after uploads finish, without a prevention action for classified outbound files
Explanation
Correct Answer
C:Data loss prevention evaluates data classification or content patterns together with user, destination and transfer channel. A rule can block uploads of customer account numbers to personal tenants, allow approved corporate destinations and create a reviewable event for policy owners. It should handle false positives with testing, scoped exceptions and incident review so legitimate finance activity is not silently disrupted. Endpoint, secure-web-gateway or cloud-service integration may provide different enforcement coverage; select the points matching actual upload paths. The crucial control addresses attempted movement of classified content, not merely whether the file exists on a machine.
Incorrect Answers
A:Antivirus can identify known malware in an uploaded file and sometimes suspicious script behavior, so it remains a useful complementary control. A confidential customer-account spreadsheet can be entirely free of malware while still violating the data-handling policy when sent to personal cloud storage. Antivirus does not inherently classify protected account numbers or enforce approved destination rules. DLP must evaluate the content and transfer context at an appropriate egress point to block this particular leakage.
B:Domain blocking can restrict one known destination and may temporarily reduce exposure to a specific provider. It does not evaluate whether a particular file contains customer account numbers or whether the recipient tenant is authorized, and users may transfer the same data through other services. The organization wants a consistent policy with reviewable evidence across upload paths. Content-aware DLP rules and destination context provide broader, more precise governance than blocking a single hostname.
D:Post-transfer audit logs can identify accounts, destination applications and timestamps for an investigation, and they should be retained. However, the spreadsheet may already have left the organization by the time a log review begins. The stated requirement includes preventing unauthorized transfers and preserving evidence. A DLP policy capable of blocking before completion, logging policy decisions and supporting approved exceptions addresses both requirements. Audit-only operation would provide detection but not the requested preventive effect.
Question 253
An enterprise auditor needs a repeatable way to compare Windows and Linux host configurations with approved security baselines and to report machine-readable deviations. The team already operates tools that understand security-content standards. Which approach best satisfies the requirement?
- Run host vulnerability scans focused on patch levels but treat their results as complete evidence of configuration-baseline conformance
- Use SCAP-compatible benchmark and configuration evaluations with versioned assessment content
- Rely on handwritten administrator assurances without technical configuration evidence
- Export desired configuration-management templates and infer that every host still matches them without checking observed state
Explanation
Correct Answer
B:The Security Content Automation Protocol ecosystem supports standardized machine-readable configuration and vulnerability-assessment content, including checklists and rules consumed by compatible tools. Versioned benchmarks let the auditor identify exactly which settings were evaluated on which hosts and compare results over time. The team must choose profiles applicable to each operating system, verify scanning privileges and document justified exceptions; a standard format does not make every rule universally appropriate. This method produces repeatable, attributable compliance evidence rather than subjective declarations, while still requiring people to interpret findings and business exceptions. Store both the benchmark version and the actual observed host-state results.
Incorrect Answers
A:Vulnerability scanning can identify missing updates or recognizable insecure versions and supports host security assessments. Yet an approved hardening baseline also includes policy settings, permitted services, file permissions and audit rules that a patch-only scan may not measure. Reporting those patch results as complete baseline compliance would overstate coverage. Versioned SCAP-compatible configuration checks provide machine-readable results against explicit controls, while patch data remains an additional input.
C:Administrator attestations can supplement governance records but do not independently demonstrate that a required setting is present on a server. Humans can misunderstand the baseline, miss configuration drift or report intentions instead of observed state. The auditor needs reproducible technical measurements and an exception process tied to named systems and approved profiles. Self-reported compliance alone does not provide that validation.
D:A configuration template records intended settings and is useful for building a repeatable secure baseline. Real machines can drift because of manual changes, unsupported agents, failed deployments or local overrides. Merely storing templates does not measure current compliance. The audit requires observed host-state checks, mapped to versioned baseline rules, and evidence of which requirements pass or fail. SCAP-compatible evaluations can provide that machine-readable comparison when the relevant platforms and content are supported.
Question 254
A security manager proposes replacing the organization's daily intrusion-monitoring service with a vulnerability scanner that runs every Saturday. The scanner identifies missing patches and exposed services. Which assessment of this proposal is most accurate?
- A weekly scanner will immediately detect and investigate every intrusion attempt that occurs between scans
- Once the scanner reports no issues, runtime attacks against patched applications are impossible
- Vulnerability scans can identify exposure only if they also capture full packet contents of every network session
- Scheduled vulnerability discovery and continuous intrusion monitoring serve different purposes and should not be treated as interchangeable
Explanation
Correct Answer
D:A vulnerability scanner answers questions such as which hosts run affected software, lack updates or expose weak configurations. Intrusion detection instead looks for suspicious activity as it happens using endpoint, network and identity telemetry. The two controls can inform each other—for example, a vulnerable host can raise an alert's priority—but a weekly assessment cannot replace continuous event collection and response. The manager should retain time-sensitive monitoring while using scan results for remediation prioritization, coverage analysis and risk tracking. Both require configuration and visibility checks, but their goals, time horizons and evidence are different.
Incorrect Answers
A:Weekly vulnerability scanning inspects known weakness indicators during its configured windows. It may not observe an attacker authenticating with stolen credentials on Tuesday or detect rapid malicious process activity on a host. An empty Saturday report does not substitute for events collected during the week. Detection of ongoing suspicious behavior requires relevant continuous telemetry, detection logic and response procedures.
B:Patching known vulnerabilities reduces one class of exposure but does not prevent every intrusion route. Valid accounts may be misused, new application logic errors can arise, and zero-day flaws may be exploited before a scanner recognizes them. A clean scan also reflects the scope and checks it successfully performed. A security operation needs active monitoring and incident response in addition to periodic configuration and vulnerability assessments.
C:Most vulnerability scanners gather service information, configuration results and signatures rather than maintaining complete packet payload capture. Capturing every byte is neither necessary for scanning nor sufficient to determine all types of risk. Network encryption and host-only activity would also complicate packet-based detection. Confusing collection methods does not resolve the proposal's fundamental mismatch between exposure assessment and ongoing attack observation.
Question 255
An incident team must retain privileged-access logs for three years under a legal and internal policy. A compromised administrator account could otherwise delete or alter ordinary files on the central log server. Which log-storage approach most directly protects the evidence?
- Store the only log copy as an editable file owned by the same administrative account
- Rely exclusively on short-lived local event logs that rotate every week
- Forward logs promptly to access-restricted, integrity-protected immutable storage with policy-based retention
- Encrypt the network connection during forwarding but permit unrestricted deletion from the destination
Explanation
Correct Answer
C:Use authenticated forwarding and a storage service configured with immutable or write-once retention controls that prevent even ordinary administrators from modifying protected records during the required interval. Apply role separation, restricted read access, reliable timestamps and lifecycle policies matched to legal requirements. Verify that log sources are actually arriving and that deletion attempts are denied. Immutability does not guarantee an event was collected correctly or that its contents were truthful, so collection health and audit trails still matter. The design nevertheless directly addresses post-collection tampering by a compromised privileged identity and supports future investigation.
Incorrect Answers
A:An editable log file controlled by the same administrator who may be compromised is vulnerable to deletion or modification. Even accurate initial events may be altered before investigators receive them. A dedicated evidence store with separation of duties and tamper-resistant retention reduces that risk. Local operational copies may remain convenient, but they should not be the sole authoritative record when privileged-account misuse is part of the threat model.
B:Weekly local rotation is incompatible with the three-year retention requirement and can erase the earliest evidence of an intrusion. Logs on a compromised host may also be altered before collection. Endpoint logs can support immediate troubleshooting, but important security events should be forwarded in a timely and authenticated manner to a separate protected destination. Retention and integrity need to be designed together, not replaced by a short rolling buffer.
D:Encryption in transit protects log records against eavesdropping and some tampering while they cross the network, but it does not prevent a privileged account from deleting them after delivery. The case explicitly includes a destination administrator who might be compromised. End-to-end evidence protection requires authorization boundaries, retention enforcement and integrity controls at rest, in addition to secure transport. A TLS-protected upload to freely editable storage leaves the central risk unresolved.
Question 256
An operations queue contains 200 low-confidence port-scan alerts against test hosts and one alert showing a privileged cloud account created a new external access key, followed by a large sensitive-data export. The security team can investigate only one event immediately. What should determine the initial escalation?
- Escalate the port scans because the greatest number of alerts always represents the highest severity
- Treat all alerts as equal because the SIEM already assigned them a label
- Prioritize the privileged export event using asset criticality, behavioral context and likely business impact
- Investigate the privileged export only after confirming the port-scan alert queue has no false positives.
Explanation
Correct Answer
C:The account has elevated authority, a new external-access credential was created and a large sensitive export followed. Those connected facts raise the potential for account compromise or unauthorized data movement and justify urgent triage. Confirm identity activity, expected change records and destination details, then apply proportionate containment if the sequence is unauthorized. The alert count from the port-scan queue is less decision-useful than the likely loss and immediacy of the privileged event. Escalation reflects combined confidence, exposure, criticality and impact, not a raw count of notifications or an assumption that all anomalies are confirmed attacks.
Incorrect Answers
A:A large number of observations can indicate broad activity, but counts do not directly measure risk. Low-confidence scans against isolated test devices may have limited impact or an authorized explanation. The privileged key and export event affects sensitive data and suggests an active misuse path. Triaging only the most numerous category could divert analysts from a potentially consequential event that requires immediate validation and containment.
B:SIEM labels provide an initial classification but are derived from rules whose accuracy varies with local configuration. The same technical alert may be harmless in a laboratory and serious when associated with a production identity or sensitive record store. Analysts need context such as who performed the action, whether the credential was expected and what information may have left the organization. Treating all labels as equally urgent prevents risk-based allocation of scarce response capacity.
D:False-positive tuning can free analyst capacity and improve alert confidence, but it is not a prerequisite for investigating an apparent privileged key creation followed by sensitive-data export. Those actions have potentially immediate consequences for high-value information. The team has insufficient capacity for simultaneous investigation, so it should prioritize by asset importance and evidence of harm. Delaying the stronger event until a less critical alert queue is cleaned up reverses that risk-based order.
Question 257
A network IDS blocks known malicious payloads using signatures, but a new intrusion changes command patterns and uses an unusual sequence of legitimate cloud API calls. The existing signatures never fire. Which monitoring change best improves the chance of detecting this behavior?
- Retire signature analytics and use only a behavioral baseline for all network and cloud API activity
- Record approved cloud API operations in an inventory but avoid examining the order and timing of live calls
- Increase the log-retention period without applying any detection logic to the new records
- Add behavioral and anomaly analytics over relevant API, identity and network activity alongside maintained signatures
Explanation
Correct Answer
D:Behavioral analytics can flag unusual identity-to-resource relationships, high-volume API sequences, unfamiliar source locations or a combination of otherwise legitimate actions that indicates abuse. Establish baselines and tune thresholds to avoid treating every change in working patterns as malicious. Combine API audit records with identity and network context, and preserve signatures for known indicators. Analysts should validate alerts against approved automation and changes because anomalies are clues, not automatic proof of attack. The layered approach is more resilient to novel tactics than depending on one fixed payload pattern while retaining the efficient known-threat coverage of signatures.
Incorrect Answers
A:Behavioral baselines can reveal suspicious changes that fixed signatures miss, but they can also produce false positives and need careful tuning for evolving legitimate workloads. The described evasion does not mean known malicious payload signatures have stopped being useful. Maintaining both approaches gives defenders complementary coverage across recognizable exploits and novel sequences. Removing the existing signatures would unnecessarily forfeit a valid detection channel while adding an unproven replacement.
B:An application and API inventory helps identify expected operations, owners and business roles, which can improve the context for anomaly detection. But the intrusion specifically uses an unusual sequence of otherwise legitimate calls; examining names on an inventory list would miss that behavioral pattern. The team needs time-correlated API, identity and network telemetry to test what actually occurred, not only an approved catalogue of possible functions.
C:Longer retention helps retrospective analysis, but the events still need parsing, correlation and meaningful detection criteria. Simply storing logs for more months does not alert the team when a legitimate API is used at an abnormal rate or from a new location. The organization should preserve relevant events while also using analytics to compare current activity to established baselines and multi-source indicators. Retention is supportive, not the detection change requested.
Question 258
A company publishes an HTTPS business API for five contracted partners. The application must not be reachable from arbitrary Internet hosts, and engineers have confirmed the partners' stable public egress IP ranges. What firewall change best satisfies the access requirement?
- Allow every source to reach all TCP ports on the API server because TLS is enabled
- Permit only the approved partner source ranges to the required HTTPS listener and deny unrelated inbound traffic
- Allow the five partner source ranges but expose the same API through an alternate unrestricted public origin address
- Open only TCP 443 to the API from all Internet addresses and rely on application authentication for partner restriction
Explanation
Correct Answer
B:Apply a rule matching the five partners' verified source address ranges and the exact destination address and port used for the HTTPS API. Include the application's load-balancer topology and any health-check sources required to keep the service functioning, while preserving a default-deny stance for other inbound traffic. Validate partner connectivity and confirm unapproved sources are rejected using controlled tests. Source addresses alone do not replace application authentication, and partner IPs can change, so the rule needs an owner and maintenance process. It directly narrows the network attack surface without blocking authorized HTTPS use.
Incorrect Answers
A:Transport encryption protects communication content and authentication when configured correctly, but it does not restrict which Internet hosts can attempt to contact the service. A broad allow rule exposes unnecessary services and increases opportunities for exploitation or denial-of-service. Even if the application separately authenticates callers, a narrow network policy reduces unwanted exposure. TLS and firewall source restrictions address different threat layers and should be used together.
C:A narrow rule on the advertised API endpoint is useful, but the alternate unrestricted origin leaves a second path for arbitrary Internet hosts. Attackers could bypass the restricted listener and reach the backend directly. Network policy must cover every reachable ingress path, including load balancers, public origins and disaster-recovery endpoints. The supported solution restricts partner sources and the required HTTPS listener consistently rather than relying on one protected address while other routes remain open.
D:Limiting the exposed port to HTTPS reduces unnecessary services and application authentication remains essential. However, arbitrary Internet hosts could still reach the application listener and attempt exploitation or resource exhaustion. The stated requirement says only five contracted partner source ranges should have network reachability, and those ranges are stable. A firewall source allowlist to the exact HTTPS destination provides that additional boundary while retaining application-level identity checks.
Question 259
Several business units use hundreds of cloud applications through corporate identities. Procurement discovers that employees are transferring regulated documents to unsanctioned file-sharing tenants. Security wants to inventory shadow applications, monitor cloud usage and apply policy to approved versus unapproved SaaS connections. Which security capability best fits?
- Review only corporate single-sign-on reports without observing unsanctioned applications that bypass the identity provider
- Inspect outbound email attachments for confidential documents while omitting browser and SaaS upload telemetry
- A cloud access security broker or equivalent SaaS security control integrated with identity and cloud activity
- Compare procurement purchase orders with a manually maintained approved-SaaS list but omit live identity and network usage evidence
Explanation
Correct Answer
C:A CASB or comparable SaaS security platform can discover cloud services through supported identity, proxy and API integrations, evaluate application risk and apply data-access policy according to user, tenant and content. It can identify unsanctioned applications, distinguish corporate and personal destinations and create actionable security events. Coverage depends on which clients, networks and SaaS APIs are connected; agentless API discovery alone may miss unmanaged services. Integrate DLP, identity controls and approved exception handling where appropriate. This addresses the governance and data-transfer problem at the cloud-service layer rather than expecting unrelated local infrastructure to detect every service.
Incorrect Answers
A:Identity-provider sign-in reports can reveal SaaS services integrated with corporate SSO and are a useful input to shadow-application discovery. Employees may also use personal identities or OAuth flows outside the configured single-sign-on catalog, leaving unapproved tenants invisible to that view. The requirement includes discovering broad SaaS usage and enforcing policy across connections. A CASB or equivalent service with identity, proxy and supported cloud API data offers a more complete picture than SSO reports alone.
B:Email DLP inspection can help protect regulated files sent as attachments and may be an important part of the overall program. In this scenario the transfers are to unsanctioned file-sharing tenants, often through browsers or cloud application APIs rather than email. An email-only control would miss many relevant sessions and would not inventory shadow applications. SaaS-aware discovery and policy enforcement must observe the actual cloud access channels, with content controls layered where supported.
D:Purchasing records can establish which providers have formal contracts and provide a useful sanctioned-application baseline. Employees can still obtain unauthorized services using personal payment cards or free plans, so procurement alone cannot quantify actual shadow usage or data movement. The company needs observed identities, tenants and application connections before making a policy decision. A cloud access security broker combines those signals with app risk and enforcement; a static inventory cannot substitute for them.
Question 260
A hospital's managed browsers must block malicious sites and prohibited content categories. A phishing page has also been discovered at one path of a legitimate multi-tenant file-sharing service that doctors use for patient-care documents. Blocking the entire service domain would disrupt clinical work. Which centrally managed web protection most directly enforces the policy with suitable URL-level granularity?
- Use DNS reputation blocking alone for the entire file-sharing hostname, with no exception mechanism for the legitimate clinical paths
- Record browser history centrally and ask employees to avoid a prohibited URL after it has already been visited
- Use endpoint malware scanning alone, because it can determine whether every web category violates organizational policy
- Apply centrally managed URL and category rules at an appropriate secure web gateway, using permitted HTTPS inspection where necessary and scoped exceptions
Explanation
Correct Answer
D:A secure web gateway can apply enterprise URL categories and, when configured for suitable HTTPS inspection, enforce decisions for particular paths on a shared legitimate domain rather than blocking all clinical use. Administrators should use explicit allow or block precedence, approved exceptions, policy testing and logging to avoid disrupting patient-care workflows. TLS inspection may require trusted certificates, privacy safeguards and exemptions for sensitive or incompatible traffic, so it is not appropriate to decrypt everything indiscriminately. The decisive feature is a central policy enforcement point with enough web-request context to distinguish the malicious path from authorized use. Domain-only DNS controls cannot usually provide that granularity; endpoint malware scanning and passive telemetry answer different security questions.
Incorrect Answers
A:DNS filtering makes decisions mainly on domain names and sometimes related DNS indicators. It can block a malicious hostname but cannot reliably distinguish two HTTPS URL paths on the same legitimate service when the needed path information is not visible in DNS. Blocking the complete file-sharing hostname would interfere with the clinical workflow described in the question. DNS controls may remain a valuable first layer, but URL-aware inspection and explicitly governed exceptions are needed for this particular mixed-use site.
B:Central browser telemetry helps investigators and administrators understand usage trends, but retrospectively recording a visit does not prevent employees from reaching the phishing page at the time of exposure. A user warning can supplement enforcement, yet voluntary compliance is insufficient for a mandatory category and URL policy. The hospital needs a control in the web-access path that can evaluate requests before the relevant content is delivered. Visibility and enforcement are related but materially different functions.
C:Endpoint malware scanners can detect known malicious binaries, scripts or behaviors, but their ordinary malware verdicts do not implement the hospital's chosen categories and path-specific access restrictions. A site can be prohibited by policy without delivering malware, while a legitimate site can contain a compromised path. The requested decision belongs to centrally governed web-access filtering with sufficient URL context, not to host-based malicious-file detection alone. Endpoint security remains useful defense in depth.