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 solution must address both Cosmos partition key and Blob user-delegation SAS. First requirement: A Cosmos container uses a low-cardinality partition key and has hot-partition throttling. Second requirement: A partner needs time-limited upload permission to a particular blob without sharing the storage account key. Select TWO recommendations that meet these independent needs.
For the Cosmos partition key half of this two-part design, partition key distribution governs data/throughput placement and query efficiency. Verify: RU consumption distributes across partitions and the query includes its expected partition key. The other half concerns Blob user-delegation SAS.
For the Blob user-delegation SAS half of this design, a user-delegation SAS is authorized through Entra credentials and avoids distributing account keys. Check: The permitted upload works before expiry while an unauthorized operation and expired token fail. The other half concerns Cosmos partition key.
Session consistency offers read-your-writes within a session without strong global consistency. Its own validation would be: The writing session immediately reads its own update while other sessions may lag. The current paired requirement is Cosmos partition key and Blob user-delegation SAS.
Archive tier minimizes long-term storage cost but archived objects must be rehydrated before reading. This alternative solves Blob archive rehydration, while the question separately requires Cosmos partition key and Blob user-delegation SAS.
Autoscale adjusts provisioned RU/s capacity according to measured load within a maximum. The corresponding task is Cosmos autoscale: An API's Cosmos traffic varies tenfold through the day and manually fixed throughput is wasteful. It is not one of the two requested controls (Cosmos partition key and Blob user-delegation SAS).
A seven-year archive is rarely read and recovery can wait hours. A deployment must satisfy this operational criterion: An archived test object is restored to an online tier within the acceptable window. Which plan is appropriate?
Archive tier minimizes long-term storage cost but archived objects must be rehydrated before reading. The selected architecture is use Blob Archive tier for eligible block blobs with documented rehydration delay; confirm the result by checking that an archived test object is restored to an online tier within the acceptable window.
Managed disks provide block storage to Azure VMs rather than object or SMB interfaces. The relevant requirement is: A seven-year archive is rarely read and recovery can wait hours.
Directory ACLs provide path-level data authorization when hierarchical namespace is enabled. It does not solve the specified Blob archive rehydration condition.
Concurrent writes require a conflict resolution policy to prevent unintended last-writer outcomes. Its design target is Cosmos conflict handling. The stated requirement instead concerns: A seven-year archive is rarely read and recovery can wait hours.
A business unit must prevent unapproved public IP resources but permit private network components. Choose the architecture that can be validated by this result: A public IP create is denied while a private subnet deployment proceeds.
Azure Policy can deny targeted resource types without revoking all contributor operations. The selected architecture is assign a policy that disallows specified resource types or properties at the unit scope; confirm the result by checking that a public IP create is denied while a private subnet deployment proceeds.
Resource groups provide a deployment and management boundary and facilitate cohesive cleanup. The current need is: A business unit must prevent unapproved public IP resources but permit private network components.
Policy evaluates resource deployment properties and rejects noncompliant regions. That is useful for Allowed regions (Data sovereignty policy forbids new resources outside a small list of approved Azure regions). It does not meet the current Resource type restriction requirement: A business unit must prevent unapproved public IP resources but permit private network components.
Defender for Cloud aggregates recommendations and compliance state for supported frameworks. It does not solve the specified Resource type restriction condition.
The Blob versioning review proposes: Enable Blob versioning with retention controls. Which Azure behavior is the technical justification for this decision?
Versioning preserves older object versions independently of current content overwrites. It is material here because a file is frequently overwritten and teams need to restore the value before the last upload.
Bounded staleness constrains replication read lag according to allowed versions/time. That statement describes Cosmos bounded staleness, while the question asks how Blob versioning works: Versioning preserves older object versions independently of current content overwrites.
An in-memory cache reduces repeated origin queries when staleness and invalidation are controlled. Versioning preserves older object versions independently of current content overwrites.
Soft delete retains recoverable deleted objects or containers during the configured period. Versioning preserves older object versions independently of current content overwrites.
A proposed solution for ADF incremental copy is: Implement watermark-based incremental ingestion with persisted checkpoints. Select the strongest statement supporting the recommendation.
A stored watermark limits reads to changes after the last successful processed interval. It is material here because only rows changed since the last successful extraction should be copied from a large source database.
Self-hosted integration runtime initiates supported outbound communications to access private sources. A stored watermark limits reads to changes after the last successful processed interval.
OneLake offers a common analytics data foundation for supported Fabric workloads. A stored watermark limits reads to changes after the last successful processed interval.
Hybrid/private integration requires a reachable private network path rather than open public DB exposure. It belongs to Private integration access. The stated architecture instead relies on: A stored watermark limits reads to changes after the last successful processed interval.
The acceptance criterion for AKS pod disruption budget comes from this issue: Cluster upgrades evict all replicas of an API despite multiple healthy nodes. Which measured outcome is the strongest proof?
PDBs constrain voluntary disruptions but do not prevent all involuntary failures. Confirm using the measurable result: A planned node drain leaves the minimum healthy pod count running.
A zone-separated standby supports automated failover where offered. The offered observation would demonstrate PostgreSQL zone redundant HA: After a zone failure the managed standby serves database connections. The current validation is different: A planned node drain leaves the minimum healthy pod count running.
This is a resilience drill for losing an entire availability zone, not the PodDisruptionBudget check for a voluntary node drain. Zone failure can remove pods involuntarily; PDB settings alone cannot establish node-pool recovery across zones.
Front Door provides global application delivery and HTTP(S) origin failover at the edge. The Front Door global failover test checks requests shift to healthy origin after simulated regional endpoint failure; the relevant outcome is A planned node drain leaves the minimum healthy pod count running.
A service team needs a narrow set of resource restart and read operations absent from built-in roles. A deployment must satisfy this operational criterion: The operator restarts an approved service and cannot modify resource access assignments. Which plan is appropriate?
Custom role actions can grant specific management operations without broad Contributor rights. The selected architecture is create a least-privilege custom Azure RBAC role and assign it at minimal scope; confirm the result by checking that the operator restarts an approved service and cannot modify resource access assignments.
Policy deny or audit effects can enforce required metadata at supported resource scopes. That is useful for Required tag policy (Cost reporting is missing the billing cost center tag on newly created resources). It does not meet the current RBAC custom role requirement: A service team needs a narrow set of resource restart and read operations absent from built-in roles.
Management groups supply governance scope above subscriptions without moving resources into a single subscription. Its design target is Management group hierarchy. The stated requirement instead concerns: A service team needs a narrow set of resource restart and read operations absent from built-in roles.
Azure Policy can deny targeted resource types without revoking all contributor operations. It does not solve the specified RBAC custom role condition.
A legacy Windows application needs a shared SMB file path used by multiple virtual machines. Identify the most suitable implementation for an outcome where the application opens the shared UNC path from authorized machines.
Azure Files provides managed SMB file shares whereas Blob Storage is object-oriented. The selected architecture is use Azure Files SMB shares with supported identity integration; confirm the result by checking that the application opens the shared UNC path from authorized machines.
Partition key distribution governs data/throughput placement and query efficiency. Its design target is Cosmos partition key. The stated requirement instead concerns: A legacy Windows application needs a shared SMB file path used by multiple virtual machines.
Premium SSD v2 decouples some provisioned performance settings from disk capacity. It does not solve the specified Azure Files SMB condition.
Session consistency offers read-your-writes within a session without strong global consistency. The current need is: A legacy Windows application needs a shared SMB file path used by multiple virtual machines.
For Required tag policy, operations are closing a change that addressed: Cost reporting is missing the billing cost center tag on newly created resources. Which post-change signal belongs in the acceptance record?
Policy deny or audit effects can enforce required metadata at supported resource scopes. Confirm using the measurable result: An untagged deployment is denied or audited as configured and tagged deployment succeeds.
Audit effects collect compliance findings without blocking resource creation. The Policy audit versus deny test checks noncompliant deployment is logged during pilot but rejected after approved enforcement; the relevant outcome is An untagged deployment is denied or audited as configured and tagged deployment succeeds.
Consistent metadata simplifies inventory grouping and cost ownership without changing resources' technical capabilities. The offered observation would demonstrate Resource naming governance: A resource inventory export resolves owner and environment for every managed resource. The current validation is different: An untagged deployment is denied or audited as configured and tagged deployment succeeds.
Modify effects can update eligible metadata and require the required remediation permissions. The distinguishing check is: An untagged deployment is denied or audited as configured and tagged deployment succeeds.
The team has justified its Recovery drill governance design with: Schedule an isolated test failover with results and remediation records. Which statement accurately describes why the approach works?
A non-disruptive DR test validates recovery sequences and dependencies before a real disaster. It is material here because auditors require evidence that a disaster recovery plan works without disrupting production traffic.
RPO measures the maximum tolerated data loss period at a recovery point. A non-disruptive DR test validates recovery sequences and dependencies before a real disaster.
Multi-user authorization separates approval boundaries for critical backup changes. It belongs to Multifactor critical operations. The stated architecture instead relies on: A non-disruptive DR test validates recovery sequences and dependencies before a real disaster.
Immutable backup settings can prevent specified destructive operations against protected backups. That statement describes Vault immutability, while the question asks how Recovery drill governance works: A non-disruptive DR test validates recovery sequences and dependencies before a real disaster.
For RBAC custom role, operations are closing a change that addressed: A service team needs a narrow set of resource restart and read operations absent from built-in roles. Which post-change signal belongs in the acceptance record?
Custom role actions can grant specific management operations without broad Contributor rights. Confirm using the measurable result: The operator restarts an approved service and cannot modify resource access assignments.
Azure service quotas are often scoped by subscription and region and can constrain deployability. Those observations validate Quotas and limits. They do not establish the required RBAC custom role result: The operator restarts an approved service and cannot modify resource access assignments.
DeployIfNotExists requires remediation for already deployed resources where appropriate. The distinguishing check is: The operator restarts an approved service and cannot modify resource access assignments.
Policy evaluates resource deployment properties and rejects noncompliant regions. The offered observation would demonstrate Allowed regions: A forbidden-region deployment is denied and an allowed-region deployment succeeds. The current validation is different: The operator restarts an approved service and cannot modify resource access assignments.
Please check your mailbox for a message from support@examlabs.com and follow the directions.