Intermediate Azure test (Intermediate)

Sample questions

5 sample questions from the Intermediate Azure test, with the answers. Samples are taken out of the live test, so you will not meet these when you sit it.

1. When implementing network policies in an AKS cluster, which of the following statements accurately describes how network policies are enforced?

   1. Network policies are enforced at the node level, not the pod level.
   2. Network policies are not supported in AKS and must be implemented using Azure Firewall.
   3. Network policies are enforced at the pod level, not the node level.
   4. Network policies are enforced at the cluster level, not the pod or node level.

   Answer: C. Network policies are enforced at the pod level, not the node level.

   In AKS, network policies are implemented using the Azure CNI (Container Networking Interface) or the kubenet model. When using Azure CNI, network policies are enforced at the pod level, meaning that traffic between pods is filtered based on the policies defined in the network policy manifest. This is different from some other Kubernetes distributions where policies may be applied at the node level. A common mistake is assuming that network policies are enforced at the node level, which can lead to incorrect configurations and unexpected behavior in the cluster.

2. What will happen when the AKS pod autoscaler is configured to scale based on CPU utilization metrics?

   1. The autoscaler will scale out the pod count based on CPU utilization metrics.
   2. The autoscaler will scale based on memory utilization metrics by default.
   3. The autoscaler will automatically adjust the number of nodes in the cluster.
   4. The autoscaler will use custom metrics for scaling without any configuration.

   Answer: A. The autoscaler will scale out the pod count based on CPU utilization metrics.

   The AKS pod autoscaler uses metrics such as CPU utilization to determine when to scale out or scale in the number of pods in a deployment. It is designed to maintain the desired level of performance and resource utilization based on the configured metrics. The autoscaler does not scale based on memory metrics by default, does not automatically adjust the number of nodes, and does not use custom metrics unless explicitly configured.

3. Which statement correctly describes the relationship and functionality between Azure Monitor and Log Analytics?

   1. Azure Monitor provides a broader set of monitoring capabilities, including metrics, logs, and application performance management, while Log Analytics focuses primarily on log data analysis.
   2. Log Analytics provides a broader set of monitoring capabilities, including metrics, logs, and application performance management, while Azure Monitor focuses primarily on log data analysis.
   3. Azure Monitor and Log Analytics are identical in functionality and purpose.
   4. Log Analytics is a component of Azure Monitor, but they serve entirely different purposes.

   Answer: A. Azure Monitor provides a broader set of monitoring capabilities, including metrics, logs, and application performance management, while Log Analytics focuses primarily on log data analysis.

   Azure Monitor is a comprehensive monitoring service that includes Log Analytics as one of its components. Log Analytics is specifically designed for querying and analyzing log data, whereas Azure Monitor covers a wider range of monitoring needs, such as metrics, logs, and application insights.

4. When integrating an Azure App Service with an Azure Application Gateway, what is a common mistake or tricky edge case that developers often overlook?

   1. The Application Gateway must be configured with a dedicated frontend IP and bound to the App Service's custom domain.
   2. The App Service can use the Application Gateway's default frontend IP without any changes.
   3. The Application Gateway can be integrated without configuring a custom domain.
   4. The App Service automatically detects and routes traffic through the Application Gateway without configuration.

   Answer: A. The Application Gateway must be configured with a dedicated frontend IP and bound to the App Service's custom domain.

   A common mistake when integrating an App Service with an Application Gateway is assuming that the gateway can automatically route traffic without proper configuration. The Application Gateway must have a dedicated frontend IP address and be properly bound to the App Service's custom domain to ensure correct traffic routing. Other options describe incorrect or incomplete configurations that would not resolve the integration issue.

5. In Azure DevOps, how are release gates typically configured to ensure quality checks or approvals before deployment?

   1. Release gates are configured in the pipeline using conditions based on approvals or automated tests.
   2. Release gates are part of the artifact feed's configuration and are not pipeline-specific.
   3. Release gates are defined in the deployment target's configuration settings.
   4. Release gates are automatically triggered by the deployment success status.

   Answer: A. Release gates are configured in the pipeline using conditions based on approvals or automated tests.

   Release gates in Azure DevOps are used to enforce quality checks or approvals before a deployment proceeds. They are configured as conditions within the pipeline, such as requiring approvals or passing automated tests. Other options refer to unrelated concepts or incorrect implementations.