MENU
Your organization has a security policy to ensure that all Cloud SQL for PostgreSQL databases are secure. You want to protect sensitive data by using a key that meets specific locality or residency requirements. Your organization needs to control the key's lifecycle activities. You need to ensure that data is encrypted at rest and in transit. What should you do?
Suggested Answer: B
Get Premium Professional Cloud Database Engineer Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
https://cloud.google.com/sql/docs/postgres/configure-cmek#createcmekinstance
30 comments · newest first
DE
Devon
6 months ago
I feel like B covers all security needs.
VE
Verdell
6 months ago
D could work too, but it's for persistent disks only.
GW
Gwen
6 months ago
But A lacks control over the key lifecycle.
MA
Marylou
6 months ago
A seems easier though.
LA
Lamar
7 months ago
Customer-managed keys give more control.
DI
Diego
7 months ago
Why B?
LA
Lamar
7 months ago
I think B is the best choice.
TI
Timothy
7 months ago
Agree, B gives the best control over encryption!
MI
Mindy
7 months ago
I thought Google-managed keys were enough for security?
GI
Gilberto
8 months ago
Definitely need customer-managed keys for compliance.
DE
Denise
8 months ago
B is the way to go. You need to ensure you meet those locality and residency requirements.
LE
Leila
8 months ago
I agree with B. It's important to have control over the encryption keys for sensitive data.
MA
Malissa
8 months ago
Definitely option B. Customer-managed encryption keys give you more control over your data's security.
JO
Johnetta
9 months ago
B) Create the database with customer-managed encryption keys.
BE
Bev
9 months ago
I'm leaning towards B or D, but I'm not sure which one would be better. I think I need to review the details of each option to make sure I understand the differences.
ST
Stefany
9 months ago
I'm pretty confident that B is the right choice here. Customer-managed keys give us the control we need over the encryption, and it covers both data at rest and in transit.
BE
Bethanie
9 months ago
Option D sounds like the way to go. With customer-managed encryption keys on the persistent disk, we can ensure the data is encrypted and meet the locality/residency requirements.
LA
Lacresha
9 months ago
Hmm, I'm a bit confused. Do we need to encrypt the data in transit as well as at rest? If so, I'm not sure if the Google-managed encryption keys would be sufficient.
PA
Pamella
9 months ago
I think I'd go with option B. Customer-managed encryption keys give us more control over the key lifecycle, which is important for meeting our organization's security requirements.
RO
Rosendo
10 months ago
I vaguely recall that for sensitive data, customer-managed keys are usually recommended, but I need to double-check the specifics on encryption at rest and in transit.
SI
Silvana
10 months ago
I feel like Google-managed keys are easier to implement, but I’m uncertain if they meet the residency requirements we talked about.
KE
Kenneth
10 months ago
B is the way to go for customer control!
JU
Julian
11 months ago
Wait, can we really trust customer-managed keys?
CO
Coletta
11 months ago
Option B is the right choice. Gotta keep that data secure, am I right? *wink wink*
LE
Leandro
6 months ago
Right? It's all about keeping sensitive info safe!
SU
Sunny
6 months ago
Plus, you can meet those residency requirements easily.
DO
Doug
10 months ago
Agreed! Security is key, literally!
AN
Annelle
10 months ago
Definitely! Customer-managed keys give more control.
PE
Pearline
11 months ago
I think we practiced a similar question where customer-managed keys were emphasized for controlling the key lifecycle. That might be the right choice.
MA
Margot
11 months ago
I remember discussing the importance of customer-managed encryption keys for compliance with locality requirements, but I'm not sure if that applies here.