You need to ensure reliability for your application and operations by supporting reliable task scheduling for compute on GCP. Leveraging Google best practices, what should you do?
A.
Using the Cron service provided by App Engine, publish messages directly to a message-processing utility service running on Compute Engine instances.
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.
Using the Cron service provided by Google Kubernetes Engine (GKE), publish messages directly to a message-processing utility service running on Compute Engine instances.
D.
Using the Cron service provided by GKE, publish messages to a Cloud Pub/Sub topic. Subscribe to that topic using a message-processing utility service running on Compute Engine instances.
Answer is B, but this question is outdated, Today the best practices for cron is Cloud Scheduler: fully managed enterprise-grade cron job scheduler
https://cloud.google.com/scheduler/?gad_source=1&gclsrc=ds&gclsrc=ds
This seems to be an old question, despite B could be the more correct answer, it is not exactly a good one. 'Using the Cron service provided by App Engine', the cron service is provided by Cloud Scheduler, not App Engine. App Engine HTTP endpoint can be a target for the cron task.
Something feels missing/broken about this question
Even before comments in discussion that correctly mentioned Cloud Scheduler, which is not mentioned in the question
"By using Cloud Scheduler for scheduling and Pub/Sub for distributed messaging, you can build an application to reliably schedule tasks across a fleet of Compute Engine instances." https://cloud.google.com/architecture/reliable-task-scheduling-compute-engine
Answer is B. (Note: It was down to B or D but containerization was not mentioned)
Answer is B.
Cloud Scheduler provides a fully managed, enterprise-grade service that lets you schedule events. After you have scheduled a job, Cloud Scheduler will call the configured event handlers, which can be App Engine services, HTTP endpoints, or Pub/Sub subscriptions.
To run tasks on your Compute Engine instance in response to Cloud Scheduler events, you need to relay the events to those instances. One way to do this is by calling an HTTP endpoint that runs on your Compute Engine instances. Another option is to pass messages from Cloud Scheduler to your Compute Engine instances using Pub/Sub.
This solution can be implemented using both A and D
1) With App Engine - https://cloud.google.com/appengine/docs/flexible/nodejs/scheduling-jobs-with-cron-yaml
2) With GKE - https://cloud.google.com/kubernetes-engine/docs/how-to/cronjobs
They ask for best practices and it's well known that GKE (aka containers) is the best practice for building modern infra solution.
Yet another confusing PCA question on the card. Honestly, think the quality of the questions can be mightily improved.
B says Appengine.
But Cloud Scheduler is itself a managed service.
To schedule jobs via AppEngine, the cron.yaml has to be used.
It can be done similarly via GKE as well.
This question is confusing
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
JoeShmoe
Highly Voted 4 years, 11 months agoSmart
Highly Voted 4 years, 8 months agofraloca
3 years, 9 months agoxaqanik
Most Recent 9 months agoodacir
11 months, 2 weeks agoJaimeMS
4 months, 4 weeks agoJPA210
1 year agosalim_
1 year, 5 months agorr4444
1 year, 7 months agoparthkulkarni998
10 months, 2 weeks agodataqueen_3110
1 year, 9 months agobeehive
1 year, 10 months agohabros
1 year, 11 months agomegumin
1 year, 11 months agoAzureDP900
2 years agoNirca
2 years, 1 month agoSbgani
2 years, 1 month agozellck
2 years, 1 month agozr79
2 years agoFAD04
2 years, 2 months agopp0709
2 years, 2 months agoBiddlyBdoyng
2 years agopp0709
2 years, 2 months agokapara
1 year, 3 months agomedi01
1 year, 6 months ago6721sora
2 years, 2 months ago