AZ-900 | Aula 02 | Curso Completo | Microsoft Azure Fundamentals | Preparação para o Exame AZ900

Overview

This video is the first lesson in a full AZ-900 (Microsoft Azure Fundamentals) course, focused on Module 1: Cloud Concepts. It introduces what cloud computing is, compares public, private, and hybrid cloud models, and explains core cloud service categories and concepts commonly tested on the AZ-900 exam.

Cloud computing: Definition and value

• Cloud computing uses cloud processing + storage + analytics capacity, often with a focus on cost analysis versus on-premises environments.
• Business motivations include:
  • not always knowing the actual compute capability
  • uncertainty about how quickly you can scale
  • risk of scaling failures
• Cloud enables:
  • Scalability: rapid, dynamic increase/decrease of resources
  • Fast provisioning/deprovisioning of infrastructure

Cloud models: Public, Private, and Hybrid

1) Public Cloud

• Offered by major vendors (examples mentioned: AWS, GCP, IBM Cloud, Alibaba Cloud).
• Enables quick provisioning with controlled costs.
• Uses a shared provider model, where the service is available to many customers.
• Security is framed as strong: public cloud is described as more secure than typical company data centers, which rely on physical controls (e.g., secured access like biometric/secure doors).
• Security/compliance is explained via provider adherence to industry standards and contractual commitments (conceptually referenced with SOX-like compliance ideas).

2) Private Cloud

• Access is primarily restricted to the organization (inside-company access).
• The organization gains control, but also accepts more operational responsibility and associated risk.
• Examples include internal resources (e.g., domain controllers, websites, databases) hosted within the company or in a third-party data center.
• If failures occur in the company environment, clients can lose service.

3) Hybrid Cloud

• Combines the scalability/elastic capacity of public cloud with the security/control of private cloud, connected together.
• Often used for:
  • temporary expansion (e.g., handling peak workloads)
  • experimentation, such as testing AI or new databases without repeating full private infrastructure procurement and bureaucracy
• Benefits include enabling people with on-prem infrastructure experience to transition into cloud administration roles.

Cost, provisioning, scaling, and elasticity (exam-relevant)

CapEx vs OpEx

• Capital Expenditure (CapEx) vs Operating Expenditure (OpEx)
  • Public cloud is framed largely as OpEx: pay for what you use, and deprovision when not needed.
  • Private cloud is framed more like CapEx: buy resources upfront.

Provisioning vs deprovisioning

• Provisioning: creating/providing resources.
• Deprovisioning: removing resources afterward; payment stops when usage stops.

Scaling types

• Vertical scaling: increase capacity of the same resource (resize/refactor).
• Horizontal scaling: add more instances/resources (the lesson emphasizes scaling may be both vertical and horizontal).

Elasticity

• Resources can scale out for a period, then return to normal automatically.
• Driven by usage patterns (usage-based behavior).

High availability and disaster recovery

High Availability (HA)

• Availability commitments are tied to Service Level Agreements (SLAs).
• If uptime targets aren’t met, the lesson indicates contractual protections (conceptually compensation/penalties).

Disaster Recovery (DR) vs HA

• Disaster Recovery is not the same as High Availability.
• DR uses backups to recover and distribute data to another region quickly after a major failure.
• The lesson illustrates the concept with a scenario involving using another geographic location if a disaster occurs.

Other cloud benefits

• Agility: faster provisioning/configuration compared to on-premises bureaucracy.
• Global reach: deploy services across countries/regions without needing local providers.
• Latency management: improve responsiveness by measuring and optimizing.
• Predictable cost: estimate spending over time (the explanation references a timeframe such as 30–60 days).

Cloud service models (pizza analogy)

The video uses a “pizza” analogy to explain layers and who is responsible for what:

Infrastructure as a Service (IaaS)

• The provider manages underlying infrastructure (e.g., VMs, storage, networking).
• The customer manages/configures the operating system and application stack running on the VM.

Platform as a Service (PaaS)

• The provider manages more of the underlying stack.
• The customer focuses on results/application/data usage, with less infrastructure maintenance.

Software as a Service (SaaS)

• The customer mainly uses the application.
• The provider delivers the complete application capability; the customer primarily concerns themselves with data.

Earlier, the lesson also uses an idea like “local services / you do everything” to convey that more responsibility sits with the consumer as you move toward lower-level control.

Serverless computing

• Serverless runs code in response to events, removing the need to manage servers directly.
• The provider manages where/how the infrastructure runs.
• The customer focuses on code and event triggers.
• It is still described as usage-based (consumption model), and the user typically selects a region at most.

Mini practice questions (AZ-900 style)

The speaker includes quick multiple-choice checks, such as:

• Which option is not a category of cloud computing
  • Mentions: Networks as a Service, PaaS, IaaS, SaaS
  • The incorrect option varies based on what was covered next.
• Which statement about OpEx is true
  • Selected answer: Operations Expenses (OpEx) means you pay/pay attention to only the computing resources you use.
• Which option is not a benefit of cloud services
  • Selected answer: geographic isolation (“doesn’t exist” in that phrasing).
• A question identifying a type that is not a category/type
  • Mentions distributed cloud as the wrong choice.

Main speakers / sources

• Single main instructor/speaker (teaching in Portuguese; refers to themselves as “with me” and signs off with “see you in the next video”).
• Microsoft Azure is the primary product context.
• Cloud provider examples referenced: AWS, Google Cloud (GCP), IBM Cloud, Alibaba Cloud.
• AZ-900 exam references include DP-900 mentioned in passing (in related terminology context, such as provisioning concepts).