Azure Solutions Architect Expert Renewal Assessment - Comprehensive Review
Azure Solutions Architect Expert Renewal Assessment
Comprehensive Review Examination | Non-Proctored | 60 Minutes | 57% Passing Score
Scenario 1
A multinational retail company hosts its order processing system on Azure SQL Database. The system must remain available
during regional outages with a recovery point objective (RPO) of zero and a recovery time objective (RTO) of less than 30
seconds. The database is currently configured as a General Purpose tier with geo-redundant backup. The company has two
Azure regions in its deployment: East US and West Europe. Read workloads are distributed globally, and write workloads
originate from the East US region only. The existing deployment does not use any active geo-replication or failover group
configuration.
Q1: You need to recommend a high availability and disaster recovery solution that meets the RPO and RTO
requirements while minimizing configuration complexity. What should you recommend?
A. Configure active geo-replication with manual failover and use Azure Traffic Manager to route read traffic to
the secondary replica
B. Deploy a SQL Database failover group with auto-failover policy between East US and West Europe,
using the same service tier in both regions [CORRECT]
C. Enable zone-redundant deployment in East US and configure geo-redundant backups with a 7-day retention
period
D. Implement Azure Site Recovery to replicate the virtual machines hosting the SQL Server to West Europe with
a recovery plan
Correct Answer: B
Rationale: Correct because a SQL Database failover group with auto-failover policy provides an RPO of near-zero
through asynchronous replication and automatic failover meets the RTO of less than 30 seconds without manual
intervention. This matches the requirement for minimal configuration complexity since failover groups manage the
DNS listener, replication link, and failover logic as a single unit.
Q2: Which Azure Cosmos DB consistency level guarantees that reads always return the most recent committed
write and provides linearizability across all regions?
A. Bounded Staleness
B. Session
C. Strong [CORRECT]
D. Consistent Prefix
Correct Answer: C
Rationale: Correct because Strong consistency in Azure Cosmos DB provides linearizability, meaning reads are
guaranteed to return the most recent committed write across all regions. This matches the highest level of
consistency available in Cosmos DB, trading off higher latency and lower availability during partition-level failures.
Q3: You are designing an Azure Kubernetes Service (AKS) cluster for a web application that experiences
unpredictable traffic spikes. The application has a latency-sensitive API that must respond within 200
milliseconds. You need to ensure the cluster scales automatically to handle demand while minimizing costs during
low-traffic periods. Which combination of scaling strategies should you recommend?
Page 1
, Azure Solutions Architect Expert Renewal Assessment - Comprehensive Review
A. Enable the Cluster Autoscaler with a minimum of 3 nodes and a maximum of 20 nodes, and configure the
Horizontal Pod Autoscaler with a target CPU utilization of 80%
B. Configure the Vertical Pod Autoscaler to adjust resource requests dynamically and set the Cluster Autoscaler
to a fixed node count of 10
C. Deploy Azure Container Instances as a burst compute layer using virtual nodes and disable the Cluster
Autoscaler
D. Use the Kubernetes Event-driven Autoscaling (KEDA) with an Azure Service Bus queue trigger and set
the Cluster Autoscaler minimum to 1 node [CORRECT]
Correct Answer: D
Rationale: Correct because KEDA extends the Horizontal Pod Autoscaler with event-driven scaling capabilities,
allowing the application to scale based on the number of messages in the Service Bus queue rather than just CPU
metrics. This matches the requirement to handle unpredictable traffic spikes while setting the Cluster Autoscaler
minimum to 1 node minimizes costs during idle periods.
Mini-Case 1
A financial services company is refactoring a monolithic loan processing application into microservices. The current
monolith handles loan origination, credit scoring, document verification, and disbursement as a single deployable unit. The
company wants each microservice to have independent scaling, deployment, and technology choices. Services must
communicate asynchronously to prevent cascading failures. The existing infrastructure includes an Azure Service Bus
namespace with topics and subscriptions already configured for other messaging workloads. The company requires that all
inter-service communication be auditable and that failed messages be automatically retried with a dead-letter mechanism.
Q4: You need to recommend a communication pattern for the microservices architecture that meets the
company's requirements. Which approach should you recommend?
A. Use synchronous HTTP calls between services with Azure API Management as a gateway and implement retry
logic using Polly in each service
B. Implement an event-driven architecture using Azure Service Bus topics with dead-lettering enabled,
and use Azure Monitor to track all message deliveries [CORRECT]
C. Configure direct gRPC connections between microservices with circuit breaker patterns using Envoy sidecar
proxies and store audit logs in Azure Blob Storage
D. Deploy Azure Event Grid with webhook subscriptions for each microservice and use Azure Cosmos DB as a
durable message store for failed events
Correct Answer: B
Rationale: Correct because Azure Service Bus topics support publish/subscribe messaging patterns with built-in
dead-lettering, automatic retries, and message auditing through Azure Monitor integration. This matches the
requirement for asynchronous communication that prevents cascading failures, leverages the existing Service Bus
namespace, and provides the auditability and dead-letter mechanism the company requires.
Q5: A data analytics company runs a large data warehouse on Azure SQL Database. The database is 40 TB in size
and receives complex analytical queries that scan large portions of the data. The company needs to restore the
database to any point in time within the last 14 days. The current General Purpose tier is experiencing
performance degradation during peak query hours. Which service tier should you recommend?
A. Migrate to the Business Critical tier with zone-redundant configuration and enable read-scale replicas
B. Migrate to Azure SQL Managed Instance with the General Purpose tier and configure cross-database queries
Page 2
Azure Solutions Architect Expert Renewal Assessment
Comprehensive Review Examination | Non-Proctored | 60 Minutes | 57% Passing Score
Scenario 1
A multinational retail company hosts its order processing system on Azure SQL Database. The system must remain available
during regional outages with a recovery point objective (RPO) of zero and a recovery time objective (RTO) of less than 30
seconds. The database is currently configured as a General Purpose tier with geo-redundant backup. The company has two
Azure regions in its deployment: East US and West Europe. Read workloads are distributed globally, and write workloads
originate from the East US region only. The existing deployment does not use any active geo-replication or failover group
configuration.
Q1: You need to recommend a high availability and disaster recovery solution that meets the RPO and RTO
requirements while minimizing configuration complexity. What should you recommend?
A. Configure active geo-replication with manual failover and use Azure Traffic Manager to route read traffic to
the secondary replica
B. Deploy a SQL Database failover group with auto-failover policy between East US and West Europe,
using the same service tier in both regions [CORRECT]
C. Enable zone-redundant deployment in East US and configure geo-redundant backups with a 7-day retention
period
D. Implement Azure Site Recovery to replicate the virtual machines hosting the SQL Server to West Europe with
a recovery plan
Correct Answer: B
Rationale: Correct because a SQL Database failover group with auto-failover policy provides an RPO of near-zero
through asynchronous replication and automatic failover meets the RTO of less than 30 seconds without manual
intervention. This matches the requirement for minimal configuration complexity since failover groups manage the
DNS listener, replication link, and failover logic as a single unit.
Q2: Which Azure Cosmos DB consistency level guarantees that reads always return the most recent committed
write and provides linearizability across all regions?
A. Bounded Staleness
B. Session
C. Strong [CORRECT]
D. Consistent Prefix
Correct Answer: C
Rationale: Correct because Strong consistency in Azure Cosmos DB provides linearizability, meaning reads are
guaranteed to return the most recent committed write across all regions. This matches the highest level of
consistency available in Cosmos DB, trading off higher latency and lower availability during partition-level failures.
Q3: You are designing an Azure Kubernetes Service (AKS) cluster for a web application that experiences
unpredictable traffic spikes. The application has a latency-sensitive API that must respond within 200
milliseconds. You need to ensure the cluster scales automatically to handle demand while minimizing costs during
low-traffic periods. Which combination of scaling strategies should you recommend?
Page 1
, Azure Solutions Architect Expert Renewal Assessment - Comprehensive Review
A. Enable the Cluster Autoscaler with a minimum of 3 nodes and a maximum of 20 nodes, and configure the
Horizontal Pod Autoscaler with a target CPU utilization of 80%
B. Configure the Vertical Pod Autoscaler to adjust resource requests dynamically and set the Cluster Autoscaler
to a fixed node count of 10
C. Deploy Azure Container Instances as a burst compute layer using virtual nodes and disable the Cluster
Autoscaler
D. Use the Kubernetes Event-driven Autoscaling (KEDA) with an Azure Service Bus queue trigger and set
the Cluster Autoscaler minimum to 1 node [CORRECT]
Correct Answer: D
Rationale: Correct because KEDA extends the Horizontal Pod Autoscaler with event-driven scaling capabilities,
allowing the application to scale based on the number of messages in the Service Bus queue rather than just CPU
metrics. This matches the requirement to handle unpredictable traffic spikes while setting the Cluster Autoscaler
minimum to 1 node minimizes costs during idle periods.
Mini-Case 1
A financial services company is refactoring a monolithic loan processing application into microservices. The current
monolith handles loan origination, credit scoring, document verification, and disbursement as a single deployable unit. The
company wants each microservice to have independent scaling, deployment, and technology choices. Services must
communicate asynchronously to prevent cascading failures. The existing infrastructure includes an Azure Service Bus
namespace with topics and subscriptions already configured for other messaging workloads. The company requires that all
inter-service communication be auditable and that failed messages be automatically retried with a dead-letter mechanism.
Q4: You need to recommend a communication pattern for the microservices architecture that meets the
company's requirements. Which approach should you recommend?
A. Use synchronous HTTP calls between services with Azure API Management as a gateway and implement retry
logic using Polly in each service
B. Implement an event-driven architecture using Azure Service Bus topics with dead-lettering enabled,
and use Azure Monitor to track all message deliveries [CORRECT]
C. Configure direct gRPC connections between microservices with circuit breaker patterns using Envoy sidecar
proxies and store audit logs in Azure Blob Storage
D. Deploy Azure Event Grid with webhook subscriptions for each microservice and use Azure Cosmos DB as a
durable message store for failed events
Correct Answer: B
Rationale: Correct because Azure Service Bus topics support publish/subscribe messaging patterns with built-in
dead-lettering, automatic retries, and message auditing through Azure Monitor integration. This matches the
requirement for asynchronous communication that prevents cascading failures, leverages the existing Service Bus
namespace, and provides the auditability and dead-letter mechanism the company requires.
Q5: A data analytics company runs a large data warehouse on Azure SQL Database. The database is 40 TB in size
and receives complex analytical queries that scan large portions of the data. The company needs to restore the
database to any point in time within the last 14 days. The current General Purpose tier is experiencing
performance degradation during peak query hours. Which service tier should you recommend?
A. Migrate to the Business Critical tier with zone-redundant configuration and enable read-scale replicas
B. Migrate to Azure SQL Managed Instance with the General Purpose tier and configure cross-database queries
Page 2
