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

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 .

Setting ConflictResolutionMode to Custom and configuring a custom stored procedure with the " conflictingItems " parameter will allow you to implement a custom conflict resolution policy. This will ensure that any conflicts are sent to the conflict feed for resolution.

Children who do no have parents defined will appear on the list = NO

Children who do not have parents defined will not appear on the list. This is because the document schema defines the children property as an array of objects that contain the firstName and gender properties of each child, as well as a parents property that references the id values of the parents. If a child does not have parents defined, it means that the parents property is either missing or empty for that child. Therefore, such a child will not be included in the list of children who have parents defined.

Children who have more than one pet will appear on the list multiple times. = Yes

Children who have more than one pet will appear on the list multiple times. This is because the document schema defines the pets property as an array of objects that contain the givenName and type properties of each pet, as well as a children property that references the id values of the children who own the pet. If a child has more than one pet, it means that the child’s id value will appear in the children property of multiple pet objects. Therefore, such a child will be included in the list of children who have pets multiple times.

Children who do no have pets defined will appear on the list = No

Children who do not have pets defined will not appear on the list. This is because the document schema defines the pets property as an array of objects that contain the givenName and type properties of each pet, as well as a children property that references the id values of the children who own the pet. If a child does not have pets defined, it means that the child’s id value does not appear in the children property of any pet object. Therefore, such a child will not be included in the list of children who have pets defined.