Q: 8
Your Coustomer's Organization has decided to move to the cloud. They currently run VMs on- promise but their goal on Google cloud is to run containers, primarily on Google Kuber-nete's Engine. They have a lease for their private data center for another year that they have already paid for. What could be strategy they could adopt in migrating?
Options
Discussion
B makes the most sense. Since they're not under pressure to move right away, they can refactor the VMs into containers on-prem first and then migrate. Pretty sure "Improve and Move" is about modernizing before moving to GKE, agree?
Its B
Likely B: Had something like this in a mock, and "Improve and Move" is all about using your remaining time on-prem to update VMs into containers before heading to GKE. Since the org already paid for the datacenter, no rush, just modernize locally then shift. Pretty sure that's the idea but open to other takes.
Why do Google always give these cheesy migration names? Realistically, with a year left on the datacenter lease, wouldn't you want to modernize your stuff on-prem first rather than just tossing everything straight into GKE? Or is there some use case where you'd still go for C or D here?
B tbh
Makes sense to use B here.
Yeah B is the one. Since they've got the datacenter lease covered for another year, they can take their time to modernize VMs to containers on-prem first, then move later. Less pressure and lets them improve before migrating. Pretty sure that's what "Improve and Move" is aiming for here.
B
Probably D, not B.
Be respectful. No spam.