CompTIA Security+ SY0-701 Practice Test 50
Question 490
A court stores security events on append-only media and periodically exports them for external forensic review. Investigators worry that an administrator with temporary archive control may have removed two old events or reordered entries before a later export, leaving the remaining text plausible. Which integrity technique best detects this kind of manipulation?
- Compress the surviving records without preserving their original sequence or a trusted index
- Create an ordered hash chain across events or batches and anchor signed checkpoints outside the administrator's control
- Encrypt only the connection used to copy the already assembled archive to the investigator
- Alphabetize events before export so missing chronological entries are not apparent
Explanation
Correct Answer
B:A cryptographic hash chain includes prior digest information in later event or batch digests, making deletion, insertion and reordering detectable when compared with authentic checkpoints. Periodic signed anchors stored outside the administrator's control prevent an attacker who controls the local archive from silently rewriting the entire chain and pretending it is original. Investigators should validate the chain, checkpoint signatures and retention timelines during export. This provides tamper evidence rather than preventing all deletion; access controls and immutable retention are still useful. Ordering is essential because the court is concerned with both missing events and a false historical sequence.
Incorrect Answers
A:Compression reduces size but does not establish whether the original sequence contained other records. An administrator could remove an event and produce a new valid archive. Without externally retained sequence or integrity metadata, the investigator lacks a baseline against which to recognize tampering. A revised archive can be recompressed cleanly after deleting the very events the court needs to find.
C:Transport TLS prevents interception or tampering while the export travels, but it cannot prove that local archive content was complete before the connection began. A deliberately altered log can be transmitted securely. Integrity evidence must be established when records are collected and anchored independently of the subsequent transport channel. The log contents require tamper evidence established independently of the later transmission mechanism.
D:Alphabetizing destroys the original chronological order that investigators need to reconstruct incident causality. It also provides no cryptographic evidence of missing rows. The organization needs signed, sequential commitments to the original event stream, not a presentation transformation applied after suspicious alterations may have occurred. Alphabetical order makes it harder to prove which historical security action occurred before another.
Question 491
A university gives two outside research teams separate customer datasets. Names and account numbers have been replaced by stable pseudonymous tokens, and neither team can access the secure reversal vault. However the tokens are identical across both files, and joining them reveals rare treatment dates and purchasing histories. What privacy risk should the data owner recognize?
- Cross-dataset linkability and possible reidentification from combined attributes despite removed direct identifiers
- Guaranteed anonymity, because no research team can view the token reversal table
- Automatic encryption of every other field whenever a consistent pseudonymous token is generated
- An inability to join records because the secure reversal vault is physically separate from the datasets
Explanation
Correct Answer
A:A consistent token allows records about the same person to be linked across independent datasets, even when the mapping vault is inaccessible. Joining the files may reveal patterns distinctive enough to identify someone through outside information or rare combinations of attributes. The owner should minimize shared quasi-identifiers, restrict cross-dataset linkage, apply context-appropriate pseudonymization or aggregation and review disclosure risk. Tokenization reduces exposure of direct identifiers but does not guarantee anonymity. Security evaluation must consider what recipients can infer from the remaining columns and shared tokens, not only whether they possess the secret reversal table.
Incorrect Answers
B:Removing a person's name is helpful but does not erase distinctive combinations such as rare treatment dates and shopping patterns. Identifiability depends on the full dataset and available external information. The repeated token makes linkage easier, so claiming guaranteed anonymity is particularly unsafe for this release. Unique combinations of treatment dates may be matched against public or separately accessible information.
C:A pseudonymous token replaces selected identifiers; it does not encrypt unrelated columns by default. Purchase totals, dates and other fields may remain visible in plaintext. The researchers can correlate those attributes if data-sharing terms permit access, so confidentiality and privacy require controls beyond consistent token substitution. The research team can still read other attribute columns unless separately encrypted or removed.
D:The reversal vault controls direct translation back to stored identities, but the stable token can be compared without consulting that vault. A join on matching token values works in ordinary data analysis. Reidentification may also occur through auxiliary information, so vault separation alone does not eliminate linkability. Consistent token strings allow a normal equijoin even when nobody can reverse them to original names.
Question 492
A regulated clinical-research team stores encrypted datasets in a public cloud. The provider controls underlying disks, but the research sponsor requires the ability to suspend data decryption independently if a cloud tenant administrator is compromised. Which design best supports separate custody of sensitive encryption capability?
- Use customer-managed keys protected in a separate authorized key service, with tested revoke and recovery procedures
- Allow every cloud account administrator to manage the provider's default data keys with no independent approval
- Encrypt uploads using HTTPS but keep all storage decryption keys under the same broad cloud administrator role
- Place raw decryption keys in the CI build manifest so authorized developers can recover datasets immediately
Explanation
Correct Answer
A:Customer-managed encryption keys can separate cryptographic authority from general storage administration when key policies and custody are genuinely independent. The sponsor may disable, revoke or restrict key use following a compromise, subject to how the cloud service handles cached keys and existing copies. Test this control in the selected service: key suspension is not necessarily instantaneous for already decrypted data. Enforce dual control, rotation, audit logs and recovery procedures so legitimate clinical records are not rendered permanently inaccessible. The important requirement is separate approval for sensitive decryption, not a cosmetic change in which account holds the same keys.
Incorrect Answers
B:Unrestricted provider default key management by every cloud administrator gives the same compromised identity broad control over data and decryption. Provider encryption at rest can be useful, but it may not satisfy a sponsor requiring independent revocation and separation of duties. The exact service key policy must be evaluated. The sponsor requires an additional authority that can suspend key use without trusting the same compromised identity.
C:TLS protects transfer between endpoints, not the custody of keys for stored datasets after upload. Putting keys under the same broadly privileged administrator account makes compromise of that role potentially sufficient to expose both ciphertext and decryption capability. Independent key permissions are needed beyond encrypted transport. Cloud storage encryption must remain controlled after HTTPS terminates, especially when an administrator is compromised.
D:Build manifests are often copied into logs, artifact repositories or delivery pipelines. Embedding raw keys there spreads sensitive material and bypasses controlled cryptographic operations. Disaster recovery requires protected key backup and authorized recovery, not deliberate publication of decrypting secrets into developer-facing configuration. Build logs and source artifacts could expose the key beyond the clinically authorized recovery process.
Question 493
A bank's employee portal displays only the last four digits of customers' payment cards, although the database retains complete card numbers for authorized billing. A product manager now wants to release a public CSV dataset with no recoverable identifiers. Which privacy-control distinction should drive the export design?
- The screen's four-digit mask permanently removes full card numbers from all underlying data sources
- The CSV may include raw customer card numbers because the internal dashboard already masks its display
- User-interface masking limits what a viewer sees; external datasets require irreversible removal or robust de-identification appropriate to release risk
- Replace account numbers with their last four digits in the public CSV while leaving linkable transaction histories unchanged
Explanation
Correct Answer
C:Masking can reduce accidental exposure in a controlled display while leaving the underlying full identifier available for permitted business processes. An externally published extract needs an appropriate irreversible deletion, redaction, aggregation or other robust de-identification process, evaluated for linkability and reidentification risk. Simply truncating card numbers is not a universal guarantee of anonymity if auxiliary fields identify individuals. The bank should review the extraction query, validate output schema, apply disclosure controls and ensure public recipients cannot reconstruct the protected details. The key decision is that a presentation-layer mask is not the same as privacy-safe publication of the dataset itself.
Incorrect Answers
A:A screen mask changes presentation at one interface. Authorized internal processes may still read the full stored number, so exporting the underlying database can reproduce sensitive values unless a separate transformation is applied. The distinction is between hiding a value in one view and removing it from data released externally.
B:Internal dashboards apply their own authorization and presentation rules; those protections do not automatically follow a raw data export. Publishing complete card numbers would expose customers regardless of how an employee portal renders them. External release needs data governance and explicit transformation of every sensitive field. The outward-facing extract needs its own explicit privacy review and verified removal of sensitive fields.
D:Four-digit masking can be suitable for a restricted user interface where authorized staff already know which customer record they are viewing. A publicly released dataset is different: unusual combinations of masked digits, dates and transaction patterns may still identify individuals or expose sensitive information. The firm needs a release-specific de-identification and linkability assessment, not the assumption that a display mask guarantees irreversibility.
Question 494
A disaster-recovery vault encrypts each backup volume but stores its master decryption key in the same cloud account under the same powerful administrator role. During a red-team exercise, compromise of that role gave access to both the backup objects and key service. Which change most directly reduces simultaneous exposure?
- Retain the current architecture because the backup dashboard reports that storage volumes are encrypted
- Separate key management rights and custody from backup object administration, using explicit access policies and audited recovery
- Include the master key plaintext in the same manifest as each backup to simplify restoration
- Turn off key rotation permanently so operators always know which key protects the copies
Explanation
Correct Answer
B:Segregating backup storage permissions from cryptographic key authority reduces the chance that one compromised cloud administrator can both take protected copies and decrypt them. Use independent roles, limited key-use APIs, approval or dual control for recovery, key-access logs and tested break-glass processes. Verify how the backup application handles temporary plaintext and cached keys; a nominally separate KMS policy that automatically grants the same identity all access is insufficient. The organization should retain recoverability while preventing unauthorized key release. This is defense in depth around key custody, not a claim that encryption alone neutralizes compromised administrators.
Incorrect Answers
A:Encryption at rest does not materially protect backups from a principal that can also retrieve or use their decryption key without independent restriction. The green encryption indicator says storage is protected against certain threats, not against a compromised role holding complete data and key authority. Access separation is still needed.
C:Placing decryption keys alongside protected backups effectively gives anyone who copies the archive the means to open it. A manifest is useful for metadata and key identifiers, but not plaintext secrets. The recovery system should reference keys in a secured service and follow authorized access procedures. The compromised backup administrator could recover the listed master key without any additional approval.
D:Permanent keys increase the period during which a stolen secret remains useful and make selective recovery from compromise harder. Rotation can be planned with key versioning, wrapped data keys and restore testing. Disabling it indefinitely does not correct the shared administrator trust boundary identified in the exercise. A documented rotation and historical-key recovery process can be established while preserving access separation.
Question 495
A healthcare archive encrypts each patient's file under a distinct data key, then stores wrapped keys in a managed vault. A verified deletion request concerns patient A; a court's legal hold protects patient B's data in the same storage account. The company wants to make only A's encrypted file unrecoverable, after checking statutory retention. What deletion mechanism best matches the requirements?
- Delete the entire cloud storage account, including records protected by the independent legal hold
- Remove patient A's file name from the search index while retaining all usable decryption keys
- Destroy the shared master key for every patient without mapping which encrypted objects depend on it
- After confirming legal obligations, irrecoverably remove only patient A's usable decryption key and protected recovery copies
Explanation
Correct Answer
D:Cryptographic erasure makes ciphertext practically unrecoverable by destroying every usable copy of the decryption key, provided encryption and key separation are sound. With per-patient data keys, the owner can target patient A while retaining keys for patient B under legal hold. First verify legal retention, backup, escrow and replicated key dependencies; otherwise a hidden recovery copy could defeat erasure or a shared wrapper could affect other records. Record the approval, destruction evidence and remaining ciphertext treatment. Key destruction is not identical to physical media sanitization, but it can provide effective selective deletion when the cryptographic design and custody controls are trustworthy.
Incorrect Answers
A:Deleting shared infrastructure may affect unrelated patients, including data required under legal hold. It would create availability and compliance problems that exceed the authorized deletion scope. Key and object dependencies must be mapped so a request for one record does not unintentionally destroy legally retained information. The legal hold remains enforceable even when another patient has a valid, separately scoped deletion request.
B:Removing a filename or interface search result changes discoverability but does not prevent an authorized or malicious party with the ciphertext and key from decrypting the original file. Deletion policy must address actual recoverability, including replicas and backups, not just whether a user interface displays a record. Anyone holding archived ciphertext and the still-valid key could recover the original protected file.
C:A shared master key can wrap many patients' data keys, so destroying it without dependency analysis could render legally protected and business-critical archives inaccessible. Cryptographic erasure works best when each target has a key boundary that can be invalidated independently. Uncontrolled master-key destruction violates the selective deletion requirement. The archive must retain independently recoverable keys for patient records that are not eligible for destruction.
Question 496
A design firm has DLP rules that match exact confidential project phrases in emails. A tester places the same words in a screenshot attached to an otherwise ordinary message; the DLP engine permits it because it scans only extracted text from supported document types. What limitation must the company address?
- Exact plain-text comparison recognizes every screenshot's image pixels without any image-processing capability
- Scan each screenshot attachment’s filename and MIME type while leaving the actual image pixels unexamined
- Adding more literal strings to the same text-only rule guarantees detection of words embedded in pictures
- Exact text matching misses transformed or image-embedded content; add appropriate OCR or image analysis, classification and review
Explanation
Correct Answer
D:DLP rules based on exact text can miss confidential information placed into screenshots, scanned pages, transformed content or graphics. Image-aware inspection and text recognition may recover detectable strings, while classification labels, destination restrictions and human review can address cases where OCR is unreliable. Test against real export formats and legitimate workflows to balance sensitivity and false positives; no single detector will catch every alteration. The core lesson is that matching content depends on its representation and collection path. The firm should broaden inspection coverage and use layered controls rather than assuming one literal string engine protects every image-bearing channel.
Incorrect Answers
A:A screenshot stores visual pixels rather than searchable words unless a tool extracts or recognizes text. Plain string comparison against text content will not necessarily inspect those pixels. The control must cover the representation in which sensitive information is leaving the organization, not assume all formats carry text identically. The demonstrated bypass arises because the engine never recognizes the pixels as protected text.
B:File names and MIME types help classify an attachment and can flag suspicious formats, but they cannot reveal the confidential words embedded as pixels in a screenshot. The exact-text DLP rule misses the content because it extracts words only from supported document text. The remedy must include appropriate image interpretation or a reviewed classification workflow; inspecting metadata alone does not detect the transformed data.
C:More exact phrases may improve coverage within supported text formats, but the engine still cannot match pixels it never converts to text. Encoding, screenshots and partial transformations can evade naive literal rules. A rule-set expansion without changing inspection capabilities would leave the demonstrated bypass available. The detection pipeline must first extract relevant characters before matching a larger dictionary can help.
Question 497
A simple city-weather application asks new users to upload ten years of precise GPS history, although it needs only a rough current location to produce hourly forecasts. Its developers plan to retain the complete timeline indefinitely for convenience. Which privacy-design principle is most directly disregarded?
- Mandatory historical location collection as a default requirement for every smartphone utility
- A suitable reduction to the current approximate city or location necessary to serve the forecast
- Data minimization and purpose limitation, which restrict collection and retention to justified service needs
- Cryptographic validation of an external weather supplier's published forecast data
Explanation
Correct Answer
C:Data minimization requires collecting only information necessary for a specified purpose, and purpose limitation prevents silently repurposing that data for unrelated activities. A decade of precise GPS history is disproportionate to providing the current city's weather forecast. The app should request coarse current location when needed, explain its use and avoid indefinite storage of irrelevant movement records. Consent alone does not make overcollection good design; the team still needs necessity, retention and access analysis. This problem is about the scope and lifecycle of personal information, not the authenticity of the forecast supplied by a weather service.
Incorrect Answers
A:There is no general operational requirement that a weather utility collect a decade of location tracking. Such a rule would increase exposure of highly sensitive movement history without improving the stated forecast use case. Collection should derive from a documented specific purpose, not a blanket app-design habit. An excessive GPS archive can reveal sensitive movements unrelated to the requested short-term forecast.
B:A limited current location can be an appropriate implementation when the app only needs a city-level forecast. It illustrates a safer choice rather than the violated principle itself. The developer should avoid collecting unnecessary precise history and define a retention period based on real delivery and legal needs. The product should also avoid retaining precise location after the current weather request is fulfilled.
D:Digital signatures can verify the integrity and authenticity of forecast updates if the provider supports them, but they do not justify or limit collection of customers' movement histories. The privacy risk arises from excessive user-data requests and retention. Supplier data integrity is a separate technical concern. Forecast authenticity cannot reduce the privacy burden of an unnecessary decade of precise user movements.
Question 498
A global payment API has a recovery requirement that checkout should continue after the total loss of any one cloud region. A single standby VM in the primary region has previously been overloaded during failover tests. The architecture committee wants to remove the regional single point of failure and demonstrate sufficient capacity under loss conditions. What design best fits?
- Keep a single powered-on standby server in the same failure region as the active database
- Rely on a weekly offline archive as the only means of restoring a transaction platform
- Operate an active-passive secondary region without demonstrating standby transaction capacity, traffic failover or replication consistency
- Operate appropriately sized active-active services in independent regions and test traffic shift and data consistency
Explanation
Correct Answer
D:Active-active deployment places serving capacity in more than one independent region so a complete regional outage can be handled by surviving infrastructure. Design traffic steering, adequate headroom, database replication or conflict resolution, and monitoring that detects failure without creating split-brain writes. Run realistic failover exercises to measure service availability and confirm that one remaining region can handle peak checkout demand. This pattern is more resilient than a single underprovisioned spare in the same region, although it costs more and requires careful consistency engineering. The requirement concerns entire-region continuity, not only restoring stored files afterward.
Incorrect Answers
A:A spare instance inside the same region is vulnerable to a regional power, network or control-plane incident. It may help with individual host failure, but it does not meet the stated full-region failure condition. The design also needs tested capacity, not just a standby listed in infrastructure records. A regional outage would eliminate both the primary and the colocated hot-spare instance at once.
B:An offline archive improves recoverability from some data-loss events but cannot itself keep checkout service available when the active region disappears. Weekly backups may also lose unacceptable transaction history. Continuous availability requires live or rapidly available serving capacity and a carefully designed data strategy across failure domains. Checkout continuity requires surviving live serving capacity, not only the ability to reconstruct records later.
C:A secondary region is a credible resilience layer and can survive the geographic loss of the primary region. However, the committee already found that a small standby failed under load, and the new requirement specifically demands demonstrated sufficient capacity during regional loss. Merely deploying passive infrastructure elsewhere does not prove it can serve all checkout requests or reconcile transaction state when traffic shifts.
Question 499
A disaster-recovery exercise for a wholesale finance service begins when the production site goes offline at 09:00. Operations restore working access at 09:48 using a transaction recovery point from 08:55. The approved business impact analysis specifies a 30-minute RTO and a 10-minute RPO. Which statement accurately evaluates both metrics?
- Both targets passed because the restored transaction data was only five minutes older than the outage began
- The RTO passed but the RPO failed because the service was unavailable for more than half an hour
- RTO failed at 48 minutes; RPO passed at five minutes of lost transactions, so restoration time needs improvement
- Both metrics failed because every recovery longer than ten minutes also violates the RPO
Explanation
Correct Answer
C:The recovery time objective is 30 minutes, but the service did not return until 09:48, so the observed 48-minute outage fails RTO by 18 minutes. The recovery point objective allows up to ten minutes of data loss; restoring transactions through 08:55 when failure occurred at 09:00 loses at most five minutes under the drill's assumptions and meets RPO. The team should investigate slow provisioning, dependencies and restoration sequences to shorten recovery. It should also verify that 'working access' means the service actually met agreed business functionality. Reporting both metrics independently preserves the distinction between downtime tolerance and transaction-loss tolerance.
Incorrect Answers
A:The recovery point may satisfy the allowable data-loss threshold, but the service was unavailable for 48 minutes. RTO and RPO measure different things, so success on the data-loss dimension does not erase the excessive restoration delay. The drill report must state the separate outcomes rather than collapse them into one pass result.
B:RTO concerns the maximum acceptable time to resume operations, and 48 minutes exceeds the 30-minute limit. RPO concerns the point in time from which data must be recoverable; the 08:55 data is five minutes behind the 09:00 outage, which is within the ten-minute target. Mixing these metrics reverses the conclusions.
D:The ten-minute RPO is not a limit on how long restoration can take; that role belongs to RTO. A 48-minute outage violates RTO here, but the five-minute data gap can still satisfy RPO. Conflating elapsed outage time with recovery point age leads to an incorrect dual-failure conclusion. The relevant data gap is from 08:55 to 09:00, not from 09:00 to 09:48.
Question 500
A regional legal firm detects ransomware after an attacker gained a powerful backup administrator account. The attacker attempted to delete restore points, but a separate immutable backup copy remains protected from ordinary administrative modification. Before reconnecting the case management service, how should the recovery lead use that copy?
- Mount the immutable vault as writable media for the recovery team so restoration can use the existing high-privilege backup workflow.
- Restore the newest point straight into production without checking whether it already contains malicious modifications
- Verify protected recovery-point integrity and restore known-clean data into an isolated environment before controlled production return
- Restore directly to production from the protected vault, using successful backup metadata as the sole integrity and malware check.
Explanation
Correct Answer
C:An immutable copy helps preserve recovery material when attackers attempt to modify or delete standard restore points. The recovery team should validate access controls and integrity, identify an uncompromised point, restore it into an isolated environment, scan for persistence and confirm case-management functionality before staged return to production. Use independent credentials, retain security logs and rotate compromised secrets. Immutability alone does not guarantee that the backed-up content was clean when captured, so both source integrity and recovered system state require examination. This approach preserves the strongest remaining trust boundary while avoiding reinfection or accidental destruction during an urgent restoration.
Incorrect Answers
A:A familiar privileged recovery workflow may simplify operational scripts, but turning an immutable copy into ordinary writable storage weakens the very boundary that protected it from the compromised administrator. The attacker attempted to delete recovery points, so key and access isolation are crucial. Restores should read validated protected copies through a controlled process, not grant broad modification rights to the protected vault. Recovery speed is secondary to preserving clean source evidence.
B:The newest point may include malicious persistence, tampered case files or encrypted data if created after compromise. Restoring directly into live production risks reintroducing the threat and confusing investigators. Verify candidate backup timing and integrity, then test recovery in a contained environment before reconnecting business users. Clean-room testing helps detect retained ransomware components before the restored service handles client files.
D:Protected backup metadata can establish that an archive exists and that its retention controls were respected. It cannot alone prove the captured system state predates ransomware persistence or compromised application changes. Direct production restoration may reintroduce malware or corrupt records if the recovery point is not validated. The team should inspect an appropriate known-clean point in isolation before reconnecting the case management service under controlled conditions.