AIncorrect
Keep maintaining only on-premises.
Keeping only on-premises means the migration to AWS does not progress at all.
It does not meet the goal of migrating gradually, so it is incorrect.
A company with a large on-premises environment wants to avoid the risk of migrating everything at once and instead move systems to AWS gradually, using on-premises and AWS together until the migration is complete. Which deployment model is suitable for this period?
1 / 1
Select an answer
CorrectD
Explanation
A question asking for the deployment model suited to the period of a gradual cloud migration.
- 1「move systems to AWS gradually」Migrate gradually, not all at once.
- 2「until the migration is complete」A limited period during the migration.
- 3「using on-premises and AWS together」Connecting and coexisting both = hybrid.
BIncorrect
Migrate all systems to AWS at once immediately.
A big-bang migration is exactly the high-risk approach this question wants to avoid.
It conflicts with the requirement to migrate gradually, so it is incorrect.
CIncorrect
Distribute across multiple cloud providers at the same time.
Multi-cloud is a configuration that uses multiple cloud providers at the same time, such as AWS, Microsoft Azure, and Google Cloud, to avoid dependence on a single vendor (vendor lock-in) and improve availability.
This question is about migrating gradually while using on-premises and AWS together, not about adding more providers, so it is incorrect.
DCorrect
Migrate gradually with a hybrid cloud.
Correct. During the migration period, the practical approach is a hybrid configuration that connects on-premises and AWS and moves systems to AWS gradually. You can migrate step by step while limiting risk, and shift to all-in cloud after the migration is complete.
Key Takeaway
During a gradual migration, the hybrid cloud is the practical answer. A big-bang migration is high-risk, and keeping only on-premises stalls the migration. Shifting to all-in after the migration is the standard flow.