Microsoft Azure Fundamentals AZ-900 Dumps in PDF

Explanation:

Because of geo-distribution you can deploy apps and data to regional datacenters around the globe, thereby ensuring that your customers always have the best performance in their region.

Reference:

https://docs.microsoft.com/learn/modules/fundamental-azure-concepts/benefits-of-cloud-computing

Explanation:

Reference:

https://docs.microsoft.com/learn/modules/fundamental-azure-concepts/benefits-of-cloud-computing

Explanation:

Agility is the ability to react quickly.

In the cloud, it takes a minute or two to create a Virtual Machine that is up and running. On the other hand, it takes days or weeks when we submit a request to purchase a physical server and by when it gets delivered.

Agility enables users to be able to allocate and deallocate resources very quickly, and that is a huge benefit of the cloud.

Reference:

https://coderjony.com/blogs/cloud-computing-concepts-high-availability-scalability-elasticity-agility-fault-tolerance-and-disaster-recovery

Explanation:

Scaling up and down, which is also referred to as vertical scaling, is the process of upgrading an existing virtual machine to a more powerful virtual machine, or downgrading to a smaller, less powerful virtual machine. In Azure, this means resizing the existing VM to a larger size with more RAM and more CPU, or to a smaller size with less RAM and less CPU. Because vertical scaling involves the re-size of virtual machines, this kind of scaling results in VM restarts.

Reference:

https://cloudacademy.com/course/advanced-vm-management-in-azure-1020/vertical-scaling-vs-horizontal-scaling/

Explanation:

Box 1: Yes
CapEx (Capital Expenditures): Purchasing an asset (factory, computer system, company car) is considered a capital expenditure. It requires payment for the entire asset, and the cost becomes an entry on the company’s balance sheet, depreciated over some period of time. This asset strategy also includes other costs such as upkeep, insurance, and personnel tied to the assets use.

Reference:

https://www.archive360.com/blog/capex-or-opex-on-premise-versus-the-cloud-which-saves-more-money

Explanation:

Box 1: No
Azure Functions integrates with Azure software as a service (SaaS) offerings, including Azure Cosmos DB, Azure Mobile Apps and Azure Service Bus.

Platform as a service. Platform as a service (PaaS) is a complete development and deployment environment in the cloud, with resources that enable you to deliver everything from simple cloud-based apps to sophisticated, cloud-enabled enterprise applications.

Box 2: Yes
Software as a service (SaaS) allows users to connect to and use cloud-based apps over the Internet. Common examples are email, calendaring, and office tools (such as Microsoft Office 365).

Box 3: Yes
Azure Virtual Machines are image service instances Azure IaaS uses to deploy persistent VMs with nearly any server workload that you want.

Reference:

https://azure.microsoft.com/en-us/resources/cloud-computing-dictionary/what-is-paas/
https://azure.microsoft.com/en-us/resources/cloud-computing-dictionary/what-is-saas
https://azure.microsoft.com/en-us/resources/cloud-computing-dictionary/what-is-azure/azure-iaas

Explanation:

Box 1: High availability

Box 2: Geo-distribution
You can direct traffic with a geo-distributed app using Azure and Azure Stack Hub.

Use the geo-distributed apps pattern
With the geo-distributed pattern, your app spans regions. You can default to the public cloud, but some of your users may require that their data remain in their region. You can direct users to the most suitable cloud based on their requirements.

Box 3: Scalability

Reference:

https://docs.microsoft.com/en-us/azure/architecture/hybrid/deployments/solution-deployment-guide-geo-distributed