CompTIA Security+ SY0-701 Practice Test 20
Question 190
A marketing analyst removes customers' full names from a report and replaces them with initials. A retained lookup table and combinations of ZIP code, birth year and purchase details could still identify individuals. Management wants to describe the published data as irreversibly anonymous. Which description is justified?
- The data remain masked or pseudonymized, with reidentification risk that must be evaluated
- Removing names proves permanent anonymity under any privacy framework
- Initials constitute a one-way asymmetric encryption algorithm for the entire dataset
- The report has no personal-data exposure because the name column contains fewer characters
Explanation
Correct Answer
A:Masking or pseudonymization transforms direct identifiers, but does not necessarily prevent a person from being linked back to a record using a lookup table or combinations of other attributes. The organization should assess quasi-identifiers, access to the mapping, small population groups and possible external datasets before making an anonymity claim. Restricted access, minimization and aggregation may further reduce residual risk. Truly irreversible anonymization is a stronger assertion and depends on context and applicable standards; simply substituting initials is insufficient. This scenario specifically retains reidentification paths, so the cautious and technically accurate description is transformed personal data with continuing privacy obligations and controls.
Incorrect Answers
B:Names are only one kind of identifying information. A report can be reidentified from rare combinations of characteristics, and the scenario explicitly retains a lookup table. Eliminating full names therefore does not prove that no individual can be determined under realistic conditions. An unconditional anonymity claim would overstate the protection and could lead staff to share the report more broadly than justified.
C:Replacing names with initials is a presentation or data-transformation operation, not a public-key cryptographic system. No asymmetric keypair, ciphertext or decryption process is described. Even if encryption were applied, reversibility and key possession would still matter when evaluating whether information is truly anonymized. The team should use correct privacy terminology rather than equate masking with cryptography.
D:The reduction in characters in the name field does not eliminate identifying information in the rest of the report. A ZIP code, birth year and distinctive purchases can be combined to infer a customer, particularly when external databases are available. Retaining a lookup table makes the issue clearer. Privacy risk should be evaluated across the whole data record and likely recipients, not a single column's appearance.
Question 191
A finance team holds transaction reports subject to a statutory retention period and potential audit requests. It proposes deleting files automatically after thirty days solely to save storage cost. What should determine the records' protection and retention?
- Apply the reports' regulated classification and legal retention schedule, including integrity, access and secure disposal controls
- Follow individual employees' preferences about which transactions to keep
- Move the reports to a public file share so external auditors can retrieve them without approval
- Apply only the shortest available storage-lifecycle setting because encrypted data can be deleted at any time
Explanation
Correct Answer
A:A classification reflecting financial, legal, and contractual sensitivity should drive retention, integrity protection, authorized access, storage location, and final disposal. The team must identify the applicable statutory period, any legal hold exceptions, and the evidence needed to show records were not altered improperly. Automation can then enforce an approved schedule and secure deletion when retention actually expires. Encryption and backups support confidentiality and recoverability, but neither defines the legal duration by itself. The proposed thirty-day deletion is unsafe until compared with binding obligations. This approach balances lifecycle efficiency against demonstrable regulatory compliance for transaction reports.
Incorrect Answers
B:Employees may know the operational usefulness of reports, but individual preferences do not override statutory retention obligations or the organization's approved records policy. Inconsistent personal decisions create gaps in audit evidence and may cause premature deletion. Finance, legal, compliance, and records-management roles should define binding handling rules. Employees should execute the controlled policy rather than invent retention periods case by case.
C:Making financial reports public could expose personal or commercial information to unauthorized readers. External auditors may require evidence, but they should receive access through a controlled authorization and disclosure process, not unrestricted publication. Retention and availability do not require anonymous access. The organization must support audits while protecting sensitive information and recording who retrieved or changed each report.
D:Encryption does not eliminate required retention periods or the need to demonstrate an accurate financial record during review. A short storage lifecycle may be efficient, but deleting reports before their obligations expire could create compliance and evidence problems. Storage optimization must operate inside established legal and business requirements. Data classification and records-management owners should establish the appropriate term before automation removes files.
Question 192
A shared analytics worker processes customer data for several tenants. A software defect allows one tenant's job to read a temporary directory left by another tenant. Management needs a defense that limits cross-tenant disclosure even if a similar coding error occurs. What should be strengthened?
- Allocate a separate named directory per tenant, but run every job under the same unrestricted filesystem identity
- Encrypt the shared worker volume with one platform-managed key while retaining cross-tenant access to decrypted temporary files
- Enforce tenant-isolated execution and storage boundaries with tenant-specific authorization and clean workspace lifecycle controls
- Schedule cleanup of temporary files at the end of each batch while allowing concurrent jobs to share their storage permissions
Explanation
Correct Answer
C:Tenant separation should be enforced at several boundaries: identity-aware storage permissions, separate workspaces or containers where appropriate, resource isolation, and deletion or secure clearing of temporary data after jobs finish. Each job should access only its tenant's input and outputs, and the system should validate tenant context independently of untrusted request fields. Such controls reduce blast radius if application logic accidentally references a previous job's path. The organization must test the implemented isolation under concurrency and failure conditions, not just label directories as private. This addresses the cross-tenant data disclosure in the scenario while retaining the operational benefits of a shared analytics platform.
Incorrect Answers
A:Naming a working directory after its tenant improves organization and troubleshooting, but a directory name does not enforce a permission boundary. When all workers share unrestricted filesystem rights, a path-handling bug can still read another tenant's files. This proposal addresses accidental naming collisions without limiting what a compromised or defective job can actually access. Tenant-scoped authorization and isolation are required.
B:Volume encryption protects stored bytes if media are removed or accessed beneath the encryption layer. During normal analytics execution, the shared worker can read decrypted files; a tenant job with broad permissions could therefore still obtain another customer's results. The stated defect occurs inside a running processing environment, not through theft of raw disks. Execution and storage authorization must be separated by tenant.
D:Cleaning old workspaces reduces residual data and should be part of a safe job lifecycle. However, concurrent jobs could still access each other's directories while processing if the common identity retains unrestricted permissions. A crashed job may also bypass ordinary end-of-batch cleanup. Cleanup alone is not a reliable tenant security boundary; it must be paired with enforceable isolation and least-privileged access.
Question 193
A confidential engineering design file moves from the document repository to a collaboration platform. The company wants access restrictions and DLP rules to continue following the file, even when it changes folders. What is the strongest design?
- Attach an enforceable sensitivity classification label and configure access and DLP policies to act on that label
- Use restrictive source-folder permissions and assume those permissions will remain effective after the file is copied elsewhere
- Configure destination DLP matching only on the engineering filename pattern without assigning a persistent sensitivity label
- Trust the destination platform's general-purpose default sharing permissions without checking the document's classification
Explanation
Correct Answer
A:A persistent sensitivity label can represent the design file's approved classification independently of its current folder or extension. Integrated access and DLP policies can then restrict sharing, require encryption, prompt for justification, or log handling based on that classification across supported systems. The organization should verify label persistence, interoperability, and policy enforcement when files are exported or converted; a visual tag without enforcement is insufficient. Proper labeling helps carry owner-defined protection requirements into collaboration workflows where folder inheritance may change. The risk is not merely that the file moved, but that its sensitive content could lose controls if protection relies only on its original repository location.
Incorrect Answers
B:Folder access control can protect a document while it stays in the governed repository. A copy to a different collaboration service may inherit that service's sharing rules rather than the original folder's access control lists. This design has no independent classification signal that follows the file into the destination environment. Administrators must verify portable protection and apply policies to its sensitivity.
C:Filename-based rules can catch recognizable documents but can be bypassed when a file is renamed, converted, or exported with a different extension. They also lack reliable information about the owner's classification decision. A DLP policy may use patterns as supporting evidence, but the requirement is that restrictions follow this particular confidential design across moves. An enforceable sensitivity label is better suited to that lifecycle.
D:General sharing defaults may be suitable for ordinary documents but insufficient for unreleased engineering designs. Moving a file can change inherited permissions and effective access in ways the owner did not intend. Without checking classification and enforcing linked policies, collaborators may accidentally grant broader access. The team should derive controls from the file's sensitivity and business purpose rather than relying on generic platform behavior.
Question 194
A stock-trading service has a contractual recovery time objective measured in minutes after a data-center disaster. An alternate facility with no preinstalled servers would require several days of procurement and setup. Which recovery-site choice best fits the approved RTO?
- A cold site with power and floor space only
- A hot recovery site with preprovisioned, synchronized services capable of rapid activation
- A warm recovery site with installed standby servers but no running application or completed rapid-activation tests
- Restore daily offsite backup images into newly provisioned cloud instances only after the disaster is declared
Explanation
Correct Answer
B:A hot recovery site keeps sufficiently prepared computing, network, application, and data resources available for rapid service restoration. With tested orchestration, current dependencies, and appropriately synchronized data, it is a plausible match for a trading service that must resume in minutes. The team should verify that switchover time includes identity, connectivity, data consistency, and external market connections rather than measuring server power-on alone. Hot sites cost more and require maintenance, but they reduce the reconstruction delay characteristic of cold sites. The architecture must also satisfy the recovery point objective separately; fast activation does not guarantee that no transactions are lost. The primary selection driver here is the explicitly stringent recovery time requirement.
Incorrect Answers
A:A cold site offers space and basic utilities but normally requires significant equipment setup, software restoration, and configuration before applications can restart. That delay can be acceptable for low-priority services with generous recovery time objectives, but not a trading platform required within minutes. The organization should choose readiness according to the approved RTO, not simply minimize standing facility cost.
C:Warm sites can offer useful preinstalled infrastructure and often recover faster than facilities with no equipment. However, the option leaves application activation and integration unmeasured; installation alone does not demonstrate a recovery time measured in minutes. Under such a stringent RTO, the owner needs a demonstrably hot and rapidly activated environment with operational dependencies tested. A warm designation alone cannot establish compliance.
D:Offsite images and infrastructure automation can be valuable recovery components, but this design begins compute provisioning, image restoration, application initialization, and network validation only after the outage. Unless those processes are already proven to finish within minutes, the proposal cannot defend the contractual RTO. It also does not ensure current transaction data. A ready hot environment with tested switchover better matches the stated time constraint.
Question 195
A warm disaster-recovery environment receives database changes from production every twenty minutes. The business has approved a maximum recoverable data loss of five minutes. What is the most important gap in the current design?
- Rely on the provider's warm-site designation as evidence that any recovery point will meet the five-minute business target
- The replication interval can exceed the five-minute RPO and must be shortened or redesigned
- Upgrade standby compute capacity without altering the twenty-minute schedule for copying committed database changes
- Extend backup retention from thirty to ninety days while keeping the same replication interval into the warm site
Explanation
Correct Answer
B:An RPO is the maximum acceptable amount of transaction history lost, measured in time before the disruption. With changes replicated only every twenty minutes, the latest durable standby state can lag far beyond the approved five-minute limit, even if the standby boots immediately. Engineers should use a shorter verified replication interval, continuous replication with appropriate durability, or another tested design that meets the required recovery point. They must account for network interruptions, replication errors and data consistency, because a configured schedule alone does not guarantee outcomes. This is a data-loss problem, different from adding compute capacity merely to shorten restoration time. The site should demonstrate compliance through realistic failover exercises.
Incorrect Answers
A:Warm-site terminology describes the broad level of preparedness or equipment available for disaster recovery, not a guaranteed quantitative loss window. The business has set a five-minute recovery point objective, but copying changes only every twenty minutes can leave almost twenty minutes of unreplicated transactions. Provider labels do not prove the last durable recovery point meets that requirement. The team needs measured synchronization behavior, failure tests and recovery-point evidence rather than assuming the deployment category has a fixed RPO.
C:More CPU or memory at the standby might reduce application startup time and thus improve the recovery time objective under load. It cannot recreate transactions that were never replicated. The scenario does not state that the warm site is slow to boot; it states that committed changes arrive only once every twenty minutes. The direct gap is the age of the recoverable data, not the performance of the standby hardware. Compute upgrades could form part of a broader recovery plan but do not address the specified five-minute data-loss tolerance.
D:Longer retention preserves more historical backup versions, which may help with archival recovery, investigation or recovery from latent corruption. It does not make the most recent copy more current at the moment of a failure. A ninety-day archive could still end with a recovery point twenty minutes old. The five-minute RPO calls for more frequent verified data replication or an equivalent mechanism that reduces potential transaction loss. Retention depth and replication freshness address different dimensions of recovery readiness.
Question 196
An online ticketing service already distributes requests through a functioning health-aware load balancer. During concert releases all four healthy application instances become CPU-saturated together, and the balancer has no spare capacity to direct requests toward. The service must absorb bursts without relying on a single permanently oversized server. Which change best addresses the remaining availability limit?
- Add read-only database replicas without increasing the saturated application-server pool
- Add another load-balancer health probe while keeping the same four fixed-capacity instances
- Upgrade the CPU allocation of the busiest application instance but leave the other three and overall fleet size fixed
- Introduce tested horizontal autoscaling behind the existing load balancer, with capacity thresholds and scale-in safeguards
Explanation
Correct Answer
D:Horizontal autoscaling creates additional healthy application capacity when sustained demand exceeds the existing pool's threshold, while the already deployed load balancer distributes requests across the expanded fleet. The design should use representative load tests, application startup time, safe database-connection limits, minimum reserve capacity, and cooldown or scale-in policies that do not terminate active sessions. This is distinct from merely selecting a load balancer as the routing component: the question states that load distribution already works, but no spare compute exists. Planned scale-out, state handling, and rate controls must be validated so sudden spikes do not exhaust downstream dependencies or cause unstable repeated scaling.
Incorrect Answers
A:Read replicas can relieve database query pressure and may improve response time when a database is the bottleneck. Here, monitoring shows all four application instances are CPU-saturated and the existing load balancer has no spare instance to select. Database replicas do not by themselves increase compute capacity for application request processing. The team needs a controlled way to add application instances behind the functioning balancer.
B:Health probes allow a load balancer to avoid servers that cannot serve traffic, but more probes do not create CPU or worker capacity. All four nodes are functioning and collectively overloaded, so no selection algorithm can route work to a spare instance that does not exist. Additional checks may refine failure detection, but the critical missing capability is controlled provisioning and deprovisioning of capacity behind the existing distribution tier.
C:A vertical upgrade may provide temporary capacity on one server, but the scenario reports simultaneous saturation across the entire application pool during short release bursts. Enlarging one node does not provide the requested elastic fleet capacity and may create a new oversized dependency. It also lacks automatic expansion and safe scale-in as demand changes. Horizontal autoscaling better uses the existing health-aware request distribution.
Question 197
A critical database cluster has documented automatic failover and redundant nodes, but no one has deliberately tested loss of the active node since deployment. Leadership wants evidence that service can continue within the approved time target. What should be scheduled?
- A controlled failover exercise with measured recovery, data consistency, and rollback safeguards
- A tabletop discussion only, without observing any real cluster behavior
- Restore one database backup into an isolated lab without exercising the live cluster election and client reconnection path
- Review cluster vendor guidance and configuration settings, then sign off on failover without inducing a node transition
Explanation
Correct Answer
A:A controlled failover exercise deliberately removes or isolates the active node under an approved change and observes whether the standby takes over and clients resume successfully. The team should measure interruption time, transaction consistency, connection behavior, monitoring alerts, and the steps needed to return to normal. Testing must protect production safety, include a documented rollback, and use representative load where feasible. Architecture diagrams demonstrate intended redundancy but not actual behavior when dependencies such as quorum, DNS, storage, or credentials fail. The exercise supplies operational evidence against the recovery target while identifying issues that can be corrected before a genuine disaster. This is the appropriate validation of a claimed automatic cluster failover design.
Incorrect Answers
B:A tabletop exercise is valuable for practicing decisions and responsibilities, but it does not prove that a cluster's heartbeat, election process, application reconnection, and data consistency work during an actual node loss. Leadership seeks technical continuity evidence. A scenario discussion can supplement the test plan but cannot replace observed failover measurements. The chosen exercise should activate the relevant system behavior under controlled conditions.
C:An isolated restore is a useful backup-recoverability test and can establish that a database image opens without corruption. It does not trigger the production cluster's node election, replication promotion, connection-string behavior, or quorum dependencies. Leadership specifically needs measured continuity during loss of the active node. An observed, controlled failover test supplies that evidence while the backup test examines a different failure mode.
D:Design review can identify incorrect heartbeat timers, missing prerequisites, or unsupported cluster versions before an exercise. Yet a correct-looking configuration is not proof that standby promotion and client reconnection meet the recovery target in the deployed environment. Hidden network, authentication, or storage dependencies may fail only under transition. The owner should document the review but still conduct a controlled measurement of actual failover.
Question 198
Executives want to rehearse who declares a ransomware crisis, authorizes customer communications, invokes legal support, and approves spending. They cannot interrupt production systems for the exercise. Which recovery-readiness method is the best fit?
- Conduct a facilitated tabletop exercise using a realistic ransomware timeline and assigned roles
- Take down the production data center without warning to create realism
- Validate only whether disk snapshots can be mounted in a test VM
- Replace the incident response plan with a generic vendor checklist
Explanation
Correct Answer
A:A tabletop exercise walks decision-makers through a plausible incident narrative and asks them to practice escalation, authority, communications, and coordination without switching off production systems. Facilitators can introduce new facts, such as ransom demands or media inquiries, and observe whether executive, legal, communications, technical, and business roles align. Outcomes should include identified gaps, owners, and plan updates rather than a ceremonial meeting. Tabletop success does not prove the technical restore process will work; that requires separate hands-on exercises. This method directly matches the goal of practicing governance and communication under a no-production-disruption constraint.
Incorrect Answers
B:An unannounced shutdown could cause major operational harm and trigger contractual penalties or unsafe conditions. It tests technical disruption tolerance rather than the specific executive decision processes sought here. Full failover exercises can be useful when properly authorized and controlled, but the scenario prohibits production interruption. Readiness must be practiced within agreed safety and change-management limits.
C:Mounting a snapshot helps verify one aspect of technical recovery, but it does not rehearse legal notification decisions, executive crisis declaration, customer communications, or emergency procurement. The stakeholders want to coordinate responsibilities under evolving ransomware circumstances. Snapshot testing should be part of a broader recovery assurance program, not the sole response to an organizational decision exercise.
D:A vendor checklist may provide useful prompts, but replacing the organization's own plan would erase designated owners, contact paths, decision rights, and business-specific legal duties. The exercise should test the existing approved arrangements and improve them through observed gaps. Generic guidance cannot automatically resolve who is authorized to declare an incident or address customers for this company.
Question 199
A company places weekly full-backup copies in a physically separate offsite vault. An office fire destroys the production servers and all local storage. What property does the offsite arrangement primarily provide, and what limitation remains?
- Survival of a geographically local disaster, but restoration may be slower and data may be as old as the last copy
- Guaranteed instantaneous recovery with no transaction loss
- Protection from any malware because offsite data cannot be infected
- Assume physical separation makes regular restore rehearsals unnecessary because surviving backup media guarantee usable application data
Explanation
Correct Answer
A:An offsite backup provides a copy beyond the physical footprint of a building disaster, improving the chance that data survives when local storage is lost. However, restoring a weekly full backup can be slow and may omit changes made since the last copy, so both recovery time and recovery point depend on additional arrangements. The team should protect backup media against unauthorized access, verify integrity, and conduct restoration tests. Geographic separation is a resilience safeguard, not proof of instant application availability. The precise value in this fire scenario is recoverable data at another location, with known latency and freshness tradeoffs that should be compared with business RTO and RPO targets.
Incorrect Answers
B:A vault holding backup media does not necessarily have running applications, synchronized transaction streams, or active compute resources. Restoring data can require transport, hardware, software, and validation time. A weekly schedule also permits substantial data loss after the last backup. Instantaneous, zero-loss recovery would require substantially more capable replication and hot recovery design, not simply an offsite copy.
C:Offsite backups can still include malware or corrupted files if infection occurred before a backup was taken. A protected immutable or offline copy may resist later attacker modification, but no location alone guarantees cleanliness. Malware scanning, retention history, isolation, and restoration testing are needed. The principal protection of the offsite vault in this case is against local physical destruction, not every cyber threat.
D:Geographic separation protects the backup copy from the office fire, but surviving media do not prove the archive is intact, decryption keys are available, or dependencies can be restored. A weekly copy can also omit recent changes. Without trial restoration and integrity checks, the organization may discover unusable data only during a disaster. The correct claim must acknowledge both geographic resilience and recovery time and freshness limits.
Question 200
An encrypted legal archive has a protected recovery-key escrow with documented dual approval, and its backup checksum passes. During an exercise, however, no operator has demonstrated that the escrow access workflow can retrieve the right key and decrypt a stored archive under disaster conditions. Which next action most directly establishes recoverability?
- Rely on the checksum to prove that the encrypted archive can be read after a disaster, without attempting decryption
- Rotate the archive key identifiers immediately and treat the new metadata as proof that old backups remain recoverable
- Verify that the escrow vault's user interface is reachable, but skip approval, key release and restore testing
- Perform an authorized dual-control key-retrieval and actual test decryption, recording the recovery evidence and correcting any runbook failures
Explanation
Correct Answer
D:A representative dual-control recovery exercise demonstrates that eligible custodians can authorize access, obtain the right escrowed key version, and decrypt the protected archive without exposing key material more widely than necessary. The team should perform the test in a segregated environment, validate recovered data and application use, log custody and approvals, and update instructions for any failed dependencies. This is a verification-of-recoverability decision, not the earlier design question about selecting dual-control escrow in the first place. It converts a backup checksum and a theoretical key store into measured restoration evidence, while keeping confidentiality and separation-of-duties safeguards intact.
Incorrect Answers
A:A stored checksum can detect whether backup bytes changed relative to an expected value, but it cannot establish that the organization still possesses a usable decryption key. An archive may remain byte-for-byte intact while every authorized recovery route is broken. The question assumes that escrow already exists, so the unresolved issue is whether the recovery workflow can retrieve the corresponding material and decrypt actual records. A checksum-only inspection misses that dependency and does not meet the demonstrated recovery requirement.
B:Key rotation can be useful for limiting cryptographic exposure, but changing identifiers or encryption metadata does not prove that older ciphertext can be decrypted using the correct historical material. It can even complicate restoration if the team loses the association between archives, versions and required keys. The problem is an untested retrieval and authorization process, not evidence of a compromised key. An authorized recovery trial should validate real decryption before any key-lifecycle changes are considered evidence of resilience.
C:An accessible escrow console confirms only that a user can reach part of the recovery service. It does not prove that the required two approvers have valid authority, the correct key version can be retrieved, or the restored application can use the material safely. Real disasters expose authorization, network, custody and runbook gaps that a login screen cannot simulate. The team should complete a controlled retrieval and sample decryption, not stop at a superficial availability check.