Study DVA-C02 Encryption at Rest, In Transit and Key Management: key concepts, common traps, and exam decision cues.
Encryption questions on DVA-C02 usually look easy until they mix storage behavior, transport security, KMS permissions, and certificate handling into one stem. The exam wants you to know where encryption happens, who manages the keys, and which permission boundary can still block access.
Encryption at rest: Protection applied while data is stored in a database, object store, volume, or backup.
Encryption in transit: Protection applied while data moves between clients, services, or networks, usually through TLS.
AWS wants you to separate:
| If the question is mainly about… | Strong lane | Why |
|---|---|---|
| service stores encrypted data automatically | server-side encryption | The storage service applies encryption at rest for you. |
| application must encrypt before sending data to AWS | client-side encryption | The app controls encryption before data leaves the client. |
| app can access the service but decryption still fails | KMS key policy or grant path | Service access and key usage are different permission lanes. |
| TLS certificates for services or private trust | certificate management | This is an in-transit trust problem, not a secrets-storage problem. |
| encrypting data across account boundaries | cross-account KMS usage path | Both caller permissions and key policy must align. |
flowchart TD
A["Data protection requirement"] --> B{"Data stored or moving?"}
B -->|"Stored"| C["Choose at-rest encryption model"]
B -->|"Moving"| D["Choose TLS / certificate path"]
C --> E{"Who encrypts?"}
E -->|"Service"| F["Server-side encryption"]
E -->|"Application"| G["Client-side encryption"]
C --> H["Check KMS key access if decryption fails"]
Strong answers usually keep three questions separate:
DVA-C02 likes stems where IAM looks correct but the application still cannot decrypt. That usually means:
This is one of the clearest examples of why security questions need lane separation.
If the question asks about operational security rather than app logic, key rotation may be the stronger answer. If it asks about decryption from another account, think about both the caller’s permissions and the key’s cross-account policy path.
| Trap | Better thinking |
|---|---|
| encryption at rest and in transit are interchangeable | They protect different moments in the data path. |
| KMS permission comes automatically with service permission | Access to the service does not guarantee access to use the key. |
| certificates are just another app secret | Certificate management is a trust and transport-security lane. |
| server-side and client-side encryption are the same choice | They differ by who performs encryption and where trust is placed. |