You want to create a virtual machine (VM) in Azure Portal for a web application that requires moderate CPU and memory resources. Which VM size category should you select to balance cost and performance?
Think about a VM that offers a balanced mix of CPU and memory for typical workloads.
General purpose VM sizes provide a balanced CPU-to-memory ratio suitable for most applications, including web servers. Compute optimized are better for CPU-heavy tasks, memory optimized for large memory needs, and storage optimized for heavy disk I/O.
When creating a VM in Azure Portal, you must select an OS disk type. Which option provides the best balance between cost and performance for a general workload?
Consider a disk type that improves performance over HDD but is more affordable than premium options.
Standard SSD offers better performance than Standard HDD at a moderate cost, making it suitable for general workloads. Premium SSD and Ultra Disk provide higher performance but at higher cost, while Standard HDD is the lowest cost but slower.
You are creating a VM in Azure Portal that will host a sensitive application. Which network configuration should you apply to maximize security?
Think about isolating the VM from the internet and controlling traffic with rules.
Placing the VM in a private subnet without a public IP prevents direct internet access. Using an NSG allows you to control inbound traffic tightly. Other options expose the VM unnecessarily or lack traffic control.
You create two identical VMs in Azure Portal and place them in the same Availability Set. What is the expected effect on the VMs' uptime?
Consider how Azure manages maintenance to avoid simultaneous downtime.
An Availability Set distributes VMs across fault and update domains, so not all VMs are affected by hardware failures or maintenance at the same time, improving uptime. It does not guarantee 100% uptime or place VMs on the same server.
You created a VM in Azure Portal with a public IP and configured SSH access. However, you cannot connect to the VM via SSH from your local machine. Which of the following is the most likely cause?
Check the firewall rules controlling network traffic to the VM.
If the NSG does not allow inbound traffic on port 22, SSH connections will be blocked. Disk type and VM size do not affect SSH access. Availability Sets do not block network access.