4
0

Delete article

Deleted articles cannot be recovered.

Draft of this article would be also deleted.

Are you sure you want to delete this article?

More than 1 year has passed since last update.

AZ-900の試験を英語で受けるに至り、翻訳なしで勉強をしてまとめていく勉強ノートです。

自身の復習用としても記事を書くつもりではありますが、同じように英語で受講予定&翻訳なしでそのまま英語で勉強した方がやりやすい方の参考に少しでもなることが出来ればと思います。

日本語で勉強をしたい方は、こちらのサイトを是非参考にしてみてください:

学習内容

Describe the benefits of using cloud services
Describe the benefits of high availability and scalability in the cloud

High availability

Availability of resources when need is important.
→High availability focuses on ensuring maximum availability.

Azure is a highly available cloud environment with uptime guarantees.
The guarantees are part of service-level-agreements (SLAs).

What is SLAs?

  • Formal agreement between service providers and customer that guarantees the customer a stated level of service.

What SLAs mean for Azure

  • Up time - Represented as percentage
    • Related to the service or application availability aka up time
      • If the service was always available to use == 100% up time
  • Down time
    • When the service is unavailable
  • Credit
    • Credit a customer may be entitled to if the SLA is not met.
  • Each Azure service has its own SLA

Azure services’ uptime: mostly 99%~99.9%

99% == can be unavailable for up to…

  • 1.6 hours / week
  • 7.2 hours / month

99.9% == can be unavailable for up to…

  • 10 min / week
  • 43.2 minutes / month

Scalability

  • Ability to adjust resources to meet demand.
  • able to add more resources to better handle the increased demand, when systems are overwhelmed from a sudden peak traffic.
  • No overpayment for services
    • As the cloud is a consumption-based model == pay only for what is used.
    • can reduced resources and costs if demand drops off

Comes in two varieties: vertical and horizontal.

Vertical-scaling
Focused on increasing or decreasing the capabilities of resources.

Horizontal-scaling
Adding or subtracting the number of resources

Vertical scaling

Vertical scale up
When more processing power is needed while developing an app

  • adds more CPUs or RAM to the virtual machine

Vertical scale down
When you realized you had over-specified the needs

  • lowers CPU or RAM specifications.

Horizontal scaling

Scaling out deployed resources (either automatically or manually)
If there is a sudden steep jump in demand.

Scaling out ex:

  • add additional virtual machines or containers

Scaling in deployed resources (either automatically or manually)
If there is a significant drop in demand.


AZ-900:Describe cloud concepts① はこちら:

AZ-900:Describe cloud concepts② はこちら:

AZ-900:Describe cloud concepts③ はこちら:

AZ-900:Describe cloud concepts⑤ はこちら:

AZ-900:Describe cloud concepts⑥ はこちら:

AZ-900:Describe cloud concepts⑦ はこちら:

AZ-900:Describe cloud concepts⑧ はこちら:

AZ-900:Describe cloud concepts⑨ はこちら:

4
0
0

Register as a new user and use Qiita more conveniently

  1. You get articles that match your needs
  2. You can efficiently read back useful information
  3. You can use dark theme
What you can do with signing up
4
0

Delete article

Deleted articles cannot be recovered.

Draft of this article would be also deleted.

Are you sure you want to delete this article?