PROFESSIONAL-CLOUD-ARCHITECT · Question #74
Case Study: 4 - Dress4Win case study Company Overview Dress4win is a web-based company that helps their users organize and manage their personal wardrobe using a website and mobile application. The co
The correct answer is D. Identify the number of virtual cores and RAM associated with the application server virtual. Option D is correct because Dress4Win's application servers (Tomcat, Nginx) already run on virtual machines - the case study explicitly mentions iSCSI storage for VM hosts. Since the workloads are already virtualized, the right baseline is the virtual core and RAM specs of those
Question
Options
- APerform a mapping of the on-premises physical hardware cores and RAM to the nearest machine
- BRecommend that Dress4Win deploy application servers to machine types that offer the highest
- CRecommend that Dress4Win deploy into production with the smallest instances available, monitor
- DIdentify the number of virtual cores and RAM associated with the application server virtual
How the community answered
(27 responses)- A4% (1)
- B4% (1)
- C11% (3)
- D81% (22)
Explanation
Option D is correct because Dress4Win's application servers (Tomcat, Nginx) already run on virtual machines - the case study explicitly mentions iSCSI storage for VM hosts. Since the workloads are already virtualized, the right baseline is the virtual core and RAM specs of those existing VMs, not the underlying physical hardware. You then map those virtual specs to the nearest equivalent cloud machine type for a like-for-like migration starting point.
Why the distractors fail:
- A is wrong because mapping from physical cores and RAM is inappropriate when the workloads are already abstracted into VMs - physical specs include resources shared across many VMs, making them a misleading baseline.
- B is wrong because recommending the highest-spec machines ignores cost optimization, which is a central concern for Dress4Win's CFO and investors - over-provisioning defeats the purpose of moving to cloud.
- C is wrong because starting production with the smallest instances and monitoring is an acceptable strategy for greenfield apps, but a migration requires matching existing capacity first to avoid performance regressions before you can right-size.
Memory tip: Think "start where you are." If workloads are virtualized on-prem, your migration baseline is virtual specs → cloud specs. Physical specs are only relevant when migrating bare-metal workloads.
Topics
Community Discussion
No community discussion yet for this question.