-

-
Microsoft Azure
Fundamentals
AZ-900

III-Networking
By Sajjad Ghaffoori
YouTube.com/c/iiinetworking

Page: Facebook.com/iiinetworking
Group: Facebook.com/groups/iiinetworking

@III_Networking

Linkedin.com/in/ sajjad-ghaffoori-6b4674134
Linkedin.com/company/iii-networking

orhanergun.net/instructors/sajjad-ghaffoori
- Microsoft Azure Fundamentals
- AZ-900
- Exam Cost: 100$
- Exam Center: Pearson Vue
- NO Prerequisites
- Acquired Badges: Microsoft Certified Azure Fundamentals
- Expires: 2 years
- Questions: 30-60 MCQ’s
- Exam Length: 60 Minutes
- Azure Certifications
- Course Content
- Cloud Concepts
- Azure Core Services
- Azure Core Networking Services
- Azure Security and Compliance
- Azure Solutions
- Azure Pricing and Resources
Cloud Concepts
- The Cloud
- A host or a Company
- would build a Data center that can server thousands of real networks
- and starts providing you the service in a way
- that they’d completely care about CapEx

- Services that includes whatever you might ever need

- to build and maintain a real network
- you would hear about it, but never see it

- your role would be to operate, benefit, and shutdown

- when you benefit, pay, when not, don’t pay ☺
- Benefits of Cloud Computing
- Pay as you benefit, and pay as you grow (Economic)
- Supports services Vertical Scaling (Scale up) and Horizontal Scaling (Scale out)
- Supports distributed resources per service
- alongside with load balancers between them (Scalable)
- Internal Back-up system is taken already for all the services
- in case of disasters, your data is automatically cloned to another site
- Capital Expenses
- with on-premise networks
- everything, from getting the nodes (servers and appliances)
- till the smallest terminal that connects to the power cable on the power boards
- all the safety, electricity, fire fighting, air cooling, and operation costs are yours
- not just to pay, but to consider, design, think of, consider redundancy
- hire the right teams for it and elect the best provider for each service of these!!
- monitoring and health checks as well are your responsibility (had enough yet!)

- so, equipment costs, operation costs, labor costs, and locale costs
- are yours to consider, monitor, and optimize
- Operational Expenses
- and when it comes to software
- after all the headaches of the hardware part
- operating systems should be provided
- for servers, DNS, Load Balancers, monitors, counters, logging systems
- AND their licenses
- for each of the mentioned operating systems
- and services

- So, how would all that differ with Cloud Computing!

- it depends on the service model
- Service Models
- Infrastructure as a Service (IaaS)
- this is the infra you need
- to install an OS upon and start using
- you can decide the resources
- and Azure will build and operate in seconds
- Platform as a Service (PaaS)
- furthermore, this is an IaaS + an OS installed
- start developing and operating directly
- Service Models
- Function as a Service (FaaS)
- even the development environment is pre-installed
- upon all the previous services mentioned
- Software as a Service (SaaS)
- start benefiting directly
- from a software ready to be consumed
- Shared Responsibility Model
- IaaS
- Azure: service resources, operating resources, and accessibility
- Customer: operating system and beyond
- PaaS
- Azure: service resources, operating resources, accessibility, and OS
- Customer: Application Development and beyond
- SaaS
- Azure: service resources, operating resources, accessibility, OS, and DEV.
- Customer: nothing, just benefit
- Cloud Types and Architecture
- Public Cloud
- online, global, not owned literally by the customer
- partial selective services to be obtained
- secured and protected
- sharing resources with others
- Private Cloud
- an on-premise network of CapEX and OpEX under your responsibility
- Hybrid Cloud
- a mix of both, bridged together, covered with security, and interconnected
Core Services
- Azure Architectural Components
- Geographics
- A geographical location to provide the nearest customers in that area
- normally it would refer to a name of a geographic region on the map
- examples: USA, Canada, Asia, Europe, and Australia
- https://azure.microsoft.com/en-us/global-infrastructure/geographies/#overview
- Regions
- within a geography, there are multiple regions
- as a geography might be large enough
- having more specifically distributed locations would serve closer customer
- in a better way
- Azure Architectural Components
- Availability Zones
- zoom more inside a region
- to find 3 or more AZ’s within
- each can contain one or more Data Centers
- each DC with an independent resources supply

*services hosted within an AZ can be Zonal (you replicate) or Zone-Redundant

(automatically replicated across the AZ’s of a region)
*regions are paired between each other
*AZ’s are interconnected within a region
- Azure Service Control
- Resources Group
- a container (not a tag) that collages your services
- some of them, not all the services
- for easier selective management for those grouped services
- apply one action, all the included components will get affected
- all of which is done by the ARM
- Azure Resource Manager
- one single unified graphical dashboard
- to control the Azure services and all their functions
- Accounting Management
- Azure billing account
- an account for charging and billing
- follows and manages payments and their analytics
- receives invoices and pays them
- for one or more subscriptions
- Azure Subscriptions
- an Azure Resources Account
- group resources in a subscription
- to manage the content of the subscription financially
- Azure Virtual Machines
- Same as the on-premise virtualized, software-based machines
- hosted on Azure and supports more flexibility
- vertical scaling (scale up) for more resources per VM
- horizontal scaling (scale out) for more VM’s per application
- Network or Application Load Balancers between the VM’s
- all of that is named Scale Set
- wide distribution of the VM’s in a different locations for high availability
- Availability Sets
- Azure PaaS Services
- Azure Application Service
- a PaaS with a development environment ready to go
- based on Azure VM
- supports that same Azure VM scalability and HA features
- environments include .NET, Java, Ruby, and Python
- Azure Container Instances (ACI)
- create and deploy containers
- easy and simple to manage
- supports your own containers as well
- Azure Kubernetes Service (AKS)
- Kubernetes on Azure, for high level management of Containers
- Azure Storage Services
- Blob Storage
- object storing on the cloud
- regardless of the structure and the type of the data
- accessed remotely and serves multiple usages
- Disk Storage
- bridged and connected with VM’s
- supports Data disk, and OS disk for real storage
- and temporary disk for one power cycle storage
- File Storage
- shared “Disk” type storage
- supports SMB and NFS
- Azure support for Databases
- Azure SQL Database
- a PaaS having a VM and an OS ready to host an SQL database directly
- SQL Managed Instance
- a PaaS having a VM, an OS, and an SQL empty DB ready to host tables
- support horizontal scaling
- multi-AZ deployment, for HA
- Cosmos DB
- over the regions, highly available, multi-engine Data Base
- supports both Relational (SQL) and non-Relational (non-SQL) DB’s
- deep inquires and analytics
- API’s integration and easy migration
- Azure support for Databases
- other SQL engines
- PostgreSQL is also supported as an SQL engine to be deployed
- on Azure Managed Instances
- Azure provides
- Database Migration Service (DMS)
- with both the online and the offline migration model (method)