CompTIA Security+ SY0-701 Practice Test 27
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.
Question 261
An attacker connects a small laptop to an unused switch port and starts a DHCP server that offers a malicious default gateway to employees. The campus switches already know which uplink ports lead to the approved DHCP infrastructure. Which switch control best prevents unauthorized offers from ordinary user ports?
- Use an intrusion sensor to alert on unexpected DHCP offers without blocking server replies on user access ports
- Permit DHCP replies from every interface and rely on antivirus to identify malicious gateways
- Enable DHCP snooping, trust the legitimate server-facing ports and drop server replies from untrusted access ports
- Limit each access switch port to one learned MAC address without distinguishing DHCP client and server messages
Explanation
Correct Answer
C:DHCP snooping establishes a trust boundary between authorized server-facing switch interfaces and untrusted client access ports. The switch can accept client requests from access ports while rejecting DHCP server offer or acknowledgement messages arriving on those untrusted interfaces. Administrators must accurately mark uplinks and relay paths and validate operation across VLANs, because incorrect trust settings can interrupt legitimate address allocation. The feature also builds useful bindings for complementary controls, but the immediate protection is stopping the rogue server from distributing attacker-controlled gateways at the access layer before endpoints accept those parameters.
Incorrect Answers
A:An IDS can identify some rogue DHCP responses and notify network operations, which is useful for investigation. Alerting after packets are observed does not reliably stop an attacker from winning a client lease and pushing a malicious default gateway. The switches can enforce a clearer boundary by marking approved server-facing ports trusted and dropping offers or acknowledgements seen on untrusted access ports. Detection is complementary, but prevention at the switching edge is the requested control.
B:Allowing replies from every port preserves the attacker's ability to win the lease race and distribute a malicious gateway. Endpoint antivirus may detect malware installed later, but it does not necessarily recognize a validly formatted DHCP response as hostile. The correct boundary is on the switch access interface where unauthorized server traffic appears. Relying on downstream endpoint tools leaves the network-configuration manipulation unprevented.
D:Port-security MAC limits can discourage simple hub attachment and may reduce some unauthorized-device sharing, but a rogue DHCP server can operate from a single laptop using one allowed source MAC. Such a limit does not verify that DHCP offers originate only on approved infrastructure ports. DHCP snooping specifically filters server-origin responses at untrusted interfaces while permitting legitimate client requests. Switch-port identity controls are useful additional safeguards, not a substitute for the protocol-specific trust boundary.
Question 262
An organization is investigating mail that appears to come from its finance domain. Its administrators want a way for receivers to check whether a sending server is authorized by the domain and to verify a cryptographic signature over selected email headers and body content. Which statement accurately distinguishes the mechanisms?
- SPF verifies a message signature using DNS keys, whereas DKIM checks whether the connecting sender IP was authorized
- SPF guarantees that the visible From address matches the domain in every case without alignment rules
- DKIM guarantees the visible From domain is aligned with its signature whenever cryptographic verification succeeds
- SPF authorizes mail-sending hosts for a domain; DKIM verifies a domain-associated message signature
Explanation
Correct Answer
D:SPF and DKIM answer complementary authentication questions. SPF checks whether the connecting sender IP was authorized for the applicable envelope or HELO domain based on DNS policy. DKIM verifies that specified message content matches a signature from a domain that controls the associated public key. Neither mechanism encrypts the email or fully proves the human sender's identity. Receivers commonly combine them with DMARC alignment to evaluate spoofing of the visible From domain. Understanding the different domains involved is crucial when investigating apparent finance-domain impersonation, especially with forwarding or third-party mail providers.
Incorrect Answers
A:This reverses the two mechanisms and is a common mail-authentication confusion. SPF evaluates the connecting IP against authorized hosts for the envelope or HELO domain; it does not validate a message-body signature. DKIM verifies selected signed headers and body content using a DNS-published public key associated with the signing domain. Neither independently establishes visible From alignment. Understanding which identity is checked matters when deciding whether a spoofing defense needs DMARC as well.
B:An SPF pass means the sending IP is permitted for the domain identity checked by SPF, which can differ from the visible header From domain. Forwarding also affects SPF outcomes. DMARC adds alignment requirements tying authenticated domains to the displayed From domain; without that, a message can pass SPF for an unrelated envelope identity. Therefore a raw SPF result alone cannot guarantee the claimed brand identity seen by a recipient.
C:A valid DKIM signature proves that the message matches signed content for the DKIM signing domain; that domain need not be the same as the address shown in the visible From header. An attacker can sign mail with a domain they control while displaying a different apparent sender. DMARC evaluates alignment between an authenticated SPF or DKIM identity and the visible From domain. DKIM verification alone therefore cannot guarantee the visible sender alignment requested.
Question 263
A company publishes SPF and DKIM records, but phishing messages with a forged visible From address continue to reach customers. Security wants receiving mail services to apply a consistent policy when messages cannot authenticate using a domain aligned with the visible From address, and wants reports of failures. What should it configure?
- A DMARC policy with aligned SPF or DKIM evaluation and aggregate reporting for the sending domain
- Require DKIM signatures on outbound messages but do not specify a DMARC policy or alignment for the visible From domain
- An SPF record that grants every Internet IP permission to send for the domain
- Publish an SMTP transport-encryption policy but no visible From-domain authentication policy or reporting address
Explanation
Correct Answer
A:Domain-based Message Authentication, Reporting and Conformance tells receivers how the domain owner wants failures of aligned SPF or DKIM authentication handled, including monitor, quarantine or reject policies. Aggregate reports help identify legitimate senders that are misconfigured and sources attempting spoofing. Roll out enforcement after inventorying authorized senders so third-party services are not accidentally blocked. DMARC does not encrypt messages or stop look-alike domains outside the protected identity, but it directly addresses forged visible From addresses using domain alignment and reported receiver outcomes. DMARC reporting additionally supports safe gradual enforcement and visibility into third-party sender alignment.
Incorrect Answers
B:DKIM signing is useful for verifying the signing domain and detecting changes to protected message content. Nevertheless, a forged visible From address can coexist with a valid signature from an unrelated domain. Without DMARC alignment and published handling policy, receiving servers are not given the requested consistent decision about failures against the brand identity. DKIM is a necessary supporting authentication input, not the complete receiver-side policy and aggregate-reporting mechanism.
C:An unrestricted SPF record eliminates meaningful sender IP authorization rather than strengthening it. SPF also authenticates an envelope or HELO domain that may not match the displayed From domain. A strict-looking SPF record alone does not enforce visible From alignment or specify how receiver failures should be handled. DMARC supplies those alignment semantics and reporting feedback, with DKIM offering a second aligned authentication route when configured correctly.
D:Transport-encryption policies help mail systems protect SMTP connections and may reduce downgrade or interception risks. They do not establish whether a message was legitimately sent on behalf of the visible finance domain. An encrypted connection can carry a spoofed email just as easily as a genuine one. The requested outcome depends on aligned SPF or DKIM evaluation, receiver disposition and failure reports, which DMARC provides separately from TLS transport protection.
Question 264
A manufacturing firm receives purchase orders by email. Attackers recently sent password-protected archives containing malware to several departments, bypassing an extension-only filter. The firm wants to inspect attachments safely and block known risky content without preventing all legitimate purchase orders. Which gateway capability is most appropriate?
- Permit all archives because standard mail transport encryption protects recipients from malware
- Reject every message containing a document, even those from approved suppliers
- Treat a sender's display name as sufficient verification that an attachment is trusted
- Apply attachment inspection, controlled detonation or sandboxing where supported, and risk-based content policies at the mail gateway
Explanation
Correct Answer
D:A capable mail security gateway checks attachment types and signatures, analyzes archive contents where technically possible, and can detonate suspicious documents in an isolated environment to observe malicious behavior. Password-protected or encrypted archives may resist inspection, so the policy should quarantine or otherwise govern files that cannot be examined rather than simply mark them clean. Use sender authentication and risk-based allowlists for legitimate purchase orders, and provide a secure review workflow for exceptions. Such layered inspection addresses executable payloads and document exploits while retaining necessary supplier communication. It does not guarantee detection of every novel threat, so endpoint defenses still matter.
Incorrect Answers
A:Email transport encryption protects message transit between supporting systems; it does not establish that attached code or documents are harmless when opened by employees. A malicious archive can be transmitted securely. The firm needs content-aware analysis of incoming files and handling of archives that cannot be safely inspected, rather than relying on the fact that transport is encrypted. Sender verification remains complementary to attachment inspection.
B:Blocking all documents would stop many business-critical purchasing workflows while failing to explain how the enterprise should distinguish high-risk attachments from legitimate orders. A targeted policy can inspect file types and embedded content, quarantine uncertain items and provide a controlled exception path for verified supplier materials. Absolute rejection might be a special-case emergency response but is not a proportionate default for the stated requirement.
C:Display names are freely set by senders and can imitate familiar suppliers without authenticating a domain or verifying the attachment's behavior. Even a correctly authenticated supplier account may be compromised. The gateway should correlate identity reputation with content scanning, archive handling and observed behavior before delivery. Using only a name would make the spoofing and malware problem easier rather than harder to detect.
Question 265
An administrator discovers that a critical payment-server configuration file was changed outside an authorized maintenance window. The company wants evidence of future unauthorized changes to selected binaries, scripts and configuration files, rather than merely a list of running processes. What should it implement?
- File integrity monitoring with a protected approved baseline and alerts on relevant content or metadata changes
- Collect only endpoint process-launch alerts without comparing monitored file hashes, permissions or contents to a baseline
- Perform a manual configuration comparison once per quarter without alerting on file changes between reviews
- Forward successful administrator-login records to the SIEM without collecting protected-file modification events
Explanation
Correct Answer
A:File integrity monitoring compares selected files or metadata to a trusted baseline and reports unauthorized drift, such as changes to service configuration, executable hashes or access permissions. The approved baseline should be created under change control and stored with integrity protections so an attacker cannot silently update the reference. Authorized maintenance must refresh it through a documented process, or legitimate updates will generate unnecessary alerts. FIM cannot identify every attacker motive, but it provides direct evidence of the exact changes that matter for this server, helping the security team investigate unexpected modifications without waiting for application failure.
Incorrect Answers
B:Process telemetry can identify suspicious executables and show when services start, making it useful in a wider investigation. It may not report a subtle change to a configuration file or binary made by an otherwise authorized process. The company explicitly wants evidence of unauthorized modifications to selected files. File integrity monitoring tracks approved content and metadata baselines, while process alerts can provide context about who or what may have caused a later detected change.
C:Periodic comparisons can discover some long-lived configuration drift and supply audit evidence, but a malicious edit could affect the payment server for weeks before the next review. The requirement is evidence of future unauthorized changes to selected binaries, scripts and configurations, with useful detection timing. An integrity monitor can compare protected baselines and issue alerts when relevant content or metadata changes. Scheduled audits may confirm the state but provide weaker change visibility.
D:Authentication logs identify which identities accessed the payment server, helping investigators narrow a potential actor and time window. A legitimate administrator account or service may modify protected files while maintaining normal login events. Logs of access alone cannot prove which binary or configuration item changed, or whether its contents still match the approved version. File integrity monitoring supplies the direct modification evidence and should be correlated with privileged-access records.
Question 266
A developer's managed laptop attempts to upload an archive to a personal cloud folder. The active DLP rule finds an API credential pattern and blocks it, but many approved regression-test fixtures contain realistic-looking fake keys and trigger the same rule. Security wants to preserve blocking of real production secrets without forcing developers into unlogged workarounds. Which policy improvement best handles this distinction?
- Place developer workstations into a monitor-only DLP policy while leaving other endpoints in blocking mode.
- Create a permanent destination exception for the developer-owned cloud account after one sample file is confirmed synthetic.
- Combine validated secret or file fingerprinting with destination context and individually approved, time-limited DLP exceptions
- Retain a blocking policy for known production keys but downgrade all unrecognized credential patterns to notification-only.
Explanation
Correct Answer
C:Content fingerprints, validated test-secret patterns, and destination awareness let DLP policy distinguish approved synthetic fixtures from actual production credentials more accurately. When ambiguity remains, a documented exception can authorize a specific file or task for a defined period without broadly switching enforcement off. Reviewers should verify false-positive evidence, limit the exception by user, content, and destination, and retain immutable decision logs for later tuning. The key difference from a generic decision to deploy DLP is that blocking already exists and is working: this scenario asks how to make its exception workflow precise enough to preserve both developer productivity and meaningful protection against real secret exfiltration.
Incorrect Answers
A:Moving only developer machines to monitor-only would reduce interruptions but also allows their real credentials to leave for the personal cloud destination. Developers may have extensive production access, making this an important exposure rather than a harmless exception. The requested policy must distinguish verified synthetic fixtures from genuine secret material at the enforcement point; merely relaxing the action for an entire user group cannot meet that condition.
B:A destination exception can sometimes be justified for an approved enterprise service with additional monitoring. The personal cloud account here is not such an approved repository, and one harmless fixture does not establish that future uploads lack real credentials. Making the exemption permanent defeats inspection where developers could leak secrets. The safer decision evaluates sensitive content and the precise task, with reviewed scope and expiration, rather than whitelisting the entire destination.
D:A narrow pattern inventory might improve precision, and alert-only handling gives engineers useful feedback. However, newly rotated production credentials or keys from unlisted systems can match general secret patterns before they are registered in a fingerprint store. Automatically allowing all such matches to leave would weaken protection on the very data the policy is meant to catch. Conditional exceptions require validated test-data evidence and accountable authorization.
Question 267
A visitor plugs an unmanaged laptop into an open network jack in a conference room. The security requirement is that unknown devices must not immediately receive unrestricted internal access, even if the physical port is connected. Which network capability best addresses this?
- Network access control that authenticates devices or users and assigns access based on managed posture and policy
- Require 802.1X on office wireless access points while leaving wired conference-room switch ports unauthenticated
- Use a MAC-address allowlist for the conference ports without validating certificates, user identity or endpoint posture
- Restrict each conference port to a single connected MAC address while granting that address the default internal VLAN
Explanation
Correct Answer
A:NAC can require a device or user to authenticate using mechanisms such as 802.1X and evaluate managed posture or an approved guest identity before granting network access. A switch can place an unknown laptop into a restricted guest or remediation segment instead of the production VLAN. Policies must account for devices that cannot support the primary method and guard against unsafe fail-open behavior. Port authentication does not replace segmentation or endpoint security, but it directly prevents an arbitrary conference-room connection from becoming unrestricted internal reachability. Test exceptions and network availability so enforcement remains manageable.
Incorrect Answers
B:Wireless port authentication can protect one access method, but the visitor is using a physical wired jack that would remain open under this proposal. An unmanaged laptop could still reach internal routes if the switch port grants them. The policy must apply admission checks to the actual entry point, using NAC, user or device authentication and appropriate restricted segmentation. Protecting a different network medium does not meet the wired-device requirement.
C:A MAC allowlist may simplify peripheral onboarding and is sometimes used for devices unable to authenticate with stronger mechanisms. The reported address is easily copied or changed by an unmanaged laptop, so it does not give durable proof that the computer is trusted or compliant. The question requires that unknown devices cannot gain unrestricted internal reachability. NAC policies using stronger device or user identity and posture provide more reliable admission evidence than a claimed MAC alone.
D:Limiting the number of learned MAC addresses can reduce casual connection of multiple devices through a small hub, but a single unmanaged visitor laptop still fits the limit and can be placed onto the production VLAN. No posture or authorization check is performed. The requested security decision concerns which device or identity may enter which network segment, not how many Ethernet addresses a port learns. NAC should grant appropriate restricted access only after policy evaluation.
Question 268
Endpoint tooling reports that a digitally signed executable on a finance workstation created a new scheduled task, copied itself to a persistence directory and contacted an unfamiliar Internet host. The publisher certificate chains correctly. What should the analyst conclude?
- Investigate the suspicious behavior and provenance; a valid code signature does not establish the executable is benign
- Validate the software publisher certificate and compare its approved deployment package before examining runtime actions
- Disable endpoint process auditing to reduce alerts for trusted publishers
- Approve the executable from its matching finance product name and company software inventory entry without examining the unexpected task
Explanation
Correct Answer
A:A valid signature can establish that a file was signed with the corresponding private key and has not changed in a way that invalidates the signature, subject to trust and revocation checks. It does not prove the publisher's software is harmless or that the signer was never compromised. Persistence creation and unexpected outbound communications warrant reviewing process lineage, binary hash, certificate details, prevalence, change records and contacted destinations. The team should validate whether this is approved software before deciding on isolation. The behavior is the incident clue, while the signature is one contextual data point rather than an automatic safety verdict.
Incorrect Answers
B:Publisher validation and package provenance are useful checks, especially when attackers may substitute a malicious binary. Yet a valid signature can cover code that later becomes compromised, abused, or intentionally malicious. Here the signed executable has already created persistence and contacted an unfamiliar host, which are behavior-based investigation triggers. Provenance should be assessed alongside those actions, not treated as a reason to postpone collecting process and network evidence.
C:Turning off process auditing would weaken the ability to trace how the executable launched and what persistence it established. Analysts need those events to distinguish authorized software updates from stealthy execution. If a detection proves benign, tune it narrowly while preserving logs; do not disable a class of evidence because the binary is signed. Signature status and execution behavior should be evaluated together.
D:An asset inventory and familiar application name can provide initial context about whether a program belongs on a workstation. They do not prove that a running instance has not been hijacked or used for unauthorized persistence. The unexpected scheduled task, self-copy and external connection are more probative than a filename or catalogue entry alone. The analyst should validate version, code origin, process lineage and behavior rather than automatically dismiss the event.
Question 269
A security operations center wants to connect identity-provider anomalies, endpoint process chains and cloud API abuse into a common incident view. Its endpoint-only antivirus platform can show local malware events but has no identity or cloud integrations. Which detection architecture best fits the broader requirement?
- An XDR-capable platform with supported cross-domain telemetry ingestion and correlation
- Expand the endpoint antivirus detection rules but leave the platform without cloud API and identity-provider connectors
- A packet capture on a single branch router with no identity information
- Export separate weekly identity, endpoint and cloud incident reports without joining their event identifiers or timelines
Explanation
Correct Answer
A:Extended detection and response can bring endpoint, identity, email, network and cloud-service signals into related investigations, depending on actual connector support. A SOC can associate a suspicious sign-in with a process that obtained tokens and subsequent cloud API use, rather than chasing separate tools manually. Deployment still requires normalized identities, time synchronization, sufficient retention and appropriately restricted data access. The label XDR does not guarantee every vendor integration works; the architect should confirm the specified sources are connected and correlated. This matches the case's cross-domain incident requirement, not only malware scanning on one device.
Incorrect Answers
B:More comprehensive endpoint detections can identify additional malware behavior on managed computers and remain useful in the SOC. The stated investigation also requires correlating anomalous cloud sign-ins and API activity that the endpoint-only product does not receive. No amount of local signature tuning reconstructs events that never enter the platform. An XDR-capable architecture with verified cross-domain integrations can connect the required evidence, while endpoint protection remains one contributing sensor.
C:A branch-router packet capture can record traffic observed at that network point but cannot reconstruct events inside cloud audit APIs or show which user identity generated an action without additional correlation. Remote users and encrypted services may bypass the chosen observation point. Packet capture is valuable for targeted investigation, yet one router cannot meet the requirement for coordinated endpoint, identity and cloud security visibility.
D:Periodic exports can help leadership understand workload and provide evidence that individual controls are operating. They do not build a timely common incident view linking an account anomaly to a process chain and subsequent cloud API abuse. Without normalized identities and timestamps, analysts must manually reconstruct each relationship and may miss fast attacks. The requirement calls for active cross-domain correlation and response, not merely collecting unlinked summary reports from each tool.
Question 270
A privileged administrator normally manages storage systems from one region during scheduled hours. Over three days the identity begins executing bulk export commands from a new location just after midnight, although the credentials and MFA prompts appear valid. Which use of analytics is most appropriate?
- Automatically declare the administrator malicious without checking any approved work change
- Ignore the events because the identity successfully completed MFA
- Shut down all privileged accounts permanently to eliminate unusual behavior
- Use user and entity behavior analytics to flag deviations, then corroborate the commands and context before response
Explanation
Correct Answer
D:UEBA establishes patterns of normal user and entity activity and can raise the risk of abnormal command volume, location, access times and resource choices. For this administrator, correlate the new exports with identity events, change records, privileged session logs, destination storage and data sensitivity. A confirmed authorized disaster-recovery exercise could explain the events; unapproved new credentials and sensitive exports may justify immediate revocation and incident response. Analytics guides prioritization by comparing behavior to baselines, but anomalies require case-specific validation and human or policy-driven decisions rather than being treated as proof on their own.
Incorrect Answers
A:A deviation is an investigative lead, not definitive attribution to a malicious actor. Traveling staff, emergency maintenance and approved automation can all produce unfamiliar times or source locations. The data export volume and privilege level raise urgency, but the team should review change tickets and session evidence before reaching a conclusion. Conflating a behavioral anomaly with proof could cause unjustified disruption or mislabel legitimate activity.
B:A successful MFA challenge reduces some authentication risks but does not guarantee that every subsequent operation is authorized. Phishing-resistant methods can still coexist with stolen sessions or abused legitimate admin privileges. The unexpected bulk exports and location change should be examined even if the credential technically passed authentication. Monitoring privileged behavior complements login protections; it does not disappear once a second factor is used.
C:Disabling every privileged identity would severely affect administration, recovery and routine service management while failing to identify the observed account's actual risk. Proportionate containment should target suspected sessions or credentials when warranted by corroborated evidence and business impact. The organization needs a scoped investigative response, not an indiscriminate shutdown that creates a major availability incident and leaves root cause unknown.