Exam Professional Cloud Architect topic 1 question 63 discussion

A. Cloud Functions - managed service scales down to 0 B. Compute Engine - not a managed service C. Google Kubernetes Engine - not a managed service and wont scale down to 0 D. AppEngine flexible environment - managed service but wont scale down to 0

A. Cloud Functions

The only correct answer here is cloud run which isn't listed as an option. (A) can scale to zero, but is mean't for event driven workloads,not full sized applications, especially in the routing department (B) Needs manual stoppage, managed groups also keep one instance alive always (C) You're billed for the control plane even if the node pools are empty (D) Flex can't scale down to zero currently

This question is confused. It's seems that the answer is cloud function because is the only platform that can scale 0 natively. If you want to scale to zero k8s, you have to create a solution based in scheduler, function and pub sub. Compute Engine is not a managed service, and app engine flex doesn't scale to 0. I would go to A but it's not clear.

agree A

Selected answer: D I choosed D, it appears that we do not. have a right answer here. A. Cloud Functions - its more for event driven computing, not for full application B. Compute Engine - not a managed service C. Google Kubernetes Engine - not a managed service and wont scale down to 0 D. AppEngine flexible environment - Only Standard App Engine can scale to 0.

For an application that is only used during business hours and needs to scale to zero during periods of inactivity to minimize costs, a good choice would be a Function-as-a-Service (FaaS) product like AWS Lambda or Google Cloud Functions.

A a cloud function is not an application B compute engine via MIG you can use an autoscaler with a schedule. https://cloud.google.com/compute/docs/autoscaler/scaling-schedules You then can go from 0 to more instance when required C K8s is two complex for this. You can have an autoscaler for the cluster in order to get the node number to 0, but it require the node to have no pods running. So you have to configure your deployments and all your workload to scale to 0 too. Other interference will be pod affinity, anti-affinity, disruption budget or unmanaged pod preventing pod eviction from node. But if the pod is not evicted, the node cannot be deleted. "autoscaler respects scheduling and eviction rules set on Pods. These restrictions can prevent a node from being deleted by the autoscaler. " => https://cloud.google.com/kubernetes-engine/docs/concepts/cluster-autoscaler#scheduling-and-disruption D flexible cannot scale to 0

A. Cloud Functions

Why not D? App Engines also can scale down to zero when there is no activity. https://cloud.google.com/appengine/docs/the-appengine-environments#:~:text=Intended%20to%20run%20for%20free,when%20there%20is%20no%20traffic. Intended to run for free or at very low cost, where you pay only for what you need and when you need it. For example, your application can scale to 0 instances when there is no traffic.

the only to scale to 0 is A

The correct answer is A. Cloud Functions. Cloud Functions is a serverless compute service that lets you run code without provisioning or managing infrastructure. One of the key benefits of using Cloud Functions is that it automatically scales to meet the demands of your workload and automatically scales down to zero when there is no activity. This means that you only pay for the compute resources that you consume, which can help to reduce costs when your application is not in use. Additionally, Cloud Functions is easy to use and allows you to deploy your code with minimal effort, making it a good choice for a minimum viable product release.

vote A this is easy one. key word: managed product, scales to zero scale to zero: app engine standard, cloud function

Answer is B

Cloud Functions can scale to zero when not in use

Answer is A, As Option D App engine flexible can have minimum 1 instance active.

Answer is A, As Option D App engine flexible can have minimum 1 instance active.