Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Cisco Exam 300-910 Topic 2 Question 69 Discussion

Actual exam question for Cisco's 300-910 exam
Question #: 69
Topic #: 2
[All 300-910 Questions]

A team must roll out updates on the production instance of an application. To avoid any service down time, the new version must be released alongside the old version. After the team ensures that the new version operates as it should, traffic will be redirected to the new version. Then the old version will be shut down.

Which deployment strategy must be used?

Show Suggested Answer Hide Answer
Suggested Answer: B

The new version of the application is deployed to one of the environments, and then traffic is gradually shifted to the updated environment. This strategy allows the team to test the new version before releasing it to the public, ensuring that it is operating as expected. After the new version is tested and approved, traffic is fully shifted to the new environment and the old environment is shut down.


Contribute your Thoughts:

William
4 months ago
That's true, but blue/green deployment is more commonly used for this type of situation.
upvoted 0 times
...
Katheryn
4 months ago
But canary deployment could also work, right? It allows for a gradual rollout to a subset of users.
upvoted 0 times
...
Cassi
4 months ago
I agree with William. Blue/green deployment is the most suitable for this scenario.
upvoted 0 times
...
William
4 months ago
I think the answer is blue/green deployment because it allows for zero downtime.
upvoted 0 times
...
Judy
5 months ago
I believe the shadow deployment strategy could also be considered, as it allows testing in a production-like environment without impacting users.
upvoted 0 times
...
Shoshana
5 months ago
I agree with Tegan. Using the blue/green deployment strategy ensures zero downtime during the release.
upvoted 0 times
...
Tegan
5 months ago
I think the deployment strategy that must be used is blue/green.
upvoted 0 times
...
Daisy
6 months ago
Rolling deployment does sound like the way to go. That way we can gradually roll out the new version and easily roll back if we run into any issues. Plus, it's a pretty standard approach for this kind of scenario.
upvoted 0 times
Berry
5 months ago
Rolling deployment does sound like the way to go. That way we can gradually roll out the new version and easily roll back if we run into any issues. Plus, it's a pretty standard approach for this kind of scenario.
upvoted 0 times
...
Ernest
5 months ago
D) canary
upvoted 0 times
...
Kaitlyn
5 months ago
C) shadow
upvoted 0 times
...
Ahmad
5 months ago
B) blue/green
upvoted 0 times
...
Veronika
5 months ago
A) rolling
upvoted 0 times
...
...
Sarah
6 months ago
Hmm, I'm not sure about the canary approach. That's usually more for testing new features with a small subset of users, not a full version migration. I'm leaning more towards the rolling deployment.
upvoted 0 times
...
Ilene
6 months ago
Yeah, I agree. Blue/green is out. I'm thinking either the rolling or canary strategy would work here. The key is being able to gradually shift traffic to the new version without interrupting service.
upvoted 0 times
...
Lacey
6 months ago
Oh god, Tom, don't even joke about that. Can you imagine the chaos? 'Why is my order not showing up?' 'Sorry, it's just in the shadow realm right now.'
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77