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
An external-facing consumer application requires local and social identity sign-in separate from workforce identities. The acceptance test is: The consumer completes the intended registration journey without receiving workforce resource roles. Which design recommendation best satisfies both?
External ID consumer capabilities support customer journeys distinct from employee workforce governance. The selected architecture is use an appropriate Microsoft Entra External ID customer identity design; confirm the result by checking that the consumer completes the intended registration journey without receiving workforce resource roles.
Key Vault RBAC data permissions differ from vault resource-management permissions. The current need is: An external-facing consumer application requires local and social identity sign-in separate from workforce identities.
Administrative units scope eligible directory management roles to selected objects, not data visibility. It does not solve the specified Consumer sign-in condition.
Management locks guard against accidental resource deletes and operate separately from authorization roles. The relevant requirement is: An external-facing consumer application requires local and social identity sign-in separate from workforce identities.
An architect must sign off on SQL database PITR. The business problem is: A deployment accidentally truncates a transaction table and the database must be recovered before the change. What observed test result provides valid evidence?
Azure SQL automatic full differential and log backups support restoring database state at a selected time. Confirm using the measurable result: A restored database contains transactions immediately preceding the truncation.
Failback is a separate operational sequence after workloads run in the recovery site. The distinguishing check is: A restored database contains transactions immediately preceding the truncation.
Share snapshots preserve file-share point-in-time state for supported restoration. The Azure Files snapshots test checks an earlier version of an overwritten spreadsheet is recovered from a share snapshot; the relevant outcome is A restored database contains transactions immediately preceding the truncation.
Geo-restore is backup-based recovery with different RTO/RPO than active geo-replication. The offered observation would demonstrate SQL geo-restore: A region-loss exercise recovers a database from the latest supported geo backup. The current validation is different: A restored database contains transactions immediately preceding the truncation.
A proposed solution for SQL schema isolation is: Use one managed database per tenant when isolation and lifecycle needs outweigh extra operations. Select the strongest statement supporting the recommendation.
Database-per-tenant provides a distinct security and backup boundary versus one shared schema. It is material here because a multitenant app needs strong tenant-level database isolation and easy tenant backup/restore.
Flexible Server provides managed MySQL compute storage and backups. Database-per-tenant provides a distinct security and backup boundary versus one shared schema.
Dynamic data masking limits exposure in query results but is not a substitute for database access control. Database-per-tenant provides a distinct security and backup boundary versus one shared schema.
Active geo-replication creates readable asynchronously updated secondary databases while primary remains writable. It belongs to SQL geo-replication reporting. The stated architecture instead relies on: Database-per-tenant provides a distinct security and backup boundary versus one shared schema.
Architecture rationale review—SQL database monitoring: Use Azure SQL query performance insight and Azure Monitor metrics/diagnostics. Which explanation accurately distinguishes this capability?
Query and resource telemetry helps distinguish costly queries from insufficient database compute. It is material here because dBAs need CPU, DTU/vCore, wait and query performance evidence before changing the tier.
Hyperscale decouples storage scale from compute and supports large database sizes. Query and resource telemetry helps distinguish costly queries from insufficient database compute.
Dynamic data masking limits exposure in query results but is not a substitute for database access control. It belongs to SQL dynamic data masking. The stated architecture instead relies on: Query and resource telemetry helps distinguish costly queries from insufficient database compute.
Ledger records cryptographically verifiable tamper-evidence for supported relational tables. That statement describes SQL ledger immutability, while the question asks how SQL database monitoring works: Query and resource telemetry helps distinguish costly queries from insufficient database compute.
Architecture rationale review—Storage bulk offline transfer: Use an appropriate Azure Data Box physical transfer service. Which explanation accurately distinguishes this capability?
Physical data transfer can shorten initial bulk migration when network transfer is impractical. It is material here because a remote facility must move 500 TB to Azure but WAN bandwidth is too slow for the deadline.
Offline migration can simplify cutover when application downtime is acceptable. Physical data transfer can shorten initial bulk migration when network transfer is impractical.
PostgreSQL migration requires extension, version and connectivity compatibility checks. It belongs to PostgreSQL migration. The stated architecture instead relies on: Physical data transfer can shorten initial bulk migration when network transfer is impractical.
Hidden dependencies can break after migration even when VM replication succeeds. Physical data transfer can shorten initial bulk migration when network transfer is impractical.
An application depends on PostgreSQL extensions and wants managed PostgreSQL without a VM. Which Azure architecture would most directly achieve the required result: The required extension is available and the app connects without an OS-managed database host?
Flexible Server offers managed open-source PostgreSQL with supported extensions and deployment options. The selected architecture is select Azure Database for PostgreSQL Flexible Server and verify extension availability; confirm the result by checking that the required extension is available and the app connects without an OS-managed database host.
Dynamic data masking limits exposure in query results but is not a substitute for database access control. It does not solve the specified PostgreSQL flexible server condition.
SQL auditing captures database events as configured separately from application request telemetry. Its design target is SQL auditing. The stated requirement instead concerns: An application depends on PostgreSQL extensions and wants managed PostgreSQL without a VM.
Elastic pools share resources across independent databases with non-synchronized demand. The current need is: An application depends on PostgreSQL extensions and wants managed PostgreSQL without a VM.
The acceptance criterion for AKS container diagnosis comes from this issue: An AKS deployment repeatedly restarts and the team needs pod-level logs and cluster health. Which measured outcome is the strongest proof?
Container insights exposes Kubernetes workload health and container logs beyond generic virtual-machine statistics. Confirm using the measurable result: The restarting pod and its container events are visible with node and namespace context.
Resource diagnostic settings forward selected resource logs whereas subscription Activity Log tracks management operations. The Database resource diagnostics test checks sQL diagnostic records appear in the target workspace and can be filtered by database name; the relevant outcome is The restarting pod and its container events are visible with node and namespace context.
Managed Prometheus collects Prometheus-format metrics separately from traditional container log collection. The offered observation would demonstrate Managed Prometheus: A PromQL dashboard graphs the selected container metric with the expected Kubernetes labels. The current validation is different: The restarting pod and its container events are visible with node and namespace context.
KQL summarizes timestamped structured log data across dimensions such as operation and cloud role. Those observations validate Error trend queries. They do not establish the required AKS container diagnosis result: The restarting pod and its container events are visible with node and namespace context.
A large transaction table suffers scans on historical data and needs time-based management. Identify the most suitable implementation for an outcome where execution plans prune irrelevant historical partitions for the test query.
Partition elimination and aligned indexes can reduce scans when predicates match partition keys. The selected architecture is design appropriate table partitioning and indexing for workload query patterns; confirm the result by checking that execution plans prune irrelevant historical partitions for the test query.
SQL auditing captures database events as configured separately from application request telemetry. The relevant requirement is: A large transaction table suffers scans on historical data and needs time-based management.
Always Encrypted supports encryption and decryption in capable clients to reduce exposure to the database engine. It does not solve the specified SQL database partitioning condition.
Read replicas offload eligible read-only queries but are asynchronously updated from the writer. Its design target is PostgreSQL read replica. The stated requirement instead concerns: A large transaction table suffers scans on historical data and needs time-based management.
A solution must address both Key Vault secrets and Key Vault cryptographic signing. First requirement: A service depends on a vendor API password that rotates frequently. Second requirement: An application must sign payloads with a centrally controlled key without exporting its private material. Select TWO recommendations that meet these independent needs.
For the Key Vault cryptographic signing half of this design, Key Vault keys can perform cryptographic operations while restricting private key exposure. Check: The application receives a valid signature but cannot export the private key material. The other half concerns Key Vault secrets.
For the Key Vault secrets half of this two-part design, Key Vault secrets support controlled retrieval and rotation separate from packaged application code. Verify: The service uses the new secret version without an embedded password in deployment artifacts. The other half concerns Key Vault cryptographic signing.
A user-assigned identity has a lifecycle separate from each consuming Azure resource. The corresponding task is Shared workload identity: Two Functions apps need the same persistent workload identity even when one app is recreated. It is not one of the two requested controls (Key Vault secrets and Key Vault cryptographic signing).
Data-plane roles control access to blob content and least-scope assignment reduces unnecessary privileges. That plan is appropriate for Managed-identity scope. The two controls sought here are Key Vault secrets and Key Vault cryptographic signing.
Administrative units scope eligible directory management roles to selected objects, not data visibility. Its own validation would be: The regional admin can reset an assigned user's password but cannot administer an out-of-scope user. The current paired requirement is Key Vault secrets and Key Vault cryptographic signing.
Cost reporting is missing the billing cost center tag on newly created resources. A deployment must satisfy this operational criterion: An untagged deployment is denied or audited as configured and tagged deployment succeeds. Which plan is appropriate?
Policy deny or audit effects can enforce required metadata at supported resource scopes. The selected architecture is use an Azure Policy require-tag rule at the appropriate scope; confirm the result by checking that an untagged deployment is denied or audited as configured and tagged deployment succeeds.
Infrastructure as code declares desired resources and allows review and repeat deployment. That is useful for Standardized IaC (Operations wants reproducible Azure environment deployments from version-controlled definitions). It does not meet the current Required tag policy requirement: Cost reporting is missing the billing cost center tag on newly created resources.
Defender for Cloud aggregates recommendations and compliance state for supported frameworks. It does not solve the specified Required tag policy condition.
Azure service quotas are often scoped by subscription and region and can constrain deployability. The relevant requirement is: Cost reporting is missing the billing cost center tag on newly created resources.
Architecture review: Physical server migration and Azure File Sync. Requirement A: A legacy application runs on a physical Windows server and needs an IaaS move. Requirement B: A branch file server should retain local caching while most data moves to Azure Files. Which complete two-part proposal satisfies both constraints?
For requirement A, physical migration requires source capture and replication methods different from VMware agentless VM migration. For requirement B, file Sync preserves local namespace access while synchronizing with Azure file shares. Verify both independently: A cutover VM starts in Azure with its application settings preserved; Frequently used files remain locally available and cold files tier to cloud.
File Sync preserves local namespace access while synchronizing with Azure file shares. The other proposed action (evaluate replatforming to Azure SQL Managed Instance or Database after compatibility tests) does not implement the first control. Physical migration requires source capture and replication methods different from VMware agentless VM migration.
Physical migration requires source capture and replication methods different from VMware agentless VM migration. The other proposed action (perform schema and compatibility assessment before choosing Azure SQL Database or Managed Instance) addresses a different operation. File Sync preserves local namespace access while synchronizing with Azure file shares.
Both proposed halves address other use cases: Replatform database and Database schema assessment. The requested pair is Physical server migration and Azure File Sync.
Please check your mailbox for a message from support@examlabs.com and follow the directions.