Knowledge Check - Compute and Elasticity

Test your understanding of the key concepts from Module 4. Select the best answer for each question, then submit to see your results. You need to score at least 60% to pass.

1.

FinCorp's internal reporting tool runs on Linux in the non-production contract. It needs little CPU today, but its RAM need will grow over the next year as more reports are added, and the team wants to grow it without a migration. A team member proposes Cubes because they can attach Block Storage. What should the architect recommend?

2.

FinCorp's portal servers in Frankfurt boot from a private golden image with cloud-init user data. The recovery VDC in Berlin must be able to provision identical servers. Which approach works?

3.

FinCorp's staging portal runs as a VM Auto Scaling group behind an ALB. The scale-in and scale-out thresholds are 25% and 70% CPU, the range is 120 seconds, and the cooldown is 2 minutes. New replicas need about 6 minutes to boot, run cloud-init and pass the ALB health check, and the group keeps adding and removing replicas. What is the best fix?

4.

The FinCorp team updated the replica configuration of the staging auto scaling group with a new image and more RAM. A week later, the running replicas still use the old image. How should the architect roll out the change?

5.

FinCorp's core-banking systems run on VMware. The operations team must keep its vSphere tooling, the risk office requires single-tenant hardware in Germany, the migration must complete within one quarter, and storage is growing faster than compute. Which design should the architect recommend?