Google Associate Cloud Engineer Google Cloud Certified – Associate Cloud Engineer Online Training
Google Associate Cloud Engineer Online Training
The questions for Associate Cloud Engineer were last updated at Nov 23,2024.
- Exam Code: Associate Cloud Engineer
- Exam Name: Google Cloud Certified – Associate Cloud Engineer
- Certification Provider: Google
- Latest update: Nov 23,2024
You want to run a single caching HTTP reverse proxy on GCP for a latency-sensitive website. This specific reverse proxy consumes almost no CPU. You want to have a 30-GB in-memory cache, and need an additional 2 GB of memory for the rest of the processes. You want to minimize cost.
How should you run this reverse proxy?
- A . Create a Cloud Memorystore for Redis instance with 32-GB capacity.
- B . Run it on Compute Engine, and choose a custom instance type with 6 vCPUs and 32 GB of memory.
- C . Package it in a container image, and run it on Kubernetes Engine, using n1-standard-32 instances as nodes.
- D . Run it on Compute Engine, choose the instance type n1-standard-1, and add an SSD persistent disk of 32 GB.
You want to run a single caching HTTP reverse proxy on GCP for a latency-sensitive website. This specific reverse proxy consumes almost no CPU. You want to have a 30-GB in-memory cache, and need an additional 2 GB of memory for the rest of the processes. You want to minimize cost.
How should you run this reverse proxy?
- A . Create a Cloud Memorystore for Redis instance with 32-GB capacity.
- B . Run it on Compute Engine, and choose a custom instance type with 6 vCPUs and 32 GB of memory.
- C . Package it in a container image, and run it on Kubernetes Engine, using n1-standard-32 instances as nodes.
- D . Run it on Compute Engine, choose the instance type n1-standard-1, and add an SSD persistent disk of 32 GB.
You want to run a single caching HTTP reverse proxy on GCP for a latency-sensitive website. This specific reverse proxy consumes almost no CPU. You want to have a 30-GB in-memory cache, and need an additional 2 GB of memory for the rest of the processes. You want to minimize cost.
How should you run this reverse proxy?
- A . Create a Cloud Memorystore for Redis instance with 32-GB capacity.
- B . Run it on Compute Engine, and choose a custom instance type with 6 vCPUs and 32 GB of memory.
- C . Package it in a container image, and run it on Kubernetes Engine, using n1-standard-32 instances as nodes.
- D . Run it on Compute Engine, choose the instance type n1-standard-1, and add an SSD persistent disk of 32 GB.
You want to run a single caching HTTP reverse proxy on GCP for a latency-sensitive website. This specific reverse proxy consumes almost no CPU. You want to have a 30-GB in-memory cache, and need an additional 2 GB of memory for the rest of the processes. You want to minimize cost.
How should you run this reverse proxy?
- A . Create a Cloud Memorystore for Redis instance with 32-GB capacity.
- B . Run it on Compute Engine, and choose a custom instance type with 6 vCPUs and 32 GB of memory.
- C . Package it in a container image, and run it on Kubernetes Engine, using n1-standard-32 instances as nodes.
- D . Run it on Compute Engine, choose the instance type n1-standard-1, and add an SSD persistent disk of 32 GB.
You want to run a single caching HTTP reverse proxy on GCP for a latency-sensitive website. This specific reverse proxy consumes almost no CPU. You want to have a 30-GB in-memory cache, and need an additional 2 GB of memory for the rest of the processes. You want to minimize cost.
How should you run this reverse proxy?
- A . Create a Cloud Memorystore for Redis instance with 32-GB capacity.
- B . Run it on Compute Engine, and choose a custom instance type with 6 vCPUs and 32 GB of memory.
- C . Package it in a container image, and run it on Kubernetes Engine, using n1-standard-32 instances as nodes.
- D . Run it on Compute Engine, choose the instance type n1-standard-1, and add an SSD persistent disk of 32 GB.
You want to run a single caching HTTP reverse proxy on GCP for a latency-sensitive website. This specific reverse proxy consumes almost no CPU. You want to have a 30-GB in-memory cache, and need an additional 2 GB of memory for the rest of the processes. You want to minimize cost.
How should you run this reverse proxy?
- A . Create a Cloud Memorystore for Redis instance with 32-GB capacity.
- B . Run it on Compute Engine, and choose a custom instance type with 6 vCPUs and 32 GB of memory.
- C . Package it in a container image, and run it on Kubernetes Engine, using n1-standard-32 instances as nodes.
- D . Run it on Compute Engine, choose the instance type n1-standard-1, and add an SSD persistent disk of 32 GB.
In your on-premises network, configure your DNS server to resolve *.googleapis.com as a CNAME to restricted.googleapis.com.
In your on-premises network, configure your DNS server to resolve *.googleapis.com as a CNAME to restricted.googleapis.com.
In your on-premises network, configure your DNS server to resolve *.googleapis.com as a CNAME to restricted.googleapis.com.
In your on-premises network, configure your DNS server to resolve *.googleapis.com as a CNAME to restricted.googleapis.com.