Given the following prepared query, what steps can be taken to easily redirect users to a new version of an application? (select two)
{
"Name": “hashiconf-app",
"Service": {
"Service": “conference-app",
"Tags": ["v9.10"]
}
}
A . create a new prepared query to reflect the changes required
B. update the prepared query to reflect the new build number
C. update DNS or the URL that clients use to access your application
D. register the updated service as conference-app – include the new build number of the application as a tag
Answer: B,D
Explanation:
To redirect users to a new version of the application, all you’d have to do is register the new services with the proper tag (i.e., tag = v9.11) and update the prepared query with the new build. This update to the prepared query will immediately redirect users to any healthy nodes running the conference-app that includes v9.11 as a tag when the services registered with Consul.
The best part of all, since the prepared query doesn’t need to be recreated, the DNS record, or URL that the client uses to access the application doesn’t change either. This quick change is a super simple way to quickly migrate users to newer versions of the application without requiring additional changes. https://learn.hashicorp.com/consul/developer-discovery/geo-failover#static-policy
By the way, this simple prepared query example came from my presentation at HashiConf ’19. Note that the build numbers included in this question are the dates from HashiCorp 🙂 Check it out here if interested.
Latest Consul Associate Dumps Valid Version with 171 Q&As
Latest And Valid Q&A | Instant Download | Once Fail, Full Refund