Both Database and the Web application need to be available. Production apps should have full availability.

Reference

https://landing.google.com/sre/sre-book/chapters/service-level-objectives/

1MB maximum size of a cached data value is 1 MB (10^6 bytes).

Reference

https://cloud.google.com/appengine/docs/standard/python/memcache/

Using gcloud is very important for this exam around Kubernetes since the gcloud commands are what interact with GCP resources that create and manage the clusters and then the kubectl, which is the Kubernetes command line tool is used to run commands against Kubernetes clusters on GKE.

Archive formerly Coldline(Cloud Storage) is meant for storing data over 90 days. It is the most economic option in GCP.

Reference

https://cloud.google.com/storage/docs/storage-classes

Kubernetes ingress is a collection of routing rules that govern how external users access services running in a Kubernetes cluster. The edge proxy is commonly called an ingress controller because it is commonly configured using ingress resources in Kubernetes, however the edge proxy can also be configured

To ingest logs, you must deploy the Stackdriver Logging agent to each node in your cluster. The agent is a configured fluentd instance, where the configuration is stored in a ConfigMap and the instances are managed using a Kubernetes DaemonSet. The actual deployment of the ConfigMap and DaemonSet for your cluster depends on your individual cluster setup. Stackdriver is the default logging solution for clusters deployed on Google Kubernetes Engine. Stackdriver Logging is deployed to a new cluster by default unless you explicitly opt-out.

Create and run shutdown scripts that execute commands right before an instance is terminated or restarted, on a best-effort basis. This is useful if you rely on automated scripts to start up and shut down instances, allowing instances time to clean up or perform tasks, such as exporting logs, or syncing with other systems.

Reference

https://cloud.google.com/compute/docs/shutdownscript

The Premium Tier delivers traffic over Google’s well-provisioned, low latency, highly reliable global network.

Reference

https://cloud.google.com/network-tiers/

An instance group is a collection of virtual machines (VM) instances that you can manage as a single entity. There are two types Managed and Unmanaged Instance Groups.

Reference

https://cloud.google.com/compute/docs/instance-groups

The edge proxy is commonly called an ingress controller because it is commonly configured using ingress resources in Kubernetes, however the edge proxy can also be configured with custom resource definitions (CRDs) or annotations.