Practice Exams:

Microsoft DP-900 Dumps

EXAM: Microsoft Azure Data Fundamentals
Verified By Experts
Premium Bundle
$40.00
$59.97 $99.97

DP-900 Premium Bundle


  • Premium File 332 Questions & Answers
  • Training Course 32 Lectures
  • Study Guide 672 Pages

Microsoft DP-900 Practice Test 57

Question 560

At Harborline Research immutable experiment archives must be retrievable within a planned lead time. Which shortcut most directly threatens the intended data outcome?

  1. Promise an instant restore from archive without planning rehydration.
  2. Assume every rare-access object must be archived offline even when prompt retrieval is required.
  3. Provision throughput based only on storage capacity without testing query complexity.
  4. Put daily application assets directly into archive tier to minimize storage price alone.

Answer & Explanations

Correct answer: A

A.

Promise an instant restore from archive without planning rehydration. The scenario is: At Harborline Research immutable experiment archives must be retrievable within a planned lead time. This undermines the mechanism: Archived blob data requires rehydration before normal online access and has special retention/cost constraints. Instead: Move long-term rarely accessed backups to archive tier only when rehydration delays are acceptable.

B.

Assume every rare-access object must be archived offline even when prompt retrieval is required. This concerns another issue: At Silverbridge Insurance last year's claim attachments are accessed only occasionally. In the stated case—At Harborline Research immutable experiment archives must be retrievable within a planned lead time—reject: Promise an instant restore from archive without planning rehydration. The safer response is: Move long-term rarely accessed backups to archive tier only when rehydration delays are acceptable.

C.

Provision throughput based only on storage capacity without testing query complexity. This concerns another issue: At Pineport Retail product searches consume more resources than simple ID reads. In the stated case—At Harborline Research immutable experiment archives must be retrievable within a planned lead time—reject: Promise an instant restore from archive without planning rehydration. The safer response is: Move long-term rarely accessed backups to archive tier only when rehydration delays are acceptable.

D.

Put daily application assets directly into archive tier to minimize storage price alone. This concerns another issue: At Pinefield Retail product images are fetched continuously by shoppers. In the stated case—At Harborline Research immutable experiment archives must be retrievable within a planned lead time—reject: Promise an instant restore from archive without planning rehydration. The safer response is: Move long-term rarely accessed backups to archive tier only when rehydration delays are acceptable.

Question 561

At Westlake Finance statement exports move from hot to cool after an approved interval. Which design or Azure data approach best fits this requirement?

  1. Select an appropriate Cosmos DB consistency level based on acceptable stale reads and business semantics.
  2. Use lifecycle management rules to transition eligible Azure blobs between tiers based on age or access needs.
  3. Use immutable blob policies when regulated records must be protected from alteration or deletion during retention.
  4. Store large binary images and backups as blobs in Azure Blob Storage with appropriate container access policies.

Answer & Explanations

Correct answer: B

A.

Select an appropriate Cosmos DB consistency level based on acceptable stale reads and business semantics. This addresses a different situation: At Silverline Events a newly reserved seat must have a carefully defined visibility guarantee. The present case is: At Westlake Finance statement exports move from hot to cool after an approved interval. The relevant action here is: Use lifecycle management rules to transition eligible Azure blobs between tiers based on age or access needs.

B.

Use lifecycle management rules to transition eligible Azure blobs between tiers based on age or access needs. This works because: A lifecycle policy applies configured conditions to objects rather than requiring ad hoc manual movement. The scenario is: At Westlake Finance statement exports move from hot to cool after an approved interval. Verify the outcome by: Create test objects with different prefixes and verify only the approved eligible prefix changes tier.

C.

Use immutable blob policies when regulated records must be protected from alteration or deletion during retention. This addresses a different situation: At Harborland Securities trade evidence requires enforced retention. The present case is: At Westlake Finance statement exports move from hot to cool after an approved interval. The relevant action here is: Use lifecycle management rules to transition eligible Azure blobs between tiers based on age or access needs.

D.

Store large binary images and backups as blobs in Azure Blob Storage with appropriate container access policies. This addresses a different situation: At Harborcrest Media hundreds of thousands of images need private object storage. The present case is: At Westlake Finance statement exports move from hot to cool after an approved interval. The relevant action here is: Use lifecycle management rules to transition eligible Azure blobs between tiers based on age or access needs.

Question 562

At Westlake Finance statement exports move from hot to cool after an approved interval. The team proposes this approach: Use lifecycle management rules to transition eligible Azure blobs between tiers based on age or access needs. Which technical principle explains the choice?

  1. Partition keys determine entity grouping and affect efficient lookup and potential hot partitions.
  2. Cosmos DB automatically indexes data under its policy; excluding unnecessary paths can reduce index maintenance for writes.
  3. Archived blob data requires rehydration before normal online access and has special retention/cost constraints.
  4. A lifecycle policy applies configured conditions to objects rather than requiring ad hoc manual movement.

Answer & Explanations

Correct answer: D

A.

Partition keys determine entity grouping and affect efficient lookup and potential hot partitions. That explains a separate situation: At Pineport Logistics each region has a large independent group of shipment metadata records. The current case is: At Westlake Finance statement exports move from hot to cool after an approved interval. The actual mechanism is: A lifecycle policy applies configured conditions to objects rather than requiring ad hoc manual movement.

B.

Cosmos DB automatically indexes data under its policy; excluding unnecessary paths can reduce index maintenance for writes. That explains a separate situation: At Silvercrest Logistics rapid telemetry writes rarely query most optional JSON properties. The current case is: At Westlake Finance statement exports move from hot to cool after an approved interval. The actual mechanism is: A lifecycle policy applies configured conditions to objects rather than requiring ad hoc manual movement.

C.

Archived blob data requires rehydration before normal online access and has special retention/cost constraints. That explains a separate situation: At Cedarbank Records files legally retained for a decade are rarely requested. The current case is: At Westlake Finance statement exports move from hot to cool after an approved interval. The actual mechanism is: A lifecycle policy applies configured conditions to objects rather than requiring ad hoc manual movement.

D.

A lifecycle policy applies configured conditions to objects rather than requiring ad hoc manual movement. This principle supports the intervention: Use lifecycle management rules to transition eligible Azure blobs between tiers based on age or access needs. The relevant scenario is: At Westlake Finance statement exports move from hot to cool after an approved interval. Verify the result by: Create test objects with different prefixes and verify only the approved eligible prefix changes tier.

Question 563

At Westlake Finance statement exports move from hot to cool after an approved interval. After implementing this approach—Use lifecycle management rules to transition eligible Azure blobs between tiers based on age or access needs—which result would most directly confirm success?

  1. Measure a sample workload with repeated object reads and verify the chosen tier supports required latency.
  2. Write a synthetic value and test subsequent reads across configured clients and regions.
  3. Create test objects with different prefixes and verify only the approved eligible prefix changes tier.
  4. Attempt a controlled deletion of a test retained object and verify policy prevents it.

Answer & Explanations

Correct answer: C

A.

Measure a sample workload with repeated object reads and verify the chosen tier supports required latency. This tests a separate situation: At Pinefield Retail product images are fetched continuously by shoppers. The observed case is: At Westlake Finance statement exports move from hot to cool after an approved interval. Use this acceptance check instead: Create test objects with different prefixes and verify only the approved eligible prefix changes tier.

B.

Write a synthetic value and test subsequent reads across configured clients and regions. This tests a separate situation: At Silverline Events a newly reserved seat must have a carefully defined visibility guarantee. The observed case is: At Westlake Finance statement exports move from hot to cool after an approved interval. Use this acceptance check instead: Create test objects with different prefixes and verify only the approved eligible prefix changes tier.

C.

Create test objects with different prefixes and verify only the approved eligible prefix changes tier. This tests the targeted action: Use lifecycle management rules to transition eligible Azure blobs between tiers based on age or access needs. The reason is: A lifecycle policy applies configured conditions to objects rather than requiring ad hoc manual movement. The reported case is: At Westlake Finance statement exports move from hot to cool after an approved interval.

D.

Attempt a controlled deletion of a test retained object and verify policy prevents it. This tests a separate situation: At Harborland Securities trade evidence requires enforced retention. The observed case is: At Westlake Finance statement exports move from hot to cool after an approved interval. Use this acceptance check instead: Create test objects with different prefixes and verify only the approved eligible prefix changes tier.

Question 564

At Westlake Finance statement exports move from hot to cool after an approved interval. Which shortcut most directly threatens the intended data outcome?

  1. Put all high-volume independent tenants into one constant partition key without considering load.
  2. Rename the database endpoint without evaluating driver and operator support.
  3. Apply immediate deletion across all containers without checking compliance retention.
  4. Assume locally redundant copies within one site protect against every regional disaster.

Answer & Explanations

Correct answer: C

A.

Put all high-volume independent tenants into one constant partition key without considering load. This concerns another issue: At Pineport Logistics each region has a large independent group of shipment metadata records. In the stated case—At Westlake Finance statement exports move from hot to cool after an approved interval—reject: Apply immediate deletion across all containers without checking compliance retention. The safer response is: Use lifecycle management rules to transition eligible Azure blobs between tiers based on age or access needs.

B.

Rename the database endpoint without evaluating driver and operator support. This concerns another issue: At Harborpoint Software an existing document app uses MongoDB clients. In the stated case—At Westlake Finance statement exports move from hot to cool after an approved interval—reject: Apply immediate deletion across all containers without checking compliance retention. The safer response is: Use lifecycle management rules to transition eligible Azure blobs between tiers based on age or access needs.

C.

Apply immediate deletion across all containers without checking compliance retention. The scenario is: At Westlake Finance statement exports move from hot to cool after an approved interval. This undermines the mechanism: A lifecycle policy applies configured conditions to objects rather than requiring ad hoc manual movement. Instead: Use lifecycle management rules to transition eligible Azure blobs between tiers based on age or access needs.

D.

Assume locally redundant copies within one site protect against every regional disaster. This concerns another issue: At Cedarbank Payments retained transaction exports require defined regional resilience. In the stated case—At Westlake Finance statement exports move from hot to cool after an approved interval—reject: Apply immediate deletion across all containers without checking compliance retention. The safer response is: Use lifecycle management rules to transition eligible Azure blobs between tiers based on age or access needs.

Question 565

At Pinecrest Media raw footage archives transition after editorial signoff. Which design or Azure data approach best fits this requirement?

  1. Apply time-to-live settings to automatically expire Cosmos DB items when the application's retention policy permits deletion.
  2. Move long-term rarely accessed backups to archive tier only when rehydration delays are acceptable.
  3. Use lifecycle management rules to transition eligible Azure blobs between tiers based on age or access needs.
  4. Use immutable blob policies when regulated records must be protected from alteration or deletion during retention.

Answer & Explanations

Correct answer: C

A.

Apply time-to-live settings to automatically expire Cosmos DB items when the application's retention policy permits deletion. This addresses a different situation: At Pinebank Services temporary user sessions must disappear after a defined window. The present case is: At Pinecrest Media raw footage archives transition after editorial signoff. The relevant action here is: Use lifecycle management rules to transition eligible Azure blobs between tiers based on age or access needs.

B.

Move long-term rarely accessed backups to archive tier only when rehydration delays are acceptable. This addresses a different situation: At Cedarbank Records files legally retained for a decade are rarely requested. The present case is: At Pinecrest Media raw footage archives transition after editorial signoff. The relevant action here is: Use lifecycle management rules to transition eligible Azure blobs between tiers based on age or access needs.

C.

Use lifecycle management rules to transition eligible Azure blobs between tiers based on age or access needs. This works because: A lifecycle policy applies configured conditions to objects rather than requiring ad hoc manual movement. The scenario is: At Pinecrest Media raw footage archives transition after editorial signoff. Verify the outcome by: Create test objects with different prefixes and verify only the approved eligible prefix changes tier.

D.

Use immutable blob policies when regulated records must be protected from alteration or deletion during retention. This addresses a different situation: At Harborland Securities trade evidence requires enforced retention. The present case is: At Pinecrest Media raw footage archives transition after editorial signoff. The relevant action here is: Use lifecycle management rules to transition eligible Azure blobs between tiers based on age or access needs.

Question 566

At Pinecrest Media raw footage archives transition after editorial signoff. The team proposes this approach: Use lifecycle management rules to transition eligible Azure blobs between tiers based on age or access needs. Which technical principle explains the choice?

  1. A lifecycle policy applies configured conditions to objects rather than requiring ad hoc manual movement.
  2. The NoSQL API addresses JSON items through containers, partition keys and the service's own query model.
  3. WORM-style immutable storage controls restrict modifications or deletions according to configured retention or hold settings.
  4. SAS credentials can grant defined resource operations and expiry without granting the recipient broad storage account administration.

Answer & Explanations

Correct answer: A

A.

A lifecycle policy applies configured conditions to objects rather than requiring ad hoc manual movement. This principle supports the intervention: Use lifecycle management rules to transition eligible Azure blobs between tiers based on age or access needs. The relevant scenario is: At Pinecrest Media raw footage archives transition after editorial signoff. Verify the result by: Create test objects with different prefixes and verify only the approved eligible prefix changes tier.

B.

The NoSQL API addresses JSON items through containers, partition keys and the service's own query model. That explains a separate situation: At Cedarfield Apps developers build a new JSON-first profile service. The current case is: At Pinecrest Media raw footage archives transition after editorial signoff. The actual mechanism is: A lifecycle policy applies configured conditions to objects rather than requiring ad hoc manual movement.

C.

WORM-style immutable storage controls restrict modifications or deletions according to configured retention or hold settings. That explains a separate situation: At Harborland Securities trade evidence requires enforced retention. The current case is: At Pinecrest Media raw footage archives transition after editorial signoff. The actual mechanism is: A lifecycle policy applies configured conditions to objects rather than requiring ad hoc manual movement.

D.

SAS credentials can grant defined resource operations and expiry without granting the recipient broad storage account administration. That explains a separate situation: At Silverlake Media a partner needs temporary read access to one approved asset. The current case is: At Pinecrest Media raw footage archives transition after editorial signoff. The actual mechanism is: A lifecycle policy applies configured conditions to objects rather than requiring ad hoc manual movement.

Question 567

At Pinecrest Media raw footage archives transition after editorial signoff. After implementing this approach—Use lifecycle management rules to transition eligible Azure blobs between tiers based on age or access needs—which result would most directly confirm success?

  1. Run a representative test using the application's MongoDB driver and verify its required operations.
  2. Create test objects with different prefixes and verify only the approved eligible prefix changes tier.
  3. Review a fictional availability requirement and confirm the selected redundancy option matches its scope.
  4. Measure a sample workload with repeated object reads and verify the chosen tier supports required latency.

Answer & Explanations

Correct answer: B

A.

Run a representative test using the application's MongoDB driver and verify its required operations. This tests a separate situation: At Harborpoint Software an existing document app uses MongoDB clients. The observed case is: At Pinecrest Media raw footage archives transition after editorial signoff. Use this acceptance check instead: Create test objects with different prefixes and verify only the approved eligible prefix changes tier.

B.

Create test objects with different prefixes and verify only the approved eligible prefix changes tier. This tests the targeted action: Use lifecycle management rules to transition eligible Azure blobs between tiers based on age or access needs. The reason is: A lifecycle policy applies configured conditions to objects rather than requiring ad hoc manual movement. The reported case is: At Pinecrest Media raw footage archives transition after editorial signoff.

C.

Review a fictional availability requirement and confirm the selected redundancy option matches its scope. This tests a separate situation: At Cedarbank Payments retained transaction exports require defined regional resilience. The observed case is: At Pinecrest Media raw footage archives transition after editorial signoff. Use this acceptance check instead: Create test objects with different prefixes and verify only the approved eligible prefix changes tier.

D.

Measure a sample workload with repeated object reads and verify the chosen tier supports required latency. This tests a separate situation: At Pinefield Retail product images are fetched continuously by shoppers. The observed case is: At Pinecrest Media raw footage archives transition after editorial signoff. Use this acceptance check instead: Create test objects with different prefixes and verify only the approved eligible prefix changes tier.

Question 568

At Pinecrest Media raw footage archives transition after editorial signoff. Which shortcut most directly threatens the intended data outcome?

  1. Grant subscription-wide owner access solely to read a single blob.
  2. Replace an SMB-dependent application's shared drive with a blob URL and expect identical file-lock behavior.
  3. Apply immediate deletion across all containers without checking compliance retention.
  4. Rename the database endpoint without evaluating driver and operator support.

Answer & Explanations

Correct answer: C

A.

Grant subscription-wide owner access solely to read a single blob. This concerns another issue: At Meadowcrest Banking one analytics service reads a restricted statements container. In the stated case—At Pinecrest Media raw footage archives transition after editorial signoff—reject: Apply immediate deletion across all containers without checking compliance retention. The safer response is: Use lifecycle management rules to transition eligible Azure blobs between tiers based on age or access needs.

B.

Replace an SMB-dependent application's shared drive with a blob URL and expect identical file-lock behavior. This concerns another issue: At Meadowfield Accounting two virtual machines share legacy report files through SMB. In the stated case—At Pinecrest Media raw footage archives transition after editorial signoff—reject: Apply immediate deletion across all containers without checking compliance retention. The safer response is: Use lifecycle management rules to transition eligible Azure blobs between tiers based on age or access needs.

C.

Apply immediate deletion across all containers without checking compliance retention. The scenario is: At Pinecrest Media raw footage archives transition after editorial signoff. This undermines the mechanism: A lifecycle policy applies configured conditions to objects rather than requiring ad hoc manual movement. Instead: Use lifecycle management rules to transition eligible Azure blobs between tiers based on age or access needs.

D.

Rename the database endpoint without evaluating driver and operator support. This concerns another issue: At Harborpoint Software an existing document app uses MongoDB clients. In the stated case—At Pinecrest Media raw footage archives transition after editorial signoff—reject: Apply immediate deletion across all containers without checking compliance retention. The safer response is: Use lifecycle management rules to transition eligible Azure blobs between tiers based on age or access needs.

Question 569

At Meadowfield Accounting two virtual machines share legacy report files through SMB. Which design or Azure data approach best fits this requirement?

  1. Use Azure Table Storage for a simple scalable key-attribute store organized by partition and row keys.
  2. Use Azure Files when applications need shared file-system access through supported SMB or NFS rather than object APIs.
  3. Use an appropriate cool or cold blob tier for infrequently accessed but still online objects.
  4. Use controlled Cosmos DB indexing policies to match query paths while accounting for write costs.

Answer & Explanations

Correct answer: B

A.

Use Azure Table Storage for a simple scalable key-attribute store organized by partition and row keys. This addresses a different situation: At Harborpoint IoT device status values are accessed by tenant and device ID. The present case is: At Meadowfield Accounting two virtual machines share legacy report files through SMB. The relevant action here is: Use Azure Files when applications need shared file-system access through supported SMB or NFS rather than object APIs.

B.

Use Azure Files when applications need shared file-system access through supported SMB or NFS rather than object APIs. This works because: Azure Files exposes managed file shares with file-system protocols and compatible directory semantics. The scenario is: At Meadowfield Accounting two virtual machines share legacy report files through SMB. Verify the outcome by: Mount a synthetic file share from two approved hosts and verify both can read a test document.

C.

Use an appropriate cool or cold blob tier for infrequently accessed but still online objects. This addresses a different situation: At Silverbridge Insurance last year's claim attachments are accessed only occasionally. The present case is: At Meadowfield Accounting two virtual machines share legacy report files through SMB. The relevant action here is: Use Azure Files when applications need shared file-system access through supported SMB or NFS rather than object APIs.

D.

Use controlled Cosmos DB indexing policies to match query paths while accounting for write costs. This addresses a different situation: At Silvercrest Logistics rapid telemetry writes rarely query most optional JSON properties. The present case is: At Meadowfield Accounting two virtual machines share legacy report files through SMB. The relevant action here is: Use Azure Files when applications need shared file-system access through supported SMB or NFS rather than object APIs.

Question 570

At Meadowfield Accounting two virtual machines share legacy report files through SMB. The team proposes this approach: Use Azure Files when applications need shared file-system access through supported SMB or NFS rather than object APIs. Which technical principle explains the choice?

  1. Cosmos DB automatically indexes data under its policy; excluding unnecessary paths can reduce index maintenance for writes.
  2. Table Storage stores schemaless entities addressed by their PartitionKey and RowKey rather than relational joins.
  3. Cooler online tiers reduce capacity cost when data is seldom read, subject to minimum duration and access charges.
  4. Azure Files exposes managed file shares with file-system protocols and compatible directory semantics.

Answer & Explanations

Correct answer: D

A.

Cosmos DB automatically indexes data under its policy; excluding unnecessary paths can reduce index maintenance for writes. That explains a separate situation: At Silvercrest Logistics rapid telemetry writes rarely query most optional JSON properties. The current case is: At Meadowfield Accounting two virtual machines share legacy report files through SMB. The actual mechanism is: Azure Files exposes managed file shares with file-system protocols and compatible directory semantics.

B.

Table Storage stores schemaless entities addressed by their PartitionKey and RowKey rather than relational joins. That explains a separate situation: At Harborpoint IoT device status values are accessed by tenant and device ID. The current case is: At Meadowfield Accounting two virtual machines share legacy report files through SMB. The actual mechanism is: Azure Files exposes managed file shares with file-system protocols and compatible directory semantics.

C.

Cooler online tiers reduce capacity cost when data is seldom read, subject to minimum duration and access charges. That explains a separate situation: At Silverbridge Insurance last year's claim attachments are accessed only occasionally. The current case is: At Meadowfield Accounting two virtual machines share legacy report files through SMB. The actual mechanism is: Azure Files exposes managed file shares with file-system protocols and compatible directory semantics.

D.

Azure Files exposes managed file shares with file-system protocols and compatible directory semantics. This principle supports the intervention: Use Azure Files when applications need shared file-system access through supported SMB or NFS rather than object APIs. The relevant scenario is: At Meadowfield Accounting two virtual machines share legacy report files through SMB. Verify the result by: Mount a synthetic file share from two approved hosts and verify both can read a test document.

Microsoft Azure Data Fundamentals (DP-900) Practice Tests