Exam Professional Cloud Architect topic 3 question 3 discussion

Answer C seems to be ok. Triggering Pub/Sub to invoke Cloud Functions seems to be relevant. Cloud Storage doesn't make any sense. It would have been straight forward if Cloud Scheduler is mentioned in Option C instead of Deployment Job. But if you make a bit of research on deployment jobs, it's pointing me to cron jobs which is making perfect sense. https://cloud.google.com/appengine/docs/flexible/nodejs/scheduling-jobs-with-cron-yaml https://cloud.google.com/scheduler/docs/tut-pub-sub

Answer is A

Totally agree with C

Passed the GCP test today, answer is C The key is to use google's native tools

How is A even an option? What do you use cloud storage for? A good architecture is event driven, as it would be more resilient to failures, change in time, error and it is easier to debung, log and scale. That is what Pub/Sub is for.

A is simple and clean compared to the other options provided.

Answer C seems to be right. There are 2 requirements here, 1. Run every time it is released on Tuesday 2. Set Airwolf to run weekly Since a new version of the predictive capability application is released every tuesday evening at 3.00 am, the deployment job would run every time its released which is every week recurring. So both the requirements above are satisfied

Should be C. Cannot be A, to schedule cloud task you need to know when the deployment is complete, deployments usually are unpredictable and do not meet scheduled time. With option C, CICD pipeline which deploys the code and publish a message to pub/sub to trigger cloud function - better solution to trigger via http endpoint if that is an option. pub/sub is till okay.

To run Airwolf against the predictive capability application as soon as it is released every Tuesday, you should configure the deployment job to notify a Pub/Sub queue that triggers a Cloud Function.

Cloud task is supports scheduling

c fits scenario

Answer A seems correct since cloud tasks support scheduled delivery but pub/sub doesn't see https://cloud.google.com/pubsub/docs/choosing-pubsub-or-cloud-tasks

To set up Airwolf to run at a recurring weekly cadence, the correct option would be C: Configure the deployment job to notify a Pub/Sub queue that triggers a Cloud Function. To set up Airwolf to run at the desired weekly cadence, you can configure the deployment job to send a notification to a Pub/Sub queue when a new version of the predictive capability application is released. Then, you can set up a Cloud Function that is triggered by messages in the Pub/Sub queue and runs the Airwolf penetration test. This way, the Cloud Function will be triggered every time a new message is published to the queue, which will occur every Tuesday evening at 3 a.m. UTC when a new version of the application is released.

answer A does not make sense why put a cloud task and check a storage (which is never updated) for cloud function? If the release has some late the task run for nothing. Pub sub + cloud function is best practice

The correct answer is A: Set up Cloud Tasks and a Cloud Storage bucket that triggers a Cloud Function. To set up Airwolf to run at a recurring weekly cadence, you should set up Cloud Tasks and a Cloud Storage bucket that triggers a Cloud Function. Cloud Tasks is a fully managed service that allows you to schedule and execute background jobs in a scalable and reliable way. You can use Cloud Tasks to create a recurring task that runs at a specified interval (e.g., every week). When the task is triggered, it can send a message to a Cloud Storage bucket, which can then trigger a Cloud Function to run the Airwolf penetration test. Option B: Setting up a Cloud Logging sink and a Cloud Storage bucket would not allow you to schedule the task to run at a recurring weekly cadence. Option C: Configuring the deployment job to notify a Pub/Sub queue would not allow you to schedule the task to run at a recurring weekly cadence. Option D: Setting up Identity and Access Management (IAM) and Confidential Computing would not allow you to schedule the task to run at a recurring weekly cadence.

C Is the Correct Answer

I vote on A cloud task can trigger CF ... with limit to 30 days - here it is weekly - so far so good however not sure why it would need any cloud storage .. potentially to store results of dony by CF answer C - has no schedule option example: https://cloud.google.com/tasks/docs/tutorial-gcf