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
Architecture review: Resource group lifecycle and Role assignment scope. Requirement A: Short-lived environments must be removed together without deleting shared platform services. Requirement B: An engineer only operates one network resource group but has Contributor for the whole subscription. Which complete two-part proposal satisfies both constraints?
For requirement A, resource groups provide a deployment and management boundary and facilitate cohesive cleanup. For requirement B, RBAC assignments inherit downward so narrower scope reduces unintended changes. Verify both independently: Deleting an approved test resource group removes only the intended environment resources; The engineer can change the assigned network group but not another group's resources.
RBAC assignments inherit downward so narrower scope reduces unintended changes. The other proposed action (adopt a standardized resource naming and tagging strategy in landing-zone governance) does not implement the first control. Resource groups provide a deployment and management boundary and facilitate cohesive cleanup.
This combines Resource naming governance and Cost export, which do not satisfy the distinct requirements for Resource group lifecycle and Role assignment scope.
The option covers one requirement but substitutes Cost export for Role assignment scope. The missing acceptance result is: The engineer can change the assigned network group but not another group's resources.
The target environment adopts this approach for Storage migration validation: Validate file hashes, metadata and permissions against a migration manifest. What property makes it suitable?
Object count alone cannot establish content integrity or ACL preservation. It is material here because after copying storage objects the team assumes file count equality proves complete accuracy.
Hidden dependencies can break after migration even when VM replication succeeds. Object count alone cannot establish content integrity or ACL preservation.
Retiring unused assets reduces migration risk and cloud cost rather than copying unnecessary VMs. Object count alone cannot establish content integrity or ACL preservation.
Rehosting prioritizes speed and minimal code changes over immediate PaaS modernization. It belongs to Rehost versus refactor. The stated architecture instead relies on: Object count alone cannot establish content integrity or ACL preservation.
An integration service needs an ordered log of changes to objects without scanning containers every minute. Which Azure architecture would most directly achieve the required result: The consumer reads expected object creation and deletion change records?
Blob change feed records changes to blob objects for downstream processing. The selected architecture is enable the Blob change feed for supported storage accounts; confirm the result by checking that the consumer reads expected object creation and deletion change records.
ADLS Gen2 adds directory semantics and access ACLs to blob-backed storage. That is useful for Blob HNS namespace (Analytics engines require directory-aware ACLs and atomic directory rename semantics over object storage). It does not meet the current Blob change feed requirement: An integration service needs an ordered log of changes to objects without scanning containers every minute.
Blob Storage manages massively scalable object data rather than SMB-compatible shared volumes. It does not solve the specified Blob change feed condition.
Versioning preserves older object versions independently of current content overwrites. The relevant requirement is: An integration service needs an ordered log of changes to objects without scanning containers every minute.
Before approving Private integration access, the reviewer assesses this requirement: Cloud pipelines must access a private database over private routing without publishing its port. Which of the reported outcomes is decisive?
Hybrid/private integration requires a reachable private network path rather than open public DB exposure. Confirm using the measurable result: The pipeline reads the database through the authorized private path while public access fails.
Service Bus is an enterprise message broker with delivery and dead-letter semantics. The distinguishing check is: The pipeline reads the database through the authorized private path while public access fails.
Delta Lake transaction logs enable reliable table updates and versioning on cloud object stores. The Databricks Delta Lake test checks a MERGE updates matching records atomically and table history contains the transaction; the relevant outcome is The pipeline reads the database through the authorized private path while public access fails.
Data Explorer is designed for large-scale append-oriented telemetry exploration with KQL. The offered observation would demonstrate Azure Data Explorer telemetry: A filtered time-series KQL query returns the needed event trend within response goals. The current validation is different: The pipeline reads the database through the authorized private path while public access fails.
Architecture review: SQL compute scaling and SQL elastic pool. Requirement A: A database must grow compute during a seasonal sales period but not during idle months. Requirement B: Hundreds of tenant databases have peaks at different times and waste money with dedicated compute. Which complete two-part proposal satisfies both constraints?
For requirement A, managed SQL compute tiers can scale resources but scaling may have operational consequences. For requirement B, elastic pools share resources across independent databases with non-synchronized demand. Verify both independently: A scheduled scale-up meets throughput and a later scale-down reduces cost; Aggregated tenant peaks stay within pool limits at lower cost than individually overprovisioned databases.
Managed SQL compute tiers can scale resources but scaling may have operational consequences. Elastic pools share resources across independent databases with non-synchronized demand. The proposed steps (run Azure SQL migration assessment and remediate feature compatibility findings; configure supported Azure SQL active geo-replication and route stale-tolerant reads to the replica) address other capabilities instead of this required pair.
The first step implements SQL migration assessment instead of SQL compute scaling. The necessary change is to plan supported vertical compute scaling and evaluate tier limits and transition impacts.
One action is correct. The other targets SQL geo-replication reporting, leaving SQL elastic pool unsolved. Its necessary action is: Place eligible Azure SQL databases in an elastic pool with shared compute.
A solution must address both Key Vault certificate lifecycle and Key Vault cryptographic signing. First requirement: A customer-facing API's TLS certificate needs controlled renewal before expiration. 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 certificate lifecycle.
For the Key Vault certificate lifecycle half of this two-part design, Key Vault certificates support managed lifecycle and distribution to compatible Azure integrations. Verify: The renewed certificate is used by the endpoint before the old certificate expires. The other half concerns Key Vault cryptographic signing.
App-only permissions grant service principal operations without a delegated signed-in user. This alternative solves Application permissions, while the question separately requires Key Vault certificate lifecycle and Key Vault cryptographic signing.
Delegated permissions represent what an application can do on behalf of an authenticated user. The corresponding task is App registration API scopes: A backend API should expose delegated scopes to a client on behalf of a signed-in user. It is not one of the two requested controls (Key Vault certificate lifecycle and Key Vault cryptographic signing).
Secure secret handling removes reusable credentials from source while preserving automation. That plan is appropriate for Secrets in deployment pipeline. The two controls sought here are Key Vault certificate lifecycle and Key Vault cryptographic signing.
Partners need one secured API entry point with subscription policies quotas and versioned back ends. Identify the most suitable implementation for an outcome where an expired subscription key fails while an authorized request routes to the correct version.
APIM applies gateway policies authentication mediation throttling and API lifecycle controls. The selected architecture is place Azure API Management in front of approved back-end APIs; confirm the result by checking that an expired subscription key fails while an authorized request routes to the correct version.
Asynchronous projections can lag writes and need clear read-after-write expectations. It does not solve the specified API Management gateway condition.
Queueing decouples front-end latency from downstream worker availability. Its design target is Queue asynchronous processing. The stated requirement instead concerns: Partners need one secured API entry point with subscription policies quotas and versioned back ends.
At-least-once message delivery requires application logic to deduplicate business side effects. The relevant requirement is: Partners need one secured API entry point with subscription policies quotas and versioned back ends.
To validate the App Configuration feature flags deployment, reviewers revisit this operational need: Operators must turn a feature on for a pilot group without rebuilding application binaries. What result confirms it was met?
App Configuration centralizes feature settings; secrets should remain in Key Vault. Confirm using the measurable result: Pilot users see the feature after refresh and others retain the previous behavior.
Front Door rule sets change eligible request and response behavior at the edge according to match conditions. The distinguishing check is: Pilot users see the feature after refresh and others retain the previous behavior.
Failure handling isolates unhealthy dependencies and avoids request pileups. The Application resilience timeout test checks simulated downstream failure produces prompt controlled errors while healthy requests remain available; the relevant outcome is Pilot users see the feature after refresh and others retain the previous behavior.
Event Grid distributes discrete source events to configured subscribers. The offered observation would demonstrate Event Grid notification: Only event handlers matching the subject filter are invoked for the test upload. The current validation is different: Pilot users see the feature after refresh and others retain the previous behavior.
A seasonal workload has normal daily peaks and a fixed metric threshold floods the alert queue. Choose the architecture that can be validated by this result: The routine daily spike is tolerated while an atypical surge creates an actionable alert.
Dynamic thresholds adapt alert boundaries to historical metric patterns after sufficient data exists. The selected architecture is evaluate Azure Monitor dynamic threshold metric alerts for its established behavioral baseline; confirm the result by checking that the routine daily spike is tolerated while an atypical surge creates an actionable alert.
Metrics are low-latency numeric series and alert evaluation can trigger actions independently of a log query. Its design target is CPU threshold alerts. The stated requirement instead concerns: A seasonal workload has normal daily peaks and a fixed metric threshold floods the alert queue.
AMPLS provides private connectivity to supported Azure Monitor ingestion and query endpoints. The relevant requirement is: A seasonal workload has normal daily peaks and a fixed metric threshold floods the alert queue.
DCRs specify collected streams destinations and transformations for supported agent sources. It does not solve the specified Dynamic baseline alerts condition.
Architecture review: Database schema assessment and Replatform database. Requirement A: An on-prem SQL app calls deprecated features that Azure SQL Database may not support. Requirement B: A SQL application can move to managed SQL with a few configuration changes but needs no redesign. Which complete two-part proposal satisfies both constraints?
For requirement A, target compatibility determines whether code changes or a different managed target are required. For requirement B, replatforming changes hosting characteristics while preserving most app behavior. Verify both independently: The assessment reports blocking SQL features and chosen remediation before migration; Migration validation shows required database features function on the selected managed tier.
Target compatibility determines whether code changes or a different managed target are required. The other proposed action (run Azure Migrate discovery and assessment with dependency analysis where supported) addresses a different operation. Replatforming changes hosting characteristics while preserving most app behavior.
Both proposed halves address other use cases: Migration landing zone and Azure Migrate inventory. The requested pair is Database schema assessment and Replatform database.
One action is correct. The other targets Migration landing zone, leaving Database schema assessment unsolved. Its necessary action is: Perform schema and compatibility assessment before choosing Azure SQL Database or Managed Instance.
A solution must address both Storage migration validation and Azure File Sync. First requirement: After copying storage objects the team assumes file count equality proves complete accuracy. Second requirement: A branch file server should retain local caching while most data moves to Azure Files. Select TWO recommendations that meet these independent needs.
For the Azure File Sync half of this design, file Sync preserves local namespace access while synchronizing with Azure file shares. Check: Frequently used files remain locally available and cold files tier to cloud. The other half concerns Storage migration validation.
For the Storage migration validation half of this two-part design, object count alone cannot establish content integrity or ACL preservation. Verify: Checksums, timestamps and access checks reconcile source and destination. The other half concerns Azure File Sync.
Target compatibility determines whether code changes or a different managed target are required. The corresponding task is Database schema assessment: An on-prem SQL app calls deprecated features that Azure SQL Database may not support. It is not one of the two requested controls (Storage migration validation and Azure File Sync).
Replatforming changes hosting characteristics while preserving most app behavior. This alternative solves Replatform database, while the question separately requires Storage migration validation and Azure File Sync.
Landing-zone foundations provide policy, connectivity and subscription placement for incoming workloads. The corresponding task is Migration landing zone: A program plans 100 app moves but lacks identity, DNS, governance and network foundations. It is not one of the two requested controls (Storage migration validation and Azure File Sync).
Please check your mailbox for a message from support@examlabs.com and follow the directions.