Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Google Professional Cloud DevOps Engineer Exam - Topic 1 Question 91 Discussion

You are deploying an application that needs to access sensitive information. You need to ensure that this information is encrypted and the risk of exposure is minimal if a breach occurs. What should you do?
A) Store the encryption keys in Cloud Key Management Service (KMS) and rotate the keys frequently
B) Inject the secret at the time of instance creation via an encrypted configuration management system.
C) Integrate the application with a Single sign-on (SSO) system and do not expose secrets to the application
D) Leverage a continuous build pipeline that produces multiple versions of the secret for each instance of the application.

Google Professional Cloud DevOps Engineer Exam - Topic 1 Question 91 Discussion

Actual exam question for Google's Professional Cloud DevOps Engineer exam
Question #: 91
Topic #: 1
[All Professional Cloud DevOps Engineer Questions]

You are deploying an application that needs to access sensitive information. You need to ensure that this information is encrypted and the risk of exposure is minimal if a breach occurs. What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: A

https://cloud.google.com/security-key-management


by Cammy at May 04, 2025, 02:53 PM

Limited Time Offer

25%

Off

Get Premium Professional Cloud DevOps Engineer Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Luann
7 months ago
D sounds complicated, not sure if it's necessary.
upvoted 0 times
...
Martina
7 months ago
Wait, can you really trust KMS with everything?
upvoted 0 times
...
Alisha
7 months ago
C is a solid choice, keeps secrets out of the app!
upvoted 0 times
...
Leigha
7 months ago
I think B is more secure, though.
upvoted 0 times
...
Margot
8 months ago
A is the best option for key management!
upvoted 0 times
...
Francesco
8 months ago
Leveraging a continuous build pipeline sounds interesting, but I’m not clear on how that would help with encryption. I might lean towards A or B instead.
upvoted 0 times
...
Sharika
8 months ago
I recall a practice question where SSO was mentioned as a way to avoid exposing secrets. Option C might be relevant, but I feel like it doesn't directly address encryption.
upvoted 0 times
...
Yvonne
8 months ago
I think injecting secrets during instance creation is a good practice, but I wonder if it really minimizes exposure as much as storing keys in KMS.
upvoted 0 times
...
Allene
9 months ago
I remember studying about key management and how important it is to rotate keys regularly. Option A seems like a solid choice, but I'm not entirely sure if it's the best one.
upvoted 0 times
...
Winfred
9 months ago
Leveraging a continuous build pipeline with multiple secret versions for each instance is an interesting idea. I'll have to think through the implementation details, but it could be a robust solution.
upvoted 0 times
...
Dong
9 months ago
Integrating with an SSO system and not exposing secrets directly to the application sounds like a good way to minimize risk. I'll make sure to consider that as an option.
upvoted 0 times
...
Shelia
9 months ago
Hmm, I'm a bit unsure about this one. Injecting the secret at instance creation could work, but I'm not sure how that would handle key rotation. Maybe I should look into that option a bit more.
upvoted 0 times
...
Sherita
9 months ago
This seems like a straightforward security question. I think storing the encryption keys in a managed service like KMS and rotating them regularly is a solid approach.
upvoted 0 times
...
Fabiola
1 year ago
Ooh, encryption, you say? I bet I could crack that in my sleep! But seriously, great idea. Maybe we could even throw in some two-factor authentication for good measure.
upvoted 0 times
Taryn
11 months ago
Agreed. It's important to constantly monitor and assess our security measures to ensure the safety of the sensitive information.
upvoted 0 times
...
Margret
11 months ago
We should also regularly update our encryption methods to stay ahead of potential threats.
upvoted 0 times
...
Lea
12 months ago
Two-factor authentication is definitely a good additional layer of security. It's always better to be safe than sorry.
upvoted 0 times
...
Margart
1 year ago
That's not something to joke about. Encryption is serious business when it comes to protecting sensitive information.
upvoted 0 times
...
...
Destiny
1 year ago
I think we should also consider using multi-factor authentication to add an extra layer of security.
upvoted 0 times
...
Pamela
1 year ago
Hmm, encryption is a good start, but I wonder if we should also consider other security measures like data segmentation and regular security audits to really lock things down.
upvoted 0 times
Freeman
1 year ago
I agree, a combination of encryption, data segmentation, and regular security audits can help minimize the risk of exposure in case of a breach.
upvoted 0 times
...
Mike
1 year ago
Regular security audits are crucial to identify any vulnerabilities and ensure that our encryption methods are up to date.
upvoted 0 times
...
Amos
1 year ago
I think implementing encryption along with data segmentation and regular security audits is a solid approach to minimize the risk of exposure in case of a breach.
upvoted 0 times
...
Yvette
1 year ago
Encryption is definitely important, but I agree that data segmentation and regular security audits can add an extra layer of protection.
upvoted 0 times
...
Lenny
1 year ago
Yes, encryption is definitely important. Data segmentation can also help limit access to sensitive information.
upvoted 0 times
...
...
Fatima
1 year ago
In addition, we should regularly update our security measures to stay ahead of potential threats.
upvoted 0 times
...
Laurena
1 year ago
Definitely, encryption is key here. I would also recommend implementing robust access controls and authentication measures to further secure the application.
upvoted 0 times
Devorah
1 year ago
Agreed, encryption, access controls, and authentication are all essential for securing sensitive information.
upvoted 0 times
...
Vincenza
1 year ago
Implementing strong access controls and authentication measures will add an extra layer of security.
upvoted 0 times
...
Lawrence
1 year ago
Encrypting the sensitive information is crucial to protect it from exposure.
upvoted 0 times
...
...
Maybelle
1 year ago
Agreed, we can also implement access controls to limit who can view the information.
upvoted 0 times
...
Annice
1 year ago
We should use strong encryption algorithms to protect the sensitive information.
upvoted 0 times
...
Cyndy
1 year ago
I think we should use a strong encryption algorithm like AES-256 to protect the sensitive data. That will help minimize the risk of exposure if a breach occurs.
upvoted 0 times
Salina
1 year ago
Using strong encryption like AES-256 is crucial to ensure the security of the sensitive information.
upvoted 0 times
...
Blossom
1 year ago
Agreed, AES-256 is a strong encryption algorithm that will help minimize the risk of exposure.
upvoted 0 times
...
Vi
1 year ago
We should definitely use AES-256 encryption to protect the sensitive data.
upvoted 0 times
...
...

Save Cancel