Ir al contenido

Part 1: Services, solutions, and tools in Azure:

Welcome to the first phase of your preparation! This module is the foundation of everything. Let's break down each concept in your index.

0views

Welcome to the first phase of your preparation! This module is the foundation for everything. We are going to break down every concept in your index.

Formal Definition:

(According to Part_1, Page 45) It is the delivery of computing services over the Internet. This allows for faster innovation, flexible resources, and pay-as-you-go pricing.

Instructor's Note (Analogy):

Think about electricity. Previously, factories had their own generators (expensive, high maintenance). Today, they connect to the electrical grid and pay only for what they consume. The cloud is the “electrical grid” of computing.

Here we define where services reside.

  • Definition: (According to Part_1, Page 74) It is owned by the hosting provider (Microsoft, Amazon, Google). It provides resources and services to multiple organizations and users over the Internet.
  • Key advantage: No capital expenditures (CapEx). You only pay for what you use (OpEx).
  • Disadvantage: Less control over security and data residency (although this is managed with Regions).
  • Definition: (According to Part_1, Page 72) Organizations create a cloud environment in their own data center.
  • Key advantage: Total control over security and infrastructure.
  • Disadvantage: Requires high initial investment (CapEx) and the organization is responsible for all maintenance.
  • Definition: (According to Part_1, Page 70) Combines public and private clouds, allowing applications to run in the most suitable location.
  • Key advantage: (According to Part_1, Page 27) Provides the greatest flexibility. You can keep sensitive data private while using the power of the public cloud for less critical applications.
FeaturePublic CloudPrivate CloudHybrid Cloud
Initial ExpenditureNo (OpEx)Yes (CapEx)Mixed
ScalabilityFast and “limited”Slow (hardware must be purchased)Flexible
ControlLow (Provider manages)Total (You manage)Mixed
MaintenanceProviderYouShared

These are “keywords” for the exam. You must know what each one means:

  • High Availability (HA): Ensures that applications have the maximum possible uptime, even if components fail.
  • Scalability: Capacity to increase or decrease resources (e.g., more CPU, more RAM).
  • Elasticity: The cloud's capacity to automatically add or remove resources based on demand (e.g., a traffic spike on Black Friday).
  • Agility: Speed to deploy new resources.
  • Fault Tolerance: The ability of a service to continue functioning if one of its components fails.
  • Disaster Recovery (DR): The ability to recover from a major failure (e.g., an entire data center).
  • Global Reach: Deploy applications close to your users anywhere in the world.
  • Predictive cost considerations: Models for estimating expenditure (OpEx).
  • Security: Physical and digital infrastructure protected by the provider.

This is a fundamental concept for the exam.

  • CapEx (Capital Expenditure): (According to Part_1, Page 24) It is the initial expenditure of money on physical infrastructure (buying servers, disks, buildings). The value of this investment decreases over time (depreciation).
  • Example: Buying a server for your office.
  • OpEx (Operating Expenditure): (According to Part_1, Page 24) It is the expenditure on products and services as needed (pay-as-you-go). It is billed immediately.
  • Example: Paying the monthly Azure bill.

Instructor Note: The cloud transforms IT spending from CapEx to OpEx.

This defines how much you manage and how much Microsoft manages.

  • Definition: (According to Part_1, Page 43) You rent the basic infrastructure: virtual servers (VMs), storage, and networks.
  • Your Responsibility: You manage the Operating System, patches, middleware, and the application.
  • Analogy (Pizza): Microsoft gives you the kitchen, the oven, and the gas (infrastructure). You bring the ingredients (OS) and cook the pizza (your app).
  • Example: Azure Virtual Machines.
  • Definition: (According to Part_1, Page 78) Provides an environment to compile, test, and deploy software applications. You don't worry about the underlying infrastructure (nor the OS).
  • Your Responsibility: You only manage your application and your data.
  • Analogy (Pizza): You order pizza for delivery. Microsoft (the pizzeria) manages the kitchen, the oven, and the cooking. You only take care of the table and the drinks (your app).
  • Example: Azure App Services, Azure SQL Database.
  • Definition: (According to Part_1, Page 89) Ready-to-use software, typically under a subscription model.
  • Your Responsibility: Practically none, you only manage your data and who accesses it.
  • Analogy (Pizza): You eat at the restaurant. Microsoft (the restaurant) manages everything.
  • Example: Microsoft 365, Gmail.

THE MOST IMPORTANT TRICK QUESTION IN THE AZ-900!

You must memorize who is responsible for what in each model. (Ref: Part_1, Page 66).

ResponsibilityOn-Premise (Local)IaaSPaaSSaaS
Data and AccessYouYouYouYou
ApplicationsYouYouYouMicrosoft
Runtime / MiddlewareYouYouMicrosoftMicrosoft
Operating SystemYouYouMicrosoftMicrosoft
Virtual MachinesYouMicrosoftMicrosoftMicrosoft
Compute / Network / StorageYouMicrosoftMicrosoftMicrosoft
Physical Data CenterYouMicrosoftMicrosoftMicrosoft

Key Summary:

  • In IaaS, your responsibility starts at the Operating System.
  • In PaaS, your responsibility starts at the Application.
  • In SaaS, you only manage Data and Access.

This section is the Azure “catalog”. It is crucial to differentiate what each service does.

1. Azure Architecture (Physical and Logical Infrastructure)

Sección titulada «1. Arquitectura de Azure (La Infraestructura Física y Lógica)»
  • Definition: (According to Parte_1, Página 87) A region is composed of one or more nearby data centers.
  • Purpose: It provides flexibility and the ability to deploy resources close to customers (reducing latency) and allows compliance with data residency requirements (e.g., laws requiring European citizens' data to remain in Europe).
  • Definition: (According to Parte_1, Página 80) Each Azure region is “paired” with another region within the same geography (e.g., West Europe with North Europe).
  • Separation: They are at least 500 km apart to protect against regional disasters (earthquakes, hurricanes).
  • Key Benefits (Exam Trap):
    1. Prioritized Recovery: If there is a massive outage, recovery of one region from each pair is prioritized.
    2. Sequential Updates: Microsoft updates the platform sequentially (first one region, then the other) to minimize downtime.
    3. Automatic Replication: Some services (such as Geo-Redundant Storage - GRS) automatically replicate data to the region pair.
  • High Availability (HA): Refers to keeping services running within a data center or region if a component fails (a server, a disk). Availability Zones provide HA.
  • Disaster Recovery (DR): Refers to recovering services after a catastrophic event that takes down an entire region. Region Pairs are used for DR.
  • Definition: (According to Parte_1, Página 105) They are data centers that are physically separate within the same region.
  • Characteristics: Each zone has its own power, cooling, and independent networks.
  • Purpose: Provides protection against downtime due to data center failures (e.g., a fire or a power outage in a building).
  • SLA: Using Availability Zones for your VMs gives you a 99.99% SLA.

Summary Cheat Sheet (Region vs. Zone vs. Pair):

  • Region: A geographic area (e.g., "Western Europe").
  • Availability Zones: Several buildings within that area. They protect against building failures (HA).
  • Region Pairs: A distant region (e.g., "North Europe"). Protects against regional disasters (DR).
  • Definition: (According to Parte_1, Página 39) A container to manage and group resources (VMs, DBs, Networks) into a single unit.
  • Key Rules:
    • A resource can only belong to one resource group.
    • Resources in a group can be in different regions.
    • If you delete a resource group, all the resources it contains are deleted.
    • They are used to group resources with the same lifecycle (e.g., “AppProject_Production”).
  • Definition: (According to Parte_1, Página 12) It is the management layer that allows you to create, update, and delete resources in your subscription.
  • Function: It is the “brain” of Azure. When you click on the portal, run a PowerShell or CLI command, you are talking to the ARM API.
  • Benefits: It allows for idempotent deployments (the result is the same no matter how many times you run it) using JSON/Bicep templates.
  • Definition: (According to Parte_1, Página 93) It provides authenticated and authorized access to Azure accounts.
  • Purposes:
    1. Billing Boundary: Generates separate invoices for each subscription.
    2. Access Control Boundary: Manages who can access which resources (RBAC).
  • Definition: (According to Parte_1, Página 37) Containers for subscriptions.
  • Purpose: They allow applying policies (Azure Policy) and access control (RBAC) to multiple subscriptions at once. They create a hierarchy above subscriptions (e.g., “Production Department”, “Development Department”).
  • Definition: (According to Parte_1, Página 18) Software emulations of physical machines.
  • Model: IaaS (Infrastructure as a Service).
  • Control: You have full control and customization over the OS and software.
  • Definition: (According to Parte_1, Página 4) A fully managed platform (PaaS) to create, deploy, and scale web applications and APIs.
  • Support: .NET, .NET Core, Node.js, Java, Python, PHP.
  • Advantage: You don't manage the OS, patches, or the web server. Just upload your code.
  • Definition: (According to Parte_1, Página 8) Lightweight virtualized environments that do not require OS administration.
  • Key Services:
    1. Azure Container Instances (ACI): (PaaS) The fastest way to run a container in Azure. No servers to manage.
    2. Azure Kubernetes Service (AKS): A complete orchestration service for managing large volumes of containers and distributed architectures.

Windows Virtual Desktop (now Azure Virtual Desktop)

Sección titulada «Windows Virtual Desktop (ahora Azure Virtual Desktop)»
  • Definition: (According to Parte_1, Página 103) Application and desktop virtualization that runs in the cloud.
  • Use case: Allows employees to access their Windows 10/11 desktop from any device. Supports Windows 11 multi-session (multiple users on the same VM).

Azure Networking Services (Ref: Parte_1, Página 91)

Sección titulada «Servicios de Redes de Azure (Ref: Parte_1, Página 91)»
  • Azure Virtual Network (VNet): Allows Azure resources (such as VMs) to communicate securely with each other, with the Internet, and with local networks (On-Premise).
  • Virtual Private Network Gateway (VPN): Sends encrypted traffic between an Azure VNet and an on-premises location (On-Premise) via the public Internet.
  • Azure ExpressRoute: Extends local networks to Azure via a private connection (does not use the Internet) provided by a provider. It is faster, more reliable, and more secure than a VPN.

Azure Storage Service (Ref: Parte_1, Página 16)

Sección titulada «Azure Storage Service (Ref: Parte_1, Página 16)»
  • Containers (Blob Storage): Optimized for storing massive amounts of unstructured data (text, binaries, videos, logs, images).
  • Disk Storage: Disks (SSD or HDD) for virtual machines to use as C:, D:, etc., drives.
  • Azure Files: Sets up network file shares (shared folders) that can be accessed via the standard SMB protocol (like a network drive in Windows).

This is key to optimizing costs.

  1. Hot: Optimized for data that is accessed very frequently. (Higher storage cost, lower access cost).
  2. Cool: For data that is accessed infrequently and is stored for at least 30 days. (Lower storage cost, higher access cost).
  3. Archive: For data that is rarely accessed (backups) and stored for at least 180 days. (Minimal storage cost, very high access cost).
    • Key note: Has flexible latency requirements (takes hours to “rehydrate” or become available).
  • Azure Cosmos DB: globally distributed NoSQL database service. Allows scaling performance and storage independently anywhere in the world.
  • Azure SQL Database: (PaaS) Relational Database as a Service (DaaS) based on the Microsoft SQL Server engine. You do not manage the server.
  • Azure Database for MySQL: (PaaS) Fully managed MySQL database service.
  • Azure Database for PostgreSQL: (PaaS) Relational database service based on the Postgres engine.

In the theory section, we saw what services are. Now we will see how we interact with them and create them. The AZ-900 exam expects you to know the different management methods.

There are several methods to create a resource like a VM. Each has a different purpose.

  • Reference: Parte_1, Página 32.
  • Method: The Azure Portal is the web-based graphical user interface (GUI).
  • Why it is important: It is the most visual and intuitive way. It is ideal for learning, for specific tasks, or for exploring new configuration options, as it guides you step-by-step (a “wizard”).
  • Key Concepts:
    • You must select an Image (e.g., Windows Server 2022, Ubuntu).
    • You must select a Size (e.g., “B2s” - defines CPU, RAM, and cost).
    • You must configure the Network (a VNet and Subnet, either new or existing).
    • You must create an administrator username and password (or SSH key).
  • Reference: Parte_1, Página 96.
  • Method: The Azure CLI (Command Line Interface) is a terminal tool (text commands) that runs on Windows (CMD/PowerShell), Mac, or Linux (Bash).
  • Why it is important: It is fundamental for automation and scripts. It is faster than the portal once you know the commands. The common command is az vm create ....
  • Key Concepts: You must provide the same information (Resource Group, Name, Image, etc.) but as parameters in a command.
  • Reference: Parte_1, Página 100.
  • Method: Azure PowerShell is a module that adds Azure commands (cmdlets) to PowerShell.
  • Why it is important: Just like the CLI, it is used for automation. It is the preferred tool in environments that are already highly standardized on Windows and PowerShell for server administration. The common command is New-AzVM ....
  • Reference: Parte_1, Página 98.
  • Method: Using an Azure Resource Manager (ARM) Template. This is a JSON (or Bicep) file that defines all resources, their configurations, and dependencies.
  • Why It's Important (Exam Trap!): This is the method for Infrastructure as Code (IaC).
    • Idempotency: The template ensures that the final result is always the same, no matter how many times you deploy it.
    • Repeatability: It is the best way to create identical environments (e.g., Development, Testing, and Production) without human error.
MethodTypeMain Use Case
Azure PortalGraphical (GUI)Learning, one-off tasks, visual exploration.
Azure CLICommand LineAutomation, scripting (especially on Linux/Mac).
Azure PowerShellCommand LineAutomation, scripting (especially in Windows).
ARM TemplateDeclarative (IaC)Complex, repeatable, and consistent deployments.
  • Reference: Parte_1, Página 30.
  • Why it is important: The VNet is the pillar of your infrastructure (IaaS). It is your private network in the cloud.
  • Key Concepts:
    1. Address Space: The total range of private IPs for the network (e.g., 10.1.0.0/16).
    2. Subnets: Divisions of that address space (e.g., 10.1.1.0/24 for VMs, 10.1.2.0/24 for DBs). Resources are deployed within the subnets.
  • Reference: Parte_1, Página 94.
  • Why it is important: This lab teaches you how to create a PaaS (Platform as a Service) service.
  • Key Concepts (Exam Trap!):
    1. Unlike a VM, here you do not manage the OS.
    2. To create an Azure SQL Database, you must first create a Logical Server (Azure SQL Server). This logical server is not a VM, it is an administration point (an endpoint) that contains one or more databases.
    3. You must configure the firewall rules of the logical server to allow your IP (or Azure services) to connect to it.

In this section, we cover high-level solutions (IoT, AI, Big Data) and the key tools we use to monitor and optimize our environment.

  • Definition: (According to Parte_1, Página 62) It is the ability of devices to collect and transmit information for data analysis.
  • Key Services:
    • Azure IoT Central: A fully managed SaaS solution. It is the fastest way to get started with IoT, as it provides a ready-to-use web interface to connect, monitor, and manage devices.
    • Azure IoT Hub: A PaaS service. It acts as a central message hub for large-scale bidirectional communication (device-to-cloud and cloud-to-device). It is more customizable than IoT Central.
    • Azure Sphere: A high-security platform for IoT devices that includes a microcontroller (hardware), a customized Linux OS (software), and a cloud security service.
  • Azure Synapse Analytics: (Formerly SQL Data Warehouse). It is a cloud-based enterprise data warehouse that unifies big data analytics and data warehousing.
  • Azure HDInsight: A fully managed open-source analytics service for enterprises. It allows you to run clusters of Apache Spark, Hadoop, Kafka, etc.
  • Azure Databricks: An analytics service based on Apache Spark, optimized for the Azure platform and focused on collaborative data science and data engineering.

Artificial Intelligence (AI) and Machine Learning (ML) (Ref: Parte_1, Página 49)

Sección titulada «Inteligencia artificial (IA) y Aprendizaje Automático (ML) (Ref: Parte_1, Página 49)»
  • Azure Machine Learning: (PaaS) A cloud-based service to develop, train, and deploy machine learning (ML) models.
  • Cognitive Services: These are pre-built APIs that enable applications to see, hear, speak, understand, and interpret. You don't need to be a data scientist to use them.
    • Examples: Vision Service (face recognition), Speech Service (audio transcription), Language Service (sentiment detection).
  • Azure Bot Service: Provides an environment to develop intelligent “bots” for the enterprise.

“Serverless” doesn't mean there are no servers; it means you don't manage them.

  • Azure Functions: (PaaS) Event-driven code. It is a block of code that runs in response to a “trigger,” such as a file upload or an HTTP request. You only pay for execution time (consumption model).
  • Azure Logic Apps: (PaaS) A service to automate and orchestrate tasks and workflows. It is a visual tool (graphical designer) to integrate applications and services (e.g., “When an email arrives in Office 365, if it has an attachment, save it in Blob Storage and send a message to Teams”).

Developing applications with DevOps and GitHub (Ref: Parte_1, Página 35)

Sección titulada «Desarrollar aplicaciones con DevOps y GitHub (Ref: Parte_1, Página 35)»
  • Azure DevOps: A set of collaboration tools for development:
    • Azure Pipelines: For CI/CD (continuous integration and deployment).
    • Azure Boards: Kanban boards for task management.
    • Azure Repos: Private Git code repositories.
  • GitHub: Development hosting platform (owned by Microsoft).
  • GitHub Actions: CI/CD directly within GitHub. It allows you to automate workflows to build, test, and deploy from GitHub to Azure.
  • Azure DevTest Labs: Allows you to quickly create development/test environments in Azure, controlling costs and minimizing waste (e.g., automatically shutting down VMs at night).

They are the interfaces that “speak” to the Azure Resource Manager (ARM).

  • Azure Portal: Graphical web interface (GUI).
  • Azure PowerShell: Automation module for Windows PowerShell.
  • Azure CLI: Cross-platform command-line tool (Windows, Linux, Mac).
  • Azure Cloud Shell: A terminal (Bash or PowerShell) integrated within the browser in the Azure Portal.
  • Azure Mobile App: App to manage resources from your mobile device.
  • Azure REST API: The underlying API used by all the previous tools.
  • Definition: (According to Parte_1, Página 2) Analyzes your deployed resources and provides customized recommendations based on best practices.
  • Key Categories (Exam Trap!):
    1. Cost: (e.g., “Resize this underutilized VM”).
    2. Security: (e.g., “Enable MFA on this account”).
    3. Reliability: (e.g., “Configure backups for your VM”).
    4. Performance: (e.g., “Improve your database performance”).
    5. Operational Excellence: (e.g., “Create Service Health alerts”).
  • Definition: (According to Parte_1, Página 10) A centralized service to collect, analyze, and act on telemetry (logs and metrics) from your cloud and on-premises environments.
  • Components:
    • Application Insights: (Part of Monitor) Focuses on monitoring the performance of your applications (APM).
    • Log Analytics: (Part of Monitor) The tool for writing queries (using KQL) against the collected logs.
    • Smart Alerts: Notifies you when issues are detected.
  • Definition: (According to Parte_1, Página 14) Provides you with a customized view of the status of Azure services and the regions you use.
  • Key Difference (Monitor vs. Service Health):
    • Azure Monitor: Monitors your applications and resources. (Is my VM running well?).
    • Azure Service Health: Monitors Microsoft's services. (Is there a problem in the “West Europe” region that affects me?).