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 63

Question 620

At Cedarbank Payments retained transaction exports require defined regional resilience. Which shortcut most directly threatens the intended data outcome?

  1. Assume locally redundant copies within one site protect against every regional disaster.
  2. Provision throughput based only on storage capacity without testing query complexity.
  3. Publish a perpetual account-level SAS with write and delete rights for a one-file download.
  4. Put all high-volume independent tenants into one constant partition key without considering load.

Answer & Explanations

Correct answer: A

A.

Assume locally redundant copies within one site protect against every regional disaster. The scenario is: At Cedarbank Payments retained transaction exports require defined regional resilience. This undermines the mechanism: LRS, ZRS and geographically redundant options provide different replica placement and disaster-protection properties. Instead: Choose appropriate Azure Storage redundancy based on durability, availability and geographic recovery requirements.

B.

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 Cedarbank Payments retained transaction exports require defined regional resilience—reject: Assume locally redundant copies within one site protect against every regional disaster. The safer response is: Choose appropriate Azure Storage redundancy based on durability, availability and geographic recovery requirements.

C.

Publish a perpetual account-level SAS with write and delete rights for a one-file download. This concerns another issue: At Silverlake Media a partner needs temporary read access to one approved asset. In the stated case—At Cedarbank Payments retained transaction exports require defined regional resilience—reject: Assume locally redundant copies within one site protect against every regional disaster. The safer response is: Choose appropriate Azure Storage redundancy based on durability, availability and geographic recovery requirements.

D.

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 Cedarbank Payments retained transaction exports require defined regional resilience—reject: Assume locally redundant copies within one site protect against every regional disaster. The safer response is: Choose appropriate Azure Storage redundancy based on durability, availability and geographic recovery requirements.

Question 621

At Westport Research backups must survive a documented site-level failure scenario. Which design or Azure data approach best fits this requirement?

  1. Choose appropriate Azure Storage redundancy based on durability, availability and geographic recovery requirements.
  2. Pick sensible partition keys for Table Storage based on common access patterns and partition distribution.
  3. Move long-term rarely accessed backups to archive tier only when rehydration delays are acceptable.
  4. Choose Azure Cosmos DB for globally distributed document applications with defined latency and consistency needs.

Answer & Explanations

Correct answer: A

A.

Choose appropriate Azure Storage redundancy based on durability, availability and geographic recovery requirements. This works because: LRS, ZRS and geographically redundant options provide different replica placement and disaster-protection properties. The scenario is: At Westport Research backups must survive a documented site-level failure scenario. Verify the outcome by: Review a fictional availability requirement and confirm the selected redundancy option matches its scope.

B.

Pick sensible partition keys for Table Storage based on common access patterns and partition distribution. This addresses a different situation: At Pineport Logistics each region has a large independent group of shipment metadata records. The present case is: At Westport Research backups must survive a documented site-level failure scenario. The relevant action here is: Choose appropriate Azure Storage redundancy based on durability, availability and geographic recovery requirements.

C.

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 Westport Research backups must survive a documented site-level failure scenario. The relevant action here is: Choose appropriate Azure Storage redundancy based on durability, availability and geographic recovery requirements.

D.

Choose Azure Cosmos DB for globally distributed document applications with defined latency and consistency needs. This addresses a different situation: At Silverbrook Commerce customers in several continents update shopping preferences. The present case is: At Westport Research backups must survive a documented site-level failure scenario. The relevant action here is: Choose appropriate Azure Storage redundancy based on durability, availability and geographic recovery requirements.

Question 622

At Westport Research backups must survive a documented site-level failure scenario. The team proposes this approach: Choose appropriate Azure Storage redundancy based on durability, availability and geographic recovery requirements. Which technical principle explains the choice?

  1. Partition keys determine entity grouping and affect efficient lookup and potential hot partitions.
  2. Consistency choices trade visibility guarantees, availability and latency; stronger guarantees may be essential for some decisions.
  3. Blob Storage is object storage designed for unstructured content, independently of relational table structures.
  4. LRS, ZRS and geographically redundant options provide different replica placement and disaster-protection properties.

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 Westport Research backups must survive a documented site-level failure scenario. The actual mechanism is: LRS, ZRS and geographically redundant options provide different replica placement and disaster-protection properties.

B.

Consistency choices trade visibility guarantees, availability and latency; stronger guarantees may be essential for some decisions. That explains a separate situation: At Silverline Events a newly reserved seat must have a carefully defined visibility guarantee. The current case is: At Westport Research backups must survive a documented site-level failure scenario. The actual mechanism is: LRS, ZRS and geographically redundant options provide different replica placement and disaster-protection properties.

C.

Blob Storage is object storage designed for unstructured content, independently of relational table structures. That explains a separate situation: At Harborcrest Media hundreds of thousands of images need private object storage. The current case is: At Westport Research backups must survive a documented site-level failure scenario. The actual mechanism is: LRS, ZRS and geographically redundant options provide different replica placement and disaster-protection properties.

D.

LRS, ZRS and geographically redundant options provide different replica placement and disaster-protection properties. This principle supports the intervention: Choose appropriate Azure Storage redundancy based on durability, availability and geographic recovery requirements. The relevant scenario is: At Westport Research backups must survive a documented site-level failure scenario. Verify the result by: Review a fictional availability requirement and confirm the selected redundancy option matches its scope.

Question 623

At Westport Research backups must survive a documented site-level failure scenario. After implementing this approach—Choose appropriate Azure Storage redundancy based on durability, availability and geographic recovery requirements—which result would most directly confirm success?

  1. Review a fictional availability requirement and confirm the selected redundancy option matches its scope.
  2. Query one tenant's fictional records by partition and row key while measuring request behavior.
  3. Write a synthetic value and test subsequent reads across configured clients and regions.
  4. Organize fictional partitioned data under dated directories and verify directory-level move or access behavior.

Answer & Explanations

Correct answer: A

A.

Review a fictional availability requirement and confirm the selected redundancy option matches its scope. This tests the targeted action: Choose appropriate Azure Storage redundancy based on durability, availability and geographic recovery requirements. The reason is: LRS, ZRS and geographically redundant options provide different replica placement and disaster-protection properties. The reported case is: At Westport Research backups must survive a documented site-level failure scenario.

B.

Query one tenant's fictional records by partition and row key while measuring request behavior. This tests a separate situation: At Pineport Logistics each region has a large independent group of shipment metadata records. The observed case is: At Westport Research backups must survive a documented site-level failure scenario. Use this acceptance check instead: Review a fictional availability requirement and confirm the selected redundancy option matches its scope.

C.

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 Westport Research backups must survive a documented site-level failure scenario. Use this acceptance check instead: Review a fictional availability requirement and confirm the selected redundancy option matches its scope.

D.

Organize fictional partitioned data under dated directories and verify directory-level move or access behavior. This tests a separate situation: At Oakridge Analytics Spark jobs work with folder-based lake partitions. The observed case is: At Westport Research backups must survive a documented site-level failure scenario. Use this acceptance check instead: Review a fictional availability requirement and confirm the selected redundancy option matches its scope.

Question 624

At Westport Research backups must survive a documented site-level failure scenario. Which shortcut most directly threatens the intended data outcome?

  1. Put every large image into an Azure Table Storage entity expecting full binary-object semantics.
  2. Re-export the entire container for every notification and assume no duplicate updates can occur.
  3. Assume locally redundant copies within one site protect against every regional disaster.
  4. Grant ordinary application users delete rights to all archived compliance evidence.

Answer & Explanations

Correct answer: C

A.

Put every large image into an Azure Table Storage entity expecting full binary-object semantics. This concerns another issue: At Harborcrest Media hundreds of thousands of images need private object storage. In the stated case—At Westport Research backups must survive a documented site-level failure scenario—reject: Assume locally redundant copies within one site protect against every regional disaster. The safer response is: Choose appropriate Azure Storage redundancy based on durability, availability and geographic recovery requirements.

B.

Re-export the entire container for every notification and assume no duplicate updates can occur. This concerns another issue: At Harborview Retail inventory changes feed a search-index updater. In the stated case—At Westport Research backups must survive a documented site-level failure scenario—reject: Assume locally redundant copies within one site protect against every regional disaster. The safer response is: Choose appropriate Azure Storage redundancy based on durability, availability and geographic recovery requirements.

C.

Assume locally redundant copies within one site protect against every regional disaster. The scenario is: At Westport Research backups must survive a documented site-level failure scenario. This undermines the mechanism: LRS, ZRS and geographically redundant options provide different replica placement and disaster-protection properties. Instead: Choose appropriate Azure Storage redundancy based on durability, availability and geographic recovery requirements.

D.

Grant ordinary application users delete rights to all archived compliance evidence. This concerns another issue: At Harborland Securities trade evidence requires enforced retention. In the stated case—At Westport Research backups must survive a documented site-level failure scenario—reject: Assume locally redundant copies within one site protect against every regional disaster. The safer response is: Choose appropriate Azure Storage redundancy based on durability, availability and geographic recovery requirements.

Question 625

At Harborland Securities trade evidence requires enforced retention. Which design or Azure data approach best fits this requirement?

  1. Move long-term rarely accessed backups to archive tier only when rehydration delays are acceptable.
  2. Use immutable blob policies when regulated records must be protected from alteration or deletion during retention.
  3. Use lifecycle management rules to transition eligible Azure blobs between tiers based on age or access needs.
  4. Use a point read with both ID and partition key when a known Cosmos DB item must be retrieved efficiently.

Answer & Explanations

Correct answer: B

A.

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 Harborland Securities trade evidence requires enforced retention. The relevant action here is: Use immutable blob policies when regulated records must be protected from alteration or deletion during retention.

B.

Use immutable blob policies when regulated records must be protected from alteration or deletion during retention. This works because: WORM-style immutable storage controls restrict modifications or deletions according to configured retention or hold settings. The scenario is: At Harborland Securities trade evidence requires enforced retention. Verify the outcome by: Attempt a controlled deletion of a test retained object and verify policy prevents it.

C.

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

D.

Use a point read with both ID and partition key when a known Cosmos DB item must be retrieved efficiently. This addresses a different situation: At Cedarbrook Finance an application looks up one invoice document by known keys. The present case is: At Harborland Securities trade evidence requires enforced retention. The relevant action here is: Use immutable blob policies when regulated records must be protected from alteration or deletion during retention.

Question 626

At Harborland Securities trade evidence requires enforced retention. The team proposes this approach: Use immutable blob policies when regulated records must be protected from alteration or deletion during retention. Which technical principle explains the choice?

  1. Blob Storage is object storage designed for unstructured content, independently of relational table structures.
  2. WORM-style immutable storage controls restrict modifications or deletions according to configured retention or hold settings.
  3. Table Storage stores schemaless entities addressed by their PartitionKey and RowKey rather than relational joins.
  4. Consistency choices trade visibility guarantees, availability and latency; stronger guarantees may be essential for some decisions.

Answer & Explanations

Correct answer: B

A.

Blob Storage is object storage designed for unstructured content, independently of relational table structures. That explains a separate situation: At Harborcrest Media hundreds of thousands of images need private object storage. The current case is: At Harborland Securities trade evidence requires enforced retention. The actual mechanism is: WORM-style immutable storage controls restrict modifications or deletions according to configured retention or hold settings.

B.

WORM-style immutable storage controls restrict modifications or deletions according to configured retention or hold settings. This principle supports the intervention: Use immutable blob policies when regulated records must be protected from alteration or deletion during retention. The relevant scenario is: At Harborland Securities trade evidence requires enforced retention. Verify the result by: Attempt a controlled deletion of a test retained object and verify policy prevents it.

C.

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 Harborland Securities trade evidence requires enforced retention. The actual mechanism is: WORM-style immutable storage controls restrict modifications or deletions according to configured retention or hold settings.

D.

Consistency choices trade visibility guarantees, availability and latency; stronger guarantees may be essential for some decisions. That explains a separate situation: At Silverline Events a newly reserved seat must have a carefully defined visibility guarantee. The current case is: At Harborland Securities trade evidence requires enforced retention. The actual mechanism is: WORM-style immutable storage controls restrict modifications or deletions according to configured retention or hold settings.

Question 627

At Harborland Securities trade evidence requires enforced retention. After implementing this approach—Use immutable blob policies when regulated records must be protected from alteration or deletion during retention—which result would most directly confirm success?

  1. Simulate tenant traffic and verify the selected key supports efficient reads without one dominant hot key.
  2. Attempt a controlled deletion of a test retained object and verify policy prevents it.
  3. Retrieve an older fictional monthly report directly and compare total expected storage and read costs.
  4. Upload and retrieve a synthetic image while an unauthenticated test request is denied by policy.

Answer & Explanations

Correct answer: B

A.

Simulate tenant traffic and verify the selected key supports efficient reads without one dominant hot key. This tests a separate situation: At Meadowfield Games user profiles are read by unique player ID under heavy load. The observed case is: At Harborland Securities trade evidence requires enforced retention. Use this acceptance check instead: Attempt a controlled deletion of a test retained object and verify policy prevents it.

B.

Attempt a controlled deletion of a test retained object and verify policy prevents it. This tests the targeted action: Use immutable blob policies when regulated records must be protected from alteration or deletion during retention. The reason is: WORM-style immutable storage controls restrict modifications or deletions according to configured retention or hold settings. The reported case is: At Harborland Securities trade evidence requires enforced retention.

C.

Retrieve an older fictional monthly report directly and compare total expected storage and read costs. This tests a separate situation: At Silverbridge Insurance last year's claim attachments are accessed only occasionally. The observed case is: At Harborland Securities trade evidence requires enforced retention. Use this acceptance check instead: Attempt a controlled deletion of a test retained object and verify policy prevents it.

D.

Upload and retrieve a synthetic image while an unauthenticated test request is denied by policy. This tests a separate situation: At Harborcrest Media hundreds of thousands of images need private object storage. The observed case is: At Harborland Securities trade evidence requires enforced retention. Use this acceptance check instead: Attempt a controlled deletion of a test retained object and verify policy prevents it.

Question 628

At Harborland Securities trade evidence requires enforced retention. 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. Grant ordinary application users delete rights to all archived compliance evidence.
  3. Replace an SMB-dependent application's shared drive with a blob URL and expect identical file-lock behavior.
  4. Rename the database endpoint without evaluating driver and operator support.

Answer & Explanations

Correct answer: B

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 Harborland Securities trade evidence requires enforced retention—reject: Grant ordinary application users delete rights to all archived compliance evidence. The safer response is: Use immutable blob policies when regulated records must be protected from alteration or deletion during retention.

B.

Grant ordinary application users delete rights to all archived compliance evidence. The scenario is: At Harborland Securities trade evidence requires enforced retention. This undermines the mechanism: WORM-style immutable storage controls restrict modifications or deletions according to configured retention or hold settings. Instead: Use immutable blob policies when regulated records must be protected from alteration or deletion during retention.

C.

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 Harborland Securities trade evidence requires enforced retention—reject: Grant ordinary application users delete rights to all archived compliance evidence. The safer response is: Use immutable blob policies when regulated records must be protected from alteration or deletion during retention.

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 Harborland Securities trade evidence requires enforced retention—reject: Grant ordinary application users delete rights to all archived compliance evidence. The safer response is: Use immutable blob policies when regulated records must be protected from alteration or deletion during retention.

Question 629

At Cedarpoint Care compliance attachments cannot be rewritten during a legal hold. Which design or Azure data approach best fits this requirement?

  1. Choose appropriate Azure Storage redundancy based on durability, availability and geographic recovery requirements.
  2. Move long-term rarely accessed backups to archive tier only when rehydration delays are acceptable.
  3. Choose the Azure Cosmos DB for NoSQL API when an application uses native JSON item operations and SQL-like queries for documents.
  4. Use immutable blob policies when regulated records must be protected from alteration or deletion during retention.

Answer & Explanations

Correct answer: D

A.

Choose appropriate Azure Storage redundancy based on durability, availability and geographic recovery requirements. This addresses a different situation: At Cedarbank Payments retained transaction exports require defined regional resilience. The present case is: At Cedarpoint Care compliance attachments cannot be rewritten during a legal hold. The relevant action here is: Use immutable blob policies when regulated records must be protected from alteration or deletion during retention.

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 Cedarpoint Care compliance attachments cannot be rewritten during a legal hold. The relevant action here is: Use immutable blob policies when regulated records must be protected from alteration or deletion during retention.

C.

Choose the Azure Cosmos DB for NoSQL API when an application uses native JSON item operations and SQL-like queries for documents. This addresses a different situation: At Cedarfield Apps developers build a new JSON-first profile service. The present case is: At Cedarpoint Care compliance attachments cannot be rewritten during a legal hold. The relevant action here is: Use immutable blob policies when regulated records must be protected from alteration or deletion during retention.

D.

Use immutable blob policies when regulated records must be protected from alteration or deletion during retention. This works because: WORM-style immutable storage controls restrict modifications or deletions according to configured retention or hold settings. The scenario is: At Cedarpoint Care compliance attachments cannot be rewritten during a legal hold. Verify the outcome by: Attempt a controlled deletion of a test retained object and verify policy prevents it.

Question 630

At Cedarpoint Care compliance attachments cannot be rewritten during a legal hold. The team proposes this approach: Use immutable blob policies when regulated records must be protected from alteration or deletion during retention. Which technical principle explains the choice?

  1. Container or item TTL can remove expired records according to the configured lifetime and policy.
  2. A lifecycle policy applies configured conditions to objects rather than requiring ad hoc manual movement.
  3. Management-plane roles and data-access permissions do not automatically mean the same thing, so users need appropriate scoped data access.
  4. WORM-style immutable storage controls restrict modifications or deletions according to configured retention or hold settings.

Answer & Explanations

Correct answer: D

A.

Container or item TTL can remove expired records according to the configured lifetime and policy. That explains a separate situation: At Pinebank Services temporary user sessions must disappear after a defined window. The current case is: At Cedarpoint Care compliance attachments cannot be rewritten during a legal hold. The actual mechanism is: WORM-style immutable storage controls restrict modifications or deletions according to configured retention or hold settings.

B.

A lifecycle policy applies configured conditions to objects rather than requiring ad hoc manual movement. That explains a separate situation: At Westlake Finance statement exports move from hot to cool after an approved interval. The current case is: At Cedarpoint Care compliance attachments cannot be rewritten during a legal hold. The actual mechanism is: WORM-style immutable storage controls restrict modifications or deletions according to configured retention or hold settings.

C.

Management-plane roles and data-access permissions do not automatically mean the same thing, so users need appropriate scoped data access. That explains a separate situation: At Meadowcrest Banking one analytics service reads a restricted statements container. The current case is: At Cedarpoint Care compliance attachments cannot be rewritten during a legal hold. The actual mechanism is: WORM-style immutable storage controls restrict modifications or deletions according to configured retention or hold settings.

D.

WORM-style immutable storage controls restrict modifications or deletions according to configured retention or hold settings. This principle supports the intervention: Use immutable blob policies when regulated records must be protected from alteration or deletion during retention. The relevant scenario is: At Cedarpoint Care compliance attachments cannot be rewritten during a legal hold. Verify the result by: Attempt a controlled deletion of a test retained object and verify policy prevents it.

Microsoft Azure Data Fundamentals (DP-900) Practice Tests