Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
Question 28 of 373
Free Preview · 373 of 1,242 · questions 1–373 of 1,242 are free. Sign up free to sync your progress across devices.
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
In a Zero Trust design the same principle holds: never trust the data path. Microsoft Azure Storage uses CRC32C and MD5 hashes for object integrity validation; database systems use checksum pages and reconciliation jobs; Purview and data-quality services rely on row counts and hash comparisons. These are the mechanisms that directly prove the data has not been altered or lost. Everything else is supporting defense. The reconciliation routines are the primary technical control that makes integrity measurable and enforceable.
The keyword in the question was integrity. CIA triad, how do you determine integrity and the data hasn’t changed? With hashes and checksums.
Application data integrity risk primarily concerns ensuring that data remains accurate, consistent, and unaltered during storage, processing, or transfer. Reconciliation routines such as checksums, hash totals, and record counts are specifically designed to detect changes or modifications to the data. These methods verify that the data has not been tampered with or corrupted by comparing stored data to its original state.