exam questions

Exam Associate Cloud Engineer All Questions

View all questions & answers for the Associate Cloud Engineer exam

Exam Associate Cloud Engineer topic 1 question 5 discussion

Actual exam question from Google's Associate Cloud Engineer
Question #: 5
Topic #: 1
[All Associate Cloud Engineer Questions]

You are using multiple configurations for gcloud. You want to review the configured Kubernetes Engine cluster of an inactive configuration using the fewest possible steps. What should you do?

  • A. Use gcloud config configurations describe to review the output.
  • B. Use gcloud config configurations activate and gcloud config list to review the output.
  • C. Use kubectl config get-contexts to review the output.
  • D. Use kubectl config use-context and kubectl config view to review the output.
Show Suggested Answer Hide Answer
Suggested Answer: D 🗳️

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
zukko78
Highly Voted 4 years, 9 months ago
D is correct
upvoted 46 times
nhusain
3 years, 9 months ago
https://medium.com/google-cloud/kubernetes-engine-kubectl-config-b6270d2b656c explains it well
upvoted 11 times
...
...
poogcp
Highly Voted 4 years, 8 months ago
C is correct , Use kubectl config get-contexts to review the output : shows the clusters and the configurations and based on the output we can identify the inactive configurations
upvoted 25 times
Gurnoor
4 years, 7 months ago
This is wrong get-contexts does not show clusters it only shows contexts.
upvoted 11 times
jilly
4 years, 7 months ago
True . Will give only below results kubectl config get-contexts CURRENT NAME CLUSTER AUTHINFO NAMESPACE * white white dazwilkin black black dazwilkin
upvoted 1 times
...
...
fracila
2 years, 2 months ago
kubectl config get-contexts displays a list of contexts as well as the clusters that use them. Here's a sample output.
upvoted 2 times
...
...
AKVT
Most Recent 2 weeks, 1 day ago
Selected Answer: C
In Kubernetes, "kubectl config get-contexts" is a command used to list all available contexts within your Kubernetes configuration, essentially showing you all the different cluster connections you can access, while "kubectl config use-context" allows you to switch to a specific context from that list, effectively changing which cluster you are currently interacting with; essentially letting you move between different Kubernetes environments using a single kubectl command line. Key points about these commands: kubectl config get-contexts: Displays a list of all configured contexts, including their names and current status (whether they are the active context). Useful to see which clusters you can connect to and which one is currently selected. kubectl config use-context: Allows you to switch to a specific context by providing its name as an argument. Example: kubectl config use-context "my-cluster-context" would switch to the context named "my-cluster-context".
upvoted 1 times
AKVT
2 weeks, 1 day ago
The question is to view the inactive context config hence Answer: D is right.
upvoted 1 times
...
...
Roman1988
1 month, 1 week ago
Selected Answer: D
The right answer is D https://medium.com/google-cloud/kubernetes-engine-kubectl-config-b6270d2b656c
upvoted 1 times
...
user263263
2 months, 1 week ago
Selected Answer: A
A. gcloud config configurations describe <inactive-config-name> will show the configured GKE cluster as value for property container/cluster ("Name of the cluster to use by default when working with Kubernetes Engine.") B. more steps than A, so not "fewest possible steps" C. and D. not necessarily specific to GKE and a named gcloud configuration
upvoted 1 times
...
Bagesh
2 months, 3 weeks ago
The answer is A. Use gcloud config configurations describe to review the output. This command directly outputs the details of the specified configuration, including the configured Kubernetes Engine cluster, without requiring you to activate the configuration or switch contexts.
upvoted 1 times
...
denno22
3 months, 3 weeks ago
Selected Answer: D
D is correct.
upvoted 1 times
...
Buruguduystunstugudunstuy
4 months, 2 weeks ago
Selected Answer: D
Answer A: Using `gcloud config configurations described` will only show you the details of the current configuration, not the Kubernetes Engine cluster of an inactive configuration. Answer B: Using `gcloud config configurations activate` and `gcloud config list` to review the output will only show you the list of configurations and activate one of them, but it won't provide you with the details of the Kubernetes Engine cluster of an inactive configuration. Answer C: Using `kubectl config get-contexts` will only list the available contexts, including their clusters, but it won't provide you with the details of the Kubernetes Engine cluster of an inactive configuration.
upvoted 2 times
...
sivakarthick16
4 months, 2 weeks ago
Selected Answer: C
This command allows you to see the contexts available in your kubeconfig file, including those associated with inactive configurations, without needing to activate any configuration. It provides a straightforward way to review the clusters and contexts without additional steps.
upvoted 1 times
...
nubelukita45852
4 months, 2 weeks ago
Selected Answer: A
To review inactive gcloud configuration, the most direct and efficient command is to use gcloud config configurations describe, as it allows you to view the details of a specific configuration without needing to activate it first. This is ideal for reviewing the Kubernetes Engine cluster configured in that configuration without changing the active context. B involves activating the setting first, which requires additional steps. C and D refer to kubectl commands, which are not directly related to gcloud configuration but rather to managing Kubernetes contexts.
upvoted 1 times
...
nubelukita45852
4 months, 2 weeks ago
To review inactive gcloud configuration, the most direct and efficient command is to use gcloud config configurations describe, as it allows you to view the details of a specific configuration without needing to activate it first. This is ideal for reviewing the Kubernetes Engine cluster configured in that configuration without changing the active context. B involves activating the setting first, which requires additional steps. C and D refer to kubectl commands, which are not directly related to gcloud configuration but rather to managing Kubernetes contexts.
upvoted 1 times
...
harsh5kalsait
5 months, 4 weeks ago
Best Choice: A Option A is the best choice. It allows you to review the details of the configurations using the `gcloud config configurations describe`, which provides a straightforward way to examine the configurations themselves. This approach does not require activating the configuration and provides the necessary configuration details directly. If you need to see details about the Kubernetes Engine cluster in an inactive configuration, you might typically need to activate the configuration first and then use gcloud commands to list clusters, but since the goal is to use the fewest steps and you are only reviewing configurations, gcloud config configurations describe is the best fit for directly reviewing the configuration details.
upvoted 1 times
...
Sami_27
6 months ago
Option D assumes you know the configuration name and want to make it active for reviewing purposes. But to review a configuration you need not make it active. If you don’t want to activate the inactive configuration, then: Use gcloud config configurations list or Use kubectl config get-contexts to view the name of the configuration and it’s status (active/inactive). This won't give cluster-related information. There is No correct option. But, to review the configured Kubernetes Engine cluster, kubectl config view is a must. Note: the gcloud commands will only provide gcp-related details, not cluster-specific.
upvoted 1 times
...
EMPERBACH
7 months, 3 weeks ago
Selected Answer: A
The fewest steps to review the configured Kubernetes Engine cluster of an inactive configuration involve using the gcloud command-line tool and its configuration functionality: 1. Use gcloud config configurations describe: This command displays details about a specific configuration named after your inactive cluster setup. It provides information about the project, compute zone, and other cluster settings without needing to activate it.
upvoted 2 times
...
subha.elumalai
8 months, 2 weeks ago
Correct Answer: D Reference: https://medium.com/google-cloud/kubernetes-engine-kubectl-config-b6270d2b656c
upvoted 2 times
...
billytran89z
11 months, 4 weeks ago
C. Use kubectl config get-contexts to review the output. Option C, using kubectl config get-contexts, allows you to directly see the available contexts, including those from inactive configurations, and review the Kubernetes Engine clusters associated with them. This approach provides the necessary information efficiently. Option D (Use kubectl config use-context and kubectl config view to review the output) involves changing the active context and viewing the Kubernetes configuration but may involve unnecessary steps.
upvoted 1 times
...
zesymu
1 year ago
Selected Answer: D
D is right answer! Get Up-to-date: https://www.pinterest.com/pin/937522847419093171
upvoted 2 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
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.

SaveCancel
Loading ...
exam
Someone Bought Contributor Access for:
SY0-701
London, 1 minute ago