CompTIA SY0-701 Bundle

True anonymization aims to prevent practical re-identification, including linkage through auxiliary datasets, and is appropriate when identifying the same customer over time is unnecessary. This dashboard explicitly needs identifiers that remain joinable across records. Full anonymization can destroy that association; a controlled token scheme preserves joins while restricting access to the original payment values.

Application-level encryption protects values such as salary fields at rest or in selected database columns. It may be useful for financial confidentiality, but encrypting an unrelated salary field does not address card-number identifiers in this dashboard. Even encrypted card numbers may be unsuitable join keys depending on keying and encryption mode; tokenization targets the stated need.

Dynamic masking hides portions of sensitive values when presented to users, for instance showing only the last four digits of a card. The original card number may still be stored in the underlying database, and a masked display may not provide a stable, non-sensitive join key. The requirement is to avoid storing card numbers in dashboard records.

Tokenization replaces a sensitive value with a surrogate and keeps a protected mapping in a token service. It can reduce exposure of stored salary identifiers in some designs, but the stated requirement is that only authorized payroll clients decrypt salary amounts while the database stores rows. Token replacement does not directly describe application-controlled decryption of those amount fields.

Content-aware DLP detects or blocks outbound transmission of protected data based on content classifications and destination policy. It does not prevent a database administrator or storage service from reading salary fields already stored in plaintext. DLP helps contain exfiltration after access, while field-level encryption limits who can obtain the sensitive values in the first place.

Dynamic masking changes how salary values appear to users with limited roles, perhaps by hiding digits in query results or the presentation layer. The unmasked values may still reside in the database and could remain accessible through other paths or privileged roles. The case requires encryption with keys unavailable to the database engine rather than view-only redaction.

Field-level encryption hides confidential application values from unauthorized readers, such as sensitive salary amounts. Firmware integrity verification asks whether the downloaded bytes changed, not whether the image contents should be confidential. Encrypting the image without an authenticated reference still may not reveal unauthorized modification in the intended verification workflow.

Authenticated TLS protects transfer traffic and authenticates the remote endpoint during a session. It can prevent certain network changes while downloading firmware, but it does not by itself compare a stored file against a known approved image after the download. An altered file at the server or disk may be delivered over correctly authenticated TLS; digest verification targets the stored artifact bytes.

DLP egress policies inspect outbound information for sensitive content and prevent unapproved transfers. They do not normally establish whether a firmware binary matches its intended original bytes. The workflow is inbound artifact integrity verification, not stopping employee exfiltration of regulated records; a trusted digest is the relevant check.

Encrypting salary fields protects compensation information in storage or from components lacking the appropriate key. The question concerns partial display of national identifiers to support operators, not salary data. Even encrypted identifiers must be decrypted or otherwise formatted to reveal the allowed suffix, so role-appropriate masking directly addresses the display requirement.

Cryptographic digest verification detects changes by comparing a computed hash to an expected value. It does not selectively reveal the last digits of a person's identifier or enforce which employees may view them. A one-way digest is also generally unsuitable when the application must display a specific original suffix.

Content-aware DLP egress rules can prevent sensitive identifiers from being emailed or uploaded to unauthorized destinations. They do not control whether a help-desk screen exposes the entire identifier to an operator during legitimate work. Mask the role's permitted view, then use DLP as an additional outbound safeguard.

Tokenization substitutes protected identifiers with reference tokens and may be appropriate when an application needs to retain links without exposing original values. It does not monitor or block a user uploading an existing file containing regulated identifiers to an unauthorized cloud provider. The stated event is an outbound transfer requiring a policy enforcement point.

Authenticated TLS encrypts communications to the cloud drive and protects the transport against some network attackers. It can securely carry the very unauthorized file the employee is trying to upload. Transport encryption does not decide whether the destination is sanctioned or whether the content includes prohibited regulated identifiers.

Application or field encryption can reduce exposure when a particular salary or customer field is stored by an application. It does not necessarily inspect an arbitrary employee file or enforce restrictions on its upload to personal cloud storage. The requirement is to recognize sensitive content in an outbound document and apply a destination policy.

Mandatory label-based access control governs who can read or modify resources according to centrally administered classification and clearance decisions. It does not determine how long legal records must remain recoverable before eligible disposal. Legal hold and retention scheduling are lifecycle controls distinct from information-access labels.

Removing unnecessary personal fields is data minimization, which is valuable before collection and when a record no longer needs particular information. It cannot justify deleting legally required records early or specify the seven-year recoverability deadline. Minimize within lawful retention requirements, then dispose of the mandated record at the approved point.

Enterprise repository governance can control document ownership, sharing permissions and audit logs, supporting compliant records management. The general concept does not itself state the legally required seven-year retention and post-expiry destruction behavior. A specific enforceable retention schedule, with exceptions for holds, is what directly satisfies the requirement.

A retention policy determines when records must be preserved and when they should be removed, but it does not decide whether full birth dates should be collected at all. The service can avoid unnecessary sensitive data from the start, reducing both breach consequences and later storage/disposal obligations. Data minimization is the primary control here.

Anonymization can transform datasets to reduce re-identification risk before public sharing or secondary research. The newsletter service has no legitimate need for birth dates in the first place, so anonymizing those values adds processing complexity rather than eliminating unnecessary collection. Remove the field instead of collecting a secret only to transform it later.

Confidential computing and process isolation protect sensitive information while applications process it in memory. They are relevant when the system truly must handle protected data, not when the business function does not need the information. Strong in-use protection cannot compensate for purposeless collection of birth dates.

Application-level encryption limits unauthorized access to selected sensitive fields at rest and can protect data against database-level disclosure. The analytics engine must decrypt the customer values to compute over them, however, so ordinary field encryption alone does not protect the plaintext during runtime memory processing. The question specifically asks about the in-use exposure that remains after disk encryption.

Authenticated TLS protects customer data crossing service-to-service network links and authenticates endpoints. It does not encrypt data while the analytics process holds it in RAM for computation. A malicious local process or compromised privileged host component may inspect plaintext memory even when every inbound connection used TLS.

Controlled pseudonymous identifiers hide direct names while allowing records to be linked under a separate mapping. This can reduce data exposure for many analytics tasks, but the scenario says the engine operates on decrypted customer data in memory. Pseudonymization does not establish an execution boundary to prevent another process or host administrator from reading that working set.

Application or field encryption is appropriate when particular sensitive database values must remain protected from storage components or unprivileged clients. The issue here is plaintext service-to-service API transport across shared infrastructure, not the custody of salary fields at rest. Encrypted storage does not automatically protect network packets once data is decrypted for transmission.

Confidential computing and process isolation can protect data being used within a service's memory or separate risky workloads. They do not inherently encrypt API bytes on the network between two services or authenticate the remote endpoint. Protect the interservice transport as well as endpoint execution; these are distinct security boundaries.

Content-aware DLP can flag unauthorized outbound movement of confidential information through monitored network or endpoint channels. The requirement is to protect legitimate microservice calls from interception and modification, not to stop export to unsanctioned destinations. DLP rules do not replace encryption and authenticated identities on the application transport.

The Bell–LaPadula simple-security property prevents a subject from reading information above its clearance or active security level. It does not stop a subject that has already read Secret information from writing to a lower Public object. The analyst is expressly permitted to read the Secret report, and the violation would occur during the later downward write. The required rule therefore concerns destination classification during a write, not clearance checking when reading a document.

Biba models integrity rather than secrecy and uses rules intended to protect high-integrity information from untrusted modification. Its no-write-up restriction addresses lower-integrity subjects changing higher-integrity objects; that is not the data flow described here. The incident involves Secret contents being copied into a less classified Public file, so Bell–LaPadula confidentiality controls are the closer fit. Reversing the purpose of the two models would confuse integrity assurance with prevention of disclosure.

Discretionary access control allows an owner or delegated principal to grant access within the system’s policy boundaries, but owner approval alone does not enforce classification-based information flow. A Public document owner might invite many readers without knowing that its contents came from a Secret report. The mandatory no-write-down restriction must reject the high-to-low transfer independently of any discretionary ACL, because confidentiality cannot rely on the document creator’s choice.

Least-privilege ACLs control who can read or modify files inside an approved repository or shared folder. They are useful, but the developer already has access to the proprietary code and can export copies to a personal account. Governance of repository integrations, managed endpoints and outbound synchronization is needed in addition to internal file permissions.

Data lineage and provenance records reveal how a dataset or artifact was created and transformed, supporting reproducibility and auditability. They do not prevent a developer from syncing an entire proprietary repository to an unmanaged personal service. Source control history may help investigate the export, but it is not the primary containment mechanism.

Mandatory label-based access controls could restrict use of classified source artifacts according to centrally enforced classifications. The case does not establish a formal classification-label regime; it describes an uncontrolled personal synchronization path. Enterprise repository governance and managed identity/device enforcement more directly address the observed behavior.