Question 340
A team confuses containers with fully independent VMs when planning an API service. The infrastructure decision is at its first architecture-review gate before production deployment. What should the team verify FIRST before committing to a solution?
Explanation
Correct Answer
The required decision is check isolation, OS requirements, deployment unit and orchestration scale. It addresses this operating condition: a team confuses containers with fully independent VMs when planning an API service.
Incorrect Answers
“Verify active users, dependent integrations, legal retention and ownership” concerns retire redundant application. It does not address the stated condition (a team confuses containers with fully independent VMs when planning an API service. The infrastructure decision is at its first architecture-review gate before production deployment); the closer match is check isolation, OS requirements, deployment unit and orchestration scale.
“Inventory VM dependencies, unsupported components, latency needs and migration window” concerns lift and shift legacy app. It does not address the stated condition (a team confuses containers with fully independent VMs when planning an API service. The infrastructure decision is at its first architecture-review gate before production deployment); the closer match is check isolation, OS requirements, deployment unit and orchestration scale.
“Map coupling, release bottlenecks and data consistency dependencies” concerns refactor monolith for release cycles. It does not address the stated condition (a team confuses containers with fully independent VMs when planning an API service. The infrastructure decision is at its first architecture-review gate before production deployment); the closer match is check isolation, OS requirements, deployment unit and orchestration scale.