Question-14: Companies that want to improve the speed and reliability of the solutions they offer within their digital business should move their software development efforts further to the right into I and O teams by adopting the tenants of Site Reliability Engineering. This will allow the companies to better serve their customers (SRE). The Site Reliability Engineering (SRE) paradigm was first established at Google to assist the company in operating the google.com website in a manner that was scalable, fluid, and reliable. Fundamentally, what occurs when you ask a software engineer to build an operations function, is how the term software reliability engineering (SRE) is defined. An SRE team will conduct an analysis of business services to identify the real necessary dependability of those services (hint: it is seldom ever 100%), and based on that analysis, they will describe the operational strategy including the deployment frequency. This often creates a delicate balancing act between improving the software deployment pace and keeping the appropriate level of dependability in order to provide new features to consumers as quickly as possible. You need to offer dependable task scheduling for compute on Google Cloud Platform in order to guarantee the dependability of both your application and your operations. Using Google's recommended procedures, what actions should you take?
A. Messages can be published directly to a message-processing utility service running on Compute Engine instances by utilising the Cron service that is made available by App Engine.
B. Using the Cron service provided by App Engine, publish messages to a Cloud Pub/Sub topic. Subscribe to that topic using a message-processing utility service running on Compute Engine instances.
C. You can publish messages directly to a message-processing utility service that is running on Google Compute Engine instances by utilising the Cron service that is made available by Google Kubernetes Engine (GKE).
D. Publish messages to a Cloud Pub/Sub topic by utilising the Cron service that is made available by GKE. You can sign up for updates about this topic through the use of a message-processing utility service that is hosted on Google Compute Engine instances.
Correct Answer
Get All 340 Questions and Answer for Google Professional Cloud Architect
: 2 Explanation: Cron is the programme that is pre-installed on all Unix-based computers and is used to schedule tasks that run at predetermined intervals. When the systems that you design get more complicated and distributed, it is conceivable for a single computer that is running cron to become a critical point of failure. This is because of the distributed nature of the systems. It is conceivable that autoscaling will result in the instance being terminated, or its network segment may get separated from the systems it needs to interface with. Both of these outcomes are feasible. With the assistance of Cloud Scheduler, an enterprise-grade solution that is in its entirety managed, you are able to schedule events. Following the scheduling of a job, Cloud Scheduler will initiate communication with the event handlers that were previously configured. App Engine services, HTTP endpoints, or Pub/Sub subscriptions might be used as event handlers in this context. If you wish to have tasks carried out on your Compute Engine instance in response to events that are created by Cloud Scheduler, you will need to make sure that the events are sent to your Compute Engine instances. One of the ways in which you may achieve this objective is by making a call to an HTTP endpoint that is hosted on one of your Compute Engine instances. You also have the option of using Pub/Sub to send messages from Cloud Scheduler to the instances of Compute Engine that you manage. This is one of the options that are available to you. The second design pattern is shown here as an illustration for its use. Option 2 and option 4 are both viable approaches to putting this proposal into action. Option 1: Using Google's App Engine; Option 2: Using Google's Container Engine They ask for best practises, and it is common knowledge that using Google's Container Engine (also known as containers) is the best practise for constructing a contemporary infrastructure solution. On the card was another question that was difficult for PCA. In all honesty, I believe there is room for a significant improvement in the overall quality of the questions. If all you need is cron scheduling, then GKE is too pricey for what you need. You are able to plan events with the help of Cloud Scheduler, which is an enterprise-grade service that is entirely managed. After a task has been scheduled, Cloud Scheduler will contact the event handlers that have been set. These event handlers may be App Engine services, HTTP endpoints, or Pub/Sub subscriptions.