DP-420 Exam Dumps : Designing and Implementing Cloud-Native Applications Using Microsoft Azure Cosmos DB

This is because the write concern is mapped to the default consistency level configured on your Azure Cosmos DB account, which is strong in this case. Strong consistency ensures that every write operation is synchronously committed to every region associated with your Azure Cosmos DB account. The eventual consistency level that the application uses only applies to the read operations. Eventual consistency offers higher availability and better performance, but it does not guarantee the order or latency of the reads.

App1 queries the con-product and con-productVendor containers.

Note: Request unit is a performance currency abstracting the system resources such as CPU, IOPS, and memory that are required to perform the database operations supported by Azure Cosmos DB.

Scenario:

Develop an app named App1 that will run from all locations and query the data in account1.

Once multi-region writes are configured, maximize the performance of App1 queries against the data in account1.

Whenever there are multiple solutions for a requirement, select the solution that provides the best performance, as long as there are no additional costs associated.

Box 1 = Randomized

Box 2 = Deterministic

Always Encrypted for Az ure Cosmos DB supports two types of encryption: deterministic and randomized 1 . Deterministic encryption always produces the same encrypted value for any given plain text value. Randomized encryption produces a different encrypted value for the same plain text value.

For dateOfBirth, randomized encryption is the strongest type of encryption because it provides better protection against statistical analysis and brute-force attacks.  Deterministic encryption would not be suitable for dateOfBirth because it could r eveal patterns or allow equality comparisons 1 .

For healthStatus, deterministic encryption is the strongest type of encryption because it allows queries to perform equality comparisons and filters on the encrypted prop erty.  Randomized encryption would not be suitable for healthStatus because it would prevent any queries on the encrypted property 1 .