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.

Practice

1. Why is messaging important in cloud systems like Google Cloud Pub/Sub?

easy

A. It stores large files permanently.

B. It speeds up the internet connection.

C. It replaces the need for databases.

D. It allows different parts of a system to communicate reliably.

Solution

1. Step 1: Understand messaging role in cloud systems

   Messaging enables components to send and receive information without direct connection, ensuring reliable communication.

2. Step 2: Identify the correct purpose of messaging

   Messaging is not about speeding internet, storing files, or replacing databases but about reliable communication.

3. Final Answer:

   It allows different parts of a system to communicate reliably. -> Option D

4. Quick Check:

   Messaging = Reliable communication [OK]

Hint: Messaging means reliable communication between system parts [OK]

Common Mistakes:

• Confusing messaging with file storage
• Thinking messaging speeds up internet
• Assuming messaging replaces databases

2. Which of the following is the correct way to create a Pub/Sub topic using gcloud CLI?

easy

A. gcloud pubsub topics create my-topic

B. gcloud create pubsub topic my-topic

C. gcloud pubsub create topic my-topic

D. gcloud topic pubsub create my-topic

Solution

1. Step 1: Recall gcloud Pub/Sub topic creation syntax

   The correct command is 'gcloud pubsub topics create [TOPIC_NAME]'.

2. Step 2: Match the command to options

   Only gcloud pubsub topics create my-topic matches the correct syntax exactly.

3. Final Answer:

   gcloud pubsub topics create my-topic -> Option A

4. Quick Check:

   Correct gcloud topic creation command = gcloud pubsub topics create my-topic [OK]

Hint: Remember: 'gcloud pubsub topics create' is the syntax [OK]

Common Mistakes:

• Mixing order of words in command
• Using 'create pubsub topic' instead of 'pubsub topics create'
• Omitting 'topics' keyword

3. Given this Pub/Sub setup code snippet, what will be the output if a message is published successfully?

from google.cloud import pubsub_v1
publisher = pubsub_v1.PublisherClient()
topic_path = publisher.topic_path('my-project', 'my-topic')
future = publisher.publish(topic_path, b'Hello World')
print(future.result())

medium

A. The message ID string confirming successful publish

B. An error message about missing credentials

C. None, because publish is asynchronous

D. The content of the message 'Hello World'

Solution

1. Step 1: Understand publish method behavior

   The publish method returns a future that resolves to a message ID string when successful.

2. Step 2: Analyze the print statement

   Calling future.result() waits for completion and returns the message ID, not the message content.

3. Final Answer:

   The message ID string confirming successful publish -> Option A

4. Quick Check:

   future.result() returns message ID [OK]

Hint: future.result() returns message ID, not message content [OK]

Common Mistakes:

• Thinking publish returns message content
• Assuming publish is fully synchronous without future
• Confusing error output with success

4. You wrote this code to subscribe to a Pub/Sub topic but get no messages:

from google.cloud import pubsub_v1
subscriber = pubsub_v1.SubscriberClient()
subscription_path = subscriber.subscription_path('my-project', 'my-subscription')
def callback(message):
    print(f'Received: {message.data}')
    message.ack()
subscriber.subscribe(subscription_path, callback=callback)

What is the likely problem?

medium

A. The subscriber client is not initialized correctly.

B. The callback function is missing the message.ack() call.

C. The subscription does not exist or is not attached to the topic.

D. The topic name is incorrect in the subscription path.

Solution

1. Step 1: Check subscription existence and linkage

   If the subscription does not exist or is not linked to the topic, no messages will be received.

2. Step 2: Verify other code parts

   The callback acknowledges messages correctly, subscriber client is initialized properly, and subscription path uses correct subscription name.

3. Final Answer:

   The subscription does not exist or is not attached to the topic. -> Option C

4. Quick Check:

   Missing or unlinked subscription = no messages [OK]

Hint: Check subscription exists and links to topic first [OK]

Common Mistakes:

• Forgetting to create subscription before subscribing
• Assuming callback runs without subscription
• Mixing topic and subscription names

5. You want to build a system where multiple services process messages independently but reliably from the same stream of events. Which Pub/Sub feature best supports this?

hard

A. Use Cloud Storage instead of Pub/Sub for message sharing.

B. Create multiple subscriptions on the same topic for each service.

C. Publish messages to different topics for each service.

D. Use a single subscription and share it among all services.

Solution

1. Step 1: Understand message delivery to multiple consumers

   Pub/Sub allows multiple subscriptions on one topic, so each service can get all messages independently.

2. Step 2: Evaluate options for independent processing

   Sharing one subscription means messages are load balanced, not duplicated; publishing to different topics duplicates effort; Cloud Storage is not for messaging.

3. Final Answer:

   Create multiple subscriptions on the same topic for each service. -> Option B

4. Quick Check:

   Multiple subscriptions = independent reliable processing [OK]

Hint: Use multiple subscriptions on one topic for independent consumers [OK]

Common Mistakes:

• Using one subscription shared by all services
• Publishing to separate topics unnecessarily
• Confusing storage with messaging service