Free Practice Questions for Microsoft DP-420 Exam

Box 1: country

The country field is filterable.

Note: filterable: Indicates whether to enable the field to be referenced in $filter queries. Filterable differs from searchable in how strings are handled. Fields of type Edm.String or Collection(Edm.String) that are filterable do not undergo lexical analysis, so comparisons are for exact matches only.

Box 2: name

The name field is not Retrievable.

Retrievable: Indicates whether the field can be returned in a search result. Set this attribute to false if you want to use a field (for example, margin) as a filter, sorting, or scoring mechanism but do not want the field to be visible to the end user.

Note: searchable: Indicates whether the field is full-text searchable and can be referenced in search queries.

Box 1 = The request level options

Azure Cosmos DB offers five well-defined consistency levels: strong, bounded staleness, session, consistent prefix and eventual.  You can configure the default consistency level on your Azure Cosmos DB accou nt at any time 2 .  The default consistency level applies to all databases and containers under that account 1 .  You can also over ride the default consistency level for a specific request by using the request options 2 .

Box 2 = The request level options

To modify the consistency level of a read operation in Azure Cosmos DB, you can use request-level options to override the account ' s default consistency setting. Therefore, to ensure that the read operations of App1 can request either consistent prefix or session consistency, you need to modify the request-level options for each operation. Reference: - https://docs.microsoft.com/en-us/azure/cosmos-db/consistency-levels

C:\Users\Waqas Shahid\Desktop\Mudassir\Untitled.jpg

Batch size: An integer that represents how many objects are being written to Cosmos DB collection in each batch. Usually, starting with the default batch size is sufficient. To further tune this value, note:

Cosmos DB limits single request ' s size to 2MB. The formula is " Request Size = Single Document Size * Batch Size " . If you hit error saying " Request size is too large " , reduce the batch size value.

The larger the batch size, the better throughput the service can achieve, while make sure you allocate enough RUs to empower your workload.

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.

If the primary write region fails, applications that write to the database must use a different connection string to continue to use the service. = NO

You do not need to use a different connection string to continue to use the service if the primary write region fails.  This is because Azure Cosmos DB supports automatic failover, which means that it will automatically switch the primary write region to another region in case of a regional o utage 2 .  The application doe s not need to change the connection string or specify the failover priority 3 .  The connection string contains a list of all the regions associated with your account, and Azure Cos mos DB will route the requests to the appropriate region based on the availability and latency 1 .

The primary Read-Only SQL Connection String and the Secondary Read-Only SQL Connection String will connect to different regions from an application running in the East US Azure region = Yes

The primary read-only SQL connection string and the secondary read-only SQL connection string will connect to different regions from an application running in the East US Azure region. This is because the primary read-only SQL connection string contains the endpoint for the East US region, which is the same as the primary write region. The secondary read-only SQL connection string contains the endpoint for the West US region, which is the additional read region. Therefore, if an application running in the East US Azure region uses these connection strings, it will connect to different regions depending on which one it chooses.

Applications can choose from which region by setting the PreferredLocations property within their connection properties = Yes

Applications can choose from which region by setting the PreferredLocations property within their connection properties.  This property allows you to specify a list of regions that you prefer to read from based on their proximity to your application 2 .  Azure Cosmos DB will route the requests to the appropriate region based on the availability and latency 1 .  You can also set the ApplicationRegion property to the region where your application is deployed, and Azure Cosmos DB will automatically populate the PreferredLocations property based on the geo-proximity from that location 1 .

Based on the characteristics of the application and the provided document structure, the most suitable partition key value for coll1 in the given scenario would be the customerId, Option B.

The application frequently creates new orders by different customers and customers often view their past order history. Using customerId as the partition key would ensure that all orders associated with a particular customer are stored in the same partition. This enables efficient querying of past order history for a specific customer and reduces cross-partition queries, resulting in lower costs and improved performance.

a partition key is a JSON property (or path) within your documents that is used by Azure Cosmos DB to distribute data among multiple partitions 3 .  A partition key should have a high cardinali ty, which means it should have many distinct values, such as hundreds or thousands 1 .  A partition key should also align with the most co mmon query patterns of your application, so that you can efficiently retrieve data by using the partition key value 1 .

Based on these criteria, one possible partition key that you could use for coll1 is  B. customerId .

This partition key has the following advantages:

It has a high cardinality, as each customer will have a unique ID 3 .

It aligns with the query patterns of the application, a s customers will often view their past order history 3 .

It minimizes costs, as it reduces the number of cross-partition queries and optimizes the storage and throughput utilization 1 .

This partition key also has some limitations, such as:

It may not be optimal for scenarios where orders need to be queried independently from customers or aggregated by date or other criteria 3 .

It may result in hot partitions or throttling if som e customers create orders more frequently than others or have more data than others 1 .

It may not support transactions a cross multiple customers, as transactions are scoped to a single logical partition 2 .

Depending on your specific use case and requirements, you may need to adjust this partition key or choose a different one.  For example, you could use a synthetic partition key that conc atenates multiple properties of an item 2 , or you could use a partition key with a random or pre-calculated suffix to distribute the workload more evenly 2 .