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
A user can view a storage account resource but cannot download its blobs. Which Azure architecture would most directly achieve the required result: The user downloads an approved blob without gaining storage management privileges?
Management-plane Azure RBAC Reader does not automatically authorize blob data-plane reads. The selected architecture is assign an appropriate Blob Data Reader role rather than only management-plane Reader; confirm the result by checking that the user downloads an approved blob without gaining storage management privileges.
Key Vault RBAC data permissions differ from vault resource-management permissions. The current need is: A user can view a storage account resource but cannot download its blobs.
Key Vault secrets support controlled retrieval and rotation separate from packaged application code. Its design target is Key Vault secrets. The stated requirement instead concerns: A user can view a storage account resource but cannot download its blobs.
Azure SQL supports Entra authentication and compatible managed identities can eliminate stored SQL secrets. It does not solve the specified Resource RBAC versus data access condition.
The team has justified its Load Balancer internal L4 design with: Use Azure Standard Internal Load Balancer with probes and backend pool. Which statement accurately describes why the approach works?
Azure Load Balancer routes Layer 4 traffic inside a VNet without parsing HTTP URLs. It is material here because a TCP database-proxy cluster needs one private IP balancing connections to multiple healthy nodes.
Network Watcher diagnostic tools identify effective network behavior and filtering decisions. It belongs to Network Watcher diagnosis. The stated architecture instead relies on: Azure Load Balancer routes Layer 4 traffic inside a VNet without parsing HTTP URLs.
Service endpoints keep the platform public endpoint while allowing VNet-based service firewall authorization. That statement describes Service endpoint, while the question asks how Load Balancer internal L4 works: Azure Load Balancer routes Layer 4 traffic inside a VNet without parsing HTTP URLs.
Peering connects VNet address spaces through the Microsoft backbone without creating transitive routing by default. Azure Load Balancer routes Layer 4 traffic inside a VNet without parsing HTTP URLs.
The Azure-to-Azure ASR networking review proposes: Plan ASR recovery VNet, IP addressing, NSGs, routing and DNS before failover. Which Azure behavior is the technical justification for this decision?
Compute replication does not automatically guarantee complete application network reachability. It is material here because replicated VMs boot in the secondary region but application private DNS and subnets are unavailable.
Independent crash-consistent snapshots may not preserve database write ordering across disks. Compute replication does not automatically guarantee complete application network reachability.
RTO is the maximum acceptable restoration duration, not the amount of lost data. Compute replication does not automatically guarantee complete application network reachability.
Geo-redundant vault storage can provide recovery copies in a paired region subject to feature settings. It belongs to Cross-region backup. The stated architecture instead relies on: Compute replication does not automatically guarantee complete application network reachability.
The target environment adopts this approach for SQL offline migration: Use an appropriate offline Azure Database Migration Service path after compatibility review. What property makes it suitable?
Offline migration can simplify cutover when application downtime is acceptable. It is material here because a small SQL database can tolerate a planned maintenance outage for cutover.
Replatforming changes hosting characteristics while preserving most app behavior. Offline migration can simplify cutover when application downtime is acceptable.
Rebuild replaces the application rather than merely moving its binaries. Offline migration can simplify cutover when application downtime is acceptable.
Hidden dependencies can break after migration even when VM replication succeeds. It belongs to Application dependency mapping. The stated architecture instead relies on: Offline migration can simplify cutover when application downtime is acceptable.
For Blob archive rehydration, operations are closing a change that addressed: A seven-year archive is rarely read and recovery can wait hours. Which post-change signal belongs in the acceptance record?
Archive tier minimizes long-term storage cost but archived objects must be rehydrated before reading. Confirm using the measurable result: An archived test object is restored to an online tier within the acceptable window.
Tiering trades storage price against access and retrieval cost based on usage. Those observations validate Blob hot/cool/cold. They do not establish the required Blob archive rehydration result: An archived test object is restored to an online tier within the acceptable window.
Session consistency offers read-your-writes within a session without strong global consistency. The Cosmos session consistency test checks the writing session immediately reads its own update while other sessions may lag; the relevant outcome is An archived test object is restored to an online tier within the acceptable window.
Cosmos DB provides a distributed document database with configurable consistency and throughput. The offered observation would demonstrate Cosmos DB NoSQL: The app reads JSON documents across the planned partitions with predictable latency. The current validation is different: An archived test object is restored to an online tier within the acceptable window.
A solution must address both Web transaction traces and Synthetic uptime. First requirement: Users report failed checkout requests across a multi-tier web app and only CPU graphs are available. Second requirement: A public site sometimes fails before user telemetry is received and operations need outside-in availability tests. Select TWO recommendations that meet these independent needs.
For the Synthetic uptime half of this design, synthetic tests independently probe URL availability and latency even when no real customer transaction occurs. Check: A deliberate endpoint outage is detected from multiple test locations before users file reports. The other half concerns Web transaction traces.
For the Web transaction traces half of this two-part design, application Insights correlates application requests exceptions and downstream dependencies rather than relying only on infrastructure CPU. Verify: A failed transaction trace identifies its failing dependency and correlated exception. The other half concerns Synthetic uptime.
Analytics and longer-term retention options have different query and storage cost characteristics. That plan is appropriate for Log retention tiers. The two controls sought here are Web transaction traces and Synthetic uptime.
VM insights and the agent collect supported guest operating-system counters and process data. Its own validation would be: Per-VM guest memory and disk metrics appear with host identity in Azure Monitor. The current paired requirement is Web transaction traces and Synthetic uptime.
Virtual network flow logs represent observed network flows and Traffic Analytics derives traffic insights. The corresponding task is Network-flow telemetry: Network engineers require VNet-level flow visibility for troubleshooting east-west connections without packet capture. It is not one of the two requested controls (Web transaction traces and Synthetic uptime).
A solution must address both Shared workload identity and Workload identity federation. First requirement: Two Functions apps need the same persistent workload identity even when one app is recreated. Second requirement: A CI/CD job in GitHub Actions must deploy Azure resources without storing a long-lived service principal secret. Select TWO recommendations that meet these independent needs.
For the Workload identity federation half of this design, federated credentials exchange trusted external OIDC assertions for Entra access tokens. Check: An approved pipeline deploys without a stored client secret and an untrusted subject is rejected. The other half concerns Shared workload identity.
For the Shared workload identity half of this two-part design, a user-assigned identity has a lifecycle separate from each consuming Azure resource. Verify: Both functions access the approved store and identity remains after one app is replaced. The other half concerns Workload identity federation.
Azure Files can integrate with supported directory-based SMB authentication while share and NTFS ACLs govern access. Its own validation would be: Approved domain users mount the share and unauthorized users fail the access test. The current paired requirement is Shared workload identity and Workload identity federation.
Key Vault keys can perform cryptographic operations while restricting private key exposure. This alternative solves Key Vault cryptographic signing, while the question separately requires Shared workload identity and Workload identity federation.
Key Vault secrets support controlled retrieval and rotation separate from packaged application code. That plan is appropriate for Key Vault secrets. The two controls sought here are Shared workload identity and Workload identity federation.
For the Event Hubs telemetry requirement, the proposed architecture uses: Use Event Hubs partitions and consumer groups for streaming ingestion. Why does that design fit?
Event Hubs provides a replayable ordered stream within partitions for large event volumes. It is material here because thousands of kiosks upload constant high-volume telemetry that several analytic consumers replay.
At-least-once message delivery requires application logic to deduplicate business side effects. Event Hubs provides a replayable ordered stream within partitions for large event volumes.
Shared session state survives an individual stateless app worker replacement. Event Hubs provides a replayable ordered stream within partitions for large event volumes.
Durable orchestrations checkpoint progress and coordinate stateful serverless workflows. That statement describes Durable Functions orchestration, while the question asks how Event Hubs telemetry works: Event Hubs provides a replayable ordered stream within partitions for large event volumes.
To validate the Blob HNS namespace deployment, reviewers revisit this operational need: Analytics engines require directory-aware ACLs and atomic directory rename semantics over object storage. What result confirms it was met?
ADLS Gen2 adds directory semantics and access ACLs to blob-backed storage. Confirm using the measurable result: A Spark user renames an eligible directory atomically and directory ACLs are enforced.
Autoscale adjusts provisioned RU/s capacity according to measured load within a maximum. Those observations validate Cosmos autoscale. They do not establish the required Blob HNS namespace result: A Spark user renames an eligible directory atomically and directory ACLs are enforced.
NetApp Files offers enterprise file protocols and performance controls for supported workloads. The distinguishing check is: A Spark user renames an eligible directory atomically and directory ACLs are enforced.
An in-memory cache reduces repeated origin queries when staleness and invalidation are controlled. The Azure Cache for Redis test checks cache hits reduce SQL query volume and expired entries refresh correctly; the relevant outcome is A Spark user renames an eligible directory atomically and directory ACLs are enforced.
An architect must sign off on Migration landing zone. The business problem is: A program plans 100 app moves but lacks identity, DNS, governance and network foundations. What observed test result provides valid evidence?
Landing-zone foundations provide policy, connectivity and subscription placement for incoming workloads. Confirm using the measurable result: The first migrated app uses approved network, DNS and access standards.
Object count alone cannot establish content integrity or ACL preservation. The distinguishing check is: The first migrated app uses approved network, DNS and access standards.
PostgreSQL migration requires extension, version and connectivity compatibility checks. The PostgreSQL migration test checks the database app passes read/write tests against the target flexible server; the relevant outcome is The first migrated app uses approved network, DNS and access standards.
Physical migration requires source capture and replication methods different from VMware agentless VM migration. The offered observation would demonstrate Physical server migration: A cutover VM starts in Azure with its application settings preserved. The current validation is different: The first migrated app uses approved network, DNS and access standards.
An architect must sign off on Networking cutover DNS. The business problem is: A migrated app uses a new Azure IP but clients have a hardcoded old DNS endpoint. What observed test result provides valid evidence?
DNS cutover requires propagation and dependency planning independent of VM replication. Confirm using the measurable result: Clients resolve the new endpoint and the rollback procedure returns traffic if needed.
Target compatibility determines whether code changes or a different managed target are required. The Database schema assessment test checks the assessment reports blocking SQL features and chosen remediation before migration; the relevant outcome is Clients resolve the new endpoint and the rollback procedure returns traffic if needed.
Refactoring changes application structure and decouples independent workloads. The offered observation would demonstrate Refactor monolith: One service can scale independently and failures are isolated through messaging. The current validation is different: Clients resolve the new endpoint and the rollback procedure returns traffic if needed.
Server migration replication supports lift-and-shift of eligible VM workloads to Azure. Those observations validate VM agentless migration. They do not establish the required Networking cutover DNS result: Clients resolve the new endpoint and the rollback procedure returns traffic if needed.
Please check your mailbox for a message from support@examlabs.com and follow the directions.