CompTIA Security+ SY0-701 Practice Test 53
Question 520
An ICU's cardiac telemetry monitor requires a manufacturer update to remove a management-interface vulnerability, but applying it now would interrupt essential patient monitoring. The bedside telemetry stream uses a different approved network port. A firewall currently allows guest-wireless clients to reach the vulnerable management interface. Which bounded interim control most directly reduces exposure while clinicians plan a safe update window?
- Increase password complexity on the monitor but leave the exposed pre-authentication management endpoint available to guest clients
- Deny the guest-to-management route, restrict maintenance access to named biomedical engineering stations, preserve bedside telemetry and document the clinical patch deferral
- Rate-limit guest traffic to the management port while preserving universal guest reachability for emergency convenience
- Disable every service on the monitor, including the required telemetry channel, before clinicians authorize an alternate monitoring method
Explanation
Correct Answer
B:The temporary control should remove the unnecessary guest route to the vulnerable management plane while keeping the separately defined clinical telemetry port available. Firewall policy can allow maintenance only from named biomedical engineering stations with approved authentication and logging. Clinicians should validate telemetry continuity, sign off the time-limited patch deferral, and schedule the manufacturer's update under a safe maintenance plan. This differs from applying a generic network zone or a virtual patch to all device traffic: the case identifies one unnecessary pre-authentication management path that can be closed immediately without stopping patient monitoring. Residual risk still exists on authorized paths, so observation and update scheduling remain necessary.
Incorrect Answers
A:Password complexity helps against guessed credentials but does not eliminate exposure to a flaw that can be reached before authentication. The relevant attack path is the management listener being available from an untrusted guest network. Keeping that route open merely with stronger account passwords does not address a vulnerable pre-login interface. Password policy may remain a supporting control after the network path is restricted, while the manufacturer update is scheduled according to patient-safety needs.
C:A rate limiter may slow repeated connection attempts or some denial-of-service behavior, but it still permits unauthorized clients to communicate with the vulnerable management service. A guest user could deliver a malicious packet within the allowed rate. Because bedside telemetry runs on a separate approved port, administrators can remove the unsafe management reachability without interrupting clinical monitoring. The correct interim action limits the callers and functions that can reach the vulnerable interface, rather than simply reducing their traffic volume.
D:Stopping every network service would remove the attack path, but the device is currently providing clinically required telemetry. Doing so without a validated substitute could directly affect patient safety, which the scenario explicitly rules out. A security control for medical equipment must be assessed with the clinical owner and biomedical engineering team. More selective firewall restrictions can block guest management access while preserving the separate monitoring stream until the manufacturer patch is safely implemented.
Question 521
A university vulnerability scanner can enumerate listening ports on research servers without logging in. Its operators also have narrowly authorized credentials to inspect local operating-system patches, installed packages and secure configuration. The network-only results appear far less detailed than the credentialed report. Which explanation correctly distinguishes the assessment methods?
- Unauthenticated port banners reveal the exact version and configuration of every local package, including services with no listener
- A credentialed scan should intentionally ignore package inventory and only repeat banner enumeration
- Authenticated assessment can check local settings and patch state that a remote service scan cannot reliably observe
- Running the same unauthenticated port scan from another subnet provides equivalent proof of installed patch levels
Explanation
Correct Answer
C:Credentialed vulnerability scanning can inspect package databases, patch records, configuration baselines and local artifacts that are invisible or ambiguous from the network. Unauthenticated scanning instead observes reachable services and exposed interfaces, an important but narrower view. Combining both methods provides better coverage, with carefully scoped scan identities, credential rotation and tested safe checks. Some findings still require manual validation, especially backported vendor patches or fragile systems. The distinction is about evidence available through each trust boundary rather than asserting that one technique always proves every vulnerability or makes the other unnecessary.
Incorrect Answers
A:Remote banners may reveal some service names or versions, but they do not provide authoritative inventory of every installed library, inactive package or local security setting. Services can hide version details or be patched without changing visible banners. Host-level access supplies a different evidence channel. An unexposed package may still need a local update despite not advertising a version in its banner.
B:Repeating only network banner checks while holding approved credentials wastes the opportunity to inspect local patch and configuration state. Credentialed assessment is valuable precisely because it can access authenticated host metadata. Its permissions still need scope and secure handling; access does not require unrestricted administrator privileges everywhere. Local assessment should validate required settings rather than reproduce the limits of unauthenticated checks.
D:A scan from another network location might discover additional exposed ports because firewalls differ, but it still lacks local package and patch inventory. The perspective changes reachability, not access to operating-system configuration. Credentialed checks supply evidence that remote port observation alone cannot reconstruct accurately. It can reveal firewall reachability differences, but not the complete host inventory behind the services.
Question 522
A cloud team launches short-lived containers and virtual machines for batch jobs. Many run for only twenty minutes, so weekly vulnerability scans often miss them entirely, yet the same vulnerable image launches dozens of times daily. Which change most directly improves assessment coverage?
- Scan only the permanent bastion host and assume its software inventory matches every disposable worker
- Keep weekly scanning unchanged while retaining reports for a longer period
- Assess base images in CI and continuously discover and check newly launched workloads through automated inventory and runtime controls
- Replace cloud inventory tags with a spreadsheet maintained manually at the end of each month
Explanation
Correct Answer
C:Assessing signed deployment images before release can detect vulnerable dependencies before ephemeral instances are created. Dynamic asset discovery and automated checks at launch or during runtime then detect drift and issues introduced after build. Integrate findings with deployment identities and ownership so short-lived workloads are not invisible simply because weekly jobs miss them. Scan safely and avoid blocking critical releases without an agreed exception process. This moves vulnerability coverage closer to the lifecycle of the cloud resources rather than relying exclusively on a calendar interval designed for static servers. Continuous visibility complements, rather than completely replaces, periodic deeper assessment.
Incorrect Answers
A:The bastion has a different operating-system image and software purpose than short-lived batch workers. Its patch state is not evidence of the libraries embedded in the ephemeral deployment image. Scanning only permanent assets systematically misses the actual vulnerable workloads. An ephemeral worker may have entirely different dependencies and vulnerabilities from the fixed management bastion.
B:Longer report retention helps historical analysis but cannot create observations of instances that appeared and disappeared between scans. The coverage gap is in assessment timing and deployment pathways. The scanning system must adapt to workload lifecycle, not merely keep the same sparse results longer. The gap arises before a report is generated, when no short-lived worker is present during scanning.
D:A monthly static spreadsheet is likely to lag behind workloads lasting minutes and does not supply automatic evidence of each image version. Tags can help attribute ephemeral resources, but inventory should update as instances launch and terminate. Manual recording alone would be neither timely nor reliable enough for this environment.
Question 523
A chemical plant removed a fragile industrial controller from routine vulnerability scans after an earlier probe interrupted monitoring. Four years later the exclusion still has no named approver, expiry or alternative assessment, although the controller remains connected to production systems. Which governance requirement should be added?
- A time-limited, approved exception with accountable ownership, safe alternative checks, monitoring and periodic reassessment
- A permanent scanner exclusion stored only as an informal operator note without renewal dates
- Reclassify the controller as an untracked asset and close its historical risks when it no longer appears in reports
- Publish an annual statement that the excluded device has no new vulnerabilities even though it is not assessed
Explanation
Correct Answer
A:Fragile systems can justify avoiding disruptive scans, but the residual exposure must still be managed. Record the risk owner, reason, scope, expiry, operational safeguards and safe alternative vulnerability assessment, such as passive monitoring or vendor-advisory review. Schedule reassessment as threats and support status change, with clinical or industrial operations involved in approvals. A controlled exception preserves safety without converting an old incident into indefinite absence of security oversight. The key is accountable, evidenced risk treatment rather than forcing a hazardous scan or hiding the device. Safe checks should be defined with plant engineers so vulnerability oversight does not interrupt physical operations.
Incorrect Answers
B:A note in the scanner only tells technicians that the host is skipped; it does not establish who accepted the risk or when the decision should be reviewed. Persistent exclusions can survive staff turnover and software changes. Security governance requires visible ownership and periodic recertification. The control owner must revisit the risk as the device ages and new advisories emerge.
C:Removing the asset from tracked inventories makes risk less visible while the physical controller still operates. It also impairs patch decisions, incident response and lifecycle planning. A scanning exception should never become an excuse to erase the device or its prior unresolved findings from accountability records. The controller remains physically connected and should still appear in the asset and risk inventory.
D:An annual clean-status claim would be unsupported if the controller receives neither direct checks nor defensible alternative evidence. New flaws may emerge in its firmware or exposed protocols. Reports must disclose assessment limitations and monitoring results instead of asserting absence of vulnerability without testing. Any confidence statement must describe the safe alternative evidence and the limitations of unavailable scans.
Question 524
A SOC's SIEM creates five copies of one blocked-login alert when a log source retries delivery. In the same environment, a broad suppression rule hides every privileged sign-in anomaly, including different accounts and destinations. The team wants less noise without losing high-value detections. What tuning approach is justified?
- Collapse every alert sharing a public source IP, even if that host attempts several separate privileged accounts
- Deduplicate true repeat events using stable identifiers while preserving independent privileged sign-in indicators
- Keep one daily alert per source IP and discard all other activity even when separate incidents occur
- Replace the privileged-login rule with an aggregate count that never opens an individual investigation
Explanation
Correct Answer
B:True duplicates can be collapsed when they share event identifiers, source record hashes and relevant context, reducing repeated notifications for one underlying activity. Privileged sign-in anomalies should remain distinct when accounts, sessions or targets differ. Tune grouping windows and thresholds with test cases to ensure important events still produce actionable incidents. The objective is to improve analyst signal-to-noise without creating blind spots for abuse of powerful identities. Document tuning decisions and monitor missed detections after deployment. A broad source-IP suppression rule is attractive operationally but can erase meaningful differences hidden behind shared infrastructure.
Incorrect Answers
A:One IP can be used for multiple independent sessions, particularly behind shared NAT or cloud egress. Suppressing all activity from that address could conceal different attempted accounts, devices or attack phases. Deduplication must use evidence that records are truly repeats rather than treating superficial field similarity as identity. A single NAT address can represent multiple targeted user accounts and distinct malicious sessions.
C:A per-IP daily cap can merge unrelated users or later attacker activity into the first low-priority event. It sacrifices detection coverage for a simple metric and is poorly suited to high-value identity monitoring. Separate privileged sessions need enough context to investigate even when they originate from the same address. The first event might be innocuous while a later privileged-login attempt deserves immediate response.
D:Aggregate counts may support dashboards and trend analysis, but a privileged sign-in anomaly may require immediate investigation tied to a specific identity and session. A rule that never generates case-level evidence removes that operational path. Summaries should supplement, not suppress, meaningful incident signals. The operations team still needs an actionable alert tied to the suspicious privileged identity.
Question 525
An identity provider reports a suspicious cloud login to a finance user's account at 01:04. Five minutes later, the user's managed laptop runs an unusual PowerShell child process and cloud storage records a large object download. The SOC wants to determine whether these observations belong to one intrusion. Which monitoring method is strongest?
- Evaluate only the sign-in IP and timestamp, ignoring endpoint execution and storage-access records
- Associate the login with a hostname but omit process ancestry and later object reads from the case
- Join session identity, device process lineage and storage data-plane events using normalized timestamps and identifiers
- Declare completed exfiltration as soon as PowerShell executes after the anomalous sign-in, without confirming any data movement
Explanation
Correct Answer
C:A correlation timeline can link an identity session to endpoint parent-child processes, relevant command-line data and object-level cloud access, using reliable clocks and session or device identifiers. The combination helps determine whether the suspicious login and script activity represent one coordinated event or unrelated operations. Review authentication factors and actual data transfers before claiming theft. Preserve source logs and document uncertainty where mappings are incomplete, such as shared NAT addresses. This approach makes each telemetry source contribute what it can prove rather than asserting causality from temporal proximity alone. The result is a stronger incident hypothesis and more targeted containment.
Incorrect Answers
A:A sign-in alert supplies important identity evidence but cannot explain what a process later executed or which objects were accessed. Restricting the investigation to one timestamp may miss the connection between credential use, endpoint activity and cloud data. Cross-source context is needed to test the suspected chain. The object-access event is necessary to determine whether sensitive records were downloaded during the session.
B:Matching a device name can narrow the investigation but leaves out whether the suspicious command started from a document, scheduled task or user action. It also cannot establish which data operations followed. The SOC needs a sequence of actual activities rather than an isolated identity-to-host relationship. PowerShell command lines and child processes may identify the actual mechanism of the suspected compromise.
D:PowerShell may be used legitimately, and executing it does not prove that protected data left the environment. Storage download logs and network telemetry are required to assess actual transfer and destination. The incident is suspicious enough to investigate, but a categorical exfiltration verdict from process execution alone exceeds the evidence.
Question 526
A manufacturing organization sends security events from three branches to a central SIEM. One device runs five minutes slow, another runs two minutes fast, and analysts see impossible sequences in which a firewall appears to block traffic before an endpoint initiated it. What data-quality practice best restores meaningful correlation?
- Discard all original device timestamps and use only the SIEM's arrival time as the historical event time
- Synchronize event-source clocks and retain original times and known offsets during normalization and incident reconstruction
- Suppress clock-drift alerts after applying one identical UTC offset to every branch device
- Subtract five minutes from every event regardless of which device generated it or its configured time zone
Explanation
Correct Answer
B:Time synchronization through managed NTP or appropriate trusted time services reduces drift among devices, while normalization converts source timestamps into a common reference such as UTC. Retain raw time values, time zones and measured offsets so historical incidents can be reconstructed even before all clocks are corrected. Monitor drift and verify event ordering using known test events. A two-minute fast device requires different correction from a five-minute slow one; one global adjustment cannot fix both. Reliable time context is essential for joining network, identity and endpoint evidence into a valid attack sequence.
Incorrect Answers
A:SIEM ingestion time is useful for transport diagnostics, but network delays and batching mean it may differ significantly from when the source event occurred. Replacing all event times with receipt time can reorder incidents and hide causality. Preserve both source and ingestion values for an accurate reconstruction. Arrival timestamps can lag source events because of buffering or intermittent branch connectivity.
C:Applying a single UTC offset can handle a common time-zone conversion but not independent clock errors on separate devices. Suppressing drift alerts would hide continuing inaccuracies. Each event source needs controlled synchronization and transparent normalization rules. Different branch clocks have different errors, so one correction may reorder the evidence even further.
D:A universal five-minute correction would improve the slow device only if its error direction were handled correctly, while worsening devices that are fast or accurate. The SIEM should use source-specific offset data rather than assume every branch clock has the same misconfiguration. The fast device would move farther from the correct timeline under the wrong universal adjustment.
Question 527
Following a SIEM parser update, the company still receives its usual 400,000 firewall messages per hour. However a detection rule checking normalized fields `src_ip` and `dest_port` no longer triggers, even when raw logs plainly contain those attributes. Which troubleshooting action addresses the most likely failure?
- Increase SIEM log ingestion capacity to process more firewall messages even though raw event volume has not declined
- Inspect extraction and normalization mappings for the new log format, then retest rules with representative raw events
- Remove the detection rule because a zero alert count proves no suspicious traffic occurred
- Raise the rule's severity without repairing its missing source and port fields
Explanation
Correct Answer
B:Detection rules operate on normalized attributes rather than arbitrary text when the SIEM schema expects fields such as `src_ip` and `dest_port`. A parser change can leave raw events intact while extracting nothing into those fields, causing true events to fail the rule condition. Compare representative raw messages with parsed records, fix field mappings and verify detection using known test cases. Preserve source logs and check for related rules that depend on the same schema. This distinguishes event ingestion from semantic normalization and avoids treating the absence of alerts as proof that underlying activity disappeared.
Incorrect Answers
A:More ingestion capacity is sometimes needed when network sources outgrow a collector and data is lost before parsing. In this scenario the SIEM still receives its normal message volume, so throughput is not the observed failure. The parser update has stopped populating fields used by the detection rule. Inspect raw-to-normalized mappings and test representative events rather than scaling an already functioning intake path.
C:Zero detections following an ingestion or parser change may signal a broken analytic pipeline. Deleting the rule would convert a diagnostic symptom into a permanent monitoring blind spot. The SOC should validate known triggering examples before deciding the original rule is obsolete. A parser regression can silently suppress detections even when security events continue to occur.
D:Severity affects triage priority after a rule matches; it does not supply missing IP or port attributes for the condition. Increasing severity on a rule that never matches cannot restore coverage. The engineer must repair data extraction before tuning alert importance. A more urgent alert severity is useless if the matching fields are absent from normalized records.
Question 528
A revenue database normally sends roughly 1.5 GB of data externally per day. On Sunday night it transfers 80 GB through TLS to an unfamiliar cloud address while no backup change is scheduled. Executives ask whether the encrypted traffic can be ignored. Which analytic response is most appropriate?
- Assume the transfer is approved because the database team sometimes runs encrypted backups
- Compare the deviation with workload baselines, process identity, authorized jobs, destination ownership and data-access evidence
- Trust the destination because a successful TLS handshake proves it is the intended business recipient
- Identify the responsible employee using only the NAT gateway's public IP, without session or host correlation
Explanation
Correct Answer
B:An eighty-gigabyte transfer against a 1.5-gigabyte baseline is a significant anomaly that merits investigation rather than immediate attribution. Join network flow data with source process, identity, destination registration, scheduled jobs and database access logs. Determine whether a legitimate transfer was misconfigured or a compromised workload staged sensitive information. TLS may limit payload visibility, so contextual evidence is particularly important. The SOC should preserve the incident trail and apply proportional containment if risk is high. Baselines help identify deviations but do not by themselves prove exfiltration or misconduct; verification provides a defensible conclusion.
Incorrect Answers
A:A backup process can legitimately move large volumes, but the time, destination and size differ substantially from the observed baseline. Authorization must be corroborated with job records, process ownership and data content. Merely using encryption does not make an unexpected export approved. The Sunday destination and volume must be reconciled with actual approved backup jobs and processes.
C:TLS can authenticate a certificate presented by the destination but does not establish that a business owner authorized sending database records to that organization. An attacker-controlled endpoint can have a valid certificate. Destination legitimacy and approved data flows require separate verification. A newly registered attacker cloud service may also use a valid, trusted TLS certificate.
D:A NAT public address may represent many internal hosts, users and services. It cannot uniquely identify the responsible principal without source-port mapping, flow logs and workload identity context. Concluding employee attribution from that address alone risks misidentification and leaves the actual initiating process unexplored. A source NAT address must be joined to internal sessions and workload identity records for attribution.
Question 529
A SOC director celebrates a sharp fall in mean time to detect after the dashboard team removes incidents that stayed open longer than seven days. Some of the excluded investigations had the slowest detection timelines. The remaining data looks cleaner but management has not disclosed exclusions. What reporting defect has been introduced?
- A valid improvement because incidents older than seven days no longer count toward any detection objective
- An accurate metric as long as the system calculates the arithmetic mean of the selected convenient cases
- A fully transparent result because using a median would eliminate any need to mention missing incidents
- Selection bias that hides slow or unresolved incidents and makes detection performance appear better than it is
Explanation
Correct Answer
D:Removing unresolved or slow cases from a detection-time dashboard creates selection bias: the retained incidents are disproportionately easy or quick, so the reported mean improves without any operational change. Define consistent start and detection timestamps, document exclusions and handle still-open incidents explicitly rather than silently dropping them. Report counts and distribution alongside summary figures, so leadership sees whether long delays remain. A true improvement should persist under comparable inclusion criteria over time. The problem is not simply choosing mean versus median; it is altering the analyzed incident set in a way that conceals unfavorable performance.
Incorrect Answers
A:Removing difficult cases does not make their detection delays disappear from the organization's performance. A metric intended to represent incident detection should use a defined population and disclose legitimate exclusions. Otherwise the apparent improvement may come only from changing the denominator rather than operational capability. The director should compare performance over a stable incident population rather than dropping difficult cases.
B:The arithmetic formula can be calculated correctly on a biased subset and still misrepresent the true incident population. Selection criteria matter as much as the mathematical average. Excluding long-running or slow-detection cases without explanation may understate systemic delays and mislead resourcing decisions. This dataset omits precisely the slow observations most relevant to detection improvement efforts.
C:Medians can reduce sensitivity to extreme values but do not cure undisclosed omission of a class of incidents. The dashboard needs transparent inclusion rules and separate treatment of open or censored observations. Changing the summary statistic is not a substitute for honest population definition. A transparent report would disclose excluded investigations and show how they affect interpretation.
Question 530
A professional-services firm allows employees to use managed desktops and personal laptops for its client portal. Security discovers a set of devices running unsupported operating systems and wants to block access to confidential engagements from those machines without disabling otherwise healthy employee accounts. Which control offers targeted enforcement?
- Block the public IP addresses currently used by the unsupported devices without checking future device posture
- Require longer passwords for every employee while leaving unsupported machines authorized to reach the portal
- Install endpoint monitoring agents but permit full access even when the compliance engine reports unsupported software
- Use conditional access that denies the sensitive application when the requesting endpoint fails defined OS and device-compliance requirements
Explanation
Correct Answer
D:Conditional access can evaluate the requesting device's supported OS status, management enrollment and compliance state before granting a session to sensitive applications. Users on healthy managed devices can continue working while unsupported endpoints are denied or directed to a remediation workflow. Apply exceptions only through documented approvals, verify how device claims are trusted and monitor false positives. The control targets risky sessions rather than disabling employee identities globally. MFA remains useful but cannot alone compensate for an unpatched operating system allowed to handle confidential engagement data. The access rule can preserve approved employee access through compliant devices while blocking unsupported endpoints.
Incorrect Answers
A:Public IPs can change, be shared by many users or hide behind NAT, so they are weak evidence of a specific device's patch status. An IP block can disrupt compliant employees and fail when a noncompliant laptop changes networks. Conditional policy should evaluate verified device attributes rather than location alone.
B:Stronger passwords address credential guessing but do not fix unsupported operating systems with unpatched vulnerabilities. The goal is to restrict risky device sessions, not punish every account. Identity and device posture are complementary checks and should not be substituted for each other. Unsupported kernels can still be exploited after a user supplies a correct complex password.
C:An EDR agent can provide visibility, but a monitoring-only deployment does not prevent a noncompliant endpoint from accessing client records. The compliance verdict must affect authorization decisions for protected applications. Ignoring the failed status leaves the known unsupported-platform risk untreated. The client portal should enforce the compliance decision rather than merely collect a report.