According to Cloud Tasks API, when the audience field is unset, it will take the default value of the specified URI in the
HttpRequest's target. However, this could become a problem when the URI itself contains parts such as query parameters or fragments. Having these in the audience field will lead to 401.

Part of this issue lies with the APIs, but as far as documentation and examples go, we should make the audience field specific to avoid having such problems for customers who start using the product from Google provided examples.