AZ-305 Question 84

Community Discussion

Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.

• 1

  Azure SQL product: A single Azure SQL database Service tier: Hyperscale Dimensionamento automático de recursos de computação conforme a demanda Cobrança por segundo Esses requisitos correspondem ao Azure SQL Database no modelo Serverless, que está disponível para Single Database na camada General Purpose, não na Hyperscale. Porém, como a questão não apresenta "Serverless" entre as opções de nível de serviço, ela costuma seguir a lógica das provas antigas da Microsoft, nas quais o Hyperscale era a opção associada ao escalonamento automático.

• 2

  Requirements Automatically scales compute based on workload Per-second billing This is Serverless compute tier behavior. Only Azure SQL Database (single database) supports Serverless. Elastic pool ❌ doesn't auto scale per DB Managed Instance ❌ no serverless / per-second billing So product = Single Azure SQL Database Now service tier: Serverless is available under: General Purpose (serverless) ✅ Not: Basic ❌ Standard ❌ Business Critical ❌ Hyperscale ❌ (no serverless auto pause)

• 1

  Requirements: Auto-scale compute based on workload Per-second billing This is Azure SQL Database serverless. Serverless is available only for: Single Azure SQL database General Purpose tier (serverless compute) Answer: Azure SQL product: A single Azure SQL database Service tier: General Purpose Why: Serverless auto-scales compute ✔ Auto-pause + per-second billing ✔ Elastic pool → no per-second billing Managed Instance → no serverless Hyperscale/Business Critical → provisioned only