Pub/Sub Push Subscription Message Retry: HTTP Status Code Impact

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  Create a Pub/Sub topic, then create a push subscription with the HTTPS endpoint URL

  Why this is correct

  This is the correct order because a topic must exist before a subscription can reference it, and a push subscription requires the endpoint URL at creation time.

• ✗

  Create a push subscription without an endpoint, then create the topic, then update the subscription with the endpoint

  Why it's wrong here

  This is incorrect because a subscription cannot be created without a topic, and the push endpoint must be specified when creating the subscription; it cannot be added later via update.

• ✗

  Configure the HTTPS endpoint to accept messages, then create the topic, then create the subscription

  Why it's wrong here

  This is incorrect because while the endpoint must be ready to receive messages, the topic and subscription should be created first (or in parallel). The order of endpoint setup relative to Pub/Sub resources is not strictly required, but the typical workflow creates the Pub/Sub resources first.

• ✗

  Create a topic, then create a pull subscription, then change it to a push subscription

  Why it's wrong here

  This is incorrect because a subscription's delivery type (push or pull) cannot be changed after creation. To use push delivery, you must create a push subscription directly.