CompTIA Security+ SY0-701 Practice Test 33
Question 320
Investigators find firewall records showing traffic from a shared NAT gateway to a suspicious IP address. The gateway serves hundreds of employees and service accounts. Leadership requests the specific employee responsible before any endpoint or identity correlation is performed. What should the lead analyst report?
- The gateway's public address uniquely identifies the employee who used the connection
- Attribution needs correlated NAT translation records, internal host/process evidence and authenticated account activity before naming a person
- Combine the firewall destination with a list of active directory users logged on to the shared subnet, without retrieving NAT port translations
- Use destination reverse DNS and the gateway’s source address as the final attribution evidence, without internal connection mapping
Explanation
Correct Answer
B:Shared NAT hides which internal source initiated a public connection unless the mapping and relevant ports can be recovered for the exact time. Investigators should link translation or proxy records to an internal device, then examine endpoint process activity and reliable account authentication. Even that can identify a machine or credential without proving the human operator, particularly if malware or stolen tokens were involved. Report the observed network facts and remaining attribution uncertainty rather than naming someone prematurely. This approach supports accurate incident investigation and prevents a mistaken disciplinary or legal claim based on a shared address.
Incorrect Answers
A:The same public gateway can carry sessions from many internal devices at once. Without translation mappings, source ports and timestamps, the observed external connection cannot identify a unique workstation, much less a human employee. Even a unique workstation may be controlled by malware. The public address is a routing identifier in this architecture, not a personal identity credential.
C:The subnet login list can identify candidate accounts active during an interval, but many people and service processes may share the same gateway concurrently. Without time- and port-specific NAT mapping, it cannot establish which internal host originated the suspicious connection. Even a mapped host does not necessarily prove a person acted, because malware can transmit in the background. Endpoint process and authenticated session records are needed before naming an employee.
D:Reverse DNS may attach a hostname to the suspicious remote service, which is valuable for contextual intelligence. It does not recover the private source address, ephemeral port or authenticated user behind the shared NAT gateway. A public address could represent hundreds of unrelated sessions. Investigators should correlate gateway translation logs with host and identity evidence; a destination name is not a reliable audit trail of which internal employee initiated the flow.
Question 321
A manufacturer issues company laptops to engineers. Some employees install personal games and unlicensed tools, but the existing firewall configuration is technically correct. Management wants a governance document that clearly states permitted and prohibited employee use of these devices. Which document best fits the request?
- An acceptable-use policy specifying employee responsibilities and permissible activities on company systems
- A firewall rule standard listing approved ports and address groups
- A disaster recovery procedure for reconstructing endpoints after an outage
- An endpoint application-control baseline that permits approved executable hashes but does not define user conduct or licensing obligations
Explanation
Correct Answer
A:An acceptable-use policy addresses how employees may use organizational assets, networks and services, including unlicensed engineering utilities. It can prohibit unauthorized personal software, unlicensed tools and inappropriate data handling while defining acknowledgment, enforcement and escalation. The policy should align with supporting technical controls and legal requirements but is not itself a firewall configuration. In this case, management needs employee-facing behavioral expectations across laptops, not a specific port list or recovery runbook. Clear ownership and communication make the rule enforceable even when an individual device's technical firewall policy is otherwise correct.
Incorrect Answers
B:A firewall standard prescribes technical configuration such as permitted services, network zones and rule review intervals. It may block some unwanted traffic, but it does not define whether employees may install games or unlicensed software. The misuse can occur even if firewall rules work exactly as designed. The organization needs a governance rule directed at acceptable behavior and device use, potentially backed by application control.
C:A disaster recovery procedure describes how to restore endpoints or services after disruption. It is not the main authority for permitted personal use, licensing or disciplinary consequences. Although unwanted software might complicate recovery, the request is prospective behavioral governance rather than rebuilding after a fault. A device acceptable-use policy is the appropriate policy-level document.
D:A device execution baseline can help technically prevent unapproved software from starting, which is useful after misuse is identified. It does not tell employees which personal activities or unlicensed programs are forbidden, how exceptions are requested, or the consequences of violating acceptable-use requirements. Management explicitly wants a behavioral governance document for company-owned laptops. The technical baseline should implement and reinforce the acceptable-use policy, not replace the employee-facing rule.
Question 322
The board approves a high-level requirement that accounts must use strong authentication. Security engineering must translate it into a company-wide measurable rule specifying minimum password length, blocklisted values and permitted exceptions. Which type of document should contain these exact mandatory parameters?
- A mandatory enterprise authentication policy saying passwords must be strong, without specifying any testable thresholds or exception limits
- An employee onboarding checklist for the help desk
- A general mission statement promoting secure access
- An authentication standard with testable mandatory password and exception requirements
Explanation
Correct Answer
D:A standard converts broad policy intent into consistent, measurable requirements teams can implement and audit. It can define minimum length, prohibited compromised passwords, MFA requirements where applicable, exception authority and verification mechanisms. Engineers can then configure identity platforms and assess compliance against known criteria. The board's high-level policy establishes what must be achieved, while the standard specifies mandatory technical parameters. In the scenario, reproducibility across all business units matters; leaving the values to informal guidance would lead to inconsistent access protection. A standard should also be maintained when threat guidance or supported authentication technology changes.
Incorrect Answers
A:A high-level policy can establish that strong authentication is obligatory and assign overall accountability. That is the instruction the board has already supplied. Engineering still needs an enforceable technical standard defining measurable password length, blocked credentials and approved exceptions across systems. Repeating broad policy language would leave each platform team to interpret strong authentication differently. The standard translates the intent into auditable implementation criteria, while the policy remains its governing authority.
B:An onboarding checklist can tell help-desk staff how to provision an account under an existing requirement. It is a procedure for one workflow, not the authoritative source of company-wide password parameters. If length or exception rules are inconsistent, checklists would replicate that confusion. The standard should define the criteria before procedures implement them.
C:A mission statement is directional and intentionally high level. It cannot be used as a precise acceptance test for blocked passwords, authentication factors or exception duration. A broad policy is similarly insufficient without implementing detail. The question requests measurable requirements that remain consistent across systems, which belongs in a prescriptive standard rather than organizational aspiration.
Question 323
A hospital has an approved identity policy and an account-provisioning standard. New hires still receive inconsistent clinical application access because different technicians take different steps. The security manager wants a document specifying sequence, approvals, verification and evidence to retain for each onboarding request. What should be written?
- A broad security policy restating that access should be limited
- An optional guideline suggesting that technicians be careful
- A step-by-step access-provisioning procedure with required checks and records
- A configuration reference listing the clinical application’s entitlement groups but omitting technician approval sequence and verification records
Explanation
Correct Answer
C:A procedure translates policy and standard requirements into repeatable actions by staff performing a defined workflow. It should specify how to validate the hiring request, obtain data-owner approval, assign role-based clinical entitlements, test login scope, record ticket identifiers, and handle failed requests or exceptions. These steps reduce technician variability while generating the evidence an auditor or access-review owner needs. In a hospital, an error can expose patient information or impede care, so operational clarity matters. The procedure must reference the underlying access standard rather than invent new entitlement rules that conflict with governance.
Incorrect Answers
A:A policy expresses leadership's requirements for access control and accountability, but it usually does not explain every technician action and artifact. The hospital already has an approved policy, and the failure occurs during execution. Repeating broad limited-access language does not instruct staff which approval to collect or what evidence to retain. The problem calls for an operational procedure.
B:A guideline can provide useful recommendations when discretion is appropriate, but inconsistent clinical entitlement provisioning requires mandatory steps and verification. Suggesting caution leaves approval and evidence collection to individual interpretation. A procedure gives technicians a reproducible path and a way to demonstrate compliance, while a guideline cannot reliably close this particular control gap.
D:A reference list of role names helps technicians identify available entitlements and can prevent spelling mistakes. It does not tell them how to validate new hires, obtain data-owner approval, confirm the correct access scope or retain evidence. The defect in the scenario is inconsistent execution of already approved requirements. A documented procedure should combine role references with mandatory ordered steps and decision points, rather than rely on a static catalog alone.
Question 324
A ransomware outbreak has spread beyond one department, and the SOC needs authority to isolate shared storage, notify executives and preserve evidence. Executives ask which governing requirement should assign response leadership and mandatory escalation before specific playbooks are chosen. What should the incident commander rely on?
- A ransomware containment playbook listing command sequences for isolating endpoints but no designated authority for shared-storage or executive decisions
- A SOC triage runbook that scores ransomware alerts and routes tickets without assigning enterprise-wide containment approval or legal notification duties
- A vendor sales contract that describes future security features
- The incident-response policy defining decision authority, responsibilities, reporting and escalation
Explanation
Correct Answer
D:An incident-response policy establishes the organization's mandatory expectations and authority structure for handling security events. It should identify accountable incident command, notification requirements, evidence preservation principles, and escalation for disruptive actions such as isolating shared storage. Detailed playbooks then operationalize these requirements for particular attack patterns. In this case, containment may affect several business units, so clearly authorized decisions and executive/legal communications are essential. The incident commander should use the policy to determine who can approve enterprise-impacting actions, then follow current procedures and record decisions. A technical checklist alone cannot replace governance of those decisions.
Incorrect Answers
A:A containment playbook is valuable once an incident commander has decided which actions are authorized. It can describe EDR isolation commands and evidence collection, but a command sequence does not determine who may disrupt shared storage or initiate enterprise-wide escalation. The stem explicitly asks for the governing authority before technical playbooks are selected. An incident-response policy must establish that accountable decision chain and reporting obligations.
B:A triage runbook can standardize severity scoring and initial investigation of ransomware detections. It cannot by itself authorize organization-wide storage isolation or specify who represents the company in legal and executive reporting unless those responsibilities are established by governance. The outbreak has crossed departmental boundaries, making decision rights and escalation essential. The incident-response policy is the appropriate authoritative source, with the runbook serving as its operational implementation.
C:A vendor contract might allocate obligations when a third party is involved, but it cannot by itself establish all internal command, notification and containment responsibilities for this ransomware outbreak. The vendor may provide tools, whereas the organization remains responsible for its incident governance. Contract requirements can supplement the response policy but do not replace it.
Question 325
Flooding closes a company's only regional service center for several days. Management must keep high-priority customer support operating from another location while IT rebuilds the destroyed network and server equipment. Which statement correctly separates the two plans?
- Disaster recovery governs staff shift schedules, while business continuity is limited to rebuilding servers
- Business continuity and disaster recovery are interchangeable because both occur after disruptions
- Business continuity sustains essential customer functions while disaster recovery restores the underlying technology and facilities
- Use the tested IT recovery sequence as the entire continuity plan while leaving alternate customer-service staffing and communications undefined
Explanation
Correct Answer
C:Business continuity planning emphasizes maintaining or resuming critical organizational activities despite disruption, including alternate staffing, temporary locations, customer communications and manual workarounds. Disaster recovery concentrates on restoring information systems, data, connectivity and infrastructure to meet recovery targets. Both plans should align to the same business impact analysis, but their scopes differ. In this flood scenario, continued customer support from another location is continuity, while replacing damaged network equipment and rebuilding servers is disaster recovery. Coordinating both prevents the mistaken assumption that the business must remain idle until the original site is repaired.
Incorrect Answers
A:Disaster recovery often coordinates technical restoration, not the primary design of customer-support staffing and alternate service processes. Business continuity addresses how the service center's essential functions stay available despite lost premises. Swapping these labels would assign the wrong scope to each plan. IT may support alternative locations, but support-service continuity remains a business-led resilience concern.
B:The two disciplines are closely related but not synonymous. A company can keep answering customers using an alternate call center while repairing the flooded primary site; these activities have different owners and success measures. Treating them as one undifferentiated plan risks omitting staffing and service workarounds or neglecting detailed system restoration. Coordinated separate responsibilities are preferable.
D:A tested recovery sequence can restore servers and networks after flooding, and it belongs in the disaster recovery workstream. It does not ensure that customers receive essential support during several days of facility unavailability. Business continuity also needs an alternate operating location, staff schedules, communications and processes that can function while IT rebuilds the primary site. Treating technical restoration as the whole plan omits the immediate service objective the scenario explicitly requires.
Question 326
A retail company decides why customer purchase histories are collected and which marketing analyses are permitted. A contracted analytics vendor processes those histories only under the retailer's documented instructions. Which allocation of data-protection roles is the best fit for this arrangement?
- Both parties must be controllers solely because the vendor operates the analytics servers
- The retailer is the controller of processing purposes and the vendor is a processor acting on its instructions
- The analytics vendor becomes the controller whenever its data scientists execute a query
- Treat the vendor as joint controller solely because it chooses server locations and query-optimization methods within the retailer’s instructions
Explanation
Correct Answer
B:The retailer determines the purposes and essential means of using customer purchase histories, so it acts as controller in this described relationship. The analytics vendor carries out processing under documented instructions and therefore acts as processor for that activity. Their agreement should specify permitted operations, access restrictions, security, incident notice and deletion or return of data. Roles are functional, not simply titles printed on a contract. If the vendor independently begins using histories for its own unrelated purposes, its role for that separate processing may change. In the stated scenario, however, the retailer retains decision authority over the use of the data.
Incorrect Answers
A:Owning or operating analytics infrastructure does not automatically determine why personal data is processed. The vendor can manage servers and still act only on the retailer's instructions. What matters is who decides processing purposes and relevant means for the activity. Treating both as controllers solely due to infrastructure ownership ignores the substantive role allocation stated in the scenario.
C:Running an analysis requested by the retailer is operational processing, not necessarily independent determination of the data's purpose. The vendor does not become a controller every time an employee executes a query within the documented service. It could take on a separate role if it independently repurposed the data, but that is outside the described authorized arrangement. The question asks about the existing contractual relationship.
D:A processor can choose many nonessential technical implementation details while carrying out the controller’s documented purposes. Selecting server hardware or efficient database query plans does not automatically give the vendor independent authority to repurpose customer histories. The retailer still determines why data are processed and the permitted marketing analyses. A different role could arise for processing outside the instructions, but the scenario describes no such independent use. Joint controller status is not established merely by operating infrastructure.
Question 327
A healthcare organization assigns a department director authority to decide which staff may access its patient billing dataset. An infrastructure administrator manages backups, storage permissions and retention jobs according to those decisions. Which role assignment best describes the relationship?
- The infrastructure administrator is the data owner because they control the physical storage
- The director is the data owner and the administrator is the custodian implementing authorized protections
- The director is the custodian because they approve access, while the administrator owns the data
- Both roles are identical because they share responsibility for protecting the same dataset
Explanation
Correct Answer
B:A data owner is accountable for the information's classification, acceptable use and access decisions, while a custodian performs technical stewardship under those directions. The department director sets who needs patient billing access and what restrictions apply. The administrator implements approved permissions, backups, secure storage and retention operations and reports exceptions. A custodian may flag an unsafe request, but that does not ordinarily transfer the owner's business decision authority. Clearly distinguishing the roles supports least privilege, audit accountability and consistent handling of the dataset over its lifecycle, particularly where sensitive clinical billing records are concerned.
Incorrect Answers
A:Operating storage infrastructure gives the administrator technical control, not the business authority to decide who should use patient billing data. Custodians configure and maintain safeguards according to owner-approved requirements. Equating physical or administrative access with ownership can encourage unauthorized access grants. The director remains accountable for access decisions, while the administrator provides implementation and operational evidence.
C:The director's authority to classify data and approve access is characteristic of an owner, not merely a custodian. The administrator's ongoing work with storage, retention and permission implementation is custodial activity. Reversing the titles would misassign who approves exceptions and who executes them. Governance depends on documenting those responsibilities clearly rather than using job seniority alone.
D:Both roles contribute to protection, but their decision rights differ. One function sets business access requirements and remains accountable; the other implements and maintains the technical controls. Combining them without distinction can blur separation of duties, cause disputes during reviews and weaken authorization evidence. The scenario explicitly separates approval authority from operation, making an owner/custodian distinction meaningful.
Question 328
A multinational organization allows regional IT teams to respond to local outages, but security policies and minimum controls must remain consistent across all offices. A subsidiary wants to disable MFA permanently to simplify support. What governance approach best balances local flexibility and organizational control?
- Allow each subsidiary to waive mandatory controls without documenting a risk decision
- Maintain centralized minimum policies and exception authority while delegating implementation and approved operational choices to regional teams
- Require headquarters to execute every local technical command regardless of urgency
- Remove region-specific procedures even where local laws or infrastructure require different approved implementation details
Explanation
Correct Answer
B:Central governance should define mandatory outcomes, risk thresholds, and who can approve departures, while regional teams can choose compliant implementation methods and respond to local operating conditions. MFA remains a baseline unless a formally authorized, time-bounded exception with compensating controls is accepted. This model preserves consistent accountability and auditability without making every technical change dependent on headquarters. Regions may document different procedures where justified, but they should still demonstrate adherence to enterprise standards or approved deviations. The key is separating policy authority from day-to-day execution rather than allowing local convenience to erase a required control.
Incorrect Answers
A:Unrecorded local waivers can create inconsistent identity protection and prevent executives from understanding aggregated risk. A subsidiary's support burden may be real, but a permanent MFA removal should not happen outside the established exception authority. Business impacts can be evaluated with temporary mitigations and accountable approval. Autonomous disregard for mandatory controls defeats the purpose of enterprise security governance.
C:Excessive central execution can delay urgent local repairs and create a bottleneck, even when the regions understand their infrastructure. Headquarters should own mandatory rules and risk acceptance boundaries, not necessarily every routine implementation command. Appropriate delegation preserves speed and accountability when accompanied by standards, evidence and escalation. The case asks for a balance, not total operational centralization.
D:Regional implementation may need to reflect language, legal, infrastructure or service differences, while still meeting enterprise control objectives. Eliminating all local procedures can make the baseline difficult to implement safely. The correct model permits documented compliant variation and approved exceptions rather than assuming that one identical procedure is practical in every operating environment.
Question 329
After a third-party breach, the security steering committee learns that high-risk vendor exceptions were repeatedly approved informally by project managers. Executives want a clear escalation path for exceptions that exceed the organization's risk appetite. Which governance change is most appropriate?
- Route every exception through the help desk because it maintains the incident ticket queue
- Assign executive or board-designated risk authority to review material exceptions, with defined thresholds, documented decisions and reporting
- Allow each project manager to approve exceptions if they also sign the purchase order
- Provide executives with quarterly aggregate exception counts while letting project managers retain final approval for risks above their delegation limits
Explanation
Correct Answer
B:Material exceptions require authority commensurate with their impact. The governance framework should define risk appetite, thresholds that trigger escalation, designated executive or board-level oversight, required risk analyses, accountable owners and periodic review of approved deviations. Project managers can supply business context but should not silently accept risks beyond their delegated limits. Documenting decisions also lets the committee see systemic exposure, such as recurring vendor control gaps across projects. This case is about strategic risk authority and escalation, not operational ticket routing. The resulting control ensures high-risk exceptions are visible to those accountable for enterprise-level consequences.
Incorrect Answers
A:A help desk can route a request or maintain a service ticket, but it generally lacks the authority to accept enterprise-wide third-party exposure. Technical support ownership is not equivalent to governance decision rights. The exception may be recorded in a ticketing system, yet escalation must reach the executive or committee designated to approve material deviations from the risk appetite.
C:Purchase approval addresses commercial spending, not necessarily acceptance of cybersecurity exposure beyond an authorized threshold. A project manager can have budget authority without being empowered to accept regulatory, legal or operational risks affecting the enterprise. Material exceptions need documented review by the proper risk owner and designated escalation authority rather than piggybacking on purchasing signatures.
D:Aggregate reporting can show that exception volume is growing, but it cannot retroactively make unauthorized material-risk approvals valid. Project managers may manage spending and delivery without authority to accept enterprise-wide third-party consequences. The committee needs escalation thresholds, assigned risk authority and traceable rationale for each significant exception. A count-only dashboard could supplement governance; leaving the decisive approval at the project level reproduces the breach-related failure.
Question 330
An online service plans to collect account profiles in several countries and host backups in a different region. Product leaders propose copying their domestic privacy notice everywhere without review. What is the most appropriate governance step before launch?
- Assume domestic policy applies worldwide because the company incorporated locally
- Use the cloud provider's default contract as the only privacy requirements document
- Inventory the jurisdictions, data flows and transfer locations, then map applicable legal and contractual obligations to policies and controls
- Apply the domestic data-retention schedule and classify the overseas backups as merely an infrastructure deployment decision
Explanation
Correct Answer
C:Cross-border processing may trigger different privacy, security, retention and transfer obligations depending on data subjects, processing activities and local law. Map where customer information is collected, used, shared, stored and backed up, then obtain qualified legal guidance on applicable requirements. Update notices, contracts, transfer safeguards, access controls and retention schedules accordingly. A single domestic notice may omit material rights or disclosures for other jurisdictions. This action is governance because it identifies the authoritative obligations before technical implementation and launch decisions. The exact requirements must be confirmed for the actual countries and processing arrangements rather than assumed from the hosting region alone.
Incorrect Answers
A:The organization's incorporation location does not automatically eliminate obligations to individuals and regulators elsewhere. Different jurisdictions can regulate collection, processing, transfers and retention based on several factors. Reusing domestic rules without analyzing the actual data flows can create compliance gaps. The organization should determine applicability with legal expertise instead of relying on a geographic assumption.
B:Cloud-provider contracts may describe shared responsibilities and certain transfer protections, but they do not replace the organization's analysis of its own processing purposes and applicable law. The provider may be unaware of each country's customer notices or data retention commitments. Contracts should be reviewed as part of a broader governance map, not treated as the only source of obligations.
D:A domestic retention standard may be an initial control reference, and cloud backup teams do have implementation responsibilities. However, customer location and cross-border transfer arrangements can change the applicable privacy and retention obligations. Treating overseas storage as a technical placement decision alone could omit required notices, contracts or transfer safeguards. Governance must map data subjects, processing purposes and jurisdictions first, then update the technical and documentary controls with qualified legal input.