Azure DP-300 key terms

A fully managed relational database service in Azure in which Microsoft handles patching, backups, and high availability, while you choose a purchasing model and service tier.

A deployment option that provides near-full SQL Server engine compatibility, including SQL Server Agent, cross-database queries, and instance-level features, while Microsoft still manages patching and backups.

A shared pool of compute and storage resources that many Azure SQL databases draw from, which is cost-effective when individual databases have unpredictable or spiky demand.

A blended unit that measures CPU, memory, and read/write throughput together, used by the older purchasing model to size a database or pool with one number.

A purchasing option that lets you choose virtual cores, memory, and hardware generation independently, so capacity maps more clearly to on-premises SQL Server hardware.

A billing option for Azure SQL Database that scales compute automatically during use and pauses the database when idle, charging only for compute actually consumed.

A service tier that separates compute from a distributed storage layer, enabling very large databases and fast scale-up or restore without copying the entire database.

Authenticating to Azure SQL with identities managed in Microsoft Entra ID, such as users, groups, and managed identities, so passwords need not be stored in the database.

A database-level principal whose password and metadata live inside the database, so it can connect without a matching server login; often used with contained and Azure SQL authentication.

Encrypts database files and backups at rest with a symmetric key protected by a certificate or Azure Key Vault key, requiring no application changes.

Encrypts selected columns inside the client driver so the database engine never sees plaintext, with column keys held in a key store outside the database.

Returns masked values to users who lack permission, such as showing only the last four digits of a number, while the stored data remains unchanged.

Uses a security policy and inline table-valued function to filter rows automatically, so each user sees only the rows they are permitted to see.

Records events such as logins, permission changes, and data access to storage, Log Analytics, or Event Hubs for compliance and investigation.

A security service that detects anomalous access and possible injection attacks and provides vulnerability assessment findings and recommendations for Azure SQL resources.

A private IP address in a virtual network that connects to an Azure SQL resource, keeping traffic on the Microsoft backbone instead of the public internet.

An allow-list entry that permits connections from a specific IP address or range to all databases on a logical Azure SQL server, filtering traffic before it reaches the engine.

A built-in feature that captures query text, execution plans, and runtime statistics over time, helping you find regressions and force a previously good plan.

A service that watches the workload and can create or drop indexes and force or revert query plans, either automatically or as recommendations you approve.

A diagnostics feature that uses machine learning to detect abnormal performance such as CPU spikes or blocking and writes an explanation with recommended actions to the diagnostics log.

Dynamic management views are system views and functions that expose live server state such as waits, sessions, and query statistics, queried with ordinary T-SQL.

Counters that record how long queries waited and on which resource, such as locks, memory, or disk, helping identify the real bottleneck instead of guessing.

A lightweight, configurable event-tracing system that captures detailed diagnostic data to a file or ring buffer for later analysis.

A SQL Server feature that limits CPU, memory, and IO used by different workload groups, protecting important workloads from noisy neighbors on the same instance.

Configuration that routes resource logs and metrics from an Azure SQL resource to destinations such as Log Analytics, storage accounts, or Event Hubs.

A store for log data in Azure Monitor that you query with KQL, letting you combine SQL logs with other resources for dashboards, alerts, and workbooks.

A condition on a metric or log query that triggers a notification or automated action when a threshold is met, catching problems before users report them.

A scheduled set of T-SQL steps, such as index rebuilds or backups, run by the SQL Server Agent service; available in Managed Instance but not Azure SQL Database.

An Azure SQL feature that runs a T-SQL script across many databases on a schedule, commonly used for maintenance across a pool or shard set.

A PowerShell or Python script hosted in Azure Automation that runs on a schedule or webhook to perform management tasks such as scaling or cleanup.

A serverless compute service that runs small pieces of code in response to timers or events, often used to automate database tasks without managing a server.

A workflow service with connectors that can trigger actions across many systems, useful for orchestrating multi-step automation with approvals and notifications around database tasks.

A package that captures a database schema and can be deployed to update a target database, commonly used in CI/CD pipelines to apply schema changes.

A group of databases on a primary and secondary server with a failover policy and a listener endpoint that clients use to reconnect after failover.

A feature that continuously replicates a database to readable secondary databases in other regions, allowing manual failover and read offloading.

Deploying replicas across availability zones within a region so the database survives a single datacenter failure; supported in certain service tiers.

A service tier using local SSD storage and multiple always-on replicas, giving low latency and fast failover, with an option for a free readable secondary.

Restores a database to an earlier moment within the retention window, creating a new database, and is used to recover from accidental data changes.

A policy that keeps full backups for months or years beyond the normal point-in-time window, typically for legal or regulatory needs, stored in Azure Blob storage.

Recovers a database from geo-replicated backups into a different Azure region when the source region is unavailable, using the most recent available backup.