AZ-900 Azure Fundamentals Reviewer
AZ-900 Azure Fundamentals Reviewer
AZ-900 Azure Fundamentals Reviewer
• Describe terms such as High Availability, Scalability, Elasticity, Agility, Fault Tolerance, and Disaster Recovery
High availability. The ability to keep services up and running for long periods of time, with very little downtime, depending on the
service in question.
Scalability. The ability to increase or decrease resources for any given workload. You can add additional resources to service a
workload (known as scaling out), or add additional capabilities to manage an increase in demand to the existing resource (known as
scaling up). Scalability doesn't have to be done automatically.
Scaling out - add additional resources (scaling in - decrease resources)
scaling up - add additional capabilities (scaling down - decrease capabilities)
Elasticity. The ability to automatically or dynamically increase or decrease resources as needed. Elastic resources match the current
needs, and resources are added or removed automatically to meet future needs when it’s needed (and from the most advantageous
geographic location). A distinction between scalability and elasticity is that elasticity is done automatically.
Agility. The ability to react quickly. Cloud services can allocate and deallocate resources quickly. They are provided on-demand via self-
service, so vast amounts of computing resources can be provisioned in minutes. There is no manual intervention in provisioning or
deprovisioning services.
Fault tolerance. The ability to remain up and running even in the event of a component (or service) no longer functioning. Typically,
redundancy is built into cloud services architecture, so if one component fails, a backup component takes its place. This type of service
is said to be tolerant of faults.
Disaster recovery. The ability to recover from an event which has taken down a cloud service. Cloud services disaster recovery can
happen very quickly, with automation and services being readily available to use.
https://azure.microsoft.com/en-us/overview/cloud-computing-dictionary/
Cloud providers such as Microsoft, Google, and Amazon are large businesses, and are able to leverage the benefits of economies of
scale, and then pass those benefits on to their customers.
This is apparent to end users in a number of ways, one of which is the ability to acquire hardware at a lower cost than if a single user
or smaller business were purchasing it.
• Describe the differences between Capital Expenditure (CapEx) and Operational Expenditure (OpEx)
Capital Expenditure (CapEx): This is the up front spending of money on physical infrastructure, and then deducting that up front
expense over time. The up front cost from CapEx has a value that reduces over time.
Operational Expenditure (OpEx): This is spending money on services or products now and being billed for them now. You can deduct
this expense in the same year you spend it. There is no up front cost, as you pay for a service or product as you use it.
The following list of cloud service types describes the management responsibilities for the user and the cloud provider as compared to
on-premises systems:
IaaS requires the most user management of all the cloud services. The user is responsible for managing the operating systems, data,
and applications.
PaaS requires less user management. The cloud provider manages the operating systems, and the user is responsible for the
applications and data they run and store.
SaaS requires the least amount of management. The cloud provider is responsible for managing everything, and the end user just
uses the software.
Describe the differences between Public, Private and Hybrid cloud models
• Describe Public cloud
A public cloud is owned by the cloud services provider (also known as a hosting provider). It provides resources and services to
multiple organizations and users, who connect to the cloud service via a secure network connection, typically over the internet.
Public cloud models have the following characteristics:
Ownership - Ownership refers to the resources that an organization or end user uses. Examples include storage and processing power.
Resources do not belong to the organization that is utilizing them, but rather they are owned and operated by a third party, such as
the cloud service provider.
Multiple end users - Public cloud modes may make their resources available to multiple organizations.
Public access - Public access allows the public to access the desired cloud services.
Availability - Public cloud is the most common cloud-type deployment model.
Connectivity - Users and organizations are typically connected to the public cloud over the internet using a web browser.
Skills - Public clouds do not require deep technical knowledge to set up and use its resources.
• Describe Private cloud
A private cloud is owned and operated by the organization that uses the resources from that cloud. They create a cloud environment
A single virtual machine with premium storage has an SLA of 99.9%. You can quickly migrate existing virtual machines to Azure
through “lift and shift”. Lift and shift is a no-code option where each application is migrated as-is, providing the benefits of the cloud
without the risks or costs of making code changes.
By placing virtual machines in an availability set, you protect against datacenter failures and increases the SLA to 99.95%.
Adding virtual machines to availability zones protects from entire datacenter failures and increases the SLA to 99.99%, which is
highest level of protection that is provided.
For multi-region disaster recovery, region pairs protect and provide data residency boundaries.
Availability sets are a way for you to ensure your application remains online if a high-impact maintenance event is required, or if a
hardware failure occurs.
Availability sets are made up of Update domains (UD) and Fault domains (FD).
Update domains. When a maintenance event occurs (such as a performance update or critical security patch applied to the host), the
update is sequenced through update domains. Sequencing updates using update domains ensures that the entire datacenter isn't
unavailable during platform updates and patching. Update domains are a logical section of the datacenter, and they are implemented
with software and logic.
Fault domains. Fault domains provide for the physical separation of your workload across different hardware in the datacenter. This
includes power, cooling, and network hardware that supports the physical servers located in server racks. In the event the hardware
that supports a server rack becomes unavailable, only that rack of servers would be affected by the outage.
Availability zones are physically separate locations within an Azure region that use availability sets to provide additional fault
tolerance.
Containers are often used to create solutions using a microservice architecture. This architecture is where you break solutions into
smaller, independent pieces. For example, you may split a website into a container hosting your front end, another hosting your back
end, and a third for storage. This split allows you to separate portions of your app into logical sections that can be maintained, scaled,
or updated independently.
Forecasts or predictions from machine learning can make apps and devices smarter. For example, when you shop online, machine
learning helps recommend other products you might like based on what you've purchased. Or when your credit card is swiped,
machine learning compares the transaction to a database of transactions and helps detect fraud. And when your robot cleaner
vacuums a room, machine learning helps it decide whether the job is done.
Azure Cognitive Services
Cognitive services are a collection of domain-specific pre-trained AI models that can be customized with your data. They are
categorized broadly into vision, speech, language, and search. For more information about each service, see the links in the resources
section.
Vision makes it possible for apps and services to accurately identify and analyze content within images and videos.
Speech services can convert spoken language into text, or produce natural-sounding speech from text using standard (or
customizable) voice fonts.
Language services can understand the meaning of unstructured text or recognize the speaker’s intent.
Knowledge services create rich knowledge resources that integrate into apps and services.
Enable apps and services to harness the power of a web-scale, ad-free search engine. Use search services to find information across
billions of web pages, images, videos, and news search results.
The Azure Machine Learning service provides a cloud-based environment you can use to develop, train, test, deploy, manage, and
track machine learning models. It fully supports open-source technologies, so you can use tens of thousands of open-source Python
packages with machine learning components such as TensorFlow and scikit-learn. Rich tools, such as Jupyter notebooks or the Visual
Studio Code Tools for AI, make it easy to interactively explore data, transform it, and then develop, and test models. Azure Machine
Learning service also includes features that automate model generation and tuning to help you create models with ease, efficiency,
and accuracy.
The Azure Machine Learning service can auto-generate a model and auto-tune it for you. It will let you start training on your local
machine, and then scale out to the cloud. When you have the right model, you can easily deploy it in a container such as Docker in
Azure. Use Machine Learning service if you work in a Python environment, you want more control over your machine learning
algorithms, or you want to use open-source machine learning libraries.
• Describe Serverless computing and Azure products that are available for serverless
computing such as Azure Functions, Logic Apps and Event Grid
Serverless computing is a cloud-hosted execution environment that runs your code but abstracts the underlying hosting
environment. You create an instance of the service and you add your code. No infrastructure configuration or maintenance is
required, or even allowed.
You configure your serverless apps to respond to events. An event could be a REST endpoint, a periodic timer, or even a message
received from another Azure service. The serverless app runs only when it's triggered by an event.
Scaling and performance are handled automatically, and you are billed only for the exact resources you use. You don't even need to
reserve resources.
Physical security is the first line of defense to protect computing hardware in the datacenter.
Identity & access controls access to infrastructure and change control.
Perimeter layer uses distributed denial-of-service (DDoS) protection to filter large-scale attacks before they can cause a denial of
service for end users.
Networking layer limits communication between resources through segmentation and access controls.
Compute layer secures access to virtual machines.
Application layer ensures applications are secure and free of vulnerabilities.
Data - In almost all cases, attackers are after data:
Stored in a database
Stored on disk inside virtual machines
Stored on a SaaS application such as Microsoft 365
Stored in cloud storage
Azure helps alleviate your security concerns. But security is still a shared responsibility. How much of that responsibility falls on us
depends on which model we use with Azure. We use the defense in depth rings as a guideline for considering what protections are
adequate for our data and environments.
Security is a shared responsibility:
You can create, enforce, and log, application and network connectivity policies across subscriptions, and virtual networks, centrally.
Azure Firewall uses a static public IP address for your virtual network resources, which allows outside firewalls to identify traffic
originating from your virtual network. The service is fully integrated with Azure Monitor for logging and analytics.
Azure Firewall provides many features, including:
Built-in high availability.
Unrestricted cloud scalability.
Inbound and outbound filtering rules.
Azure Monitor logging.
With Azure Firewall you can configure:
Application rules that define fully qualified domain names (FQDNs) that can be accessed from a subnet.
Network rules that define source address, protocol, destination port, and destination address.
Azure Application Gateway also provides a firewall, called the Web Application Firewall (WAF). WAF provides centralized, inbound
protection for your web applications against common exploits and vulnerabilities.
• Describe Azure DDoS Protection
Distributed Denial of Service (DDoS) attacks attempt to overwhelm and exhaust an application’s resources, making the application
slow or unresponsive to legitimate users. DDoS attacks can be targeted at any endpoint that is publicly reachable through the
internet. Thus, any resource exposed to the internet, such as a website, is potentially at risk from a DDoS attack.
The Azure DDoS Protection service protects your Azure applications by scrubbing traffic at the Azure network edge before it can
impact your service's availability.
An initiative definition is a set of policy definitions to help track your compliance state for a larger goal. Initiative assignments reduce
the need to make several initiative definitions for each scope.
For example, you could create an initiative named Enable Monitoring in Azure Security Center, with a goal to monitor all the available
security recommendations in your Azure Security Center.
Under this initiative, you would have the following policy definitions:
Like a policy assignment, an initiative assignment is an initiative definition assigned to a specific scope. Initiative assignments reduce
the need to make several initiative definitions for each scope. This scope could also range from a management group to a resource
group.
You can define initiatives using the Azure portal, or command-line tools. In the portal, you use the "Authoring" section.
• Describe Role-Based Access Control (RBAC)
Role-based access control provides fine-grained access management for Azure resources, enabling you to grant users only the rights
they need to perform their jobs. RBAC is provided at no additional cost to all Azure subscribers.
Examples of when you might use RBAC include when you want to:
Allow one user to manage VMs in a subscription, and another user to manage virtual networks.
Allow a database administrator (DBA) group to manage SQL databases in a subscription.
Allow a user to manage all resources in a resource group, such as VMs, websites, and subnets.
Allow an application to access all resources in a resource group.
RBAC uses an allow model. This means that when you are assigned a role, RBAC allows you to perform certain actions, such as read,
write, or delete. Therefore, if one role assignment grants you read permissions to a resource group, and a different role assignment
grants you write permissions to the same resource group, you will have write permissions on that resource group.
• Describe Locks
resource locks help you prevent accidental deletion or modification of your Azure resources. You can manage these locks from within
the Azure portal. To view, add, or delete locks, go to the SETTINGS section of any resource's settings blade.
CanNotDelete means authorized admins can still read and modify a resource, but they can't delete the resource.
ReadOnly means authorized admins can read a resource, but they can't delete or update the resource. Applying this lock is like
restricting all authorized users to the permissions granted by the Reader role.
• Describe Azure Advisor security assistance
• Describe Azure Blueprints
Azure Blueprints enable cloud architects to define a repeatable set of Azure resources that implement and adhere to an
organization's standards, patterns, and requirements. Azure Blueprint enables development teams to rapidly build and deploy new
environments with the knowledge that they're building within organizational compliance with a set of built-in components that
speed up development and delivery.
Azure Blueprint is a declarative way to orchestrate the deployment of various resource templates and other artifacts, such as:
Role assignments
Policy assignments
Azure Resource Manager templates
Resource groups
The process of implementing Azure Blueprint consists of the following high-level steps:
Create an Azure Blueprint.
Assign the blueprint.
Enabling diagnostics
• Describe the uses and options with Azure subscriptions such access control and offer
types
Azure offers free and paid subscription options to suit different needs and requirements.
A free account. Get started with 12 months of popular free services, a credit to explore any Azure service for 30 days, and 25+
services that are always free. Your Azure services are disabled when the trial ends or when your credit expires for paid products,
unless you upgrade to a paid subscription.
Pay-As-You-Go. This subscription allows you to pay for what you use by attaching a credit or debit card to your account. Organizations
can apply to Microsoft for invoicing privileges.
Member offers. Your existing membership to certain Microsoft products and services affords you credits for your Azure account and
reduced rates on Azure services. For example, member offers are available to Microsoft Visual Studio subscribers, Microsoft Partner
Network members, Microsoft BizSpark members, and Microsoft Imagine members.
• Describe subscription management using Management groups
The organizing structure for resources in Azure has four levels: management groups, subscriptions, resource groups, and resources.
The following image shows the relationship of these levels i.e. the hierarchy of organization for the various objects
https://azure.microsoft.com/pricing/tco/calculator
In the example above, if either service fails the whole application will fail. In general, the individual probability values for each service
are independent. However, the composite SLA value for this application is:
99.95 percent × 99.99 percent = approx 99.94 percent
Conversely, you can improve the composite SLA by creating independent fallback paths. For example, if SQL Database is unavailable,
you can put transactions into a Queue for processing at a later time.
With the design shown in the image above, the application is still available even if it can't connect to the database. However, it fails if
both the SQL Database and the Queue fail simultaneously. If the expected percentage of time for a simultaneous failure is 0.0001 ×
0.001, i.e. (1.0 - 0.9999) x (1.0 - 0.999), the composite SLA for this combined path would be:
Database *OR* Queue = 1.0 − (0.0001 × 0.001) = 99.99999 percent
Therefore, the total composite SLA is:
Web app *AND* (Database *OR* Queue) = 99.95 percent × 99.99999 percent = ~ 99.95 percent
• Describe how to determine an appropriate SLA for an application
Azure customers can use SLAs to evaluate how their Azure solutions meet their business requirements and the needs of their clients
and users. By creating your own SLAs, you can set performance targets to suit your specific Azure application.
When creating an Application SLA consider the following:
Identify workloads. A workload is a distinct capability or task that is logically separated from other tasks, in terms of business logic and
data storage requirements. Each workload has different requirements for availability, scalability, data consistency, and disaster
recovery. To ensure that application architecture meets your business requirements, define target SLAs for each workload. Account for
Resiliency is the ability of a system to recover from failures and continue to function. It's not about avoiding failures, but responding
to failures in a way that avoids downtime or data loss. The goal of resiliency is to return the application to a fully functioning state
following a failure. High availability and disaster recovery are two crucial components of resiliency.
When designing your architecture you need to design for resiliency, and you should perform a Failure Mode Analysis (FMA). The goal
of an FMA is to identify possible points of failure and to define how the application will respond to those failures.
Knowledge check:
1. Which of the following answers define performance targets, like uptime, for an Azure product or service?
Service-Level Agreements
That's correct. The SLA defines performance targets for an Azure product or service.
Support Plans
Usage Meters
2. You have two services with different SLAs. The composite SLA is determined by?
Adding the SLAs percentages together
Multiplying the SLAs percentages together
That's correct. To determine a composite SLA, you multiply the individual SLAs together.
Taking the lowest SLA percentage
3. Deploying an app can be done directly to what level of physical granularity?
Region
That's Correct. Azure organizes infrastructure around regions, which include multiple datacenters. You can pick the region you want
resources deployed into. You can't select a specific datacenter or location within a datacenter.
Datacenter
Server rack
4. To use Azure datacenters that are made available with power, cooling, and networking capabilities independent from other
datacenters in a region, choose a region that supports _________?
Geography distribution
Service-Level Agreements (SLAs)
Availability Zones
That's Correct. Availability Zones are datacenters set up to be an isolation boundary from others in the region, with their own power,
cooling, and networking. If one zone in a region goes down, other Availability Zones in the region continue to work.
5. Application availability refers to what?
The Service-Level Agreement of the associated resource.
Application support for an availability zone.
The overall time that a system is functional and working.
That's Correct. The time that a system is working is referred to as the application availability.
Describe service lifecycle in Azure
• Describe Public and Private Preview features
Microsoft offers previews of Azure services, features, and functionality for evaluation purposes. With Azure Previews, you can test pre-
release features, products, services, software, and even regions. Previews allow users early access to functionality. Additionally, users
providing feedback on the preview features helps Microsoft improve the Azure service.
There are two categories of preview that are available:
Private preview - An Azure feature is available to certain Azure customers for evaluation purposes.
Public preview - An Azure feature is available to all Azure customers for evaluation purposes.
Azure portal Preview
You can access preview features that are specific to the Azure portal from the https://preview.portal.azure.com page. Typical portal
preview features provide performance, navigation, and accessibility improvements to the Azure portal interface.