Q: 4
[Emerging Technologies and Threats]
Which of the following best explains the business requirement a healthcare provider fulfills by
encrypting patient data at rest?
Options
Discussion
D . CompTIA loves tossing in that privacy plus portability combo for anything healthcare, seen similar on recent practice sets.
D makes sense here. Encrypting at rest is all about protecting patient privacy but also letting providers move or store data safely, which ties directly to portability (HIPAA stuff). C is more about limiting risk after a breach, but doesn't mention portability at all. Pretty sure D is what they're looking for, though open if there's another angle.
Feels like D. Encrypting at rest isn't just about stopping identity theft (that's what C hints at), it's really to meet HIPAA's privacy rules and let data be portable between systems. Seen similar on practice exams, but open to debate.
I don’t think it’s C. Protecting from identity theft sounds good but doesn’t cover portability, which HIPAA actually cares about. D fits better for both privacy and operational needs unless I'm missing something in the question wording?
D
D , it's mainly about protecting privacy while still letting data be portable for healthcare workflows. C is tempting but doesn't fully capture the regulatory and operational need for both privacy and portability under HIPAA. Disagree?
D Encrypting at rest hits privacy and data mobility, which is what HIPAA cares about.
D imo. Encrypting data at rest is all about protecting patient privacy even when records get moved or stored elsewhere. Healthcare needs both privacy and data portability, especially with HIPAA in play. Pretty sure that's what they're after here, right?
D imo, since HIPAA wants both privacy protection and supports data portability. C is common as a trap but doesn't cover the portability that healthcare actually needs. Pretty sure that's what they're after here, unless I'm missing something subtle.
A is wrong, D. Encryption at rest is about keeping patient info private (compliance with HIPAA), but still letting the data be portable if needed across devices or systems. C just misses the portability angle, I think.
Be respectful. No spam.