Free AZ-305 flashcards

What is the documented maximum function execution timeout on the legacy Azure Functions Consumption plan?

The legacy Consumption plan has a 5-minute default and a 10-minute maximum timeout per execution. Anything longer must run on Flex Consumption, Premium, or Dedicated, which support an unbounded timeout. Long-running jobs are killed mid-flight if left on Consumption, so the ceiling must be checked before migration.

The legacy Azure Functions Consumption plan allows unbounded execution up to 60 minutes per invocation.

Unbounded execution is documented for Flex Consumption, Premium, Dedicated, and Container Apps - not the legacy Consumption plan. Legacy Consumption is capped at a 10-minute maximum timeout with a 5-minute default, so a job longer than 10 minutes will not fit.

What design path gives end-to-end observability for an AI agent hosted on Microsoft Foundry?

Start tracing in Foundry, then add the Azure Monitor OpenTelemetry Distro with the Foundry SDK for app-side instrumentation. Application Insights is the documented unified observability experience and provides built-in dashboards surfacing token consumption, latency, error rates, and quality scores. Bypassing Application Insights forfeits the prebuilt agent dashboards.

For a Foundry-hosted AI agent, you should wire Foundry traces straight to a Log Analytics workspace and skip Application Insights.

Application Insights is the documented unified observability experience for AI agents across Foundry, Copilot Studio, and third-party frameworks. Bypassing it forfeits the prebuilt agent dashboards. The documented path is to start tracing in Foundry, then add the Azure Monitor OpenTelemetry Distro with the Foundry SDK.

Which failover-group policy keeps the failover decision under human control?

Customer-managed (manual) failover policy keeps the decision with the customer, and the documentation recommends it so the business retains control over when failover happens. Microsoft-managed failover only triggers during widespread regional outages, after a grace period, and removes that human control over timing.

Setting an Azure SQL Database failover group to Microsoft-managed (automatic) failover lets business owners keep control over when failover happens.

Microsoft-managed failover only triggers during widespread regional outages and removes human control over the timing of failover. To keep the decision with the business, use customer-managed (manual) failover, which the documentation recommends so the business retains control.

Can the cadence of ASR crash-consistent recovery points be changed below five minutes?

ASR creates crash-consistent recovery points every five minutes by default and this interval cannot be modified. Only the app-consistent snapshot frequency and recovery-point retention are configurable on the replication policy, so workloads needing tighter cadence must look beyond ASR replication-policy settings.

Switching an Azure VM to Hyper-V replication lets Azure Site Recovery create crash-consistent recovery points every 30 seconds for that workload.

The 30-second cadence belongs to the Hyper-V-to-Azure (H2A) replication path, not to Azure VM A2A. For A2A workloads the crash-consistent interval is fixed at five minutes and cannot be modified by changing replication type.