Message ordering in GCP - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

How does Pub/Sub ensure message ordering with ordering keys?

Google Cloud Pub/Sub supports message ordering using ordering keys. Which statement best describes how Pub/Sub guarantees message order for messages with the same ordering key?

A Pub/Sub delivers messages with the same ordering key in the exact order they were published, but only if the publisher acknowledges each message before the next is sent.

B Pub/Sub delivers messages with the same ordering key in any order, but the subscriber must reorder them based on timestamps.

C Pub/Sub guarantees message order only if messages are published to a single partition without ordering keys.

D Pub/Sub does not support message ordering; ordering keys are ignored.

💡 Hint

Think about how Pub/Sub uses ordering keys and acknowledgments to maintain order.

Pub/Sub uses ordering keys to group messages. It ensures messages with the same ordering key are delivered in the order published, but only if each message is acknowledged before sending the next. This prevents out-of-order delivery.

❓ Architecture

intermediate

Designing a Pub/Sub system to preserve message order across multiple subscribers

You need to design a Pub/Sub system where multiple subscribers process messages but message order must be preserved per key. Which architecture best supports this requirement?

A Create multiple subscriptions without ordering keys; subscribers process messages independently and order is preserved automatically.

B Use a single subscription with multiple subscribers and enable ordering keys; each subscriber processes messages with different ordering keys to preserve order per key.

C Use multiple topics with one subscriber each; ordering keys are not needed because topics isolate message streams.

D Use a single subscription with multiple subscribers and disable ordering keys; rely on subscriber logic to reorder messages.

💡 Hint

Consider how ordering keys and subscriptions affect message order and parallel processing.

Using a single subscription with multiple subscribers and ordering keys allows messages with the same key to be processed in order by the subscriber handling that key. This design balances parallelism and order preservation.

❓ security

advanced

Impact of message ordering on Pub/Sub security and access control

How does enabling message ordering with ordering keys affect security and access control in Google Cloud Pub/Sub?

A Ordering keys do not affect security; access control is managed independently via IAM roles on topics and subscriptions.

B Ordering keys require additional IAM roles to be assigned to publishers to encrypt messages per key.

C Enabling ordering keys disables encryption, reducing security for ordered messages.

D Subscribers must have special permissions to reorder messages when ordering keys are enabled.

💡 Hint

Think about how IAM roles and encryption relate to message ordering features.

Ordering keys are a feature for message sequencing and do not change how security or access control is managed. IAM roles on topics and subscriptions control permissions regardless of ordering keys.

✅ Best Practice

advanced

Best practice for handling message ordering failures in Pub/Sub

If a subscriber fails to acknowledge a message with an ordering key, what is the best practice to handle message ordering to avoid blocking subsequent messages?

A Ignore the failure and continue publishing messages; Pub/Sub will reorder them automatically later.

B Disable ordering keys temporarily to allow messages to flow without blocking.

C Delete the subscription and recreate it to reset message ordering state.

D Pause publishing messages with that ordering key until the failed message is acknowledged or dead-lettered to prevent blocking.

💡 Hint

Consider how Pub/Sub handles unacknowledged messages with ordering keys.

When a message with an ordering key is not acknowledged, Pub/Sub blocks subsequent messages with the same key. Pausing publishing or using dead-letter topics helps avoid blocking and preserves order.

🧠 Conceptual

expert

Why does Pub/Sub require explicit enabling of message ordering?

Google Cloud Pub/Sub does not guarantee message ordering by default. Why must message ordering be explicitly enabled with ordering keys?

A Because message ordering is only supported for pull subscriptions, not push subscriptions.

B Because ordering keys require messages to be encrypted differently, which is not always needed.

C Because enabling ordering keys changes the internal message routing and delivery guarantees, which can impact throughput and latency.

D Because ordering keys are deprecated and only used for backward compatibility.

💡 Hint

Think about trade-offs between ordering guarantees and system performance.

Enabling ordering keys changes how Pub/Sub routes and delivers messages to maintain order, which can reduce throughput and increase latency. Therefore, it is an opt-in feature to allow users to choose based on needs.