You save $69.98
A SaaS backup job silently copies EU customer data to a region outside its approved data map. As the accountable security practitioner, which response BEST addresses the specific weakness without introducing a different untested control?
Residency includes backups and operational derivatives, not merely the primary database. Region pinning may not govern external support exports or vendor subprocessors.
A residency decision must cover operational derivatives, not just the main datastore.
A generic hosting claim cannot verify the actual location of all regulated copies.
Confidentiality controls cannot replace geographic and transfer authorization.
The organization implemented the response to this scenario: A SaaS backup job silently copies EU customer data to a region outside its approved data map. The approved response was: Track primary, replica, backup and logging locations, then constrain processing to approved jurisdictions. Which statement MOST accurately identifies a remaining risk or constraint?
Residency includes backups and operational derivatives, not merely the primary database. Data-flow tests find no unauthorized backup or log replicas beyond approved locations.
Primary resource controls may not reach vendor support and onward-processing channels.
Backup and log location remains part of regulated data residency and contracts.
Encryption alone does not waive jurisdictional processing or transfer restrictions.
Management implemented a response after this event: A SaaS backup job silently copies EU customer data to a region outside its approved data map. The response was: Track primary, replica, backup and logging locations, then constrain processing to approved jurisdictions. Which observed outcome BEST verifies that the intended security protection operates, rather than merely appearing in a plan?
Data-flow tests find no unauthorized backup or log replicas beyond approved locations. Residency includes backups and operational derivatives, not merely the primary database.
Primary compliance does not prove every copy follows the approved residency map.
Commercial subscription labels do not establish actual processing location.
Encryption cannot demonstrate that geographic restrictions are enforced.
A company plans to reassign SSDs containing confidential customer records to an external partner. Staff have deleted the files and emptied the recycle bin. What is the BEST prerequisite to release the devices?
NIST SP 800-88 Rev. 2 requires a risk- and media-appropriate sanitization program. File deletion changes logical references but may leave recoverable flash media data. Verification and accountable reuse decisions are required.
Logical formatting can leave data in inaccessible remapped or spare physical areas, so it is not sufficient sanitization evidence.
A test-file overwrite does not prove all confidential data locations were sanitized, particularly on wear-leveled SSDs.
Newly encrypting a filesystem does not ensure earlier residual plaintext was purged from storage.
An SSD manufacturer advertises a sanitize command that reports success. Before a security manager authorizes external reuse of the drives, what residual assurance concern MUST be addressed?
NIST SP 800-88 Rev. 2 emphasizes program-level assurance and validating accepted techniques. A tool’s success status is evidence to assess, not infallible proof for every media configuration.
Controller status may be insufficient without confidence in coverage, implementation and validation appropriate to the media.
A contract does not make residual stored bytes inaccessible after custody is transferred.
Readability and lack of access controls increase disclosure risk and do not assess sanitization effectiveness.
A storage-retirement program claims every confidential SSD released for reuse has been sanitized. Which collected evidence BEST supports that claim?
An auditable sanitization program proves which devices were handled, how the approved technique was applied and whether expected confidentiality outcomes were verified.
Without device identity and method scope, auditors cannot show every relevant drive received a suitable sanitization treatment.
Asset labeling says nothing about whether residual confidential storage is inaccessible.
Receiving custody is not evidence that protected data was sanitized before transfer.
An encrypted disk array is being retired through cryptographic erase. Its production encryption key is destroyed, but recoverable wrapped copies of the same data-encryption key remain in a backup vault. What must happen before the stored ciphertext can be considered cryptographically erased?
Deleting one instance of a key cannot make ciphertext unrecoverable while another authorized or stolen path can reconstruct the same key. Key hierarchy, backup custody and implementation suitability must be assessed.
Aliases and labels are administrative references; retained key material and a usable unwrapping path still permit decryption.
Rotation alone protects new operations but does not sanitize existing ciphertext that old keys can still decrypt.
A quick format does not verify that all encrypted sectors and retained key material are unrecoverable.
An appliance vendor claims its “crypto erase” button guarantees sanitization of all archived disks. Which issue must an assessor still examine?
Cryptographic erase can be valid only when the encryption and destruction procedures cover the actual protected data and all recovery paths. Retained keys defeat the claimed result.
Interface preference has no bearing on whether decryption-capable secrets or plaintext remain accessible.
Crypto erase relies on disabling decryption, not necessarily overwriting every ciphertext sector with zeros.
Formatting a new filesystem does not establish that historical ciphertext is cryptographically unrecoverable.
A retired encrypted storage device was sanitized by destroying its decryption keys. What test result BEST supports the destruction claim?
A negative recovery test tied to a reviewed key inventory is stronger than a single API status because old backup or wrapped keys can otherwise bypass the erase.
Removal of a display reference does not prevent recovery using escrowed decryption material.
Successful future encryption does not demonstrate old ciphertext is no longer decryptable with retained old key copies.
Rotation and destruction are separate; an audit entry cannot establish all historical decrypt paths were eliminated.
Encrypted archives must remain recoverable for seven years, but automated key deletion is scheduled after one year. What should the owner change?
Ciphertext retention without a usable authorized decryption path defeats records availability.
The archive becomes unreadable before its mandated retention period ends.
Removing confidentiality controls creates an unnecessary disclosure risk.
Indefinite keys raise exposure and exceed justified data-retention needs.
The team extends key retention through the legal archive period. What risk STILL must be addressed?
Key-lifecycle compliance requires independent recoverability and backup custody tests.
Rotated data keys and versions can be necessary to decrypt old records.
Retention calls for controlled recoverability, not unrestricted access.
Key rotation does not end the underlying legal records obligation.
or Guarantee your success by buying the full version which covers the full latest pool of questions. (484 Questions, Last Updated on Oct 31, 2026)
Please check your mailbox for a message from support@examlabs.com and follow the directions.
