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 62

Question 610

At Silverlake Media a partner needs temporary read access to one approved asset. The team proposes this approach: Use a time-bounded, narrowly scoped shared access signature when temporary Blob Storage access is required. Which technical principle explains the choice?

  1. SAS credentials can grant defined resource operations and expiry without granting the recipient broad storage account administration.
  2. Blob Storage is object storage designed for unstructured content, independently of relational table structures.
  3. Azure Files exposes managed file shares with file-system protocols and compatible directory semantics.
  4. Cosmos DB automatically indexes data under its policy; excluding unnecessary paths can reduce index maintenance for writes.

Answer & Explanations

Correct answer: A

A.

SAS credentials can grant defined resource operations and expiry without granting the recipient broad storage account administration. This principle supports the intervention: Use a time-bounded, narrowly scoped shared access signature when temporary Blob Storage access is required. The relevant scenario is: At Silverlake Media a partner needs temporary read access to one approved asset. Verify the result by: Open a fictional blob with an allowed test SAS and verify a nonallowed operation or expired token is rejected.

B.

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 Silverlake Media a partner needs temporary read access to one approved asset. The actual mechanism is: SAS credentials can grant defined resource operations and expiry without granting the recipient broad storage account administration.

C.

Azure Files exposes managed file shares with file-system protocols and compatible directory semantics. That explains a separate situation: At Meadowfield Accounting two virtual machines share legacy report files through SMB. The current case is: At Silverlake Media a partner needs temporary read access to one approved asset. The actual mechanism is: SAS credentials can grant defined resource operations and expiry without granting the recipient broad storage account administration.

D.

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 Silverlake Media a partner needs temporary read access to one approved asset. The actual mechanism is: SAS credentials can grant defined resource operations and expiry without granting the recipient broad storage account administration.

Question 611

At Silverlake Media a partner needs temporary read access to one approved asset. After implementing this approach—Use a time-bounded, narrowly scoped shared access signature when temporary Blob Storage access is required—which result would most directly confirm success?

  1. Replay a fictional read-write mix and inspect RU consumption and throttling under the chosen throughput mode.
  2. Retrieve an older fictional monthly report directly and compare total expected storage and read costs.
  3. Organize fictional partitioned data under dated directories and verify directory-level move or access behavior.
  4. Open a fictional blob with an allowed test SAS and verify a nonallowed operation or expired token is rejected.

Answer & Explanations

Correct answer: D

A.

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 Silverlake Media a partner needs temporary read access to one approved asset. Use this acceptance check instead: Open a fictional blob with an allowed test SAS and verify a nonallowed operation or expired token is rejected.

B.

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 Silverlake Media a partner needs temporary read access to one approved asset. Use this acceptance check instead: Open a fictional blob with an allowed test SAS and verify a nonallowed operation or expired token is rejected.

C.

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 Silverlake Media a partner needs temporary read access to one approved asset. Use this acceptance check instead: Open a fictional blob with an allowed test SAS and verify a nonallowed operation or expired token is rejected.

D.

Open a fictional blob with an allowed test SAS and verify a nonallowed operation or expired token is rejected. This tests the targeted action: Use a time-bounded, narrowly scoped shared access signature when temporary Blob Storage access is required. The reason is: SAS credentials can grant defined resource operations and expiry without granting the recipient broad storage account administration. The reported case is: At Silverlake Media a partner needs temporary read access to one approved asset.

Question 612

At Silverlake Media a partner needs temporary read access to one approved asset. 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. Promise an instant restore from archive without planning rehydration.
  3. Run a full container cross-partition query for every known primary-key lookup.
  4. Put every large image into an Azure Table Storage entity expecting full binary-object semantics.

Answer & Explanations

Correct answer: A

A.

Publish a perpetual account-level SAS with write and delete rights for a one-file download. The scenario is: At Silverlake Media a partner needs temporary read access to one approved asset. This undermines the mechanism: SAS credentials can grant defined resource operations and expiry without granting the recipient broad storage account administration. Instead: Use a time-bounded, narrowly scoped shared access signature when temporary Blob Storage access is required.

B.

Promise an instant restore from archive without planning rehydration. This concerns another issue: At Cedarbank Records files legally retained for a decade are rarely requested. In the stated case—At Silverlake Media a partner needs temporary read access to one approved asset—reject: Publish a perpetual account-level SAS with write and delete rights for a one-file download. The safer response is: Use a time-bounded, narrowly scoped shared access signature when temporary Blob Storage access is required.

C.

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 Silverlake Media a partner needs temporary read access to one approved asset—reject: Publish a perpetual account-level SAS with write and delete rights for a one-file download. The safer response is: Use a time-bounded, narrowly scoped shared access signature when temporary Blob Storage access is required.

D.

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 Silverlake Media a partner needs temporary read access to one approved asset—reject: Publish a perpetual account-level SAS with write and delete rights for a one-file download. The safer response is: Use a time-bounded, narrowly scoped shared access signature when temporary Blob Storage access is required.

Question 613

At Pinecrest Healthcare an external auditor downloads one file within a documented window. Which design or Azure data approach best fits this requirement?

  1. Pick sensible partition keys for Table Storage based on common access patterns and partition distribution.
  2. Use a time-bounded, narrowly scoped shared access signature when temporary Blob Storage access is required.
  3. Use immutable blob policies when regulated records must be protected from alteration or deletion during retention.
  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.

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 Pinecrest Healthcare an external auditor downloads one file within a documented window. The relevant action here is: Use a time-bounded, narrowly scoped shared access signature when temporary Blob Storage access is required.

B.

Use a time-bounded, narrowly scoped shared access signature when temporary Blob Storage access is required. This works because: SAS credentials can grant defined resource operations and expiry without granting the recipient broad storage account administration. The scenario is: At Pinecrest Healthcare an external auditor downloads one file within a documented window. Verify the outcome by: Open a fictional blob with an allowed test SAS and verify a nonallowed operation or expired token is rejected.

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 Pinecrest Healthcare an external auditor downloads one file within a documented window. The relevant action here is: Use a time-bounded, narrowly scoped shared access signature when temporary Blob Storage access is required.

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 Pinecrest Healthcare an external auditor downloads one file within a documented window. The relevant action here is: Use a time-bounded, narrowly scoped shared access signature when temporary Blob Storage access is required.

Question 614

At Pinecrest Healthcare an external auditor downloads one file within a documented window. The team proposes this approach: Use a time-bounded, narrowly scoped shared access signature when temporary Blob Storage access is required. Which technical principle explains the choice?

  1. SAS credentials can grant defined resource operations and expiry without granting the recipient broad storage account administration.
  2. Partition-key distribution affects scaling, hot partitions and the need for cross-partition queries.
  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: A

A.

SAS credentials can grant defined resource operations and expiry without granting the recipient broad storage account administration. This principle supports the intervention: Use a time-bounded, narrowly scoped shared access signature when temporary Blob Storage access is required. The relevant scenario is: At Pinecrest Healthcare an external auditor downloads one file within a documented window. Verify the result by: Open a fictional blob with an allowed test SAS and verify a nonallowed operation or expired token is rejected.

B.

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 Pinecrest Healthcare an external auditor downloads one file within a documented window. The actual mechanism is: SAS credentials can grant defined resource operations and expiry without granting the recipient broad storage account administration.

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 Pinecrest Healthcare an external auditor downloads one file within a documented window. The actual mechanism is: SAS credentials can grant defined resource operations and expiry without granting the recipient broad storage account administration.

D.

WORM-style immutable storage controls restrict modifications or deletions according to configured retention or hold settings. That explains a separate situation: At Harborland Securities trade evidence requires enforced retention. The current case is: At Pinecrest Healthcare an external auditor downloads one file within a documented window. The actual mechanism is: SAS credentials can grant defined resource operations and expiry without granting the recipient broad storage account administration.

Question 615

At Pinecrest Healthcare an external auditor downloads one file within a documented window. After implementing this approach—Use a time-bounded, narrowly scoped shared access signature when temporary Blob Storage access is required—which result would most directly confirm success?

  1. Open a fictional blob with an allowed test SAS and verify a nonallowed operation or expired token is rejected.
  2. Measure a sample workload with repeated object reads and verify the chosen tier supports required latency.
  3. Upload and retrieve a synthetic image while an unauthenticated test request is denied by policy.
  4. Update a fictional order item and verify the consumer receives the change once under idempotent processing.

Answer & Explanations

Correct answer: A

A.

Open a fictional blob with an allowed test SAS and verify a nonallowed operation or expired token is rejected. This tests the targeted action: Use a time-bounded, narrowly scoped shared access signature when temporary Blob Storage access is required. The reason is: SAS credentials can grant defined resource operations and expiry without granting the recipient broad storage account administration. The reported case is: At Pinecrest Healthcare an external auditor downloads one file within a documented window.

B.

Measure a sample workload with repeated object reads and verify the chosen tier supports required latency. This tests a separate situation: At Pinefield Retail product images are fetched continuously by shoppers. The observed case is: At Pinecrest Healthcare an external auditor downloads one file within a documented window. Use this acceptance check instead: Open a fictional blob with an allowed test SAS and verify a nonallowed operation or expired token is rejected.

C.

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 Pinecrest Healthcare an external auditor downloads one file within a documented window. Use this acceptance check instead: Open a fictional blob with an allowed test SAS and verify a nonallowed operation or expired token is rejected.

D.

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 Pinecrest Healthcare an external auditor downloads one file within a documented window. Use this acceptance check instead: Open a fictional blob with an allowed test SAS and verify a nonallowed operation or expired token is rejected.

Question 616

At Pinecrest Healthcare an external auditor downloads one file within a documented window. 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. Run a full container cross-partition query for every known primary-key lookup.
  3. Grant ordinary application users delete rights to all archived compliance evidence.
  4. Put every large image into an Azure Table Storage entity expecting full binary-object semantics.

Answer & Explanations

Correct answer: A

A.

Publish a perpetual account-level SAS with write and delete rights for a one-file download. The scenario is: At Pinecrest Healthcare an external auditor downloads one file within a documented window. This undermines the mechanism: SAS credentials can grant defined resource operations and expiry without granting the recipient broad storage account administration. Instead: Use a time-bounded, narrowly scoped shared access signature when temporary Blob Storage access is required.

B.

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 Pinecrest Healthcare an external auditor downloads one file within a documented window—reject: Publish a perpetual account-level SAS with write and delete rights for a one-file download. The safer response is: Use a time-bounded, narrowly scoped shared access signature when temporary Blob Storage access is required.

C.

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 Pinecrest Healthcare an external auditor downloads one file within a documented window—reject: Publish a perpetual account-level SAS with write and delete rights for a one-file download. The safer response is: Use a time-bounded, narrowly scoped shared access signature when temporary Blob Storage access is required.

D.

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 Pinecrest Healthcare an external auditor downloads one file within a documented window—reject: Publish a perpetual account-level SAS with write and delete rights for a one-file download. The safer response is: Use a time-bounded, narrowly scoped shared access signature when temporary Blob Storage access is required.

Question 617

At Cedarbank Payments retained transaction exports require defined regional resilience. Which design or Azure data approach best fits this requirement?

  1. Enable hierarchical namespace for Azure Data Lake Storage Gen2 when directory semantics and analytics engines require it.
  2. Pick sensible partition keys for Table Storage based on common access patterns and partition distribution.
  3. Choose appropriate Azure Storage redundancy based on durability, availability and geographic recovery requirements.
  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.

Enable hierarchical namespace for Azure Data Lake Storage Gen2 when directory semantics and analytics engines require it. This addresses a different situation: At Oakridge Analytics Spark jobs work with folder-based lake partitions. The present case is: At Cedarbank Payments retained transaction exports require defined regional resilience. The relevant action here is: Choose appropriate Azure Storage redundancy based on durability, availability and geographic recovery requirements.

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 Cedarbank Payments retained transaction exports require defined regional resilience. The relevant action here is: Choose appropriate Azure Storage redundancy based on durability, availability and geographic recovery requirements.

C.

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 Cedarbank Payments retained transaction exports require defined regional resilience. Verify the outcome by: Review a fictional availability requirement and confirm the selected redundancy option matches its scope.

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 Cedarbank Payments retained transaction exports require defined regional resilience. The relevant action here is: Choose appropriate Azure Storage redundancy based on durability, availability and geographic recovery requirements.

Question 618

At Cedarbank Payments retained transaction exports require defined regional resilience. 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. LRS, ZRS and geographically redundant options provide different replica placement and disaster-protection properties.
  2. Partition keys determine entity grouping and affect efficient lookup and potential hot partitions.
  3. Blob access tiers trade storage price for retrieval and transaction costs according to access frequency.
  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.

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 Cedarbank Payments retained transaction exports require defined regional resilience. Verify the result by: Review a fictional availability requirement and confirm the selected redundancy option matches its scope.

B.

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 Cedarbank Payments retained transaction exports require defined regional resilience. The actual mechanism is: LRS, ZRS and geographically redundant options provide different replica placement and disaster-protection properties.

C.

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 Cedarbank Payments retained transaction exports require defined regional resilience. The actual mechanism is: LRS, ZRS and geographically redundant options provide different replica placement and disaster-protection properties.

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 Cedarbank Payments retained transaction exports require defined regional resilience. The actual mechanism is: LRS, ZRS and geographically redundant options provide different replica placement and disaster-protection properties.

Question 619

At Cedarbank Payments retained transaction exports require defined regional resilience. 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. Test that a report service reads one permitted container but cannot list a protected unrelated container.
  2. Review a fictional availability requirement and confirm the selected redundancy option matches its scope.
  3. Insert a fictional JSON profile and execute a supported Cosmos DB for NoSQL query over its fields.
  4. Attempt a controlled deletion of a test retained object and verify policy prevents it.

Answer & Explanations

Correct answer: B

A.

Test that a report service reads one permitted container but cannot list a protected unrelated container. This tests a separate situation: At Meadowcrest Banking one analytics service reads a restricted statements container. The observed case is: At Cedarbank Payments retained transaction exports require defined regional resilience. Use this acceptance check instead: Review a fictional availability requirement and confirm the selected redundancy option matches its scope.

B.

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 Cedarbank Payments retained transaction exports require defined regional resilience.

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 Cedarbank Payments retained transaction exports require defined regional resilience. Use this acceptance check instead: Review a fictional availability requirement and confirm the selected redundancy option matches its scope.

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 Cedarbank Payments retained transaction exports require defined regional resilience. Use this acceptance check instead: Review a fictional availability requirement and confirm the selected redundancy option matches its scope.

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.

Microsoft Azure Data Fundamentals (DP-900) Practice Tests