You save $69.98
AZ-305 Premium Bundle
- Premium File 382 Questions & Answers
- Last Update: Nov 20, 2026
- Training Course 87 Lectures
- Study Guide 933 Pages
You save $69.98
The design team completed work on APIM rate limiting. Its governing requirement was: A popular API needs to reject excessive client requests without changing back-end services. Identify the conclusive verification result.
APIM can enforce per-client API consumption controls before requests reach backends. Confirm using the measurable result: A burst beyond the quota is throttled while permitted traffic proceeds.
At-least-once message delivery requires application logic to deduplicate business side effects. Those observations validate Reliable exactly-once effect. They do not establish the required APIM rate limiting result: A burst beyond the quota is throttled while permitted traffic proceeds.
App Configuration centralizes feature settings; secrets should remain in Key Vault. The distinguishing check is: A burst beyond the quota is throttled while permitted traffic proceeds.
Application Gateway provides application-aware path routing rather than basic L4 forwarding. The Application Gateway path routing test checks requests to each path arrive at the correct healthy backend pool; the relevant outcome is A burst beyond the quota is throttled while permitted traffic proceeds.
A CI/CD job in GitHub Actions must deploy Azure resources without storing a long-lived service principal secret. A deployment must satisfy this operational criterion: An approved pipeline deploys without a stored client secret and an untrusted subject is rejected. Which plan is appropriate?
Federated credentials exchange trusted external OIDC assertions for Entra access tokens. The selected architecture is configure workload identity federation between the trusted job issuer and an Entra application or user-assigned identity; confirm the result by checking that an approved pipeline deploys without a stored client secret and an untrusted subject is rejected.
Authentication strengths let Conditional Access require supported strong methods based on conditions. That is useful for Conditional MFA (Administrators must use phishing-resistant authentication for high-privilege cloud portal actions). It does not meet the current Workload identity federation requirement: A CI/CD job in GitHub Actions must deploy Azure resources without storing a long-lived service principal secret.
B2B collaboration supports guest principals and cross-organization access controls. It does not solve the specified Workload identity federation condition.
App-only permissions grant service principal operations without a delegated signed-in user. The relevant requirement is: A CI/CD job in GitHub Actions must deploy Azure resources without storing a long-lived service principal secret.
Architecture review: Migration landing zone and Networking cutover DNS. Requirement A: A program plans 100 app moves but lacks identity, DNS, governance and network foundations. Requirement B: A migrated app uses a new Azure IP but clients have a hardcoded old DNS endpoint. Which complete two-part proposal satisfies both constraints?
For requirement A, landing-zone foundations provide policy, connectivity and subscription placement for incoming workloads. For requirement B, DNS cutover requires propagation and dependency planning independent of VM replication. Verify both independently: The first migrated app uses approved network, DNS and access standards; Clients resolve the new endpoint and the rollback procedure returns traffic if needed.
Landing-zone foundations provide policy, connectivity and subscription placement for incoming workloads. DNS cutover requires propagation and dependency planning independent of VM replication. The proposed steps (use an appropriate offline Azure Database Migration Service path after compatibility review; choose a rebuild approach where business requirements justify new architecture) address other capabilities instead of this required pair.
Landing-zone foundations provide policy, connectivity and subscription placement for incoming workloads. The other proposed action (choose a rebuild approach where business requirements justify new architecture) addresses a different operation. DNS cutover requires propagation and dependency planning independent of VM replication.
One action is correct. The other targets SQL offline migration, leaving Migration landing zone unsolved. Its necessary action is: Create an Azure landing zone before migration waves using CAF guidance.
The Site-to-site VPN review proposes: Deploy Azure VPN Gateway site-to-site tunnels with matching local/remote IPsec settings. Which Azure behavior is the technical justification for this decision?
VPN Gateway can establish encrypted IPsec tunnels over public networks. It is material here because a small branch needs encrypted connectivity to a VNet over its existing internet link.
Virtual WAN provides managed global transit architecture with integrated branch connectivity. VPN Gateway can establish encrypted IPsec tunnels over public networks.
Point-to-site VPN authenticates individual clients for private network access. VPN Gateway can establish encrypted IPsec tunnels over public networks.
A hub centralizes connectivity services while spoke VNets isolate applications. That statement describes Hub-spoke topology, while the question asks how Site-to-site VPN works: VPN Gateway can establish encrypted IPsec tunnels over public networks.
During technical sign-off for VM disk encryption, the architect selects: Use supported disk encryption-set customer-managed keys with suitable identity and vault. Which underlying behavior should be documented?
Encryption sets connect managed disk encryption to customer-owned keys. It is material here because a finance VM needs customer-managed encryption keys for managed disks.
Memory-optimized sizes offer higher RAM-to-vCPU ratio for large in-memory working sets. Encryption sets connect managed disk encryption to customer-owned keys.
Spot instances offer lower-priced spare capacity without guaranteed availability. It belongs to Spot VM suitability. The stated architecture instead relies on: Encryption sets connect managed disk encryption to customer-owned keys.
Queue-length scaling aligns worker count with pending work rather than idle CPU metrics. Encryption sets connect managed disk encryption to customer-owned keys.
The database service must recover a read/write endpoint when the primary Azure region fails. A deployment must satisfy this operational criterion: The app reconnects after an orchestrated failover without endpoint edits. Which plan is appropriate?
Failover-group listeners abstract the primary location during regional failover. The selected architecture is configure Azure SQL failover groups and an app connection using the appropriate listener; confirm the result by checking that the app reconnects after an orchestrated failover without endpoint edits.
A zone-separated standby supports automated failover where offered. That is useful for PostgreSQL zone redundant HA (A mission-critical PostgreSQL workload requires HA across zones within a region). It does not meet the current SQL failover groups HA requirement: The database service must recover a read/write endpoint when the primary Azure region fails.
Multi-region writes allow eligible regions to accept writes but require handling conflicts. It does not solve the specified SQL failover groups HA condition.
Zone redundancy spreads eligible database availability replicas across zones. The relevant requirement is: The database service must recover a read/write endpoint when the primary Azure region fails.
The target environment adopts this approach for Managed Prometheus: Enable Azure Monitor managed service for Prometheus for supported Kubernetes clusters. What property makes it suitable?
Managed Prometheus collects Prometheus-format metrics separately from traditional container log collection. It is material here because a Kubernetes platform emits Prometheus metrics and needs Azure-native managed scraping and Grafana dashboards.
Action groups define notifications and automated responses and can be reused by alert rules. That statement describes Notification routing, while the question asks how Managed Prometheus works: Managed Prometheus collects Prometheus-format metrics separately from traditional container log collection.
Service Health reports Azure platform incidents and planned maintenance relevant to a subscription. Managed Prometheus collects Prometheus-format metrics separately from traditional container log collection.
Storage-based diagnostic archives and immutability serve compliance preservation rather than interactive KQL search. It belongs to Immutable evidence archive. The stated architecture instead relies on: Managed Prometheus collects Prometheus-format metrics separately from traditional container log collection.
A central security team needs network and application filtering across multiple spokes. An architecture board will approve a solution only if this outcome is demonstrated: Permitted HTTPS passes inspection while the prohibited destination is blocked. What should be selected?
Azure Firewall provides managed stateful filtering with network/application rule models. The selected architecture is use Azure Firewall with correct rule collections and hub routing; confirm the result by checking that permitted HTTPS passes inspection while the prohibited destination is blocked.
A hub centralizes connectivity services while spoke VNets isolate applications. The relevant requirement is: A central security team needs network and application filtering across multiple spokes.
Application Gateway provides regional Layer 7 reverse proxy and routing for private backends. That is useful for Application Gateway internal (An internal web app needs URL path routing and WAF-like inspection behind a private frontend). It does not meet the current Azure Firewall rules requirement: A central security team needs network and application filtering across multiple spokes.
Point-to-site VPN authenticates individual clients for private network access. It does not solve the specified Azure Firewall rules condition.
During technical sign-off for Route Server dynamic routing, the architect selects: Use Azure Route Server to exchange BGP routes with a supported NVA. Which underlying behavior should be documented?
Route Server enables BGP exchange with NVAs without custom per-prefix UDR maintenance. It is material here because a hub network virtual appliance advertises dynamically changing routes that Azure workloads must learn.
VNet integration is principally an outbound feature; inbound private access requires other controls. It belongs to VNet integration App Service. The stated architecture instead relies on: Route Server enables BGP exchange with NVAs without custom per-prefix UDR maintenance.
Private endpoints provide a private inbound path for supported App Service access. That statement describes Private inbound App Service, while the question asks how Route Server dynamic routing works: Route Server enables BGP exchange with NVAs without custom per-prefix UDR maintenance.
Application Gateway provides regional Layer 7 reverse proxy and routing for private backends. Route Server enables BGP exchange with NVAs without custom per-prefix UDR maintenance.
Auditors require tamper-resistant retention of exported logs that are rarely queried. An architecture board will approve a solution only if this outcome is demonstrated: A retained log blob rejects unauthorized deletion during its compliance retention window. What should be selected?
Storage-based diagnostic archives and immutability serve compliance preservation rather than interactive KQL search. The selected architecture is send the appropriate diagnostic logs to a storage account with configured immutable retention policies; confirm the result by checking that a retained log blob rejects unauthorized deletion during its compliance retention window.
Managed Prometheus collects Prometheus-format metrics separately from traditional container log collection. That is useful for Managed Prometheus (A Kubernetes platform emits Prometheus metrics and needs Azure-native managed scraping and Grafana dashboards). It does not meet the current Immutable evidence archive requirement: Auditors require tamper-resistant retention of exported logs that are rarely queried.
A log search alert can evaluate aggregated matching records instead of only raw metric time series. It does not solve the specified Immutable evidence archive condition.
Entra diagnostic export makes identity sign-in events available for central retention and KQL correlation. The current need is: Auditors require tamper-resistant retention of exported logs that are rarely queried.
A solution must address both Cosmos partition key and Blob user-delegation SAS. First requirement: A Cosmos container uses a low-cardinality partition key and has hot-partition throttling. Second requirement: A partner needs time-limited upload permission to a particular blob without sharing the storage account key. Select TWO recommendations that meet these independent needs.
For the Cosmos partition key half of this two-part design, partition key distribution governs data/throughput placement and query efficiency. Verify: RU consumption distributes across partitions and the query includes its expected partition key. The other half concerns Blob user-delegation SAS.
For the Blob user-delegation SAS half of this design, a user-delegation SAS is authorized through Entra credentials and avoids distributing account keys. Check: The permitted upload works before expiry while an unauthorized operation and expired token fail. The other half concerns Cosmos partition key.
Session consistency offers read-your-writes within a session without strong global consistency. Its own validation would be: The writing session immediately reads its own update while other sessions may lag. The current paired requirement is Cosmos partition key and Blob user-delegation SAS.
Archive tier minimizes long-term storage cost but archived objects must be rehydrated before reading. This alternative solves Blob archive rehydration, while the question separately requires Cosmos partition key and Blob user-delegation SAS.
Autoscale adjusts provisioned RU/s capacity according to measured load within a maximum. The corresponding task is Cosmos autoscale: An API's Cosmos traffic varies tenfold through the day and manually fixed throughput is wasteful. It is not one of the two requested controls (Cosmos partition key and Blob user-delegation SAS).
Please check your mailbox for a message from support@examlabs.com and follow the directions.