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 64

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.

Question 631

At Cedarpoint Care compliance attachments cannot be rewritten during a legal hold. 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. Insert a fictional JSON profile and execute a supported Cosmos DB for NoSQL query over its fields.
  2. Retrieve a synthetic device entity by both keys and confirm an unrelated partition does not match.
  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: D

A.

Insert a fictional JSON profile and execute a supported Cosmos DB for NoSQL query over its fields. This tests a separate situation: At Cedarfield Apps developers build a new JSON-first profile service. The observed case is: At Cedarpoint Care compliance attachments cannot be rewritten during a legal hold. Use this acceptance check instead: Attempt a controlled deletion of a test retained object and verify policy prevents it.

B.

Retrieve a synthetic device entity by both keys and confirm an unrelated partition does not match. This tests a separate situation: At Harborpoint IoT device status values are accessed by tenant and device ID. The observed case is: At Cedarpoint Care compliance attachments cannot be rewritten during a legal hold. Use this acceptance check instead: Attempt a controlled deletion of a test retained object and verify policy prevents it.

C.

Create test objects with different prefixes and verify only the approved eligible prefix changes tier. This tests a separate situation: At Westlake Finance statement exports move from hot to cool after an approved interval. The observed case is: At Cedarpoint Care compliance attachments cannot be rewritten during a legal hold. Use this acceptance check instead: Attempt a controlled deletion of a test retained object and verify policy prevents it.

D.

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 Cedarpoint Care compliance attachments cannot be rewritten during a legal hold.

Question 632

At Cedarpoint Care compliance attachments cannot be rewritten during a legal hold. Which shortcut most directly threatens the intended data outcome?

  1. Replace an SMB-dependent application's shared drive with a blob URL and expect identical file-lock behavior.
  2. Grant ordinary application users delete rights to all archived compliance evidence.
  3. Design a Table Storage query requiring native arbitrary multi-table joins and foreign keys.
  4. Use the same fixed partition value for all high-volume users to simplify code.

Answer & Explanations

Correct answer: B

A.

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 Cedarpoint Care compliance attachments cannot be rewritten during a legal hold—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 Cedarpoint Care compliance attachments cannot be rewritten during a legal hold. 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.

Design a Table Storage query requiring native arbitrary multi-table joins and foreign keys. This concerns another issue: At Harborpoint IoT device status values are accessed by tenant and device ID. In the stated case—At Cedarpoint Care compliance attachments cannot be rewritten during a legal hold—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.

Use the same fixed partition value for all high-volume users to simplify code. This concerns another issue: At Meadowfield Games user profiles are read by unique player ID under heavy load. In the stated case—At Cedarpoint Care compliance attachments cannot be rewritten during a legal hold—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 633

At Silverbrook Commerce customers in several continents update shopping preferences. Which design or Azure data approach best fits this requirement?

  1. Choose Azure Cosmos DB for globally distributed document applications with defined latency and consistency needs.
  2. Use a time-bounded, narrowly scoped shared access signature when temporary Blob Storage access is required.
  3. Estimate Cosmos DB request-unit throughput for reads, writes and query patterns before provisioning.
  4. Use controlled Cosmos DB indexing policies to match query paths while accounting for write costs.

Answer & Explanations

Correct answer: A

A.

Choose Azure Cosmos DB for globally distributed document applications with defined latency and consistency needs. This works because: Cosmos DB supports managed multi-region distribution for eligible APIs and workloads while design choices affect cost and consistency. The scenario is: At Silverbrook Commerce customers in several continents update shopping preferences. Verify the outcome by: Create a test document and read it from a configured second region under the selected consistency policy.

B.

Use a time-bounded, narrowly scoped shared access signature when temporary Blob Storage access is required. This addresses a different situation: At Silverlake Media a partner needs temporary read access to one approved asset. The present case is: At Silverbrook Commerce customers in several continents update shopping preferences. The relevant action here is: Choose Azure Cosmos DB for globally distributed document applications with defined latency and consistency needs.

C.

Estimate Cosmos DB request-unit throughput for reads, writes and query patterns before provisioning. This addresses a different situation: At Pineport Retail product searches consume more resources than simple ID reads. The present case is: At Silverbrook Commerce customers in several continents update shopping preferences. The relevant action here is: Choose Azure Cosmos DB for globally distributed document applications with defined latency and consistency needs.

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 Silverbrook Commerce customers in several continents update shopping preferences. The relevant action here is: Choose Azure Cosmos DB for globally distributed document applications with defined latency and consistency needs.

Question 634

At Silverbrook Commerce customers in several continents update shopping preferences. The team proposes this approach: Choose Azure Cosmos DB for globally distributed document applications with defined latency and consistency needs. Which technical principle explains the choice?

  1. A lifecycle policy applies configured conditions to objects rather than requiring ad hoc manual movement.
  2. Cosmos DB supports managed multi-region distribution for eligible APIs and workloads while design choices affect cost and consistency.
  3. The NoSQL API addresses JSON items through containers, partition keys and the service's own query model.
  4. API compatibility is a migration consideration and supported features must be confirmed for the chosen Cosmos offering.

Answer & Explanations

Correct answer: B

A.

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 Silverbrook Commerce customers in several continents update shopping preferences. The actual mechanism is: Cosmos DB supports managed multi-region distribution for eligible APIs and workloads while design choices affect cost and consistency.

B.

Cosmos DB supports managed multi-region distribution for eligible APIs and workloads while design choices affect cost and consistency. This principle supports the intervention: Choose Azure Cosmos DB for globally distributed document applications with defined latency and consistency needs. The relevant scenario is: At Silverbrook Commerce customers in several continents update shopping preferences. Verify the result by: Create a test document and read it from a configured second region under the selected consistency policy.

C.

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 Silverbrook Commerce customers in several continents update shopping preferences. The actual mechanism is: Cosmos DB supports managed multi-region distribution for eligible APIs and workloads while design choices affect cost and consistency.

D.

API compatibility is a migration consideration and supported features must be confirmed for the chosen Cosmos offering. That explains a separate situation: At Harborpoint Software an existing document app uses MongoDB clients. The current case is: At Silverbrook Commerce customers in several continents update shopping preferences. The actual mechanism is: Cosmos DB supports managed multi-region distribution for eligible APIs and workloads while design choices affect cost and consistency.

Question 635

At Silverbrook Commerce customers in several continents update shopping preferences. After implementing this approach—Choose Azure Cosmos DB for globally distributed document applications with defined latency and consistency needs—which result would most directly confirm success?

  1. Insert a fictional JSON profile and execute a supported Cosmos DB for NoSQL query over its fields.
  2. Insert a synthetic short-lived session document and verify it expires as intended without removing permanent data.
  3. Open a fictional blob with an allowed test SAS and verify a nonallowed operation or expired token is rejected.
  4. Create a test document and read it from a configured second region under the selected consistency policy.

Answer & Explanations

Correct answer: D

A.

Insert a fictional JSON profile and execute a supported Cosmos DB for NoSQL query over its fields. This tests a separate situation: At Cedarfield Apps developers build a new JSON-first profile service. The observed case is: At Silverbrook Commerce customers in several continents update shopping preferences. Use this acceptance check instead: Create a test document and read it from a configured second region under the selected consistency policy.

B.

Insert a synthetic short-lived session document and verify it expires as intended without removing permanent data. This tests a separate situation: At Pinebank Services temporary user sessions must disappear after a defined window. The observed case is: At Silverbrook Commerce customers in several continents update shopping preferences. Use this acceptance check instead: Create a test document and read it from a configured second region under the selected consistency policy.

C.

Open a fictional blob with an allowed test SAS and verify a nonallowed operation or expired token is rejected. This tests a separate situation: At Silverlake Media a partner needs temporary read access to one approved asset. The observed case is: At Silverbrook Commerce customers in several continents update shopping preferences. Use this acceptance check instead: Create a test document and read it from a configured second region under the selected consistency policy.

D.

Create a test document and read it from a configured second region under the selected consistency policy. This tests the targeted action: Choose Azure Cosmos DB for globally distributed document applications with defined latency and consistency needs. The reason is: Cosmos DB supports managed multi-region distribution for eligible APIs and workloads while design choices affect cost and consistency. The reported case is: At Silverbrook Commerce customers in several continents update shopping preferences.

Question 636

At Silverbrook Commerce customers in several continents update shopping preferences. Which shortcut most directly threatens the intended data outcome?

  1. Assume a relational T-SQL stored procedure runs unchanged against every Cosmos DB API.
  2. Publish a perpetual account-level SAS with write and delete rights for a one-file download.
  3. Assume a single-region local file database automatically delivers globally distributed consistency.
  4. Remove every indexed path even though the production app filters on nested document fields.

Answer & Explanations

Correct answer: C

A.

Assume a relational T-SQL stored procedure runs unchanged against every Cosmos DB API. This concerns another issue: At Cedarfield Apps developers build a new JSON-first profile service. In the stated case—At Silverbrook Commerce customers in several continents update shopping preferences—reject: Assume a single-region local file database automatically delivers globally distributed consistency. The safer response is: Choose Azure Cosmos DB for globally distributed document applications with defined latency and consistency needs.

B.

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 Silverbrook Commerce customers in several continents update shopping preferences—reject: Assume a single-region local file database automatically delivers globally distributed consistency. The safer response is: Choose Azure Cosmos DB for globally distributed document applications with defined latency and consistency needs.

C.

Assume a single-region local file database automatically delivers globally distributed consistency. The scenario is: At Silverbrook Commerce customers in several continents update shopping preferences. This undermines the mechanism: Cosmos DB supports managed multi-region distribution for eligible APIs and workloads while design choices affect cost and consistency. Instead: Choose Azure Cosmos DB for globally distributed document applications with defined latency and consistency needs.

D.

Remove every indexed path even though the production app filters on nested document fields. This concerns another issue: At Silvercrest Logistics rapid telemetry writes rarely query most optional JSON properties. In the stated case—At Silverbrook Commerce customers in several continents update shopping preferences—reject: Assume a single-region local file database automatically delivers globally distributed consistency. The safer response is: Choose Azure Cosmos DB for globally distributed document applications with defined latency and consistency needs.

Question 637

At Meadowport Travel a worldwide itinerary service needs low-latency document reads. Which design or Azure data approach best fits this requirement?

  1. Choose Azure Cosmos DB for globally distributed document applications with defined latency and consistency needs.
  2. Use the Cosmos DB change feed for incremental downstream processing of relevant item changes.
  3. Choose appropriate Azure Storage redundancy based on durability, availability and geographic recovery requirements.
  4. Choose a Cosmos DB partition key that spreads throughput and matches important point-read access patterns.

Answer & Explanations

Correct answer: A

A.

Choose Azure Cosmos DB for globally distributed document applications with defined latency and consistency needs. This works because: Cosmos DB supports managed multi-region distribution for eligible APIs and workloads while design choices affect cost and consistency. The scenario is: At Meadowport Travel a worldwide itinerary service needs low-latency document reads. Verify the outcome by: Create a test document and read it from a configured second region under the selected consistency policy.

B.

Use the Cosmos DB change feed for incremental downstream processing of relevant item changes. This addresses a different situation: At Harborview Retail inventory changes feed a search-index updater. The present case is: At Meadowport Travel a worldwide itinerary service needs low-latency document reads. The relevant action here is: Choose Azure Cosmos DB for globally distributed document applications with defined latency and consistency needs.

C.

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 Meadowport Travel a worldwide itinerary service needs low-latency document reads. The relevant action here is: Choose Azure Cosmos DB for globally distributed document applications with defined latency and consistency needs.

D.

Choose a Cosmos DB partition key that spreads throughput and matches important point-read access patterns. This addresses a different situation: At Meadowfield Games user profiles are read by unique player ID under heavy load. The present case is: At Meadowport Travel a worldwide itinerary service needs low-latency document reads. The relevant action here is: Choose Azure Cosmos DB for globally distributed document applications with defined latency and consistency needs.

Question 638

At Meadowport Travel a worldwide itinerary service needs low-latency document reads. The team proposes this approach: Choose Azure Cosmos DB for globally distributed document applications with defined latency and consistency needs. Which technical principle explains the choice?

  1. Cooler online tiers reduce capacity cost when data is seldom read, subject to minimum duration and access charges.
  2. Cosmos DB supports managed multi-region distribution for eligible APIs and workloads while design choices affect cost and consistency.
  3. API compatibility is a migration consideration and supported features must be confirmed for the chosen Cosmos offering.
  4. Request units measure normalized resource use; complex cross-partition queries cost more than a simple point lookup.

Answer & Explanations

Correct answer: B

A.

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 Meadowport Travel a worldwide itinerary service needs low-latency document reads. The actual mechanism is: Cosmos DB supports managed multi-region distribution for eligible APIs and workloads while design choices affect cost and consistency.

B.

Cosmos DB supports managed multi-region distribution for eligible APIs and workloads while design choices affect cost and consistency. This principle supports the intervention: Choose Azure Cosmos DB for globally distributed document applications with defined latency and consistency needs. The relevant scenario is: At Meadowport Travel a worldwide itinerary service needs low-latency document reads. Verify the result by: Create a test document and read it from a configured second region under the selected consistency policy.

C.

API compatibility is a migration consideration and supported features must be confirmed for the chosen Cosmos offering. That explains a separate situation: At Harborpoint Software an existing document app uses MongoDB clients. The current case is: At Meadowport Travel a worldwide itinerary service needs low-latency document reads. The actual mechanism is: Cosmos DB supports managed multi-region distribution for eligible APIs and workloads while design choices affect cost and consistency.

D.

Request units measure normalized resource use; complex cross-partition queries cost more than a simple point lookup. That explains a separate situation: At Pineport Retail product searches consume more resources than simple ID reads. The current case is: At Meadowport Travel a worldwide itinerary service needs low-latency document reads. The actual mechanism is: Cosmos DB supports managed multi-region distribution for eligible APIs and workloads while design choices affect cost and consistency.

Question 639

At Meadowport Travel a worldwide itinerary service needs low-latency document reads. After implementing this approach—Choose Azure Cosmos DB for globally distributed document applications with defined latency and consistency needs—which result would most directly confirm success?

  1. Fetch a fictional profile by its ID and partition key and compare its request-unit charge with a query scan.
  2. Compare a representative query and insert workload before and after adjusting a test indexing policy.
  3. Create a test document and read it from a configured second region under the selected consistency policy.
  4. Organize fictional partitioned data under dated directories and verify directory-level move or access behavior.

Answer & Explanations

Correct answer: C

A.

Fetch a fictional profile by its ID and partition key and compare its request-unit charge with a query scan. This tests a separate situation: At Cedarbrook Finance an application looks up one invoice document by known keys. The observed case is: At Meadowport Travel a worldwide itinerary service needs low-latency document reads. Use this acceptance check instead: Create a test document and read it from a configured second region under the selected consistency policy.

B.

Compare a representative query and insert workload before and after adjusting a test indexing policy. This tests a separate situation: At Silvercrest Logistics rapid telemetry writes rarely query most optional JSON properties. The observed case is: At Meadowport Travel a worldwide itinerary service needs low-latency document reads. Use this acceptance check instead: Create a test document and read it from a configured second region under the selected consistency policy.

C.

Create a test document and read it from a configured second region under the selected consistency policy. This tests the targeted action: Choose Azure Cosmos DB for globally distributed document applications with defined latency and consistency needs. The reason is: Cosmos DB supports managed multi-region distribution for eligible APIs and workloads while design choices affect cost and consistency. The reported case is: At Meadowport Travel a worldwide itinerary service needs low-latency document reads.

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 Meadowport Travel a worldwide itinerary service needs low-latency document reads. Use this acceptance check instead: Create a test document and read it from a configured second region under the selected consistency policy.

Question 640

At Meadowport Travel a worldwide itinerary service needs low-latency document reads. Which shortcut most directly threatens the intended data outcome?

  1. Re-export the entire container for every notification and assume no duplicate updates can occur.
  2. Assume a relational T-SQL stored procedure runs unchanged against every Cosmos DB API.
  3. Assume a single-region local file database automatically delivers globally distributed consistency.
  4. Publish a perpetual account-level SAS with write and delete rights for a one-file download.

Answer & Explanations

Correct answer: C

A.

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 Meadowport Travel a worldwide itinerary service needs low-latency document reads—reject: Assume a single-region local file database automatically delivers globally distributed consistency. The safer response is: Choose Azure Cosmos DB for globally distributed document applications with defined latency and consistency needs.

B.

Assume a relational T-SQL stored procedure runs unchanged against every Cosmos DB API. This concerns another issue: At Cedarfield Apps developers build a new JSON-first profile service. In the stated case—At Meadowport Travel a worldwide itinerary service needs low-latency document reads—reject: Assume a single-region local file database automatically delivers globally distributed consistency. The safer response is: Choose Azure Cosmos DB for globally distributed document applications with defined latency and consistency needs.

C.

Assume a single-region local file database automatically delivers globally distributed consistency. The scenario is: At Meadowport Travel a worldwide itinerary service needs low-latency document reads. This undermines the mechanism: Cosmos DB supports managed multi-region distribution for eligible APIs and workloads while design choices affect cost and consistency. Instead: Choose Azure Cosmos DB for globally distributed document applications with defined latency and consistency needs.

D.

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 Meadowport Travel a worldwide itinerary service needs low-latency document reads—reject: Assume a single-region local file database automatically delivers globally distributed consistency. The safer response is: Choose Azure Cosmos DB for globally distributed document applications with defined latency and consistency needs.

Microsoft Azure Data Fundamentals (DP-900) Practice Tests