Question 230
An architect proposes this change: Use Azure Policy allowed resource types at the governing scope rather than relying on RBAC to evaluate allowed SKU/type rules. The workload context is: Security wants to prevent unauthorized resource types but administrators mistakenly assume an RBAC Reader role enforces resource creation standards. Which evidence would most directly validate the change?
- Deploy an allowed and forbidden type under a user with legitimate Contributor permissions and compare outcomes.
- Attempt an ordinary delete and then validate documented break-glass unlock and approval path.
- Attempt to deploy a disallowed family from a new subsidiary subscription and confirm policy denial.
- Attempt deployment in allowed and forbidden regions and verify only forbidden creation is denied.
Explanation
Correct Answer
A:This observation directly verifies the intended design: Deploy an allowed and forbidden type under a user with legitimate Contributor permissions and compare outcomes. The architecture being tested is: Use Azure Policy allowed resource types at the governing scope rather than relying on RBAC to evaluate allowed SKU/type rules. The original symptom was: Contributors successfully deploy an explicitly banned category of Azure resource.
Incorrect Answers
B:That observation pertains to a separate failure: Resources are accidentally deleted by broad-scope administrators despite change-management requirements. Its cause is: RBAC grants were mistaken for irreversible deletion protection; no lock or break-glass process was applied. It does not confirm the result of this design. The direct proof would be: Deploy an allowed and forbidden type under a user with legitimate Contributor permissions and compare outcomes.
C:The alternative test targets: Assign an Azure Policy allowed VM SKUs definition at a governing management-group scope with approved parameter values. The scenario's actual proposed remedy is: Use Azure Policy allowed resource types at the governing scope rather than relying on RBAC to evaluate allowed SKU/type rules. Verify that one by: Deploy an allowed and forbidden type under a user with legitimate Contributor permissions and compare outcomes.
D:This observation directly verifies the intended design: Deploy an allowed and forbidden type under a user with legitimate Contributor permissions and compare outcomes.
Question 231
During architecture troubleshooting, a team reports: Contributors successfully deploy an explicitly banned category of Azure resource. Context: Security wants to prevent unauthorized resource types but administrators mistakenly assume an RBAC Reader role enforces resource creation standards. Which underlying design mistake explains the observed behavior most precisely?
- No effective policy controls resource creation locations for the governed subscriptions.
- Authorization to create resources was confused with governance rules restricting acceptable types.
- Central allowed-SKU policy was never inherited by the subsidiary scope.
- RBAC grants were mistaken for irreversible deletion protection; no lock or break-glass process was applied.
Explanation
Correct Answer
B:This is the failure mechanism rather than an incidental symptom: Authorization to create resources was confused with governance rules restricting acceptable types. It accounts for: Contributors successfully deploy an explicitly banned category of Azure resource. The architectural repair is: Use Azure Policy allowed resource types at the governing scope rather than relying on RBAC to evaluate allowed SKU/type rules.
Incorrect Answers
A:The alternative diagnosis “No effective policy controls resource creation locations for the governed subscriptions” does not match the observed symptom: Contributors successfully deploy an explicitly banned category of Azure resource. Context: Security wants to prevent unauthorized resource types but administrators mistakenly assume an RBAC Reader role enforces resource creation standards. This is the failure mechanism rather than an incidental symptom: Authorization to create resources was confused with governance rules restricting acceptable types. It accounts for: Contributors successfully deploy an explicitly banned category of Azure resource. The evidence instead supports “Authorization to create resources was confused with governance rules restricting acceptable types”.
C:The alternative diagnosis “Central allowed-SKU policy was never inherited by the subsidiary scope” does not match the observed symptom: Contributors successfully deploy an explicitly banned category of Azure resource. Context: Security wants to prevent unauthorized resource types but administrators mistakenly assume an RBAC Reader role enforces resource creation standards. This is the failure mechanism rather than an incidental symptom: Authorization to create resources was confused with governance rules restricting acceptable types. It accounts for: Contributors successfully deploy an explicitly banned category of Azure resource. The evidence instead supports “Authorization to create resources was confused with governance rules restricting acceptable types”.
D:The alternative diagnosis “RBAC grants were mistaken for irreversible deletion protection; no lock or break-glass process was applied” does not match the observed symptom: Contributors successfully deploy an explicitly banned category of Azure resource. Context: Security wants to prevent unauthorized resource types but administrators mistakenly assume an RBAC Reader role enforces resource creation standards. This is the failure mechanism rather than an incidental symptom: Authorization to create resources was confused with governance rules restricting acceptable types. It accounts for: Contributors successfully deploy an explicitly banned category of Azure resource. The evidence instead supports “Authorization to create resources was confused with governance rules restricting acceptable types”.
Question 232
The design change is: Use Azure Policy allowed resource types at the governing scope rather than relying on RBAC to evaluate allowed SKU/type rules. The original failure was: Contributors successfully deploy an explicitly banned category of Azure resource. Which ongoing control best prevents recurrence of the same root cause?
- Audit lock removal activity and restore lock after approved maintenance.
- Review policy parameters as region eligibility and data residency requirements change.
- Maintain approved SKU lists and subscription-placement inventory after corporate changes.
- Test policy compliance alongside RBAC after template or provider updates.
Explanation
Correct Answer
D:The preventive control is: Test policy compliance alongside RBAC after template or provider updates. It targets the earlier cause: Authorization to create resources was confused with governance rules restricting acceptable types. Confirm ongoing effectiveness by: Deploy an allowed and forbidden type under a user with legitimate Contributor permissions and compare outcomes.
Incorrect Answers
A:The alternative diagnosis “Audit lock removal activity and restore lock after approved maintenance” does not match the observed symptom: The design change is: Use Azure Policy allowed resource types at the governing scope rather than relying on RBAC to evaluate allowed SKU/type rules. The original failure was: Contributors successfully deploy an explicitly banned category of Azure resource. Which ongoing control best prevents recurrence of the same root cause?. The preventive control is: Test policy compliance alongside RBAC after template or provider updates. It targets the earlier cause: Authorization to create resources was confused with governance rules restricting acceptable types. The evidence instead supports “Test policy compliance alongside RBAC after template or provider updates”.
B:The alternative diagnosis “Review policy parameters as region eligibility and data residency requirements change” does not match the observed symptom: The design change is: Use Azure Policy allowed resource types at the governing scope rather than relying on RBAC to evaluate allowed SKU/type rules. The original failure was: Contributors successfully deploy an explicitly banned category of Azure resource. Which ongoing control best prevents recurrence of the same root cause?. The preventive control is: Test policy compliance alongside RBAC after template or provider updates. It targets the earlier cause: Authorization to create resources was confused with governance rules restricting acceptable types. The evidence instead supports “Test policy compliance alongside RBAC after template or provider updates”.
C:The alternative diagnosis “Maintain approved SKU lists and subscription-placement inventory after corporate changes” does not match the observed symptom: The design change is: Use Azure Policy allowed resource types at the governing scope rather than relying on RBAC to evaluate allowed SKU/type rules. The original failure was: Contributors successfully deploy an explicitly banned category of Azure resource. Which ongoing control best prevents recurrence of the same root cause?. The preventive control is: Test policy compliance alongside RBAC after template or provider updates. It targets the earlier cause: Authorization to create resources was confused with governance rules restricting acceptable types. The evidence instead supports “Test policy compliance alongside RBAC after template or provider updates”.
Question 233
A design workshop has this requirement: A subscription is part of a new Azure landing zone and must receive shared logging, policy and hub-spoke connectivity baselines automatically. Operators currently observe: New project subscriptions are manually provisioned without policy and logging controls. Select the ONE design remedy that best addresses the root cause.
- Design management-group hierarchy and subscription placement with clear platform versus landing-zone responsibilities.
- Use an approved subscription-vending and landing-zone deployment design with inherited policies, RBAC and network subscriptions.
- Assign appropriate Azure Policy modify policies with a managed identity to append or inherit approved tags.
- Organize subscriptions under Azure management groups and assign suitable policy at the shared ancestor scope.
Explanation
Correct Answer
B:The targeted implementation is: Use an approved subscription-vending and landing-zone deployment design with inherited policies, RBAC and network subscriptions. The problem is not generic resource availability: Subscription vending fails to apply the standard landing-zone configuration. Verify the result by: Provision a pilot subscription and verify inherited policies, diagnostic collection and baseline connectivity.
Incorrect Answers
A:The alternative diagnosis “Design management-group hierarchy and subscription placement with clear platform versus landing-zone responsibilities” does not match the observed symptom: New project subscriptions are manually provisioned without policy and logging controls. The targeted implementation is: Use an approved subscription-vending and landing-zone deployment design with inherited policies, RBAC and network subscriptions. The problem is not generic resource availability: Subscription vending fails to apply the standard landing-zone configuration. The evidence instead supports “Use an approved subscription-vending and landing-zone deployment design with inherited policies, RBAC and network subscriptions”.
C:The alternative diagnosis “Assign appropriate Azure Policy modify policies with a managed identity to append or inherit approved tags” does not match the observed symptom: New project subscriptions are manually provisioned without policy and logging controls. The targeted implementation is: Use an approved subscription-vending and landing-zone deployment design with inherited policies, RBAC and network subscriptions. The problem is not generic resource availability: Subscription vending fails to apply the standard landing-zone configuration. The evidence instead supports “Use an approved subscription-vending and landing-zone deployment design with inherited policies, RBAC and network subscriptions”.
D:The alternative diagnosis “Organize subscriptions under Azure management groups and assign suitable policy at the shared ancestor scope” does not match the observed symptom: New project subscriptions are manually provisioned without policy and logging controls. The targeted implementation is: Use an approved subscription-vending and landing-zone deployment design with inherited policies, RBAC and network subscriptions. The problem is not generic resource availability: Subscription vending fails to apply the standard landing-zone configuration. The evidence instead supports “Use an approved subscription-vending and landing-zone deployment design with inherited policies, RBAC and network subscriptions”.
Question 234
The planned architecture is: Use an approved subscription-vending and landing-zone deployment design with inherited policies, RBAC and network subscriptions. Workload context: A subscription is part of a new Azure landing zone and must receive shared logging, policy and hub-spoke connectivity baselines automatically. Which acceptance test demonstrates that the required behavior works?
- Deploy a test subscription under the branch and confirm its inherited policy is evaluated.
- Create a sandbox subscription and confirm it cannot inherit production-only RBAC while receiving universal governance policies.
- Deploy a new test resource and confirm the required tag values appear, including policy remediation for existing resources.
- Provision a pilot subscription and verify inherited policies, diagnostic collection and baseline connectivity.
Explanation
Correct Answer
D:The acceptance test is specific: Provision a pilot subscription and verify inherited policies, diagnostic collection and baseline connectivity. Its purpose is to establish that the proposed architecture works: Use an approved subscription-vending and landing-zone deployment design with inherited policies, RBAC and network subscriptions.
Incorrect Answers
A:That observation pertains to a separate failure: A newly created subscription bypasses enterprise restrictions because it was never attached to governance scope. Its cause is: Policy inheritance was not applied through the correct management-group hierarchy. It does not confirm the result of this design. The direct proof would be: Provision a pilot subscription and verify inherited policies, diagnostic collection and baseline connectivity.
B:The alternative test targets: Design management-group hierarchy and subscription placement with clear platform versus landing-zone responsibilities. The scenario's actual proposed remedy is: Use an approved subscription-vending and landing-zone deployment design with inherited policies, RBAC and network subscriptions. Verify that one by: Provision a pilot subscription and verify inherited policies, diagnostic collection and baseline connectivity.
C:The acceptance test is specific: Provision a pilot subscription and verify inherited policies, diagnostic collection and baseline connectivity.
Question 235
The customer states: A subscription is part of a new Azure landing zone and must receive shared logging, policy and hub-spoke connectivity baselines automatically. An incident reveals: New project subscriptions are manually provisioned without policy and logging controls. What cause best accounts for this evidence?
- Tag policy enforcement/inheritance and remediation were not implemented at the correct scope.
- Management-group segmentation and inherited role scope do not match intended trust boundaries.
- Subscription vending fails to apply the standard landing-zone configuration.
- Policy inheritance was not applied through the correct management-group hierarchy.
Explanation
Correct Answer
C:The incident is explained by: Subscription vending fails to apply the standard landing-zone configuration. The reported symptom is: New project subscriptions are manually provisioned without policy and logging controls. The corresponding design fix is: Use an approved subscription-vending and landing-zone deployment design with inherited policies, RBAC and network subscriptions.
Incorrect Answers
A:Tag policy enforcement/inheritance and remediation were not implemented at the correct scope would not address the need for subscription vending fails to apply the standard landing-zone configuration.
B:Management-group segmentation and inherited role scope do not match intended trust boundaries would not address the need for subscription vending fails to apply the standard landing-zone configuration.
D:Policy inheritance was not applied through the correct management-group hierarchy would not address the need for subscription vending fails to apply the standard landing-zone configuration.
Question 236
Workload context: A subscription is part of a new Azure landing zone and must receive shared logging, policy and hub-spoke connectivity baselines automatically. The implemented remedy is: Use an approved subscription-vending and landing-zone deployment design with inherited policies, RBAC and network subscriptions. Which ongoing practice most specifically prevents recurrence of this failure: New project subscriptions are manually provisioned without policy and logging controls.?
- Audit subscriptions without the required management-group parent after onboarding.
- Review hierarchy inheritance during subscription moves between business units.
- Continuously reconcile subscription inventory against the landing-zone baseline.
- Periodically audit untagged resources and the managed identity used for modify remediation.
Explanation
Correct Answer
C:The preventive control is: Continuously reconcile subscription inventory against the landing-zone baseline. It targets the earlier cause: Subscription vending fails to apply the standard landing-zone configuration. Confirm ongoing effectiveness by: Provision a pilot subscription and verify inherited policies, diagnostic collection and baseline connectivity.
Incorrect Answers
A:Auditing subscriptions without the required management-group parent after onboarding would not address the need for continuously reconcile subscription inventory against the landing-zone baseline.
B:Reviewing hierarchy inheritance during subscription moves between business units would not address the need for continuously reconcile subscription inventory against the landing-zone baseline.
D:Periodically audit untagged resources and the managed identity used for modify remediation would not address the need for continuously reconcile subscription inventory against the landing-zone baseline.
Question 237
A solution architect is reviewing a workload: An engineering team wants reusable infrastructure deployment patterns with drift detection and declarative review rather than manual portal clicks. The observed incident is: A new environment differs materially from the documented architecture after operators click through the portal. Which architecture choice most directly removes the identified weakness?
- Combine resource CanNotDelete locks with governance workflow and scoped privileged activation for rare approved deletion.
- Use Bicep or ARM templates deployed through version-controlled pipelines and validate the correct scope for every resource.
- Use resource-group scoped Azure RBAC for application deployment and separate centrally governed network roles.
- Use Azure Advisor cost recommendations and validate workload telemetry before resizing recommended instances.
Explanation
Correct Answer
B:This option addresses the actual design defect: Manual provisioning lacks one declarative repeatable configuration source. The correction is: Use Bicep or ARM templates deployed through version-controlled pipelines and validate the correct scope for every resource. Confirm the outcome with: Run a dry-run/what-if comparison and confirm the resulting resource state matches the approved template.
Incorrect Answers
A:Combine resource CanNotDelete locks with governance workflow and scoped privileged activation for rare approved deletion would not meet the need for bicep or ARM templates deployed through version-controlled pipelines and validate the correct scope for every resource.
C:The correction is: Use Bicep or ARM templates deployed through version-controlled pipelines and validate the correct scope for every resource.
D:Using Azure Advisor cost recommendations and validating workload telemetry would not meet the need for bicep or ARM templates deployed through version-controlled pipelines and validate the correct scope for every resource.
Question 238
An architect proposes this change: Use Bicep or ARM templates deployed through version-controlled pipelines and validate the correct scope for every resource. The workload context is: An engineering team wants reusable infrastructure deployment patterns with drift detection and declarative review rather than manual portal clicks. Which evidence would most directly validate the change?
- Test application resource creation while verifying denial of unrelated subscription networking operations.
- Run a dry-run/what-if comparison and confirm the resulting resource state matches the approved template.
- Attempt an ordinary delete and then validate documented break-glass unlock and approval path.
- Review rightsizing suggestions for known low-utilization VMs and test application impact in staging.
Explanation
Correct Answer
B:This observation directly verifies the intended design: Run a dry-run/what-if comparison and confirm the resulting resource state matches the approved template. The architecture being tested is: Use Bicep or ARM templates deployed through version-controlled pipelines and validate the correct scope for every resource. The original symptom was: A new environment differs materially from the documented architecture after operators click through the portal.
Incorrect Answers
A:The alternative test targets: Use resource-group scoped Azure RBAC for application deployment and separate centrally governed network roles. The scenario's actual proposed remedy is: Use Bicep or ARM templates deployed through version-controlled pipelines and validate the correct scope for every resource. Verify that one by: Run a dry-run/what-if comparison and confirm the resulting resource state matches the approved template.
C:That observation pertains to a separate failure: Resources are accidentally deleted by broad-scope administrators despite change-management requirements. Its cause is: RBAC grants were mistaken for irreversible deletion protection; no lock or break-glass process was applied. It does not confirm the result of this design. The direct proof would be: Run a dry-run/what-if comparison and confirm the resulting resource state matches the approved template.
D:The alternative test targets: Use Azure Advisor cost recommendations and validate workload telemetry before resizing recommended instances. The scenario's actual proposed remedy is: Use Bicep or ARM templates deployed through version-controlled pipelines and validate the correct scope for every resource. Verify that one by: Run a dry-run/what-if comparison and confirm the resulting resource state matches the approved template.
Question 239
During architecture troubleshooting, a team reports: A new environment differs materially from the documented architecture after operators click through the portal. Context: An engineering team wants reusable infrastructure deployment patterns with drift detection and declarative review rather than manual portal clicks. Which underlying design mistake explains the observed behavior most precisely?
- No workload rightsizing and recommendation review process exists.
- RBAC grants were mistaken for irreversible deletion protection; no lock or break-glass process was applied.
- Manual provisioning lacks one declarative repeatable configuration source.
- Subscription-scope Contributor was used instead of segregated scoped roles.
Explanation
Correct Answer
C:This is the failure mechanism rather than an incidental symptom: Manual provisioning lacks one declarative repeatable configuration source. It accounts for: A new environment differs materially from the documented architecture after operators click through the portal. The architectural repair is: Use Bicep or ARM templates deployed through version-controlled pipelines and validate the correct scope for every resource.
Incorrect Answers
A:The alternative diagnosis “No workload rightsizing and recommendation review process exists” does not match the observed symptom: A new environment differs materially from the documented architecture after operators click through the portal. Context: An engineering team wants reusable infrastructure deployment patterns with drift detection and declarative review rather than manual portal clicks. This is the failure mechanism rather than an incidental symptom: Manual provisioning lacks one declarative repeatable configuration source. It accounts for: A new environment differs materially from the documented architecture after operators click through the portal. The evidence instead supports “Manual provisioning lacks one declarative repeatable configuration source”.
B:The alternative diagnosis “RBAC grants were mistaken for irreversible deletion protection; no lock or break-glass process was applied” does not match the observed symptom: A new environment differs materially from the documented architecture after operators click through the portal. Context: An engineering team wants reusable infrastructure deployment patterns with drift detection and declarative review rather than manual portal clicks. This is the failure mechanism rather than an incidental symptom: Manual provisioning lacks one declarative repeatable configuration source. It accounts for: A new environment differs materially from the documented architecture after operators click through the portal. The evidence instead supports “Manual provisioning lacks one declarative repeatable configuration source”.
D:The alternative diagnosis “Subscription-scope Contributor was used instead of segregated scoped roles” does not match the observed symptom: A new environment differs materially from the documented architecture after operators click through the portal. Context: An engineering team wants reusable infrastructure deployment patterns with drift detection and declarative review rather than manual portal clicks. This is the failure mechanism rather than an incidental symptom: Manual provisioning lacks one declarative repeatable configuration source. It accounts for: A new environment differs materially from the documented architecture after operators click through the portal. The evidence instead supports “Manual provisioning lacks one declarative repeatable configuration source”.
Question 240
A design review identifies: An engineering team wants reusable infrastructure deployment patterns with drift detection and declarative review rather than manual portal clicks. The failure is: A new environment differs materially from the documented architecture after operators click through the portal. Select TWO distinct decisions that together provide the immediate technical solution AND an ongoing prevention control. A verification-only step does not replace either responsibility.
- Review inherited RBAC assignments and role actions after infrastructure team changes.
- Use Bicep or ARM templates deployed through version-controlled pipelines and validate the correct scope for every resource.
- Review template changes, what-if results and deployment permissions before release.
- Combine resource CanNotDelete locks with governance workflow and scoped privileged activation for rare approved deletion.
- Use Azure Advisor cost recommendations and validate workload telemetry before resizing recommended instances.
Explanation
Correct Answers
B:This option addresses the actual design defect: Manual provisioning lacks one declarative repeatable configuration source. The correction is: Use Bicep or ARM templates deployed through version-controlled pipelines and validate the correct scope for every resource. Confirm the outcome with: Run a dry-run/what-if comparison and confirm the resulting resource state matches the approved template.
C:This is an ongoing protection specific to the fault: Review template changes, what-if results and deployment permissions before release. The recurrence risk is: Manual provisioning lacks one declarative repeatable configuration source. It should be checked using: Run a dry-run/what-if comparison and confirm the resulting resource state matches the approved template.
Incorrect Answers
A:Auditing inherited RBAC can uncover excessive access, but it does not implement repeatable infrastructure definitions or validate template drift before deployment.
D:Deletion locks and privileged-activation controls help govern destructive operations; they do not produce versioned declarative infrastructure or preflight what-if comparisons.
E:Azure Advisor helps identify optimization opportunities, not enforce the architecture specified by version-controlled Bicep/ARM deployments.
Designing Microsoft Azure Infrastructure Solutions (AZ-305) Practice Tests