AZ 900 - Azure Fundamentals Exam Complete Solution guide June 2022.

AZ 900 - Azure Fundamentals Exam High Availability - Agreed level of uptime. If a server goes down, we have another to go to. Read in a %. Specified in an SLA. Achieved using redundancy. Availability zones and availability certifications. Scalability - Scaling up: More CPU cores, memory, or disks Scaling out: More servers Elasticity - Elastic computing is the ability to quickly expand or decrease computer processing, memory, and storage resources to meet changing demands without worrying about capacity planning and engineering for peak usage. Automatic. Can see this in action in App Service automatic traffic manager Agility - Engineering resource availability. Provisioning new resources is fast. Business response to changing conditions or opportunity is easy in Azure. How fast Azure can allocated or deallocate resources Fault Tolerance - Continue providing service to underlying application even after the failure of one or more components in any layer. Disaster Recovery - Backups, screenshots, and restore strategy. Retain multiple copies of data as a security measure in case of unforeseen loss. Global Reach - The ability to reach audiences around the globe. Customer Latency Capabilities - Provide all services around the globe with a fast connection. Predictive Cost Considerations - Essentially a cost calculator for Azure. Security - Azure can control security policies for your services. You can monitor and change these. Economies of Scale for Azure - Amazon, Microsoft, Google, are not buying the most robust enterprise grade disks, storage controllers, server chassis, etc. Cost advantages that enterprises obtain due to scale of operation. Differences between Capital Expenditure (CapEx) and Operational Expenditure (OpEx) - Capital Expenditure is an expense a business incurs to create a benefit in the future. Upfront payment. Accounted for over useful life. Ex: buying new server hardware and software for data center. Operational Expenditure is an expense required for the day to day. Monthly or yearly payment. Accounted for in current month or year. An operating cost. Ex: IaaS offering from Azure What is the consumption-based model? - Pay for what you use. Function apps and logic apps have a consumption based plan. Describe IaaS - Azure VMs. You manage Applications, Data, Runtime, Middleware, O/S :: Azure manages Virtualization, Servers, Storage, and Networking Describe PaaS - Azure cloud services, Azure App services. You manage Applications and Data :: Azure manages Runtime, Middleware, O/S, Virtualization, Servers, Storage, and Networking Describe SaaS - Azure Websites. Azure manages Application, Data, Runtime, Middleware, O/S, Virtualization, Servers, Storage, and Networking. Public Cloud - Most common way of cloud computing. Cloud resources such as storage, and server are owned and operated by a third-party cloud service provider (Azure). All hardware, software and other supporting infrastructure is owned and managed by the cloud provider. Lower costs, no maintenance, near-unlimited scalability, high reliability Benefits: No CapEx, Agility, Consumption-based. Private Cloud - Computing resources used exclusively by one business or organization. The private cloud can be physically located at an on-site datacenter, or hosted by a third-party service provider. All hardware and software are dedicated solely to the organization - governments and banks use this a lot. More flexibility, improved security, high scalability. Benefits: Control, Security Hybrid Cloud - Data can move between private and public cloud greater flexibility and more deployment options. Use public cloud for high-volume, lower security needs such as web-based email, and the private cloud for sensitive, business-critical operations like financial reporting. In hybrid cloud, "cloud bursting" is also an option: when an application or resource runs in the private cloud until there is a spike in demand, such as seasonal event or tax filing, can then burst into the public cloud for additional computing resources. Gives control, flexibility, cost-effectiveness, scalability, and ease of transferring workloads gradually. Benefits: Flexibility, Compliance Regions - A set of datacenters deployed within a latency-defined perimeter and connected through a dedicated regional low-latency network. Availability Zones - Physically separate locations within an Azure region. Each Availability Zone is made up of one or more datacenters equipped with independent power, cooling, and networking. Offer high availability and low latency. Availability Sets - Help ensure applications remain online if high-impact maintenance event is required, or hardware failure. Made up of update domains and fault domains. UD: when maintenance occurs, update is sequenced through update domains FD: provide physical separation of a workload across different hardware in the data center. Resource Groups - A container that holds related resources for an Azure solution. Includes those resources (VMs, app services, storage account), that you want to manage as a group. Azure Resource Manager - Provides a consistent management layer to perform tasks through the Azure portal. All of these capabilities are also available through AZ PowerShell, CLI, REST APIs, and client SDK. Can manage infrastructure, create/ deploy, update resources with template json files. Can deploy, manage, monitor all the resources for your solution as a group, rather than individually. Repeatedly deploy solution throughout the dev cycle and have resources deployed in a consistent state. Define dependencies between resources so they're deployed in that correct order. Apply role-based access. Apply tags to logically organize resources. Clarify organizations billing by viewing groups of tagged resources. Benefits and usage of core Azure Architectural Components. - Easy to deploy and manage. Keep organized. TBC