(AZ-204 topic) Develop Azure Compute Solutions Flashcards

Question

You are working as a developer for the Nutex Corporation. You are developing the monitor pattern to observe an arbitrary endpoint with the following code: *[FunctionName("AzureFunc-JobStatusMonitoring")] public static async Task Run( [OrchestrationTrigger] IDurableOrchestrationContext context) { int jobId = context.GetInput(); int pollingInterval = GetPollingInterval(); DateTime expiryTime = GetExpiryTime(); while (context.CurrentUtcDateTime \< expiryTime) { var jobStatus = await context.CallActivityAsync("GetJobStatus", jobId); if (jobStatus == "Completed") { // Code... await context.CallActivityAsync("SendAlert", machineId); break; } var nextCheck = context.CurrentUtcDateTime.AddSeconds(pollingInterval); await context.CreateTimer(nextCheck, CancellationToken.None); }* ``` *// Code... }* ``` You notice that the code does not work for more than seven days. How should you easily resolve the problem? (Choose two, each answer is a complete solution.) - Use the while loop for simulating a timer API - redesign the solution to use Azure Batch - redesign the function to use a Durable Function - Use the for loop for simulating a timer API

Answer 1

- Use the while loop for simulating a timer API - Use the for loop for simulating a timer API Durable timers are limited to seven days. The workaround is to simulate using the timer API in a loop, such as a while loop or a for loop. You would not redesign the function to use a Durable Function. The "AzureFunc-JobStatusMonitoring" function is already a Durable Function. In line number 3, the function uses IdurableOrchestrationContext, which means it is already a Durable Function (2.x). You would not redesign the solution to use Azure Batch. Although this action could work since Azure Batch schedules jobs to run on nodes, we have no information about which nodes the application runs on. Using timer APIs in a loop is less complicated.

Answer 2

* Add the PHP\_EXTENSIONS key in the Application Settings section of the Configuration blade. * Add PHP\_INI\_SCAN\_DIR to App Settings. You can enable extensions in the default PHP runtime by putting the extension.dll and extensions.ini files with the correct content into the directory. You can add PHP\_INI\_SCAN\_DIR Application Settings that point to the extensions.ini file. Alternatively, you can add PHP\_EXTENSIONS to the Application Settings section of the Configuration blade. You would not use a custom PHP runtime. This solution could resolve the problem if that extension is compiled to a custom PHP, but the scenario does not mention that the extension will be compiled to a custom PHP. You would not enable Composer automation in Azure. Composer automation allows you to perform git add, git commit, and git push to your app. Composer automation will not add a custom .dll extension to PHP. You would not add php.ini to the wwwroot directory. A php.ini file does not work in the web app. You would not add .htaccess to the wwwroot directory because .htaccess cannot load an extension.

Answer 3

1. Change the application code in the config\_file.cfg file. 2. Use the docker-compose up --build command to re-create the application image. 3. Tag the image with the loginServer of the container registry. 4. Use the docker push command to push the image to the registry. You would first make the change in the application by opening the config\_file.cfg file with any code or text editor and making the appropriate changes to the code. Once the application has been updated, you would re-create the application image and run the updated application. You can use the docker-compose command with the --build parameter to re-create the application image. The -d parameter should not be used because it runs containers in the background, and does not recreate the image. docker-compose up –build After you have recreated the image and tested the application, you would tag the image with the loginServer of the container registry. You can use the docker tag command to tag the image with the loginServer of the container registry. The following tags the azure-MyApp image with the loginServer of the container registry named acrNutex, and, adds :v2 to the end of the image name: docker tag azure-Myapp acrNutex/azure-Myapp:v2 Once the image has been tagged, you would push the image to the registry with the docker push command. The following pushes the image to the acrNutex loginServer: docker push azure-Myapp acrNutex/azure-Myapp:v2 You should ensure that multiple instances of the application pod are running to ensure maximum uptime. You would type the kubectl scale command to scale the resources. You can use the --replicas parameter to set the number of pods. The following command ensures that three pods are running: kubectl scale --replicas=3 deployment/MyApp-front

Answer 4

Open the freb.xsl file. ## Footnote You would open the freb.xsl file because failed request traces are stored in XML files named fr####.xml in the /LogFiles/W3SVC#########/ directory. To make it easier to view the logged information, an XSL stylesheet named freb.xsl is provided in the same directory as the XML files. You would not stream logging information with Azure CLI. By streaming logging information through Azure CLI, you can only stream information from .TXT, .LOG, or .HTM files, not .XML. With the command az webapp log tail you can stream logging information. You would not open the CSV file in blob storage because failed request trace logging information is not stored in CSV-format in blob storage. You would not use Log Parser because with the Log Parser utility you view web server logs and not failed request trace log information.

Answer 5

## Footnote *{ "bindings": [ { "name": "Timer", "type": "timerTrigger", "direction": "in", "schedule": "0 0 7 \* \* 1-5" } ], "disabled": false }* The function uses Cron Style (NCRONTAB expressions) for scheduling, in the format second, minute, hour, day, month, and day of week. The value "0 0 7 \* \* 1-5" states that the function runs at 07:00 am, not every day but only Monday through Friday. You would not modify function.json as follows: *{ "bindings": [ { "name": "Timer", "type": "timerTrigger", "direction": "in", "schedule": "0 0 0 7 1-5 \*" } ], "disabled": false }* The line "schedule": "0 0 0 7 1-5 \*" means that the function runs at 12:00 am, on day 7 of the months January through May. You would not modify function.json as follows: *{ "bindings": [ { "name": "Timer", "type": "timerTrigger", "direction": "in", "schedule": "0 0 7 1-5 \* \*" } ], "disabled": false }* The line "schedule": "0 0 7 1-5 \* \*" means that the function runs at 07:00 am, from day 1 to day 5 of the month. You would not modify function.json as follows: { "bindings": [ { "name": "Timer", "type": "timerTrigger", "direction": "in", "schedule": "0 7 1-5 \* \* \*" } ], "disabled": false } The line "schedule": "0 7 1-5 \* \* \*" means that the function runs at 7 minutes past the hour, between 01:00 am and 05:59 am.

Answer 6

Trigger: HTTP Input binding: None Output binding: Microsoft Graph The trigger will be HTTP because a webhook is HTTP-based. There is no HTTP or webhook input trigger available. Therefore the input binding in this scenario is NONE. The output binding is Microsoft Graph because this function must write to an Excel sheet. The function trigger is not using Timer because this function does not have to run on a schedule. The function trigger is not using Queue because this function is not based on another queue. The function trigger is not using Event Grid because it is not based on events. The function cannot have an input binding with None because it must be based on Blob Storage content. The function cannot use Cosmos DB as input binding because it must read blob storage content and not content from Cosmos DB. The output binding of this function is not Queue because this function does not have to write content into another queue. The output binding of this function is not Cosmos DB because this function does not have to create documents in a Cosmos DB. The output binding of this function is not SendGrid because this function does not have to send email.

Answer 7

az aks scale You would type the az aks scale command. This command is used to scale the node pool in a Kubernetes cluster. The --name parameter specifies the name of the cluster. The --resource group specifies the name of the resource group. The --node parameter specifies the number of nodes in the pool.

Answer 8

Trigger: Queue Input binding: None Output Binding: Queue In this scenario, a new queue message arrives which runs a function to write to another queue. The new queue message must trigger the function. The function will use Queue as the output binding because messages have to be written to another queue as output. This scenario does not need an input binding. The function trigger is not HTTP because, in this scenario, no HTTP request has been received. The function trigger is not Event Grid, because this function does not have to respond to an event sent to an event grid topic. The function trigger is not Timer, because this function does not have to run on a schedule. The function will not use only Blob storage for the input binding because, in this scenario, the function does not have to react to changes in the blob data along with changes in read and write values. The function is not using Cosmos DB, because the function does not have to listen for inserts and/or updates across partitions. Cosmos DB Trigger uses the Azure Cosmos DB Change Feed to listen for tasks like that. The function will not use Cosmos DB as the output binding because, in this scenario, the function does not have to write a new document to an Azure Cosmos DB database. The function will not use SendGrid as the output binding because the function does not have to send email through SendGrid. The function will not use Microsoft Graph as the output binding because, in this scenario, you do not need an Excel spreadsheet, OneDrive, or Outlook as output.

Answer 9

* Fan-out/fan-in * Aggregator * Monitoring * Function chaining With the function chaining pattern, you can use the context parameter DurableOrchestrationContext and the context.df object to invoke other functions by name, pass parameters, and return function output. A sequence of functions executes in a specific order. In this pattern, the output of one function is applied to the input of another function. You can implement control flow by using normal imperative coding constructs. Code executes from the top down. The code can involve existing language control flow semantics, such as conditionals and loops. You can include error handling logic in try/catch/finally blocks. With the monitoring pattern, you can use durable functions to create flexible recurrence intervals, manage task lifetimes, and create multiple monitor processes from a single orchestration. In a few lines of code, you can use durable functions to create multiple monitors that observe arbitrary endpoints. The monitors can end execution when a condition is met, or another function can use the durable orchestration client to terminate the monitors. You can change a monitor's wait interval based on a specific condition (for example, exponential backoff). With the fan-out/fan-in pattern, multiple functions can execute in parallel. You can use the function to send multiple messages to a queue. This is referred to as fan out. In the fan in part, you can write code to track when the queue-triggered functions end and the function outputs are stored. With the durable functions extension, you can handle the fan-out/fan-in pattern with relatively simple code. With the aggregator pattern, the data being aggregated could be received from multiple sources, sent in batches, or may be scattered over long periods of time. Sometimes the aggregator needs to take action on data when it is received, and clients need to query the aggregated data. Durable functions can use a single function to have multiple threads modifying the same data at the same time and ensure that the aggregator only runs on a single VM at a time. The Federated Identity, Gatekeeper, Valet Key, Sharding, and Cache-aside patterns cannot benefit from durable functions.

Answer 10

- Fast startup - Custom sizes - persistent storage - Per-second billing - Linux and Windows Azure Container Instances (ACI) is the service that allows you deploy a container on Azure cloud without having to manage the underlying infrastructure. ACI allows you launch containers quickly. With ACI, you incur costs only when running the container. The billing is on a per-second instead of a per-minute billing. You can isolate an application in a container like a VM environment. You can specify custom sizes for an Azure Container by specifying exact values for CPU cores and memory. With ACI, you can mount Azure files for persistent storage. The shared files are part of the container and are in a persistant state. You can have scheduled Linux containers as well as Windows containers with the same API. Microsoft recommends AKS instead of ACI when you need service discovery across multiple containers, coordinated application upgrades, and automatic scaling.

Answer 11

- Full container orchestration - Coordinated application upgrades - Service discovery across multiple containers - Automatic scaling The Azure Kubernetes Service (AKS) manages a Kubernetes environment in Azure. AKS provides full container orchestration because you deploy and manage containerized applications without container orchestration expertise. AKS is scalable to meet growing demands by designs because it includes built-in application autoscaling. Microsoft recommends AKS instead of ACI when you need service discovery across multiple containers, coordinated application upgrades, and automatic scaling.

Answer 12

Acceptable answer(s) for field 1: az aks create --name NutexAKSCluster --resource-group NutexResourceGroup az aks create --resource-group NutexResourceGroup --name NutexAKSCluster You would use the az aks create command to create an AKS cluster. You would use the --resource-group parameter to specify the resource group and the --name parameter to specify the name of the cluster.

Answer 13

* Scale up the size to P1v2 You would scale up the size to P1v2. The App Service plan needs to be in the Standard or Premium tier to use the Backup and Restore feature. In this scenario, the P1v2 instance is cheaper than an S3 or P2v2 instance. The price per hour for an S3 instance and P2v2 instance are currently $0.40/hour, while the price per hour of an P1v2 instance is $0.20/hour. ( SEE IMAGE ATTACHED) You would not deploy Windows Server 2019 Datacenter or Windows Server 2012 R2 Datacenter because the application is a Linux application, not a Windows application. You would need a Linux operating system to deploy the Linux application. You would not add the tag DailyBackup. A tag is just for information to organize Azure resources. You can use a tag to identify resources in a subscription or resource group. A tag is not needed for the Backup and Restore feature.

Answer 14

Acceptable answer(s) for field 1: * kubectl scale You would type the kubectl scale command to scale the resources. You can use the --replicas parameter to set the number of pods.

Answer 15

To configure “logging” we need to use the “az webapp log configure” command * config

Answer 16

"in" ## Footnote Suppose you want to write a new row to Azure Table storage whenver a new message appears in Azure Queue storage. this scenario can be implemented using an Azure Queue storage trigger and an Azure Table storage output binding. Here's a function.json file for this scenario: * {* * "bindings":[* * {* * "type":"queueTrigger",* * "direction": "in",* * "name":"neworder",* * "queueName":"whizlab-queue",* * "connection":"STORAGE\_CONNECTION\_3000"* * },* * {* * "type":"table",* * "direction": "out",* * "name": "$return",* * "tableName":"Orders",* * "connection":"STORAGE\_CONNECTION\_3000" }]}*

Answer 17

Ingress Controller ## Footnote You can use the Ingress controller to route traffic at the application layer The Microsoft documentation mentions the following: An ingress controller is a piece of software that provides reverse proxy, configurable traffic routing, and TLS termination for Kubernetes services. Kubernetes ingress resources are used to configure the ingress rules and routes for individual Kubernetes services. Using an ingress controller and ingress rules, a single IP address can be used to route traffic to multiple services in a Kubernetes cluster. Since this is clearly given in the documentation, all other options are incorrect. For more information on ingress controllers, please visit the following URL. [https://docs.microsoft.com/en-us/azure/aks/ingress-basic](https://docs.microsoft.com/en-us/azure/aks/ingress-basic)

Answer 18

az ad group create [https://docs.microsoft.com/en-us/azure/aks/azure-ad-rbac](https://docs.microsoft.com/en-us/azure/aks/azure-ad-rbac)

Answer 19

NotificationHubClient An example of this is given in the Microsoft documentation [https://docs.microsoft.com/en-us/azure/notification-hubs/notification-hubs-enterprise-push-notification-architecture](https://docs.microsoft.com/en-us/azure/notification-hubs/notification-hubs-enterprise-push-notification-architecture)