Question 4 — AZ-104 Case Study Set
Based on the scenario, which two changes would most directly improve Paideffort's infrastructure deployment model as the platform expands? (Select two answers)
Move service-specific resource creation into declarative ARM resources so Resource Manager can orchestrate deployment.
Divide reusable platform areas into smaller templates coordinated through a primary template as complexity increases.
Convert the remaining ARM resources into sequential CLI commands so each service can be provisioned independently.
Create an independent full infrastructure repository for every workload so components never share template definitions.
Correct answers
Move service-specific resource creation into declarative ARM resources so Resource Manager can orchestrate deployment.
Divide reusable platform areas into smaller templates coordinated through a primary template as complexity increases.
Explanations
Correct Answer:
Move service-specific resource creation into declarative ARM resources so Resource Manager can orchestrate deployment.
Divide reusable platform areas into smaller templates coordinated through a primary template as complexity increases.
Explanation:
Paideffort wants Resource Manager to coordinate resource creation and expects platform, AI, data, and tool components to become reusable. ARM deployments can orchestrate resources and create independent resources in parallel where possible. Complex templates can also be divided into smaller linked or nested components rather than maintained as one expanding deployment definition.
Wrong Answers:
Convert the remaining ARM resources into sequential CLI commands so each service can be provisioned independently.
Paideffort is trying to reduce the growing sequence of individual provisioning commands. Increasing imperative provisioning would move the design away from coordinated infrastructure as code.
Create an independent full infrastructure repository for every workload so components never share template definitions.
Paideffort specifically expects infrastructure components to be reused across workloads. Duplicating entire infrastructure definitions would increase configuration drift and maintenance overhead.