Google Cloud Certified – Professional Cloud Architect – Practice Exam (Question 57)
Your company’s test suite is a custom C++ application that runs tests throughout each day on Linux virtual machines.
The full test suite takes several hours to complete, running on a limited number of on-premises servers reserved for testing. Your company wants to move the testing infrastructure to the cloud, to reduce the amount of time it takes to fully test a change to the system, while changing the tests as little as possible.
Which cloud infrastructure should you recommend?
- A. Google Compute Engine unmanaged instance groups and Network Load Balancer
- B. Google Compute Engine managed instance groups with auto-scaling
- C. Google Cloud Dataproc to run Apache Hadoop jobs to process each test
- D. Google App Engine with Google StackDriver for logging
Correct Answer: B
Google Compute Engine enables users to launch virtual machines (VMs) on demand. VMs can be launched from the standard images or custom images created by users.
Managed instance groups offer auto scaling capabilities that allow you to automatically add or remove instances from a managed instance group based on increases or decreases in load. Autoscaling helps your applications gracefully handle increases in traffic and reduces cost when the need for resources is lower.
B: There is no mention of incoming IP data traffic for the custom C++ applications.
C: Apache Hadoop is not fit for testing C++ applications. Apache Hadoop is an open-source software framework used for distributed storage and processing of datasets of big data using the MapReduce programming model.
D: Google App Engine is intended to be used for web applications.
Google App Engine (often referred to as GAE or simply Google App Engine) is a web framework and cloud computing platform for developing and hosting web applications in Google-managed data centers.
– Autoscaling groups of instances | Compute Engine Documentation
A lead software engineer tells you that his new application design uses websockets and HTTP sessions that are not distributed across the web servers.
You want to help him ensure his application will run properly on Google Cloud Platform.
What should you do?
- A. Help the engineer to convert his websocket code to use HTTP streaming.
- B. Review the encryption requirements for websocket connections with the security team.
- C. Meet with the cloud operations team and the engineer to discuss load balancer options.
- D. Help the engineer redesign the application to use a distributed user session service that does not rely on websockets and HTTP sessions.
Correct Answer: C
Google Cloud Platform HTTP(S) load balancing provides global load balancing for HTTP(S) requests destined for your instances.
The HTTP(S) load balancer has native support for the WebSocket protocol.
A: HTTP server push, also known as HTTP streaming, is a client-server communication pattern that sends information from an HTTP server to a client asynchronously, without a client request. A server push architecture is especially effective for highly interactive web or mobile applications, where one or more clients need to receive continuous information from the server.
– External HTTP(S) Load Balancing overview
The application reliability team at your company added a debug feature to their backend service to send all server events to Google Cloud Storage for eventual analysis. The event records are at least 50 KB and at most 15 MB and are expected to peak at 3,000 events per second. You want to minimize data loss.
Which process should you implement?
- A. Append metadata to the file body. Compress individual files. Name files with serverName Timestamp. Create a new bucket if the bucket is older than 1 hour and save individual files to the new bucket. Otherwise, save files to the existing bucket.
- B. Batch every 10,000 events with a single manifest file for metadata. Compress event files and manifest files into a single archive file. Name files using serverName EventSequence. Create a new bucket if the bucket is older than 1 day and save the single archive file to the new bucket. Otherwise, save the single archive file to the existing bucket.
- C. Compress individual files. Name files with serverName EventSequence. Save files to one bucket. Set custom metadata headers for each object after saving.
- D. Append metadata to file body. Compress individual files. Name files with a random prefix pattern. Save files to one bucket.