AZ-204 Risk Assessment & Management 5

Question 1

You are designing an Azure solution where multiple microservices share a single Azure SQL database. What risk does this architecture introduce and what is the recommended mitigation?

Accepted Answer

Schema coupling and shared fate risk; mitigate by giving each service its own schema or database

Answer

Sharing a database couples microservices through the schema, and a bad migration or load spike from one service can impact all others; separate schemas or databases enforce service boundaries.

Question 2

A security audit finds that your Azure Container Registry allows anonymous pull access. What is the immediate risk and correct remediation?

Accepted Answer

Risk: unauthorized access to proprietary container images; remediation: disable anonymous pull and enforce Entra ID authentication

Answer

Anonymous pull allows any unauthenticated user on the internet to pull your container images, exposing proprietary code; disabling it and requiring Entra ID authentication prevents unauthorized access.

Question 3

When using Azure Application Insights to assess application health risk, which metric best indicates that the application is approaching a memory exhaustion condition?

Accepted Answer

Process private bytes / performanceCounters/processPrivateBytes

Answer

The performanceCounters/processPrivateBytes metric tracks the private memory allocated to the process, and a steadily increasing trend indicates a potential memory leak.

Question 4

Your organization requires that all Azure resource deployments adhere to approved configurations (e.g., no public IP addresses on VMs). Which Azure service enforces this policy risk control continuously?

Accepted Answer

Azure Policy with Deny and DeployIfNotExists effects

Answer

Azure Policy continuously evaluates resources against defined rules; the Deny effect prevents non-compliant deployments and DeployIfNotExists can auto-remediate missing configurations.

Question 5

A Cosmos DB container uses the default indexing policy. What risk does this introduce for a write-heavy workload?

Accepted Answer

Higher RU consumption per write because all properties are indexed by default

Answer

The default Cosmos DB indexing policy indexes all properties, consuming additional RU/s on every write operation; for write-heavy workloads, a custom policy excluding unnecessary paths reduces this cost and latency risk.

AZ-204 - Microsoft Azure Developer Associate Practice Test

AZ-204 - Microsoft Azure Developer Associate Practice Test

AZ-204 Risk Assessment & Management 5