Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.

After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.

You have an Azure Cosmos DB database that uses the Table API. The database contains a table that includes the student data of a school. A subset of the data is shown in the following table.

Another student named Matt Berg joins the school.

You need to add a new entity for the new student.

Solution: You run the following Azure Power Shell command.

Add-StorageTableRow -table $Table_name -partitionKey 1 -rowkey (“matt_berg_0723”) -property @{“First Name”-”Matt”; Last Name"-"Berg"; "Age"-9}

Does this meet the goal?

Reveal Solution Hide Solution

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.

After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.

You have an Azure Cosmos DB database that uses the Table API. The database contains a table that includes the student data of a school. A subset of the data is shown in the following table.

Another student named Matt Berg joins the school.

You need to add a new entity for the new student.

Solution: You run the following Azure Power Shell command.

Add-StorageTableRow -table $Table_name -partitionKey 1 -rowkey (“matt_berg_9041”) -property @{“First Name”-”Matt”; Last Name"-"Berg"; "Age"-9}

Does this meet the goal?

Reveal Solution Hide Solution

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.

After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.

You have an Azure Cosmos DB database that uses the Table API. The database contains a table that includes the student data of a school. A subset of the data is shown in the following table.

Another student named Matt Berg joins the school.

You need to add a new entity for the new student.

Solution: You run the following Azure Power Shell command.

Add-StorageTableRow -table $Table_name -partitionKey 2 -rowkey (“matt_berg_9041”) -property @{“First Name”-”Mathew”; Last Name"-"Berg"; "Age"-9}

Reveal Solution Hide Solution

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.

After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.

You have an Azure Cosmos DB account named Account1 that uses the SQL APL Account1 contains a collection named Coll1.

You create a document named doc1 and set the TTL value for the document to 86,400. Thirty-six hours later, you discover that doc1 still exists in Coll1.

You need to ensure that documents are removed from Coll1 when the TTL for the documents expires.

Solution: You set the default TTL value for Coll1 to 129,600.

Does this meet the goal?

Reveal Solution Hide Solution

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.

After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.

You have an Azure Cosmos DB account named Account1 that uses the SQL APL Account1 contains a collection named Coll1.

You create a document named doc1 and set the TTL value for the document to 86,400. Thirty-six hours later, you discover that doc1 still exists in Coll1.

You need to ensure that documents are removed from Coll1 when the TTL for the documents expires.

Solution: You set the default TTL value for Coll1 to null.

Does this meet the goal?

Reveal Solution Hide Solution

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.

After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.

You have an Azure Cosmos DB account named Account1 that uses the SQL APL Account1 contains a collection named Coll1.

You create a document named doc1 and set the TTL value for the document to 86,400. Thirty-six hours later, you discover that doc1 still exists in Coll1.

You need to ensure that documents are removed from Coll1 when the TTL for the documents expires.

Solution: You set the default consistency level of Account1 to Strong.

Does this meet the goal?

Reveal Solution Hide Solution

You have an Azure Cosmos DB account that uses the SQL API. The account has a limit of 2,500 request units per second (RU/s). The default consistency level is set to Eventual.

You discover that you frequently exceed the Ru/s limit.

You need to recommend strategies to reduce the number of request units (RUs) consumed.

Which two possible strategies can you recommend to achieve this goal? Each correct answer presents a complete solution. NOTE. Each correct selection is worth one point.

Reveal Solution Hide Solution

You are implementing security for an Azure Cosmos DB account that uses the SQL API.

The account has the following collections:

– Movies A collection of move information

– Reviews A collection of move review information

You identify three types of access for Cosmos DB as shown in the following table.

You need to identity which method to use to configure the access types. The solution must use the principle of least privilege.

Which method should you identity for each access type? To answer, drag the appropriate methods to the correct access types. Each method may be used once, more than once or not at all.

You may need to drag the split bar between panes or scroll to view content.

NOTE: Each correct selection is worth one point.

Reveal Solution Hide Solution

You have an Azure Cosmos DB account named Account1. Account1 contains a database named DB1. DB1 contains a collection named Coll1. Coll1 contains a stored procedure named Sp1. Sp1 reads the data in Coll1.

You need to create a user named User1 who will have the permissions to run Sp1.

How should you complete the code? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point.

Reveal Solution Hide Solution