Odessa interview questions

## 1. Technical Round (Azure Architect) - Conducted by an **Azure Architect**. - Focused on **scenario-based questions** around Azure IaaS and PaaS. - Key questions included: - Is your role primarily **support, troubleshooting, or something else**? - You have **1 VM and 1 database** — how would you design **high availability** and which Azure services would you use to deploy a **2-tier application**? - How do you share a **file in Azure Blob Storage** with a user who doesn’t have an Azure account, ensuring access is limited to **7 days**? - Where do you **store application secrets**? - What is a **Managed Identity**? - Difference between **Load Balancer** and **Application Gateway**. - Explain a **Disaster Recovery (DR) strategy** for VM and DB. - Difference between **Availability Zone** and **Availability Set**. - Do you write **PowerShell scripts**? - Do you work with **DevOps, Terraform, ARM Templates**? - What are the **components of an ARM template**? - In which **language are ARM templates written**? ## 2. Techno-Managerial Round - Labeled as **Techno-Managerial**, but mostly **technical questions** (appeared to be an elimination round). - Key questions included: - Difference between **Availability Zone** and **Availability Set**. - How did you set up **DR for IaaS services**? - Difference between **Azure Front Door** and **Traffic Manager**. - Questions on **Load Balancer, VM Scale Sets (VMSS)**. - **Storage SaaS** concepts. - Questions on **VPN Gateway, Point-to-Site (P2S), Site-to-Site (S2S)**. - Handling of a **recent P1 issue**. - **ARM template structure**. Most of the things were asked on Cloud only they were not much dive into azure devops. - Questions were asked in a **tricky and confusing manner**, seemingly designed to test confidence and push candidates toward mistakes. - A few **managerial questions** were included, but the majority were **deep technical checks**.