Mountkirk Games wants you to secure the connectivity from the new gaming application platform to Google Cloud. You want to streamline the process and follow Google-recommended practices. What should you do?
A.
Configure Workload Identity and service accounts to be used by the application platform.
B.
Use Kubernetes Secrets, which are obfuscated by default. Configure these Secrets to be used by the application platform.
C.
Configure Kubernetes Secrets to store the secret, enable Application-Layer Secrets Encryption, and use Cloud Key Management Service (Cloud KMS) to manage the encryption keys. Configure these Secrets to be used by the application platform.
D.
Configure HashiCorp Vault on Compute Engine, and use customer managed encryption keys and Cloud Key Management Service (Cloud KMS) to manage the encryption keys. Configure these Secrets to be used by the application platform.
A is correct .
https://cloud.google.com/kubernetes-engine/docs/how-to/workload-identity
Workload Identity is the recommended way to access Google Cloud services from applications running within GKE due to its improved security properties and manageability. For information about alternative ways to access Google Cloud APIs from GKE, refer to the alternatives section below.
A) - Because Mountkrik Game is going to use GKE clusters for its new deployment and so work load identity is the preferred way to connect the apps running on GKE
This question is vague and confusing, I have no idea what it wants to secure exactly. If we're talking about secrets like api keys and tokens another things, I'd use secrets manager, but that's not a choice, if we're talking about service account access it's workload identity. None of this is specified and thus the question is unanswerable.
A is the best option, as we know the work loads in Mountkirk. Read more what will be managed by GCP, if we go with Workload Identity: https://cloud.google.com/kubernetes-engine/docs/concepts/workload-identity#what_is
The correct answer is: A. Configure Workload Identity and service accounts to be used by the application platform.
Workload Identity is a feature of Google Cloud that allows you to map identities from your on-premises or Google Cloud identity provider to Google Cloud service accounts. By using Workload Identity, you can secure the connectivity of your application platform to Google Cloud by using the service accounts to authenticate and authorize access to Google Cloud resources.
Service accounts are Google Cloud resources that represent non-human users that your application platform can use to authenticate and authorize access to Google Cloud resources. By using service accounts, you can secure the connectivity of your application platform to Google Cloud by controlling which resources the service accounts can access and what actions they can perform.
To configure Workload Identity and service accounts, you will need to create a service account and bind it to the identity of your workload. You can then use the service account to authenticate to Google Cloud APIs and access the resources needed by your application platform. This will help to secure the connectivity from the platform to Google Cloud and streamline the process of managing access and permissions.
A. Workload Identity is the recommended way to access Google Cloud services from applications running within GKE due to its improved security properties and manageability
https://cloud.google.com/kubernetes-engine/docs/how-to/workload-identity
"Secure the connectivity" - gaming platform runs on GKE, and Workload Identity is the recommended way to connect to Google Cloud services from GKE. Hence A.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
muhasinem
Highly Voted 3 years, 4 months agodhamo_555
Highly Voted 3 years, 3 months agoSephethus
Most Recent 5 months agothewalker
1 year agoomermahgoub
1 year, 11 months agoomermahgoub
1 year, 11 months agomegumin
2 years agoAzureDP900
2 years, 1 month agomuky31dec
2 years, 9 months agovincy2202
2 years, 11 months agojoe2211
3 years agoMaxNRG
3 years, 1 month agoAri_GCP
3 years, 2 months agoPeppaPig
3 years, 3 months agokopper2019
3 years, 4 months agovictory108
3 years, 4 months agokopper2019
3 years, 4 months agoMamthaSJ
3 years, 4 months ago