Question 260
Workload context: An auditor wants temporary privileged access to modify a management-group policy assignment without permanently giving policy management rights. The implemented remedy is: Use narrowly scoped eligible PIM role activation or approved time-bound RBAC assignment at the required scope. Which ongoing practice most specifically prevents recurrence of this failure: An operator keeps permanent policy Contributor privileges after a one-time exception.?
- Audit lock removal activity and restore lock after approved maintenance.
- Review hierarchy inheritance during subscription moves between business units.
- Review eligible access and remove unused permanent management-group role assignments.
- Audit exemption expiry and justifications with the security review process.
Explanation
Correct Answer
C:The preventive control is: Review eligible access and remove unused permanent management-group role assignments. It targets the earlier cause: Standing privileged RBAC is used where just-in-time escalation meets the workflow. Confirm ongoing effectiveness by: Activate for a scheduled change and verify expiration and audit record without persistent elevated roles.
Incorrect Answers
A:Auditing lock removal activity and restoring lock after approved maintenance would not review eligible access and remove unused permanent management-group role assignments.
B:Reviewing hierarchy inheritance during subscription moves between business units would not review eligible access and remove unused permanent management-group role assignments.
D:Auditing exemption expiry and justifications with the security review process would not review eligible access and remove unused permanent management-group role assignments.
Question 261
A solution architect is reviewing a workload: A platform team wants architectural cost recommendations for oversized idle VMs, not just an invoice or monthly budget threshold. The observed incident is: Costs remain high because an oversized VM runs permanently below its needed capacity. Which architecture choice most directly removes the identified weakness?
- Create a Cost Management budget with threshold notifications at the correct subscription scope.
- Define a governed resource tagging and Cost Management cost allocation/reporting strategy with consistent department values.
- Use Azure Advisor cost recommendations and validate workload telemetry before resizing recommended instances.
- Use Bicep or ARM templates deployed through version-controlled pipelines and validate the correct scope for every resource.
Explanation
Correct Answer
C:The evidence (Costs remain high because an oversized VM runs permanently below its needed capacity.) identifies the following cause: No workload rightsizing and recommendation review process exists. The design that removes it is: Use Azure Advisor cost recommendations and validate workload telemetry before resizing recommended instances. The acceptance check is: Review rightsizing suggestions for known low-utilization VMs and test application impact in staging.
Incorrect Answers
A:Creating a Cost Management budget with threshold notifications at the correct subscription scope would not meet the need for Azure Advisor cost recommendations and validate workload telemetry.
B:Defining a governed resource tagging and Cost Management cost allocation/reporting strategy with consistent department values would not meet the need for Azure Advisor cost recommendations and validate workload telemetry.
D:Using Bicep or ARM templates deployed through version-controlled pipelines and validating the correct scope for every resource would not meet the need for Azure Advisor cost recommendations and validate workload telemetry.
Question 262
An architect proposes this change: Use Azure Advisor cost recommendations and validate workload telemetry before resizing recommended instances. The workload context is: A platform team wants architectural cost recommendations for oversized idle VMs, not just an invoice or monthly budget threshold. Which evidence would most directly validate the change?
- Review rightsizing suggestions for known low-utilization VMs and test application impact in staging.
- Raise simulated budget forecast/spend and verify email action at configured thresholds.
- Run a dry-run/what-if comparison and confirm the resulting resource state matches the approved template.
- Compare Cost Analysis departmental groupings against a tagged sample of shared resources.
Explanation
Correct Answer
A:The decisive evidence is: Review rightsizing suggestions for known low-utilization VMs and test application impact in staging. This measures the mechanism of the planned change, not an unrelated Azure service: Use Azure Advisor cost recommendations and validate workload telemetry before resizing recommended instances.
Incorrect Answers
B:This measures the mechanism of the planned change, not an unrelated Azure service: Use Azure Advisor cost recommendations and validate workload telemetry before resizing recommended instances.
C:That observation pertains to a separate failure: A new environment differs materially from the documented architecture after operators click through the portal. Its cause is: Manual provisioning lacks one declarative repeatable configuration source. It does not confirm the result of this design. The direct proof would be: Review rightsizing suggestions for known low-utilization VMs and test application impact in staging.
D:The alternative test targets: Define a governed resource tagging and Cost Management cost allocation/reporting strategy with consistent department values. The scenario's actual proposed remedy is: Use Azure Advisor cost recommendations and validate workload telemetry before resizing recommended instances. Verify that one by: Review rightsizing suggestions for known low-utilization VMs and test application impact in staging.
Question 263
During architecture troubleshooting, a team reports: Costs remain high because an oversized VM runs permanently below its needed capacity. Context: A platform team wants architectural cost recommendations for oversized idle VMs, not just an invoice or monthly budget threshold. Which underlying design mistake explains the observed behavior most precisely?
- Resource tags and allocation metadata are inconsistent or absent for shared spending.
- No budget threshold and notification workflow exists for the subscription.
- No workload rightsizing and recommendation review process exists.
- Manual provisioning lacks one declarative repeatable configuration source.
Explanation
Correct Answer
C:This is the failure mechanism rather than an incidental symptom: No workload rightsizing and recommendation review process exists. It accounts for: Costs remain high because an oversized VM runs permanently below its needed capacity. The architectural repair is: Use Azure Advisor cost recommendations and validate workload telemetry before resizing recommended instances.
Incorrect Answers
A:The alternative diagnosis “Resource tags and allocation metadata are inconsistent or absent for shared spending” does not match the observed symptom: Costs remain high because an oversized VM runs permanently below its needed capacity. Context: A platform team wants architectural cost recommendations for oversized idle VMs, not just an invoice or monthly budget threshold. This is the failure mechanism rather than an incidental symptom: No workload rightsizing and recommendation review process exists. It accounts for: Costs remain high because an oversized VM runs permanently below its needed capacity. The evidence instead supports “No workload rightsizing and recommendation review process exists”.
B:The alternative diagnosis “No budget threshold and notification workflow exists for the subscription” does not match the observed symptom: Costs remain high because an oversized VM runs permanently below its needed capacity. Context: A platform team wants architectural cost recommendations for oversized idle VMs, not just an invoice or monthly budget threshold. This is the failure mechanism rather than an incidental symptom: No workload rightsizing and recommendation review process exists. It accounts for: Costs remain high because an oversized VM runs permanently below its needed capacity. The evidence instead supports “No workload rightsizing and recommendation review process exists”.
D:The alternative diagnosis “Manual provisioning lacks one declarative repeatable configuration source” does not match the observed symptom: Costs remain high because an oversized VM runs permanently below its needed capacity. Context: A platform team wants architectural cost recommendations for oversized idle VMs, not just an invoice or monthly budget threshold. This is the failure mechanism rather than an incidental symptom: No workload rightsizing and recommendation review process exists. It accounts for: Costs remain high because an oversized VM runs permanently below its needed capacity. The evidence instead supports “No workload rightsizing and recommendation review process exists”.
Question 264
The design change is: Use Azure Advisor cost recommendations and validate workload telemetry before resizing recommended instances. The original failure was: Costs remain high because an oversized VM runs permanently below its needed capacity. Which ongoing control best prevents recurrence of the same root cause?
- Review advisor recommendations and actual performance after every major usage change.
- Audit tag completeness and update cost allocation rules as cost centers change.
- Review budget alert contacts and thresholds after contract or workload cost changes.
- Review template changes, what-if results and deployment permissions before release.
Explanation
Correct Answer
A:The key follow-up control is: Review advisor recommendations and actual performance after every major usage change. It avoids recurrence of the scenario in which: Costs remain high because an oversized VM runs permanently below its needed capacity. It addresses: No workload rightsizing and recommendation review process exists.
Incorrect Answers
B:The alternative diagnosis “Audit tag completeness and update cost allocation rules as cost centers change” does not match the observed symptom: The design change is: Use Azure Advisor cost recommendations and validate workload telemetry before resizing recommended instances. The original failure was: Costs remain high because an oversized VM runs permanently below its needed capacity. Which ongoing control best prevents recurrence of the same root cause?. The key follow-up control is: Review advisor recommendations and actual performance after every major usage change. It avoids recurrence of the scenario in which: Costs remain high because an oversized VM runs permanently below its needed capacity. The evidence instead supports “Review advisor recommendations and actual performance after every major usage change”.
C:The alternative diagnosis “Review budget alert contacts and thresholds after contract or workload cost changes” does not match the observed symptom: The design change is: Use Azure Advisor cost recommendations and validate workload telemetry before resizing recommended instances. The original failure was: Costs remain high because an oversized VM runs permanently below its needed capacity. Which ongoing control best prevents recurrence of the same root cause?. The key follow-up control is: Review advisor recommendations and actual performance after every major usage change. It avoids recurrence of the scenario in which: Costs remain high because an oversized VM runs permanently below its needed capacity. The evidence instead supports “Review advisor recommendations and actual performance after every major usage change”.
D:The alternative diagnosis “Review template changes, what-if results and deployment permissions before release” does not match the observed symptom: The design change is: Use Azure Advisor cost recommendations and validate workload telemetry before resizing recommended instances. The original failure was: Costs remain high because an oversized VM runs permanently below its needed capacity. Which ongoing control best prevents recurrence of the same root cause?. The key follow-up control is: Review advisor recommendations and actual performance after every major usage change. It avoids recurrence of the scenario in which: Costs remain high because an oversized VM runs permanently below its needed capacity. The evidence instead supports “Review advisor recommendations and actual performance after every major usage change”.
Question 265
A design workshop has this requirement: An enterprise must block deployment of public IP resources in its isolated data-subscription branch while allowing networking experts to manage approved private resources. Operators currently observe: A database subnet gains an accidental publicly reachable address after a template change. Select the ONE design remedy that best addresses the root cause.
- Assign Azure Policy allowed locations with a deny effect at the intended subscription or management-group scope.
- Design management-group hierarchy and subscription placement with clear platform versus landing-zone responsibilities.
- Assign an Azure Policy deny definition for prohibited public IP creation to the correct data management group.
- Assign an Azure Policy allowed VM SKUs definition at a governing management-group scope with approved parameter values.
Explanation
Correct Answer
C:The targeted implementation is: Assign an Azure Policy deny definition for prohibited public IP creation to the correct data management group. The problem is not generic resource availability: A management-group-scoped public IP governance restriction was not assigned or enforced. Verify the result by: Test a Public IP deployment is denied in data subscriptions while an approved private NIC succeeds.
Incorrect Answers
A:The alternative diagnosis “Assign Azure Policy allowed locations with a deny effect at the intended subscription or management-group scope” does not match the observed symptom: A database subnet gains an accidental publicly reachable address after a template change. The targeted implementation is: Assign an Azure Policy deny definition for prohibited public IP creation to the correct data management group. The problem is not generic resource availability: A management-group-scoped public IP governance restriction was not assigned or enforced. The evidence instead supports “Assign an Azure Policy deny definition for prohibited public IP creation to the correct data management group”.
B:The alternative diagnosis “Design management-group hierarchy and subscription placement with clear platform versus landing-zone responsibilities” does not match the observed symptom: A database subnet gains an accidental publicly reachable address after a template change. The targeted implementation is: Assign an Azure Policy deny definition for prohibited public IP creation to the correct data management group. The problem is not generic resource availability: A management-group-scoped public IP governance restriction was not assigned or enforced. The evidence instead supports “Assign an Azure Policy deny definition for prohibited public IP creation to the correct data management group”.
D:The alternative diagnosis “Assign an Azure Policy allowed VM SKUs definition at a governing management-group scope with approved parameter values” does not match the observed symptom: A database subnet gains an accidental publicly reachable address after a template change. The targeted implementation is: Assign an Azure Policy deny definition for prohibited public IP creation to the correct data management group. The problem is not generic resource availability: A management-group-scoped public IP governance restriction was not assigned or enforced. The evidence instead supports “Assign an Azure Policy deny definition for prohibited public IP creation to the correct data management group”.
Question 266
The planned architecture is: Assign an Azure Policy deny definition for prohibited public IP creation to the correct data management group. Workload context: An enterprise must block deployment of public IP resources in its isolated data-subscription branch while allowing networking experts to manage approved private resources. Which acceptance test demonstrates that the required behavior works?
- Attempt deployment in allowed and forbidden regions and verify only forbidden creation is denied.
- Test a Public IP deployment is denied in data subscriptions while an approved private NIC succeeds.
- Create a sandbox subscription and confirm it cannot inherit production-only RBAC while receiving universal governance policies.
- Attempt to deploy a disallowed family from a new subsidiary subscription and confirm policy denial.
Explanation
Correct Answer
B:The acceptance test is specific: Test a Public IP deployment is denied in data subscriptions while an approved private NIC succeeds. Its purpose is to establish that the proposed architecture works: Assign an Azure Policy deny definition for prohibited public IP creation to the correct data management group.
Incorrect Answers
A:Attempt deployment in allowed and forbidden regions and verify only forbidden creation is denied would not test a Public IP deployment is denied in data subscriptions while an approved private NIC succeeds.
C: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: Assign an Azure Policy deny definition for prohibited public IP creation to the correct data management group. Verify that one by: Test a Public IP deployment is denied in data subscriptions while an approved private NIC succeeds.
D:Attempt to deploy a disallowed family from a new subsidiary subscription and confirm policy denial would not test a Public IP deployment is denied in data subscriptions while an approved private NIC succeeds.
Question 267
The customer states: An enterprise must block deployment of public IP resources in its isolated data-subscription branch while allowing networking experts to manage approved private resources. An incident reveals: A database subnet gains an accidental publicly reachable address after a template change. What cause best accounts for this evidence?
- No effective policy controls resource creation locations for the governed subscriptions.
- Management-group segmentation and inherited role scope do not match intended trust boundaries.
- A management-group-scoped public IP governance restriction was not assigned or enforced.
- Central allowed-SKU policy was never inherited by the subsidiary scope.
Explanation
Correct Answer
C:The recorded behavior follows from: A management-group-scoped public IP governance restriction was not assigned or enforced. The appropriate mitigation would be: Assign an Azure Policy deny definition for prohibited public IP creation to the correct data management group. Verify with: Test a Public IP deployment is denied in data subscriptions while an approved private NIC succeeds.
Incorrect Answers
A:No effective policy controls resource creation locations for the governed subscriptions. A management-group-scoped public IP governance restriction was not assigned or enforced.
B:Management-group segmentation and inherited role scope do not match intended trust boundaries. A management-group-scoped public IP governance restriction was not assigned or enforced.
D:Central allowed-SKU policy was never inherited by the subsidiary scope. A management-group-scoped public IP governance restriction was not assigned or enforced.
Question 268
Workload context: An enterprise must block deployment of public IP resources in its isolated data-subscription branch while allowing networking experts to manage approved private resources. The implemented remedy is: Assign an Azure Policy deny definition for prohibited public IP creation to the correct data management group. Which ongoing practice most specifically prevents recurrence of this failure: A database subnet gains an accidental publicly reachable address after a template change.?
- Maintain approved SKU lists and subscription-placement inventory after corporate changes.
- Audit policy exemptions and approved connectivity patterns for data landing zones.
- Review hierarchy inheritance during subscription moves between business units.
- Review policy parameters as region eligibility and data residency requirements change.
Explanation
Correct Answer
B:This is an ongoing protection specific to the fault: Audit policy exemptions and approved connectivity patterns for data landing zones. The recurrence risk is: A management-group-scoped public IP governance restriction was not assigned or enforced. It should be checked using: Test a Public IP deployment is denied in data subscriptions while an approved private NIC succeeds.
Incorrect Answers
A:Maintaining approved SKU lists and subscription-placement inventory after corporate changes would not audit policy exemptions and approved connectivity patterns for data landing zones.
C:Reviewing hierarchy inheritance during subscription moves between business units would not audit policy exemptions and approved connectivity patterns for data landing zones.
D:Reviewing policy parameters as region eligibility and data residency requirements change would not audit policy exemptions and approved connectivity patterns for data landing zones.
Question 269
A solution architect is reviewing a workload: A company needs central evidence that new subscriptions have encryption controls and documented exceptions without granting auditors write privileges. The observed incident is: Compliance reviewers are made subscription Owners solely to view policy state. Which architecture choice most directly removes the identified weakness?
- Use Defender for Cloud regulatory compliance dashboard and appropriate standards assignments at relevant management scopes.
- Organize subscriptions under Azure management groups and assign suitable policy at the shared ancestor scope.
- Create and assign an Azure Policy initiative grouping the required definitions and parameters at appropriate scope.
- Assign governance policies and allow auditors Reader/Policy Insights access for compliance reporting at an appropriate scope.
Explanation
Correct Answer
D:The evidence (Compliance reviewers are made subscription Owners solely to view policy state.) identifies the following cause: Visibility role separation was not designed; policy reporting does not require resource ownership. The design that removes it is: Assign governance policies and allow auditors Reader/Policy Insights access for compliance reporting at an appropriate scope. The acceptance check is: Have an auditor view noncompliant resources and approved exemptions but fail to alter the policies.
Incorrect Answers
A:Using Defender for Cloud regulatory compliance dashboard and appropriate standards assignments at relevant management scopes would not assign governance policies and allow auditors Reader/Policy Insights access for compliance reporting at an appropriate scope.
B:Organizing subscriptions under Azure management groups and assigning suitable policy at the shared ancestor scope would not assign governance policies and allow auditors Reader/Policy Insights access for compliance reporting at an appropriate scope.
C:Creating and assigning an Azure Policy initiative grouping the required definitions and parameters at appropriate scope would not assign governance policies and allow auditors Reader/Policy Insights access for compliance reporting at an appropriate scope.
Question 270
An architect proposes this change: Assign governance policies and allow auditors Reader/Policy Insights access for compliance reporting at an appropriate scope. The workload context is: A company needs central evidence that new subscriptions have encryption controls and documented exceptions without granting auditors write privileges. Which evidence would most directly validate the change?
- Deploy a test subscription under the branch and confirm its inherited policy is evaluated.
- Inspect initiative compliance showing the evaluations of each included policy definition.
- Have an auditor view noncompliant resources and approved exemptions but fail to alter the policies.
- Inspect compliance controls and drill into a recommendation affecting a known subscription.
Explanation
Correct Answer
C:This observation directly verifies the intended design: Have an auditor view noncompliant resources and approved exemptions but fail to alter the policies. The architecture being tested is: Assign governance policies and allow auditors Reader/Policy Insights access for compliance reporting at an appropriate scope. The original symptom was: Compliance reviewers are made subscription Owners solely to view policy state.
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: Have an auditor view noncompliant resources and approved exemptions but fail to alter the policies.
B:The alternative test targets: Create and assign an Azure Policy initiative grouping the required definitions and parameters at appropriate scope. The scenario's actual proposed remedy is: Assign governance policies and allow auditors Reader/Policy Insights access for compliance reporting at an appropriate scope. Verify that one by: Have an auditor view noncompliant resources and approved exemptions but fail to alter the policies.
D:That observation pertains to a separate failure: Risk owners cannot correlate failing Azure resources to the applicable compliance standard. Its cause is: Security posture controls were not mapped and monitored through a common regulatory assessment view. It does not confirm the result of this design. The direct proof would be: Have an auditor view noncompliant resources and approved exemptions but fail to alter the policies.
Designing Microsoft Azure Infrastructure Solutions (AZ-305) Practice Tests