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 71

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.

Question 701

At Meadowport IoT intermediate device readings expire after aggregation. 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. Choose Azure Cosmos DB for globally distributed document applications with defined latency and consistency needs.
  3. Choose the Azure Cosmos DB for NoSQL API when an application uses native JSON item operations and SQL-like queries for documents.
  4. Apply time-to-live settings to automatically expire Cosmos DB items when the application's retention policy permits deletion.

Answer & Explanations

Correct answer: D

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 Meadowport IoT intermediate device readings expire after aggregation. The relevant action here is: Apply time-to-live settings to automatically expire Cosmos DB items when the application's retention policy permits deletion.

B.

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 Meadowport IoT intermediate device readings expire after aggregation. 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 Meadowport IoT intermediate device readings expire after aggregation. 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.

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 Meadowport IoT intermediate device readings expire after aggregation. Verify the outcome by: Insert a synthetic short-lived session document and verify it expires as intended without removing permanent data.

Question 702

At Meadowport IoT intermediate device readings expire after aggregation. 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. Container or item TTL can remove expired records according to the configured lifetime and policy.
  2. Request units measure normalized resource use; complex cross-partition queries cost more than a simple point lookup.
  3. Cosmos DB automatically indexes data under its policy; excluding unnecessary paths can reduce index maintenance for writes.
  4. LRS, ZRS and geographically redundant options provide different replica placement and disaster-protection properties.

Answer & Explanations

Correct answer: A

A.

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 Meadowport IoT intermediate device readings expire after aggregation. Verify the result by: Insert a synthetic short-lived session document and verify it expires as intended without removing permanent data.

B.

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 IoT intermediate device readings expire after aggregation. The actual mechanism is: Container or item TTL can remove expired records according to the configured lifetime and policy.

C.

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 Meadowport IoT intermediate device readings expire after aggregation. The actual mechanism is: Container or item TTL can remove expired records according to the configured lifetime and policy.

D.

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 Meadowport IoT intermediate device readings expire after aggregation. The actual mechanism is: Container or item TTL can remove expired records according to the configured lifetime and policy.

Question 703

At Meadowport IoT intermediate device readings expire after aggregation. 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. Create test objects with different prefixes and verify only the approved eligible prefix changes tier.
  2. Insert a fictional JSON profile and execute a supported Cosmos DB for NoSQL query over its fields.
  3. Insert a synthetic short-lived session document and verify it expires as intended without removing permanent data.
  4. Write a synthetic value and test subsequent reads across configured clients and regions.

Answer & Explanations

Correct answer: C

A.

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 Meadowport IoT intermediate device readings expire after aggregation. Use this acceptance check instead: Insert a synthetic short-lived session document and verify it expires as intended without removing permanent data.

B.

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 Meadowport IoT intermediate device readings expire after aggregation. 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 Meadowport IoT intermediate device readings expire after aggregation.

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 Meadowport IoT intermediate device readings expire after aggregation. Use this acceptance check instead: Insert a synthetic short-lived session document and verify it expires as intended without removing permanent data.

Question 704

At Meadowport IoT intermediate device readings expire after aggregation. Which shortcut most directly threatens the intended data outcome?

  1. Publish a perpetual account-level SAS with write and delete rights for a one-file download.
  2. Assume a single-region local file database automatically delivers globally distributed consistency.
  3. Enable an extremely short TTL on all compliance records without reviewing retention obligations.
  4. Rename the database endpoint without evaluating driver and operator support.

Answer & Explanations

Correct answer: C

A.

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 IoT intermediate device readings expire after aggregation—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.

Assume a single-region local file database automatically delivers globally distributed consistency. This concerns another issue: At Silverbrook Commerce customers in several continents update shopping preferences. In the stated case—At Meadowport IoT intermediate device readings expire after aggregation—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.

C.

Enable an extremely short TTL on all compliance records without reviewing retention obligations. The scenario is: At Meadowport IoT intermediate device readings expire after aggregation. 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.

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 Meadowport IoT intermediate device readings expire after aggregation—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.

Question 705

At Silvercrest Logistics rapid telemetry writes rarely query most optional JSON properties. Which design or Azure data approach best fits this requirement?

  1. Use an appropriate cool or cold blob tier for infrequently accessed but still online objects.
  2. Use controlled Cosmos DB indexing policies to match query paths while accounting for write costs.
  3. Estimate Cosmos DB request-unit throughput for reads, writes and query patterns before provisioning.
  4. Evaluate the Cosmos DB API for MongoDB when an existing application depends on supported MongoDB drivers and query behaviors.

Answer & Explanations

Correct answer: B

A.

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 Silvercrest Logistics rapid telemetry writes rarely query most optional JSON properties. The relevant action here is: Use controlled Cosmos DB indexing policies to match query paths while accounting for write costs.

B.

Use controlled Cosmos DB indexing policies to match query paths while accounting for write costs. This works because: Cosmos DB automatically indexes data under its policy; excluding unnecessary paths can reduce index maintenance for writes. The scenario is: At Silvercrest Logistics rapid telemetry writes rarely query most optional JSON properties. Verify the outcome by: Compare a representative query and insert workload before and after adjusting a test indexing policy.

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 Silvercrest Logistics rapid telemetry writes rarely query most optional JSON properties. The relevant action here is: Use controlled Cosmos DB indexing policies to match query paths while accounting for write costs.

D.

Evaluate the Cosmos DB API for MongoDB when an existing application depends on supported MongoDB drivers and query behaviors. This addresses a different situation: At Harborpoint Software an existing document app uses MongoDB clients. The present case is: At Silvercrest Logistics rapid telemetry writes rarely query most optional JSON properties. The relevant action here is: Use controlled Cosmos DB indexing policies to match query paths while accounting for write costs.

Question 706

At Silvercrest Logistics rapid telemetry writes rarely query most optional JSON properties. The team proposes this approach: Use controlled Cosmos DB indexing policies to match query paths while accounting for write costs. 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. API compatibility is a migration consideration and supported features must be confirmed for the chosen Cosmos offering.
  3. Consistency choices trade visibility guarantees, availability and latency; stronger guarantees may be essential for some decisions.
  4. Blob access tiers trade storage price for retrieval and transaction costs according to access frequency.

Answer & Explanations

Correct answer: A

A.

Cosmos DB automatically indexes data under its policy; excluding unnecessary paths can reduce index maintenance for writes. This principle supports the intervention: Use controlled Cosmos DB indexing policies to match query paths while accounting for write costs. The relevant scenario is: At Silvercrest Logistics rapid telemetry writes rarely query most optional JSON properties. Verify the result by: Compare a representative query and insert workload before and after adjusting a test indexing policy.

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 Silvercrest Logistics rapid telemetry writes rarely query most optional JSON properties. The actual mechanism is: Cosmos DB automatically indexes data under its policy; excluding unnecessary paths can reduce index maintenance for writes.

C.

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 Silvercrest Logistics rapid telemetry writes rarely query most optional JSON properties. The actual mechanism is: Cosmos DB automatically indexes data under its policy; excluding unnecessary paths can reduce index maintenance for writes.

D.

Blob access tiers trade storage price for retrieval and transaction costs according to access frequency. That explains a separate situation: At Pinefield Retail product images are fetched continuously by shoppers. The current case is: At Silvercrest Logistics rapid telemetry writes rarely query most optional JSON properties. The actual mechanism is: Cosmos DB automatically indexes data under its policy; excluding unnecessary paths can reduce index maintenance for writes.

Question 707

At Silvercrest Logistics rapid telemetry writes rarely query most optional JSON properties. After implementing this approach—Use controlled Cosmos DB indexing policies to match query paths while accounting for write costs—which result would most directly confirm success?

  1. Insert a synthetic short-lived session document and verify it expires as intended without removing permanent data.
  2. Replay a fictional read-write mix and inspect RU consumption and throttling under the chosen throughput mode.
  3. Compare a representative query and insert workload before and after adjusting a test indexing policy.
  4. Attempt a controlled deletion of a test retained object and verify policy prevents it.

Answer & Explanations

Correct answer: C

A.

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 Silvercrest Logistics rapid telemetry writes rarely query most optional JSON properties. Use this acceptance check instead: Compare a representative query and insert workload before and after adjusting a test indexing policy.

B.

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 Silvercrest Logistics rapid telemetry writes rarely query most optional JSON properties. Use this acceptance check instead: Compare a representative query and insert workload before and after adjusting a test indexing policy.

C.

Compare a representative query and insert workload before and after adjusting a test indexing policy. This tests the targeted action: Use controlled Cosmos DB indexing policies to match query paths while accounting for write costs. The reason is: Cosmos DB automatically indexes data under its policy; excluding unnecessary paths can reduce index maintenance for writes. The reported case is: At Silvercrest Logistics rapid telemetry writes rarely query most optional JSON properties.

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 Silvercrest Logistics rapid telemetry writes rarely query most optional JSON properties. Use this acceptance check instead: Compare a representative query and insert workload before and after adjusting a test indexing policy.

Question 708

At Silvercrest Logistics rapid telemetry writes rarely query most optional JSON properties. 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. Enable an extremely short TTL on all compliance records without reviewing retention obligations.
  3. Assume locally redundant copies within one site protect against every regional disaster.
  4. Remove every indexed path even though the production app filters on nested document fields.

Answer & Explanations

Correct answer: D

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 Silvercrest Logistics rapid telemetry writes rarely query most optional JSON properties—reject: Remove every indexed path even though the production app filters on nested document fields. The safer response is: Use controlled Cosmos DB indexing policies to match query paths while accounting for write costs.

B.

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 Silvercrest Logistics rapid telemetry writes rarely query most optional JSON properties—reject: Remove every indexed path even though the production app filters on nested document fields. The safer response is: Use controlled Cosmos DB indexing policies to match query paths while accounting for write costs.

C.

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 Silvercrest Logistics rapid telemetry writes rarely query most optional JSON properties—reject: Remove every indexed path even though the production app filters on nested document fields. The safer response is: Use controlled Cosmos DB indexing policies to match query paths while accounting for write costs.

D.

Remove every indexed path even though the production app filters on nested document fields. The scenario is: At Silvercrest Logistics rapid telemetry writes rarely query most optional JSON properties. The likely failure is: Queries become inefficient or fail to meet performance targets. Instead: Use controlled Cosmos DB indexing policies to match query paths while accounting for write costs.

Question 709

At Cedarport Retail a document catalog filters a small set of product attributes. 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. Choose Azure Cosmos DB for globally distributed document applications with defined latency and consistency needs.
  3. Use controlled Cosmos DB indexing policies to match query paths while accounting for write costs.
  4. Choose the Azure Cosmos DB for NoSQL API when an application uses native JSON item operations and SQL-like queries for documents.

Answer & Explanations

Correct answer: C

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 Cedarport Retail a document catalog filters a small set of product attributes. The relevant action here is: Use controlled Cosmos DB indexing policies to match query paths while accounting for write costs.

B.

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 Cedarport Retail a document catalog filters a small set of product attributes. The relevant action here is: Use controlled Cosmos DB indexing policies to match query paths while accounting for write costs.

C.

Use controlled Cosmos DB indexing policies to match query paths while accounting for write costs. This works because: Cosmos DB automatically indexes data under its policy; excluding unnecessary paths can reduce index maintenance for writes. The scenario is: At Cedarport Retail a document catalog filters a small set of product attributes. Verify the outcome by: Compare a representative query and insert workload before and after adjusting a test indexing policy.

D.

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 Cedarport Retail a document catalog filters a small set of product attributes. The relevant action here is: Use controlled Cosmos DB indexing policies to match query paths while accounting for write costs.

Question 710

At Cedarport Retail a document catalog filters a small set of product attributes. The team proposes this approach: Use controlled Cosmos DB indexing policies to match query paths while accounting for write costs. 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. Cooler online tiers reduce capacity cost when data is seldom read, subject to minimum duration and access charges.
  3. The NoSQL API addresses JSON items through containers, partition keys and the service's own query model.
  4. A point read targets one item directly and commonly consumes fewer request units than an equivalent broad query.

Answer & Explanations

Correct answer: A

A.

Cosmos DB automatically indexes data under its policy; excluding unnecessary paths can reduce index maintenance for writes. This principle supports the intervention: Use controlled Cosmos DB indexing policies to match query paths while accounting for write costs. The relevant scenario is: At Cedarport Retail a document catalog filters a small set of product attributes. Verify the result by: Compare a representative query and insert workload before and after adjusting a test indexing policy.

B.

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 Cedarport Retail a document catalog filters a small set of product attributes. The actual mechanism is: Cosmos DB automatically indexes data under its policy; excluding unnecessary paths can reduce index maintenance for writes.

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 Cedarport Retail a document catalog filters a small set of product attributes. The actual mechanism is: Cosmos DB automatically indexes data under its policy; excluding unnecessary paths can reduce index maintenance for writes.

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 Cedarport Retail a document catalog filters a small set of product attributes. The actual mechanism is: Cosmos DB automatically indexes data under its policy; excluding unnecessary paths can reduce index maintenance for writes.

Microsoft Azure Data Fundamentals (DP-900) Practice Tests