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 70

Question 690

At Harborview Retail inventory changes feed a search-index updater. The team proposes this approach: Use the Cosmos DB change feed for incremental downstream processing of relevant item changes. Which technical principle explains the choice?

  1. Blob Storage is object storage designed for unstructured content, independently of relational table structures.
  2. API compatibility is a migration consideration and supported features must be confirmed for the chosen Cosmos offering.
  3. The change feed exposes eligible ordered changes for consumers without requiring full collection rescans every minute.
  4. A point read targets one item directly and commonly consumes fewer request units than an equivalent broad query.

Answer & Explanations

Correct answer: C

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 Harborview Retail inventory changes feed a search-index updater. The actual mechanism is: The change feed exposes eligible ordered changes for consumers without requiring full collection rescans every minute.

B.

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 Harborview Retail inventory changes feed a search-index updater. The actual mechanism is: The change feed exposes eligible ordered changes for consumers without requiring full collection rescans every minute.

C.

The change feed exposes eligible ordered changes for consumers without requiring full collection rescans every minute. This principle supports the intervention: Use the Cosmos DB change feed for incremental downstream processing of relevant item changes. The relevant scenario is: At Harborview Retail inventory changes feed a search-index updater. Verify the result by: Update a fictional order item and verify the consumer receives the change once under idempotent processing.

D.

A point read targets one item directly and commonly consumes fewer request units than an equivalent broad query. That explains a separate situation: At Cedarbrook Finance an application looks up one invoice document by known keys. The current case is: At Harborview Retail inventory changes feed a search-index updater. The actual mechanism is: The change feed exposes eligible ordered changes for consumers without requiring full collection rescans every minute.

Question 691

At Harborview Retail inventory changes feed a search-index updater. After implementing this approach—Use the Cosmos DB change feed for incremental downstream processing of relevant item changes—which result would most directly confirm success?

  1. Update a fictional order item and verify the consumer receives the change once under idempotent processing.
  2. Retrieve a synthetic device entity by both keys and confirm an unrelated partition does not match.
  3. Fetch a fictional profile by its ID and partition key and compare its request-unit charge with a query scan.
  4. Write a synthetic value and test subsequent reads across configured clients and regions.

Answer & Explanations

Correct answer: A

A.

Update a fictional order item and verify the consumer receives the change once under idempotent processing. This tests the targeted action: Use the Cosmos DB change feed for incremental downstream processing of relevant item changes. The reason is: The change feed exposes eligible ordered changes for consumers without requiring full collection rescans every minute. The reported case is: At Harborview Retail inventory changes feed a search-index updater.

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 Harborview Retail inventory changes feed a search-index updater. Use this acceptance check instead: Update a fictional order item and verify the consumer receives the change once under idempotent processing.

C.

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 Harborview Retail inventory changes feed a search-index updater. Use this acceptance check instead: Update a fictional order item and verify the consumer receives the change once under idempotent processing.

D.

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 Harborview Retail inventory changes feed a search-index updater. Use this acceptance check instead: Update a fictional order item and verify the consumer receives the change once under idempotent processing.

Question 692

At Harborview Retail inventory changes feed a search-index updater. 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. Apply immediate deletion across all containers without checking compliance retention.
  3. Enable an extremely short TTL on all compliance records without reviewing retention obligations.
  4. Assume a relational T-SQL stored procedure runs unchanged against every Cosmos DB API.

Answer & Explanations

Correct answer: A

A.

Re-export the entire container for every notification and assume no duplicate updates can occur. The scenario is: At Harborview Retail inventory changes feed a search-index updater. This undermines the mechanism: The change feed exposes eligible ordered changes for consumers without requiring full collection rescans every minute. Instead: Use the Cosmos DB change feed for incremental downstream processing of relevant item changes.

B.

Apply immediate deletion across all containers without checking compliance retention. This concerns another issue: At Westlake Finance statement exports move from hot to cool after an approved interval. In the stated case—At Harborview Retail inventory changes feed a search-index updater—reject: Re-export the entire container for every notification and assume no duplicate updates can occur. The safer response is: Use the Cosmos DB change feed for incremental downstream processing of relevant item changes.

C.

Enable an extremely short TTL on all compliance records without reviewing retention obligations. This concerns another issue: At Pinebank Services temporary user sessions must disappear after a defined window. In the stated case—At Harborview Retail inventory changes feed a search-index updater—reject: Re-export the entire container for every notification and assume no duplicate updates can occur. The safer response is: Use the Cosmos DB change feed for incremental downstream processing of relevant item changes.

D.

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 Harborview Retail inventory changes feed a search-index updater—reject: Re-export the entire container for every notification and assume no duplicate updates can occur. The safer response is: Use the Cosmos DB change feed for incremental downstream processing of relevant item changes.

Question 693

At Oakcrest Banking updated application statuses trigger an approved analytics pipeline. 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 the Cosmos DB change feed for incremental downstream processing of relevant item changes.
  3. Use immutable blob policies when regulated records must be protected from alteration or deletion during retention.
  4. Use controlled Cosmos DB indexing policies to match query paths while accounting for write costs.

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 Oakcrest Banking updated application statuses trigger an approved analytics pipeline. The relevant action here is: Use the Cosmos DB change feed for incremental downstream processing of relevant item changes.

B.

Use the Cosmos DB change feed for incremental downstream processing of relevant item changes. This works because: The change feed exposes eligible ordered changes for consumers without requiring full collection rescans every minute. The scenario is: At Oakcrest Banking updated application statuses trigger an approved analytics pipeline. Verify the outcome by: Update a fictional order item and verify the consumer receives the change once under idempotent processing.

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 Oakcrest Banking updated application statuses trigger an approved analytics pipeline. The relevant action here is: Use the Cosmos DB change feed for incremental downstream processing of relevant item changes.

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 Oakcrest Banking updated application statuses trigger an approved analytics pipeline. The relevant action here is: Use the Cosmos DB change feed for incremental downstream processing of relevant item changes.

Question 694

At Oakcrest Banking updated application statuses trigger an approved analytics pipeline. The team proposes this approach: Use the Cosmos DB change feed for incremental downstream processing of relevant item changes. Which technical principle explains the choice?

  1. The change feed exposes eligible ordered changes for consumers without requiring full collection rescans every minute.
  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. The NoSQL API addresses JSON items through containers, partition keys and the service's own query model.

Answer & Explanations

Correct answer: A

A.

The change feed exposes eligible ordered changes for consumers without requiring full collection rescans every minute. This principle supports the intervention: Use the Cosmos DB change feed for incremental downstream processing of relevant item changes. The relevant scenario is: At Oakcrest Banking updated application statuses trigger an approved analytics pipeline. Verify the result by: Update a fictional order item and verify the consumer receives the change once under idempotent processing.

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 Oakcrest Banking updated application statuses trigger an approved analytics pipeline. The actual mechanism is: The change feed exposes eligible ordered changes for consumers without requiring full collection rescans every minute.

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 Oakcrest Banking updated application statuses trigger an approved analytics pipeline. The actual mechanism is: The change feed exposes eligible ordered changes for consumers without requiring full collection rescans every minute.

D.

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 Oakcrest Banking updated application statuses trigger an approved analytics pipeline. The actual mechanism is: The change feed exposes eligible ordered changes for consumers without requiring full collection rescans every minute.

Question 695

At Oakcrest Banking updated application statuses trigger an approved analytics pipeline. After implementing this approach—Use the Cosmos DB change feed for incremental downstream processing of relevant item changes—which result would most directly confirm success?

  1. Organize fictional partitioned data under dated directories and verify directory-level move or access behavior.
  2. Update a fictional order item and verify the consumer receives the change once under idempotent processing.
  3. Insert a fictional JSON profile and execute a supported Cosmos DB for NoSQL query over its fields.
  4. Replay a fictional read-write mix and inspect RU consumption and throttling under the chosen throughput mode.

Answer & Explanations

Correct answer: B

A.

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 Oakcrest Banking updated application statuses trigger an approved analytics pipeline. Use this acceptance check instead: Update a fictional order item and verify the consumer receives the change once under idempotent processing.

B.

Update a fictional order item and verify the consumer receives the change once under idempotent processing. This tests the targeted action: Use the Cosmos DB change feed for incremental downstream processing of relevant item changes. The reason is: The change feed exposes eligible ordered changes for consumers without requiring full collection rescans every minute. The reported case is: At Oakcrest Banking updated application statuses trigger an approved analytics pipeline.

C.

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 Oakcrest Banking updated application statuses trigger an approved analytics pipeline. Use this acceptance check instead: Update a fictional order item and verify the consumer receives the change once under idempotent processing.

D.

Replay a fictional read-write mix and inspect RU consumption and throttling under the chosen throughput mode. This tests a separate situation: At Pineport Retail product searches consume more resources than simple ID reads. The observed case is: At Oakcrest Banking updated application statuses trigger an approved analytics pipeline. Use this acceptance check instead: Update a fictional order item and verify the consumer receives the change once under idempotent processing.

Question 696

At Oakcrest Banking updated application statuses trigger an approved analytics pipeline. Which shortcut most directly threatens the intended data outcome?

  1. Run a full container cross-partition query for every known primary-key lookup.
  2. Re-export the entire container for every notification and assume no duplicate updates can occur.
  3. Provision throughput based only on storage capacity without testing query complexity.
  4. Assume locally redundant copies within one site protect against every regional disaster.

Answer & Explanations

Correct answer: B

A.

Run a full container cross-partition query for every known primary-key lookup. This concerns another issue: At Cedarbrook Finance an application looks up one invoice document by known keys. In the stated case—At Oakcrest Banking updated application statuses trigger an approved analytics pipeline—reject: Re-export the entire container for every notification and assume no duplicate updates can occur. The safer response is: Use the Cosmos DB change feed for incremental downstream processing of relevant item changes.

B.

Re-export the entire container for every notification and assume no duplicate updates can occur. The scenario is: At Oakcrest Banking updated application statuses trigger an approved analytics pipeline. This undermines the mechanism: The change feed exposes eligible ordered changes for consumers without requiring full collection rescans every minute. Instead: Use the Cosmos DB change feed for incremental downstream processing of relevant item changes.

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 Oakcrest Banking updated application statuses trigger an approved analytics pipeline—reject: Re-export the entire container for every notification and assume no duplicate updates can occur. The safer response is: Use the Cosmos DB change feed for incremental downstream processing of relevant item changes.

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 Oakcrest Banking updated application statuses trigger an approved analytics pipeline—reject: Re-export the entire container for every notification and assume no duplicate updates can occur. The safer response is: Use the Cosmos DB change feed for incremental downstream processing of relevant item changes.

Question 697

At Pinebank Services temporary user sessions must disappear after a defined window. 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. Select an appropriate Cosmos DB consistency level based on acceptable stale reads and business semantics.
  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 lifecycle management rules to transition eligible Azure blobs between tiers based on age or access needs.

Answer & Explanations

Correct answer: A

A.

Apply time-to-live settings to automatically expire Cosmos DB items when the application's retention policy permits deletion. This works because: Container or item TTL can remove expired records according to the configured lifetime and policy. The scenario is: At Pinebank Services temporary user sessions must disappear after a defined window. Verify the outcome by: Insert a synthetic short-lived session document and verify it expires as intended without removing permanent data.

B.

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 Pinebank Services temporary user sessions must disappear after a defined window. The relevant action here is: Apply time-to-live settings to automatically expire Cosmos DB items when the application's retention policy permits deletion.

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 Pinebank Services temporary user sessions must disappear after a defined window. The relevant action here is: Apply time-to-live settings to automatically expire Cosmos DB items when the application's retention policy permits deletion.

D.

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 Pinebank Services temporary user sessions must disappear after a defined window. The relevant action here is: Apply time-to-live settings to automatically expire Cosmos DB items when the application's retention policy permits deletion.

Question 698

At Pinebank Services temporary user sessions must disappear after a defined window. The team proposes this approach: Apply time-to-live settings to automatically expire Cosmos DB items when the application's retention policy permits deletion. Which technical principle explains the choice?

  1. LRS, ZRS and geographically redundant options provide different replica placement and disaster-protection properties.
  2. Container or item TTL can remove expired records according to the configured lifetime and policy.
  3. Partition-key distribution affects scaling, hot partitions and the need for cross-partition queries.
  4. Cosmos DB supports managed multi-region distribution for eligible APIs and workloads while design choices affect cost and consistency.

Answer & Explanations

Correct answer: B

A.

LRS, ZRS and geographically redundant options provide different replica placement and disaster-protection properties. That explains a separate situation: At Cedarbank Payments retained transaction exports require defined regional resilience. The current case is: At Pinebank Services temporary user sessions must disappear after a defined window. The actual mechanism is: Container or item TTL can remove expired records according to the configured lifetime and policy.

B.

Container or item TTL can remove expired records according to the configured lifetime and policy. This principle supports the intervention: Apply time-to-live settings to automatically expire Cosmos DB items when the application's retention policy permits deletion. The relevant scenario is: At Pinebank Services temporary user sessions must disappear after a defined window. Verify the result by: Insert a synthetic short-lived session document and verify it expires as intended without removing permanent data.

C.

Partition-key distribution affects scaling, hot partitions and the need for cross-partition queries. That explains a separate situation: At Meadowfield Games user profiles are read by unique player ID under heavy load. The current case is: At Pinebank Services temporary user sessions must disappear after a defined window. The actual mechanism is: Container or item TTL can remove expired records according to the configured lifetime and policy.

D.

Cosmos DB supports managed multi-region distribution for eligible APIs and workloads while design choices affect cost and consistency. That explains a separate situation: At Silverbrook Commerce customers in several continents update shopping preferences. The current case is: At Pinebank Services temporary user sessions must disappear after a defined window. The actual mechanism is: Container or item TTL can remove expired records according to the configured lifetime and policy.

Question 699

At Pinebank Services temporary user sessions must disappear after a defined window. After implementing this approach—Apply time-to-live settings to automatically expire Cosmos DB items when the application's retention policy permits deletion—which result would most directly confirm success?

  1. Update a fictional order item and verify the consumer receives the change once under idempotent processing.
  2. Create test objects with different prefixes and verify only the approved eligible prefix changes tier.
  3. Insert a synthetic short-lived session document and verify it expires as intended without removing permanent data.
  4. Replay a fictional read-write mix and inspect RU consumption and throttling under the chosen throughput mode.

Answer & Explanations

Correct answer: C

A.

Update a fictional order item and verify the consumer receives the change once under idempotent processing. This tests a separate situation: At Harborview Retail inventory changes feed a search-index updater. The observed case is: At Pinebank Services temporary user sessions must disappear after a defined window. Use this acceptance check instead: Insert a synthetic short-lived session document and verify it expires as intended without removing permanent data.

B.

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 Pinebank Services temporary user sessions must disappear after a defined window. Use this acceptance check instead: Insert a synthetic short-lived session document and verify it expires as intended without removing permanent data.

C.

Insert a synthetic short-lived session document and verify it expires as intended without removing permanent data. This tests the targeted action: Apply time-to-live settings to automatically expire Cosmos DB items when the application's retention policy permits deletion. The reason is: Container or item TTL can remove expired records according to the configured lifetime and policy. The reported case is: At Pinebank Services temporary user sessions must disappear after a defined window.

D.

Replay a fictional read-write mix and inspect RU consumption and throttling under the chosen throughput mode. This tests a separate situation: At Pineport Retail product searches consume more resources than simple ID reads. The observed case is: At Pinebank Services temporary user sessions must disappear after a defined window. Use this acceptance check instead: Insert a synthetic short-lived session document and verify it expires as intended without removing permanent data.

Question 700

At Pinebank Services temporary user sessions must disappear after a defined window. Which shortcut most directly threatens the intended data outcome?

  1. Treat every eventually consistent replica as guaranteeing immediate read-after-write globally.
  2. Enable an extremely short TTL on all compliance records without reviewing retention obligations.
  3. Replace an SMB-dependent application's shared drive with a blob URL and expect identical file-lock behavior.
  4. Assume a relational T-SQL stored procedure runs unchanged against every Cosmos DB API.

Answer & Explanations

Correct answer: B

A.

Treat every eventually consistent replica as guaranteeing immediate read-after-write globally. This concerns another issue: At Silverline Events a newly reserved seat must have a carefully defined visibility guarantee. In the stated case—At Pinebank Services temporary user sessions must disappear after a defined window—reject: Enable an extremely short TTL on all compliance records without reviewing retention obligations. The safer response is: Apply time-to-live settings to automatically expire Cosmos DB items when the application's retention policy permits deletion.

B.

Enable an extremely short TTL on all compliance records without reviewing retention obligations. The scenario is: At Pinebank Services temporary user sessions must disappear after a defined window. This undermines the mechanism: Container or item TTL can remove expired records according to the configured lifetime and policy. Instead: Apply time-to-live settings to automatically expire Cosmos DB items when the application's retention policy permits deletion.

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 Pinebank Services temporary user sessions must disappear after a defined window—reject: Enable an extremely short TTL on all compliance records without reviewing retention obligations. The safer response is: Apply time-to-live settings to automatically expire Cosmos DB items when the application's retention policy permits deletion.

D.

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 Pinebank Services temporary user sessions must disappear after a defined window—reject: Enable an extremely short TTL on all compliance records without reviewing retention obligations. The safer response is: Apply time-to-live settings to automatically expire Cosmos DB items when the application's retention policy permits deletion.

Microsoft Azure Data Fundamentals (DP-900) Practice Tests