Why messaging matters in GCP - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use messaging services in cloud applications?

Imagine you have multiple parts of an app that need to talk to each other but work independently. Why is using a messaging service like Google Cloud Pub/Sub helpful?

A It forces all parts to run at the same speed and wait for each other to finish tasks.

B It allows parts to send messages without waiting for a reply, helping them work independently and handle traffic spikes.

C It stores all data permanently like a database for later use.

D It only works if all parts are running on the same machine.

💡 Hint

Think about how apps can keep working smoothly even if one part is slow or busy.

Messaging services let different parts of an app send messages without waiting for immediate responses. This helps apps stay responsive and handle changes in traffic.

❓ service_behavior

intermediate

What happens if a subscriber fails to acknowledge a message in Pub/Sub?

In Google Cloud Pub/Sub, if a subscriber receives a message but does not acknowledge it, what will happen?

A The subscriber will be blocked from receiving any more messages.

B The message will be deleted immediately and lost forever.

C The message will be sent to all other subscribers automatically.

D The message will be redelivered after the acknowledgement deadline expires.

💡 Hint

Think about how Pub/Sub ensures messages are processed at least once.

If a message is not acknowledged, Pub/Sub assumes it was not processed and will redeliver it after the deadline to ensure it is handled.

❓ Architecture

advanced

Designing a scalable event-driven system with Pub/Sub

You want to build a system where many sensors send data to a cloud app that processes data in real-time and stores results. Which architecture best uses Pub/Sub to handle this?

A Sensors publish messages to a Pub/Sub topic; multiple processing services subscribe and process messages independently; results are stored in a database.

B Sensors write data directly to the database; processing services read from the database and update results.

C Sensors send data to a single processing service that then publishes to Pub/Sub for storage.

D Sensors send data to a message queue that only one service reads sequentially before storing.

💡 Hint

Think about how to handle many messages and scale processing easily.

Using Pub/Sub topics allows many sensors to send data asynchronously. Multiple subscribers can process data in parallel, improving scalability and reliability.

❓ security

advanced

Securing Pub/Sub topics and subscriptions

Which practice best secures access to Pub/Sub topics and subscriptions in Google Cloud?

A Store credentials in code and share them with all team members.

B Make all topics and subscriptions public so anyone can publish or subscribe.

C Use IAM roles to grant least privilege access to only needed users and services.

D Disable authentication to simplify access during development.

💡 Hint

Think about controlling who can do what with your messaging resources.

Using IAM roles with least privilege ensures only authorized users and services can publish or subscribe, protecting data and system integrity.

✅ Best Practice

expert

Handling message ordering in Pub/Sub for critical workflows

You have a workflow where message order matters, but Pub/Sub does not guarantee order by default. What is the best way to ensure messages are processed in order?

A Use Pub/Sub message ordering keys and ensure subscribers process messages with the same key sequentially.

B Use multiple topics for each message type and process them in parallel without ordering.

C Publish all messages to the same topic without ordering keys and rely on subscriber speed.

D Ignore ordering and handle it later in the database after processing.

💡 Hint

Pub/Sub supports ordering keys to group messages that must be processed in order.

Ordering keys let Pub/Sub deliver messages with the same key in order. Subscribers must process them sequentially to maintain order.