Professional Cloud Developer Exam - Question 86

Question

You are developing an application that will be launched on Compute Engine instances into multiple distinct projects, each corresponding to the environments in your software development process (development, QA, staging, and production). The instances in each project have the same application code but a different configuration. During deployment, each instance should receive the application's configuration based on the environment it serves. You want to minimize the number of steps to configure this flow. What should you do?

Examice · Accepted Answer

The most efficient approach is to configure a metadata key named 'environment' in each project, with a value corresponding to the environment it serves (e.g., development, QA, staging, or production). This allows the deployment tool to query the instance metadata and configure the application based on the 'environment' value. This setup minimizes the number of steps required, as the metadata key only needs to be set once per project, rather than for each instance, and simplifies the configuration flow.

scaenruy · Answer

I vote B

GCPCloudArchitectUser · Answer

For Answer D : 
Question says minimize steps and adding metadata to each instance seems longer route ?

KillerGoogle · Answer

D, 
'environment' is not in one of the default key
https://cloud.google.com/compute/docs/metadata/default-metadata-values

jitu028 · Answer

Answer should be B

nqthien041292 · Answer

Vote B

tomato123 · Answer

B is correct

omermahgoub · Answer

Option A, configuring a startup script using the gcloud command to determine the project name, is not a feasible solution because it requires additional steps to be taken during instance launch. Option C, deploying a deployment tool on an instance in each project and using a deployment job to retrieve the appropriate configuration file, is not a feasible solution because it requires additional steps to be taken during instance launch and involves the use of a separate deployment tool. Option D, configuring an instance custom-metadata key named "environment" during each instance launch, is not a feasible solution because it requires additional steps to be taken during instance launch.

TNT87 · Answer

https://cloud.google.com/compute/docs/metadata/querying-metadata

zellck · Answer

B is the answer.

https://cloud.google.com/compute/docs/metadata/setting-custom-metadata#set-custom

Rajan · Answer

Option B is correct we usually put this details in Environment variable.

wanrltw · Answer

https://cloud.google.com/compute/docs/metadata/setting-custom-metadata#set-custom-project-wide-metadata

thewalker · Answer

The best answer is D. During each instance launch, configure an instance custom-metadata key named ‘environment’ whose value is the environment the instance serves. Use your deployment tool to query the instance metadata, and configure the application based on the ‘environment’ value.

Here's why:

Simplicity and Efficiency: This approach is the most straightforward and efficient. It leverages existing Compute Engine features (custom metadata) and avoids the need for additional scripts or deployment tools.
Centralized Configuration: Custom metadata is associated with the instance itself, making it a centralized and reliable source of environment information.
Flexibility: Your deployment tool can easily query the instance metadata during deployment, allowing you to dynamically configure the application based on the environment.

Professional Cloud Developer Exam - Question 86

Discussion