Answer:-2. No

Note:-Instead pass the HTTP trigger payload into an Azure Service Bus queue to be processed by a queue trigger function and return an immediate HTTP success response.
Note: Large, long-running functions can cause unexpected timeout issues. General best practices include:
Whenever possible, refactor large functions into smaller function sets that work together and return responses fast. For example, a webhook or HTTP trigger function might require an acknowledgment response within a certain time limit; it's common for webhooks to require an immediate response. You can pass the HTTP trigger payload into a queue to be processed by a queue trigger function. This approach lets you defer the actual work and return an immediate response.

Reference:-https://docs.microsoft.com/en-us/azure/azure-functions/functions-best-practices

Answer:-1. Add the customer ID for the signed in user to the CorrelationContext in the web application

Reference:-https://docs.microsoft.com/en-us/azure/azure-monitor/app/correlation

Answer:-2. No
Note:- The change feed is a log of changes that are organized into hourly segments but appended to and updated every few minutes. These segments are created only when there are blob change events that occur in that hour.
Instead catch the triggered event, so move the photo processing to an Azure Function triggered from the blob upload.

Reference:-https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blob-event-overview
https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blob-change-feed

Answer:-(1) and (4)

Note:- D: The ability to specify a host override is defined in the HTTP settings and can be applied to any back-end pool during rule creation. The ability to derive the host name from the IP or FQDN of the back-end pool members. HTTP settings also provide an option to dynamically pick the host name from a back-end pool member's FQDN if configured with the option to derive host name from an individual back-end pool member.
A (not C): SSL termination and end to end SSL with multi-tenant services.In case of end to end SSL, trusted Azure services such as Azure App service web apps do not require whitelisting the backends in the application gateway.
Therefore, there is no need to add any authentication certificates.


Reference:-https://docs.microsoft.com/en-us/azure/application-gateway/application-gateway-web-app-overview

Answer:-

Note:- Box 1: await context.CallEntityAsync(input[errindex],"error")
Orchestration signals and calls an entity
Orchestrator functions can access entities by using APIs on the orchestration trigger binding.
Example:
[FunctionName("CounterOrchestration")]
public static async Task Run(
[OrchestrationTrigger] IDurableOrchestrationContext context)
{
var entityId = new EntityId(nameof(Counter), "myCounter");
// Two-way call to the entity which returns a value - awaits the response int currentValue = await context.CallEntityAsync(entityId, "Get");

Box 2: Failed -
During processing a single instance of invalid input does not cause the function to fail.
Note: RuntimeStatus: One of the following values:
Failed: The instance failed with an error.
Completed: The instance has completed normally.
Terminated: The instance was stopped abruptly.
Pending: The instance has been scheduled but has not yet started running.
Running: The instance has started running.
ContinuedAsNew: The instance has restarted itself with a new history. This state is a transient state.

Box 3: Input -
Invalid input must be available to the monitoring application.
Reference:
Reference:-https://docs.microsoft.com/en-us/azure/azure-functions/durable/durable-functions-entities
https://docs.microsoft.com/en-us/azure/azure-functions/durable/durable-functions-instance-management

Answer:-

Remove the update that causes the problem
1. Take a snapshot of the OS disk of the affected VM as a backup.
2. Attach the OS disk to a recovery VM.
3. Once the OS disk is attached on the recovery VM, run diskmgmt.msc to open Disk Management, and ensure the attached disk is ONLINE.
4. (Step 1) Open an elevated command prompt instance (Run as administrator). Run the following command to get the list of the update packages that are on the attached OS disk: dism /image::\ /get-packages > c:\temp\Patch_level
5. (Step 2) Open the C:\temp\Patch_level.txt file, and then read it from the bottom up. Locate the update that's in Install Pending or Uninstall Pending state.
6. Remove the update that caused the problem:
dism /Image::\ /Remove-Package /PackageName: 7. (Step 4) Detach the OS disk and recreate the VM. Then check whether the issue is resolved.

Reference:-https://docs.microsoft.com/en-us/troubleshoot/azure/virtual-machines/troubleshoot-stuck-updating-boot-error

Answer:-

Note:- Box 1: Docker container -
A custom handler can be deployed to every Azure Functions hosting option. If your handler requires operating system or platform dependencies (such as a language runtime), you may need to use a custom container. You can create and deploy your code to Azure Functions as a custom Docker container.

Box 2: PowerShell core -
When creating a function app in Azure for custom handlers, we recommend you select .NET Core as the stack. A "Custom" stack for custom handlers will be added in the future.
PowerShell Core (PSC) is based on the new .NET Core runtime.

Box 3: 7.0 -
On Windows: The Azure Az PowerShell module is also supported for use with PowerShell 5.1 on Windows.
On Linux: PowerShell 7.0.6 LTS, PowerShell 7.1.3, or higher is the recommended version of PowerShell for use with the Azure Az PowerShell module on all platforms.

Reference:-https://docs.microsoft.com/en-us/azure/azure-functions/functions-create-function-linux-custom-image
https://docs.microsoft.com/en-us/powershell/azure/install-az-ps?view=azps-7.1.0

Answer:-

Note:- Box 1: If WEBSITES_ENABLE_APP_SERVICE_STORAGE
If WEBSITES_ENABLE_APP_SERVICE_STORAGE setting is unspecified or set to true, the /home/ directory will be shared across scale instances, and files written will persist across restarts

Box 2: /home -
Reference:-https://docs.microsoft.com/en-us/azure/app-service/containers/app-service-linux-faq

Answer:-

Box 1: No -
The AzScheduledQueryRuleSource is Heartbeat, not CPU.

Box 2: Yes -
The AzScheduledQueryRuleSource is Heartbeat!
Note: New-AzScheduledQueryRuleTriggerCondition creates an object of type Trigger Condition. This object is to be passed to the command that creates Alerting Action object.

Box 3: No -
The schedule is 60 minutes, not two hours.
-FrequencyInMinutes: The alert frequency.
-TimeWindowInMinutes: The alert time window
The New-AzAscheduledQueryRuleSchedule command creates an object of type Schedule. This object is to be passed to the command that creates Log Alert Rule.

Reference:-https://docs.microsoft.com/en-us/powershell/module/az.monitor/new-azscheduledqueryrule
https://docs.microsoft.com/en-us/powershell/module/az.monitor/new-azscheduledqueryruletriggercondition