Microsoft AZ-203 Exam Questions Answers 2019

AZ-203 Developing Solutions for Microsoft Azure Exam is essentially the best credential for all Azure Developers who design and build cloud solutions such as applications and services. It is important to learn about Azure tools and technologies.

Dumps4free AZ-203 Exam Dumps are the best source to get the training started. Why? Well of course because these AZ-203 Dumps have received the stamp of approval from Microsoft Professionals themselves. Plus, AZ-203 exam dumps questions are compatible, convenient and not that expensive at all.

Question #1:

You use Azure Table storage to store customer information for an application. The data contains customer details and is partitioned by last name. You need to create a query that returns all customers with the last name Smith. Which code segment should you use?
A. TableQuery.GenerateFilterCondition(“PartitionKey”, Equals, “Smith”)
B. TableQuery.GenerateFilterCondition(“LastName”, Equals, “Smith”)
C. TableQuery.GenerateFilterCondition(“PartitionKey”, QueryComparisons.Equal, “Smith”)
D. TableQuery.GenerateFilterCondition(“LastName”, QueryComparisons.Equal, “Smith”)
Answer: C
Explanation:
Retrieve all entities in a partition. The following code example specifies a filter for entities where ‘Smith’ is the partition key. This example prints the fields of each entity in the query results to the console.
Construct the query operation for all customer entities where PartitionKey=”Smith”.
TableQuery query = new
TableQuery().Where(TableQuery.GenerateFilterCondition(“PartitionKey”,
QueryComparisons.Equal, “Smith”));
References:
https://docs.microsoft.com/en-us/azure/cosmos-db/table-storage-how-to-use-dotnet

Question #2:

DRAG DROP
You are developing a solution for a hospital to support the following use cases:
The most recent patient status details must be retrieved even if multiple users in different locations have updated the patient record. Patient health monitoring data retrieved must be the current version or the prior version. After a patient is discharged and all charges have been assessed, the patient billing record contains the final charges. You provision a Cosmos DB NoSQL database and set the default consistency level for the database account to Strong. You set the value for Indexing Mode to Consistent. You need to minimize latency and any impact to the availability of the solution. You must override the default consistency level at the query level to meet the required consistency guarantees for the scenarios. Which consistency levels should you implement? To answer, drag the appropriate consistency levels to the correct requirements. Each consistency level 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

Answer:

Explanation:

Box 1: Strong Strong: Strong consistency offers a linearizability guarantee. The reads are guaranteed to return the most recent committed version of an item. A client never sees an uncommitted or partial write. Users are always guaranteed to read the latest committed write.

Box 2: Bounded staleness Bounded staleness: The reads are guaranteed to honor the consistent-prefix guarantee. The reads might lag behind writes by at most “K” versions (that is “updates”) of an item or by “t” time interval. When you choose bounded staleness, the “staleness” can be configured in two ways: The number of versions (K) of the item The time interval (t) by which the reads might lag behind the writes

Box 3: Eventual Eventual: There’s no ordering guarantee for reads. In the absence of any further writes, the replicas eventually converge. Incorrect Answers: Consistent prefix: Updates that are returned contain some prefix of all the updates, with no gaps. Consistent prefix guarantees that reads never see out-of-order writes.

References: https://docs.microsoft.com/en-us/azure/cosmos-db/consistency-levels

Question #3:

You are developing a software solution for an autonomous transportation system. The solution uses large data sets and Azure Batch processing to simulate navigation sets for entire fleets of vehicles. You need to create compute nodes for the solution on Azure Batch. What should you do?
A. In Python, implement the class: TaskAddParameter
B. In Python, implement the class: JobAddParameter
C. In the Azure portal, create a Batch account
D. In a .NET method, call the method: BatchClient.PoolOperations.CreateJob
Answer: D
Explanation:
A Batch job is a logical grouping of one or more tasks. A job includes settings common to the tasks, such as priority and the pool to run tasks on. The app uses the BatchClient.JobOperations.CreateJob method to create a job on your pool.
Note:
Step 1: Create a pool of compute nodes. When you create a pool, you specify the number of compute nodes for the pool, their size, and the operating system. When each task in your job runs, it’s assigned to execute on one of the nodes in your pool.
Step 2 : Create a job. A job manages a collection of tasks. You associate each job to a specific pool where that job’s tasks will run.
Step 3: Add tasks to the job. Each task runs the application or script that you uploaded to process the data files it downloads from your Storage account. As each task completes, it can upload its output to Azure Storage.
Incorrect Answers:
C: To create a Batch pool in Python, the app uses the PoolAddParameter class to set the number of nodes, VM size, and a pool configuration.
References:
https://docs.microsoft.com/en-us/azure/batch/quick-run-dotnet

Question #4:

DRAG DROP
You develop a web app that uses the tier D1 app service plan by using the Web Apps feature of Microsoft Azure App Service. Spikes in traffic have caused increases in page load times. You need to ensure that the web app automatically scales when CPU load is about 85 percent and minimize costs.
Which four actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.

Answer:

Explanation:
Step 1
: Configure the web app to the Standard App Service Tier, The Standard tier supports auto-scaling, and we should minimize the cost.
Step 2: Enable autoscaling on the web app, First enable autoscale
Step 3: Add a scale rule
Step 4: Add a Scale condidation
References:
https://docs.microsoft.com/en-us/azure/monitoring-and-diagnostics/monitoring-autoscale-getstarted
https://azuHYPERLINK “https://docs.microsoft.com/en-us/azure/monitoring-anddiagnostics/monitoring-autoscale-get-started https:/azure.microsoft.com/en-us/pricing/details/app-service/plans/”re.microsoft.com/enus/pricing/details/app-service/plans/

Question #5:

HOTSPOT
You are creating an app that uses Event Grid to connect with other services. Your app’s event data will be sent to a serverless function that checks compliance. This function is maintained by your company. You write a new event subscription at the scope of your resource. The event must be invalidated after 3 specific period of time. You need to configure Event Grid to ensure security. What should you implement? To answer, select the appropriate options in [he answer area.
NOTE: Each correct selection is worth one point

Answer:

Explanation:
Box 1
: SAS tokens Custom topics use either Shared Access Signature (SAS) or key authentication. Microsoft recommends SAS, but key authentication provides simple programming, and is compatible with many existing webhook publishers. In this case we need the expiration time provided by SAS tokens.
Box 2: ValidationCode handshake Event Grid supports two ways of validating the subscription: ValidationCode handshake (programmatic) and ValidationURL handshake (manual). If you control the source code for your endpoint, this method is recommended.
Incorrect Answers:
ValidationURL handshake (manual): In certain cases, you can’t access the source code of the endpoint to implement the ValidationCode handshake. For example, if you use a third-party service (like Zapier or IFTTT), you can’t programmatically respond with the validation code.
References:
https://docs.microsoft.com/en-us/azure/event-grid/security-authenticationA