You deployed a new application inside your Google Kubernetes Engine cluster using the YAML file specified below.

You check the status of the deployed pods and notice that one of them is still in PENDING status:

You want to find out why the pod is stuck in pending status. What should you do?
https://kubernetes.io/docs/tasks/debug-application-cluster/debug-application/#debugging-pods
You have a single binary application that you want to run on Google Cloud Platform. You decided to automatically scale the application based on underlying infrastructure CPU usage. Your organizational policies require you to use virtual machines directly. You need to ensure that the application scaling is operationally efficient and completed as quickly as possible. What should you do?
Managed instance groups offer autoscaling capabilities that let you automatically add or delete instances from a managed instance group based on increases or decreases in load (CPU Utilization in this case). Autoscaling helps your apps gracefully handle increases intraffic and reduce costs when the need for resources is lower. You define the autoscaling policy and the autoscaler performs automatic scaling based on the measured load (CPU Utilization in this case). Autoscaling works by adding more instances to your instance group when there is more load (upscaling), and deleting instances when the need for instances is lowered (downscaling). Ref:https://cloud.google.com/compute/docs/autoscaler
(You are managing a stateful application deployed on Google Kubernetes Engine (GKE) that can only have one replica. You recently discovered that the application becomes unstable at peak times. You have identified that the application needs more CPU than what has been configured in the manifest at these peak times. You want Kubernetes to allocate the application sufficient CPU resources during these peak times, while ensuring cost efficiency during off-peak periods. What should you do?)
The Vertical Pod Autoscaler (VPA) in Kubernetes automatically adjusts the CPU and memory requests and limits of the containers within a pod based on historical and real-time resource usage. In this scenario, where a single-replica stateful application needs more CPU during peak times, VPA can dynamically increase the CPU allocated to the pod when needed and potentially decrease it during off-peak periods to optimize resource utilization and cost efficiency.
Option A: Cluster autoscaling adds or removes nodes in your GKE cluster based on the resource requests of your pods. While it can help with overall cluster capacity, it oesn't directly address the need for more CPU for a specific pod.
Option C: Horizontal Pod Autoscaler (HPA) scales the number of pod replicas based on observed CPU utilization or other select metrics. Since the application can only have one replica, HPA is not suitable.
Option D: Node auto-provisioning is similar to cluster autoscaling, automatically creating and deleting node pools based on workload demands. It doesn't directly manage the resources of individual pods.
Reference to Google Cloud Certified - Associate Cloud Engineer Documents:
The functionality and use cases of the Vertical Pod Autoscaler (VPA) are detailed in the Google Kubernetes Engine documentation, specifically within the resource management and autoscaling sections. Understanding how VPA can dynamically adjust pod resources is relevant to the Associate Cloud Engineer certification.
You need to monitor resources that are distributed over different projects in Google Cloud Platform. You want to consolidate reporting under the same Stackdriver Monitoring dashboard. What should you do?
When you intially click on Monitoring(Stackdriver Monitoring) it creates a workspac(a stackdriver account) linked to the ACTIVE(CURRENT) Project from which it was clicked.
Now if you change the project and again click onto Monitoring it would create an another workspace(a stackdriver account) linked to the changed ACTIVE(CURRENT) Project, we don't want this as this would not consolidate our result into a single dashboard(workspace/stackdriver account).
If you have accidently created two diff workspaces merge them under Monitoring > Settings > Merge Workspaces > MERGE.
If we have only one workspace and two projects we can simply add other GCP Project under
Monitoring > Settings > GCP Projects > Add GCP Projects.
https://cloud.google.com/monitoring/settings/multiple-projects
Nothing about groups https://cloud.google.com/monitoring/settings?hl=en
You are managing a project for the Business Intelligence (BI) department in your company. A data pipeline ingests data into BigQuery via streaming. You want the users in the BI department to be able to run the custom SQL queries against the latest data in BigQuery. What should you do?
When applied to a dataset, this role provides the ability to read the dataset's metadata and list tables in the dataset. When applied to a project, this role also provides the ability to run jobs, including queries, within the project. A member with this role can enumerate their own jobs, cancel their own jobs, and enumerate datasets within a project. Additionally, allows the creation of new datasets within the project; the creator is granted the BigQuery Data Owner role (roles/bigquery.dataOwner) on these new datasets.
https://cloud.google.com/bigquery/docs/access-control
Daniel Gonzalez
7 days agoKristel
26 days agoVerona
1 month agoLynelle
1 month agoShalon
2 months agoWhitley
2 months agoKristeen
2 months agoMeghan
2 months agoAlberto
3 months agoDominga
3 months agoGladys
3 months agoMi
3 months agoTrina
4 months agoJose
4 months agoLavonne
4 months agoStefan
4 months agoHoa
5 months agoKiley
5 months agoAbraham
5 months agoWalker
5 months agoCecily
6 months agoCarlene
6 months agoJohnetta
6 months agoMalinda
6 months agoTalia
7 months agoGianna
7 months agoMuriel
7 months agoAdaline
7 months agoTien
7 months agoMicah
8 months agoMargurite
8 months agoKarima
10 months agoMauricio
10 months agoPeter
11 months agoDevon
12 months agoStaci
12 months agoShelia
1 year agoAvery
1 year agoRoselle
1 year agoLuisa
1 year agoLeonida
1 year agoKati
1 year agoSheldon
1 year agoGerald
1 year agoTwanna
1 year agoTambra
1 year agoRoyal
1 year agoDelmy
1 year agoLorrine
1 year agoLoreta
1 year agoArlyne
1 year agoKristofer
1 year agoKeneth
1 year agoErasmo
1 year agoSkye
1 year agoClaribel
1 year agoGolda
1 year agoBrinda
2 years agoErick
2 years agoYvonne
2 years agoBette
2 years agoTennie
2 years agoBev
2 years agoLashaunda
2 years agoMerlyn
2 years agoJunita
2 years agoMadonna
2 years agoKeneth
2 years agoGregoria
2 years agoMabel
2 years agoBrittni
2 years agoCharlesetta
2 years agowibimosentrau
2 years ago