Question 620
An Azure SQL operations team investigates: An Azure SQL server is created successfully but the associated private endpoint deployment is absent. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.
Explanation
Correct Answers
The reported Azure SQL or SQL Server condition is: An Azure SQL server is created successfully but the associated private endpoint deployment is absent. The specific supported administrative response is: Provision Azure SQL database resources with version-controlled Bicep definitions and environment parameters through approved deployment pipelines. The technical risk is: Manual production configuration can drift from tested resource sizing, networking and backup settings. Confirm the correction with: A repeatable deployment produces the approved Azure SQL resource configuration and its change is reviewable.
The acceptance evidence for this incident (An Azure SQL server is created successfully but the associated private endpoint deployment is absent.) is: A repeatable deployment produces the approved Azure SQL resource configuration and its change is reviewable. It directly tests whether the remediation (Provision Azure SQL database resources with version-controlled Bicep definitions and environment parameters through approved deployment pipelines.) solves the specified issue, instead of proving an unrelated database control works.
Incorrect Answers
Azure automation SQL runbooks and managed identities (4.3) addresses another technical failure: Automation code containing embedded secrets or unsupported legacy Run As account patterns creates security and maintenance risk. This case instead tests Azure SQL resource deployment using bicep (4.2); the choice measures or changes another part of the system.
Infrastructure drift and declarative reconciliation (4.2) addresses another technical failure: Untracked manual overrides can break reproducibility and cause security configuration drift between environments. The required paired action and test concerns Azure SQL resource deployment using bicep (4.2); a passing result for this alternative could leave that requirement unresolved.
Maintaining job schedules across failover (4.1) would demonstrate or implement: A documented failover rehearsal shows required jobs exist, are correctly enabled and do not run twice on both nodes. The paired-answer requirement concerns Azure SQL resource deployment using bicep (4.2); this alternative does not provide the matching intervention and separate acceptance evidence.