70-532 Sample Questions & Answers

The goal of a custom retry policy is to define the conditions under which it should retry. The method should return true to retry and false to fail. The requirement is to retry ONLY on a 409 Conflict. Therefore, if the status code is anything OTHER than Conflict, the method should return false to stop the retry loop.

Azure Service Bus Topics and Subscriptions are designed for the publish/subscribe (pub/sub) pattern. The front-end publishes a single message to a topic. Multiple back-end services each listen on their own subscription to that topic, and each subscription receives a copy of the message. This allows for one-to-many message distribution. Service Bus Queues are for one-to-one delivery, and Event Hubs are for high-throughput event streaming, not individual message processing by distinct consumers.

NSGs have default rules. One default rule allows all traffic from the 'VirtualNetwork' source. Another default rule with a high priority number (65500) denies all inbound traffic from the 'Internet'. To meet the requirements, you only need to add one new inbound rule with a lower priority number (e.g., 100) that allows traffic on port 443 from the 'Internet' source. This rule will be processed before the default deny rule, allowing HTTPS traffic while the default rules correctly handle VNet traffic and deny all other internet traffic.

A Shared Access Signature (SAS) provides delegated access to resources in a storage account. It allows for granular control over permissions (read, write, delete), expiry time, and the specific resource (e.g., a single blob). This is the standard and secure way to grant temporary, limited access without exposing the account keys.

The best practice for multi-tier applications is to place the VMs for each tier into their own separate Availability Set. An Availability Set distributes VMs across Update Domains and Fault Domains. By using separate sets, you ensure that planned maintenance (which targets one Update Domain at a time) will only affect a subset of VMs within a single tier, not across different tiers simultaneously. This maintains the availability of the entire application.

Azure App Service Hybrid Connections allow an Azure application to securely access on-premises resources. It also works in reverse, allowing an on-premises application to connect to an Azure App Service. It establishes a secure tunnel without requiring a VPN or firewall changes. VPN Gateway and ExpressRoute connect entire virtual networks to on-premises networks, which is more than is needed for this specific application-to-application scenario.

Active Geo-Replication is designed for disaster recovery. It creates a continuously synchronized, readable secondary database in a different region. It provides a low RPO (data loss) and RTO (time to recover) by allowing for quick, manual failover. Point-in-time restore is for recovering from accidental data deletion within the same region, and BACPAC export is a manual backup method with a much higher RPO.

Azure Automation State Configuration is a service built on PowerShell Desired State Configuration (DSC). It allows you to write declarative configurations that define the desired state of your VMs. The service then ensures that managed nodes (your VMs) are in that state, automatically correcting any configuration drift. Custom Script Extension is imperative (it runs a script once), not declarative, and does not handle drift.

Azure API Management is designed as a turnkey solution for publishing, securing, and managing APIs. It provides a rich set of out-of-the-box policies to handle common cross-cutting concerns, including rate limiting (throttling), response caching, and request/response transformations (like JSON to XML). Application Gateway is a web traffic load balancer, and Logic Apps is a workflow orchestrator; neither provides this comprehensive set of API gateway features.

The Azure Mobile Apps client SDKs include a specific feature called Offline Data Sync. This feature provides APIs to create a local store (typically an on-device SQLite database) and manage the synchronization of data between this local store and the remote backend. It handles queuing up local changes and pushing them to the server, as well as pulling down changes from the server.