A startup company has a new feature which is used to track the customers' feedback on its main website.
On the website, there are product introductions and also customers are able to purchase the products and get them delivered.
The development team has utilized Elastic Beanstalk to deploy the new feedback system.
One developer just made a big change to the survey format and deployed the feature to a totally new Elastic Beanstalk Environment.
Then he used the “Swap URL” function to switch to the new one.
After monitoring the site for a day, by tracing the logs, the developer found that there were still few cases that old survey format was used even after about 12 hours.
Which below explanation is correct?
Click on the arrows to vote for the correct answer
A. B. C. D.Option D is Correct:
After Elastic Beanstalk completes the swap operation, users should verify that the new environment responds when they try to connect to the old environment URL.
However, do not terminate your old environment until the DNS changes have been propagated.
Besides, DNS clients exist at various levels, and not all of them obey TTL rules.
If users are dealing with mobile, particularly internationally, this is even worse.
Using DNS for blue/green deployments means the switch over will not be clean, and both sets will need to be live for a much longer period of time than they should be, costing you money.
Details please refer to.
https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features.CNAMESwap.html https://minops.com/blog/2015/02/the-dos-and-donts-of-bluegreen-deployment/Option A is incorrect:DNS TTL issue should be suspected in this case for Swap URL and if wrong code branch was deployed, there should not be just few cases that were using wrong survey formats.
Option B is incorrect:if wrong CNAME was used, all cases should be wrong however there are only few cases that were wrong.
Option C is incorrect:TTL setting may be an issue however it should affect all users.
Besides, Swap URL has modified CNAME rather than Alias record.
The issue described in the question is related to the deployment of a new feature using Elastic Beanstalk and the use of the "Swap URL" function to switch to the new environment. Despite the switch, it appears that the old survey format is still being used in some cases, even after 12 hours of monitoring.
To address the issue, we need to consider the possible causes and solutions.
Option A suggests that there may be an issue with the deployment itself, and rolling back and redeploying the environment may solve the problem. However, this option does not explain why the old survey format is still being used even after the environment has been switched.
Option B suggests that the issue may be related to Route53, which is a DNS service provided by AWS. The "Swap URL" function of Elastic Beanstalk can be used to update the DNS settings for the environment, and if the CNAME used is incorrect, it may result in some requests still being directed to the old environment. Therefore, checking and modifying the Route53 configuration may be a possible solution.
Option C is similar to Option B, but suggests that the Time To Live (TTL) settings for the website may be too high. TTL is the amount of time that a DNS record is cached by a DNS resolver. If the TTL settings are high, it may take longer for the DNS changes to propagate, and some clients may still be directed to the old environment. Therefore, modifying the TTL settings may be a possible solution.
Option D is similar to Option C, but suggests that the issue may be related to the DNS clients not complying with the TTL settings. This may happen if some DNS clients are configured to ignore TTL values or if there is a caching issue with the DNS resolver. However, this option does not explain why the old survey format is still being used in some cases.
In summary, Options B and C are the most likely explanations for the issue described in the question. Checking and modifying the Route53 configuration, including the CNAME and TTL settings, may help resolve the issue. Option A may also be worth considering if there are other issues with the deployment. Option D is less likely to be the cause of the issue, but it may still be relevant in some cases.