CompTIA Security+ SY0-701 Practice Test 3
Question 20
A contractor connects a personally managed laptop to an internal guest-adjacent subnet and asks to open an administrator console. A manager argues that the private RFC 1918 source address alone makes the request trustworthy. Under zero-trust principles, which assessment is correct?
- Validate the contractor's identity, device condition, and authorization for the console independently of the source subnet
- Treat all corporate-addressed clients as trusted administrators
- Use successful DNS resolution of the console as evidence of user identity
- Waive conditional access whenever a request originates inside the office
Explanation
Correct Answer
A:Zero trust assumes that network placement does not, by itself, prove either who a subject is or whether its device is healthy. Access to an administrative console should be based on verified user identity, approved privilege, device posture, and current request context, with enforcement at the relevant access point. The contractor's personally managed laptop may lack required controls despite receiving a private internal address. A restricted, monitored access path or managed administrative device may be necessary. The application should grant only the authorized actions and re-evaluate risk as conditions change. This is a specific authorization decision, not simply a question of whether a packet can route to the console.
Incorrect Answers
B:Private corporate addressing only identifies where a packet appears to originate; it says nothing definitive about the user or endpoint's integrity. Insider threats, compromised devices, and incorrectly bridged networks exist inside corporate address space. Granting administrative rights to every internal client would remove meaningful authorization boundaries. Network segmentation can narrow exposure but must not replace identity and device-based access checks.
C:A successful DNS lookup demonstrates that a name could be resolved to an address. It does not validate the caller's identity, permissions, or endpoint security. Attackers and ordinary users can often resolve the same administrative hostname. Name resolution is a basic connectivity dependency and might even be manipulated; it cannot serve as authentication evidence for a privileged session.
D:Waiving conditional access for office-originating traffic assumes that office connections are inherently safe. The laptop is not centrally managed, and the requester is a contractor seeking administrative functions. Those facts call for stronger verification, not a location-based exception. Even if a corporate switch authenticates a port, the app must still authorize this specific principal and evaluate the current device and session conditions.
Question 21
At a headquarters entrance, employees sometimes hold a secure door open for colleagues without badges. The facilities team needs an entrance control that physically sequences one authenticated person at a time instead of merely recording the event. Which design fits?
- An access-controlled mantrap or security vestibule with interlocked doors
- A lobby camera with video retained for thirty days
- A monthly report comparing badge entries to visitor appointments
- An endpoint file-integrity monitor deployed on reception computers
Explanation
Correct Answer
A:A mantrap or access-controlled vestibule creates a controlled passage with interlocked doors, helping prevent one person from bypassing the authorization cycle by following another through a normally opened door. To actually enforce one-person passage, the design may require occupancy sensing, appropriate egress safeguards, and alerting; interlocked doors alone are not guaranteed to detect two people closely together. The request is specifically for a physical preventive barrier rather than retrospective observation. Integrating individual badge verification and safe emergency release is important so the access control does not create an unsafe exit. Guards and cameras remain useful secondary detective layers.
Incorrect Answers
B:A camera can show that tailgating happened, identify times, and support an investigation. The camera does not physically stop a badge holder from allowing someone else through a door. Even when signs advertise surveillance, that discouragement is different from the demanded one-person admission barrier. Video is complementary to controlled passage, not a substitute for it.
C:A monthly badge-to-appointment comparison may reveal patterns such as unexpected entries or incomplete visitor registration. Its results arrive well after each person has entered, so it cannot sequence or block a second person during the same entry cycle. Better reporting can guide physical improvements, but the requirement calls for a mechanism operating at the entrance in real time.
D:File-integrity monitoring detects unauthorized changes to files or configurations on a computer. It cannot prevent an employee from holding open a building door. Even if reception systems require security software, that endpoint protection operates on a completely different asset and threat surface. The physical tailgating issue needs a controlled pedestrian entry mechanism, not host-based software monitoring.
Question 22
In a dusty warehouse, moving plastic air curtains repeatedly activate motion detectors. The security engineer wants a reliable signal when a particular exterior service door changes from fully closed to open, regardless of moving curtains elsewhere. Which sensor should be installed on that door?
- A passive infrared sensor aimed across the moving curtains
- Fit a door-mounted vibration sensor that alarms on impacts but does not report the door’s open or closed position
- A wired or supervised magnetic contact switch at the door and frame
- A wide-angle camera that is reviewed only the next day
Explanation
Correct Answer
C:A magnetic contact switch provides a direct indication that the protected door has moved away from its frame, making it a better match than area motion detection in a space with moving curtains. A properly mounted and supervised contact can detect circuit opening or tampering, and its state can feed an access alarm or monitoring console. The engineer should account for door alignment, vibration, cable protection, and magnet placement to reduce nuisance events or deliberate bypass. It does not prove who entered, so camera footage and credential logs may still be needed for investigation. Nevertheless it measures the exact door-opening condition requested.
Incorrect Answers
A:A passive infrared sensor can detect changing thermal patterns when an object moves through its field of view. In this warehouse, air curtains and other environmental movement are already producing false alerts, so another motion sensor aimed at them would retain the underlying problem. The required event is the door's open/closed state, which is more directly measured at the door itself. Motion sensing could still support area coverage elsewhere.
B:A vibration sensor can detect forceful knocks or tampering and is credible for a warehouse service entrance. It does not continuously measure the door leaf relative to its frame, so a careful opening might produce little vibration while routine forklift movement triggers noise. The requirement is a reliable open-versus-closed status despite environmental motion, not evidence that someone struck the surface. A supervised magnetic contact measures the requested state directly and can be monitored for circuit tampering.
D:A camera can document whether someone used the door, but footage examined the following day is not an immediate door-position signal. Dust or poor lighting may also reduce image quality. Live video analytics could potentially detect a door opening, yet that additional capability is not specified. A door contact switch is simpler and more direct for the stated binary sensing requirement.
Question 23
A SOC creates a fake spreadsheet labeled as confidential payroll data and places it on an instrumented share that legitimate staff never need to open. Opening the spreadsheet generates an alert with the accessor's identity and session details. What security technique is being used?
- A normal production payroll export used for business reporting
- A honeytoken consisting of fake login credentials that alerts only when someone uses them to authenticate
- A honeyfile serving as a monitored deception tripwire
- An ordinary access-audit alert on the genuine payroll export that authorized employees open every business day
Explanation
Correct Answer
C:A honeyfile is intentionally planted deceptive content that is instrumented so unexpected access suggests exploration or possible misuse. Because no approved task needs the fake payroll spreadsheet, a read or copy attempt has a strong investigative signal compared with ordinary production-file access. The alert's actor and session details can help responders correlate the event with identity, endpoint, and file-service logs. Investigators must still rule out legitimate scanning or administrator maintenance before treating the alert as proof of malice. The decoy should not contain real sensitive records or grant additional access. This is a deception and detective technique, not a replacement for access controls on actual payroll data.
Incorrect Answers
A:A production payroll export contains genuine employee information for an operational purpose and would normally be accessed by authorized payroll staff. The stem says the spreadsheet is deliberately fake and that no legitimate workflow requires it. Treating a decoy as real payroll data would also introduce unnecessary privacy exposure. Its value is the abnormal interaction signal, not accurate business reporting.
B:A honeytoken is another legitimate deception mechanism, and fake credentials can reveal unauthorized account use when an intruder attempts to log in. This scenario instead describes an instrumented spreadsheet whose opening itself generates a file-access alert, regardless of any credential being submitted. The observable trigger and planted object are therefore characteristic of a honeyfile rather than a credential-use honeytoken. Both can feed the SOC, but they test different interaction events and should not be treated as interchangeable merely because they are decoys.
D:Monitoring genuine payroll exports is a valuable detective control, and excessive access can trigger an investigation. The share in the question holds a deliberately fake payroll file that legitimate staff have no business reason to open, providing a low-noise deception tripwire. On a real export, everyday reads are expected and need user, time, and volume analysis before being considered suspicious. The content, lack of legitimate users, and alert on any opening distinguish a honeyfile from normal auditing of production records.
Question 24
A company acquires another firm. One environment requires phishing-resistant MFA for administrators; the other allows passwords alone, and their log-retention policies differ. Leadership wants a prioritized account of what must change to meet the new enterprise baseline. What activity should the team perform first?
- Purchase a new logging platform before defining target requirements
- Make the two existing environments use one another’s current security settings without agreeing on the enterprise target baseline
- Perform a gap analysis comparing each current control with the agreed target baseline
- Declare existing controls compliant because both companies were previously audited
Explanation
Correct Answer
C:A gap analysis explicitly compares current controls against the approved future standard, identifies missing requirements, and records risk and remediation priorities. Here the team can measure administrative MFA coverage, log retention, data ownership, and exception handling at each acquired business unit. The findings support a sequenced plan, assigned control owners, resource estimates, and documented acceptance of unavoidable temporary risks. It is important to define the target baseline before assessing compliance, rather than judging two environments against arbitrary past practices. This provides the requested distance between current and desired states and produces evidence leadership can use to prioritize integration work.
Incorrect Answers
A:Buying technology before understanding the desired control state can waste funds or solve the wrong problem. The two firms may need a combination of policy changes, licensing, identity integration, and operational retention procedures, not merely a different logging product. Requirements and gaps should be identified first so procurement can be justified against measurable deficiencies and risk priorities.
B:Standardizing settings can reduce administrative inconsistency after an acquisition, but copying the controls of either company is not an evidence-based risk assessment. The password-only environment might weaken administrator protection; the stricter environment might still have inadequate retention for the new business. Leadership asked which changes are needed against an agreed future baseline. A gap analysis compares both current states with that target and prioritizes justified remediation rather than treating harmonization itself as the destination.
D:A past audit only confirms what was tested against that audit's criteria at a particular time. The new enterprise baseline may impose stronger or different identity and logging requirements. Assuming compliance would ignore concrete differences described in the question and may conceal transition risk. A merger requires reassessment against the new common requirements; historical audit reports are useful inputs, not a blanket substitute for the gap analysis.
Question 25
During a ransomware containment effort, responders need an urgent firewall rule so a trusted forensic host can contact a quarantined log collector. The standard change board will not meet until after the evidence window, but an established emergency-change procedure exists. What should the engineer do?
- Insert the narrow forensic firewall permit based only on a responder colleague’s verbal agreement, then omit the emergency approval record
- Obtain the authorized emergency approval, record scope and owner, and perform the required later review
- Wait for the next monthly change meeting despite losing the evidence opportunity
- Create one temporary rule permitting every incident-response workstation to contact the entire quarantined network until the investigation ends
Explanation
Correct Answer
B:Emergency change management allows time-critical security work while retaining a defined chain of responsibility. The engineer should use the authorized emergency approver, restrict the temporary rule to the forensic host and required service, record the change owner, reason, and intended expiry, and validate the actual effect. A retrospective change review can then confirm that the exception was necessary, evidence was retained, and the firewall returned to its normal state. This avoids the two failures the question sets against each other: missing the evidence window and bypassing governance entirely. The incident severity can justify accelerated approval, but not unlimited network access.
Incorrect Answers
A:A narrowly scoped rule could preserve the evidence opportunity, and a responder might reasonably seek rapid verbal coordination. But an informal colleague agreement is not equivalent to the organization’s established emergency-change authorization, and omitting the record weakens traceability and removal controls. The question explicitly says an emergency process already exists. The engineer should obtain the designated emergency approver’s authorization, document source, destination, purpose and expiry, validate the rule, and support the required retrospective review.
C:Routine scheduled approval is appropriate for normal changes, but the scenario says waiting would lose a narrow forensic opportunity during an active incident. The organization already has an emergency process precisely to avoid such harmful delay. A controlled emergency decision is more defensible than either ignoring the business impact or making an unapproved permanent exception. The normal board can review the action afterward.
D:A temporary incident rule might feel efficient when many forensic tools are involved, and responders sometimes need rapid containment access. The stated requirement is much narrower: one trusted forensic host needs one route to a quarantined log collector during a short evidence window. An entire-workstation and entire-network permit increases lateral-movement and evidence-tampering opportunities. Emergency change approval should still authorize the smallest necessary source, destination, service and lifetime, with monitoring and a deliberate removal trigger.
Question 26
Finance and sales departments share an invoicing application. A security update affects both groups, and the change board needs one accountable person to coordinate impact assessment, approvals, the deployment team, and a recovery plan. Who should hold that responsibility?
- An executive sponsor who originally approved upgrade funding
- The chair who facilitates the change advisory board meeting
- A named change owner accountable for this specific implementation
- The engineer assigned only to execute the installation commands
Explanation
Correct Answer
C:The named change owner accepts responsibility for coordinating the entire change lifecycle: describing business impact, consulting affected departments, securing authorized approval, confirming implementation readiness, and maintaining rollback ownership. The deployment engineer and advisory board provide specific technical or governance contributions, but those contributors do not remove end-to-end accountability from the owner. For this shared application, a designated owner ensures that sales and finance dependencies are considered together rather than independently assumed safe. A clear escalation path and post-implementation validation also help the organization distinguish who executed a task from who was accountable for the decision to proceed.
Incorrect Answers
A:An executive sponsor may establish business priorities and authorize funding, but sponsorship does not automatically make that executive accountable for every technical implementation detail. This change requires an identified owner who coordinates dependencies, approvals, validation, and rollback. The sponsor can escalate business conflicts or approve budgets while an assigned change owner manages the end-to-end execution and documentation.
B:The advisory board chair supports governance by organizing risk discussion, coordinating decisions, and making sure policy is followed. The chair is not necessarily the individual managing every impacted team and restoring service if deployment fails. The question asks for a single person accountable for a particular change, not for the person chairing the collective approval forum. Those responsibilities can be separated.
D:An implementation engineer may run the installer and validate a technical checklist, but the engineer's assigned duty in the question is limited to execution. Change ownership also requires coordinating stakeholders, approval evidence, recovery planning, and operational impact outside that person's installation task. Execution and accountability can reside with one person in small organizations, but the described role does not automatically carry the broader owner responsibility.
Question 27
An organization moves a finance database to another platform. Direct connectivity, user accounts, and table checks pass, but nobody has traced inbound overnight feeds or downstream reconciliation jobs and reports. What must the team add before declaring the change safe?
- Repeat only migrated row-count and table-constraint checks
- Benchmark the new database's peak read and write latency
- Recheck encryption-at-rest keys and database administrator entitlements
- Assess upstream data feeds and downstream consumers, schedules, and failure dependencies
Explanation
Correct Answer
D:A dependency impact assessment maps which systems send data into the finance database and which rely on its outputs. The team should record service accounts, connection paths, batch timing, file formats, API contracts, failure-handling behavior, and business owners, then exercise representative end-to-end workflows in a test environment. A database can pass direct connectivity tests while reconciliation jobs silently fail hours later. By identifying upstream and downstream dependencies before the migration, the team can set acceptance criteria, coordinate a suitable change window, and prepare a rollback plan that accounts for affected consumers. That is the specific missing analysis in the scenario.
Incorrect Answers
A:Verifying row counts and table constraints helps detect missing or malformed data during migration. Those checks are necessary but insufficient to show that external jobs will continue feeding and consuming the new database. A technically correct migrated table can still break an overnight batch process that relies on a changed endpoint or schema convention. The question specifically identifies unexamined cross-system dependencies as the gap.
B:Performance benchmarking can reveal whether the new platform handles expected transaction volume and latency targets. However, fast database queries do not guarantee that reporting jobs, scheduled imports, or dependent applications are configured for the new environment. The identified risk is the relationships around the database, not solely its raw performance. Both should be considered, but this choice does not close the stated analysis gap.
C:Key management and administrator permissions are important migration security controls. A changed encryption configuration can compromise confidentiality or availability, and privileged access should be reviewed. Yet the team already knows that upstream data feeds and downstream reporting dependencies are untested. Repeating only the database's internal security settings would not reveal external batch schedules, connection strings, or interface assumptions affected by the move.
Question 28
A staged identity-provider upgrade passes its build checks but intermittently rejects valid federated sign-ins from an important business partner. The planned production deployment is scheduled for tomorrow. What should the release manager do before promotion?
- Deploy because the installation package built successfully
- Limit verification to local identities and ignore external federation
- Remove failing test records so the release scorecard appears green
- Investigate federation failures and require agreed acceptance evidence before approval
Explanation
Correct Answer
D:The release manager should stop promotion until the staging failures are understood and the agreed acceptance criteria are met or a properly authorized risk exception is documented. Federation problems may involve signing keys, trust metadata, clocks, claims, or session handling, so testing must reflect affected partner login journeys and failure modes. Fixing the root cause in staging and repeating relevant tests gives evidence that production users will not experience the same issue. A change ticket should capture results, deployment prerequisites, and rollback conditions. The distinction is between measurable readiness and an unsupported assumption based on a successful build.
Incorrect Answers
A:A successful software build shows that artifacts were produced, not that business-critical authentication paths function correctly. The staging failures are evidence of unresolved compatibility or configuration risk. Releasing without investigation could lock partner users out of production systems. Controlled change considers service-level acceptance and dependency testing, not just whether the package compiled or installed.
B:Local authentication and partner federation use different trust paths, protocols, and identity-provider configurations. Success in one flow does not prove the other works. The partner's users are explicitly important, so ignoring their failures would conceal a known business impact. The test plan must cover applicable federation metadata, token validation, claims mapping, and sign-in patterns before deployment is considered acceptable.
C:Deleting failing records would destroy useful diagnostic evidence and misrepresent the change's readiness. It would not fix the cause of intermittent federation errors. Reliable approvals require accurate test results and an explicit record of risks, not cosmetic success metrics. The responsible team should retain reproducible failure evidence, investigate it, and escalate any proposed exception through the authorized decision process.
Question 29
A new endpoint execution policy blocks a critical clinical application at half of a hospital network's sites. The rollout has an approved change ID, a tested rollback package, and a responsible change owner. What is the best immediate restoration action?
- Create an untested local bypass for the blocked executable at each site
- Manually disable endpoint enforcement across all clinics without recording individual changes
- Execute the approved rollback, document impact, and investigate the policy in staging
- Continue deploying to the unaffected clinics before addressing the outage
Explanation
Correct Answer
C:The tested backout plan is the safest available way to return affected clinics to the previously working state while preserving change traceability. The owner should execute it under the approved change, record the scope and patient-care impact, confirm application availability, and retain telemetry describing which execution rules blocked the software. Investigators can then reproduce the failure in staging, add a narrowly justified allowlist exception if appropriate, and retest before rescheduling deployment. This avoids allowing an untested security bypass or continuing a rollout with known clinical consequences. The existing rollback evidence is decisive: it offers a known path back without obscuring who changed what.
Incorrect Answers
A:An emergency exception might restore some workflows but could unintentionally allow untrusted binaries or create inconsistent enforcement rules across sites. The question already provides a tested rollback specifically designed for this change. Introducing an untested bypass during an active clinical disruption adds risk and makes follow-up validation harder. Exceptions should be narrowly approved and tested when rollback cannot meet recovery needs.
B:Disabling enforcement broadly may restore the affected app but also remove protection from unrelated systems and create site-by-site drift. Without accurate change records, responders cannot reliably determine which endpoints are still protected. The approved rollback provides a repeatable, recorded recovery path. Manual disabling is therefore a higher-risk improvisation rather than the preferred governed response.
D:Continuing a faulty rollout increases the number of sites exposed to a known availability problem. The absence of visible failure at some clinics does not prove the new policy is safe for their applications or dependencies. Production health is already impaired, so restoring service and stopping further propagation take priority. Deployment should resume only after the cause is corrected and representative sites pass acceptance checks.
Question 30
A security patch requires a twenty-minute outage of a billing application. Daytime transactions are heavy, and the overnight billing run has a short but critical completion deadline. The patch is important but not associated with active exploitation. What should determine the deployment time?
- Apply it immediately regardless of the resulting customer disruption
- Automatically defer it to the next quarterly maintenance cycle
- Select an authorized window using business impact, risk urgency, and downtime tolerance
- Choose the first convenient daytime slot on the patch administrator's calendar
Explanation
Correct Answer
C:The change owner should coordinate a maintenance window with billing stakeholders that respects transaction peaks, nightly processing deadlines, risk exposure, and recovery capability. The twenty-minute restart must fit within an acceptable interruption period, with notice, prechecks, a rollback trigger, and post-patch verification. If no safe window exists within the risk deadline, leaders may approve temporary mitigating controls or an emergency exception with documented tradeoffs. The key is using business impact and technical risk together rather than treating either security urgency or administrator convenience as absolute. That disciplined scheduling is a core change-management responsibility.
Incorrect Answers
A:Security updates can be urgent, but deploying without regard to business impact may disrupt high-volume customer transactions or critical billing deadlines. The stem does not describe active exploitation requiring an emergency outage. A controlled risk assessment should weigh vulnerability severity, exposure, and service recovery capability against operational disruption. Immediacy alone is not a sound scheduling principle.
B:An automatic quarterly deferral could leave a known weakness exposed unnecessarily, especially if the system is reachable from risky networks. The correct schedule depends on the patch's security risk and the business's allowable downtime, not on a rigid interval selected without analysis. A routine maintenance cycle may be appropriate, but only if it meets the assessed urgency and operational constraints.
D:A patch administrator's convenience is a staffing consideration but cannot override customer-facing availability commitments or critical financial processing. A daytime slot may be easy for the engineer yet coincide with peak transactions. The deployment should be coordinated with service owners and recovery personnel, ensuring that the selected time accommodates both operational impact and timely vulnerability treatment.