Fundamentals Module 1 Flashcards
Performance Predictability
Predicting the resources needed to deliver a positive experience for your customers.
Cost Predictability
Predicting or forecasting the cost of the cloud spend.
Can track your resource use in real time, monitor resources to ensure that you’re using them in the most efficient way, and apply data analytics to find patterns and trends that help better plan resource deployments.
Security needs vs cloud models
- maximum control of security => IaaS => provides physical resources but lets manage the operating systems and installed software, including patches and maintenance.
- patches and maintenance taken care of automatically => PaaS / SaaS
Types of manageability for cloud computing
- Management of the cloud: manage your cloud resources
- Management in the cloud: how you’re able to manage your cloud environment and resources
Management of the cloud
managing your cloud resources:
- Automatically scale resource deployment based on need.
- Deploy resources based on a preconfigured template, removing the need for manual configuration
- Monitor the health of resources and automatically replace failing resources.
- Receive automatic alerts based on configured metrics, so you’re aware of performance in real time.
Multi-cloud
Deal with two (or more) public cloud providers and manage resources and security in both environments.
Azure Arc
A set of technologies that helps manage your cloud environment
Azure VMware Solution
allows to run VMware workloads in Azure with seamless integration and scalability.
CapEx
a one-time, up-front expenditure to purchase or secure tangible resources.
OpEx
spending money on services or products over time.
Examples: renting a convention center, leasing a company vehicle, or signing up for cloud services are all examples of OpEx.
Benefits of consumption based model
- No upfront costs.
- No need to purchase and manage costly infrastructure that users might not use to its fullest potential.
- The ability to pay for more resources when they’re needed.
- The ability to stop paying for resources that are no longer needed.
Shared responsibility model: user is always responsible for
- The information and data stored in the cloud
- Devices that are allowed to connect to your cloud (cell phones, computers, and so on)
- The accounts and identities of the people, services, and devices within your organization
Shared responsibility model: cloud provider is always responsible for
- The physical datacenter
- The physical network
- The physical hosts
Cloud computing
the delivery of computing services over the internet
Common IT infrastructure
- virtual machines
- storage, databases
- networking
IaaS
- the cloud provider is responsible for maintaining the hardware, network connectivity (to the internet), and physical security.
- You’re responsible for everything else: operating system installation, configuration, and maintenance; network configuration; database and storage configuration; installation and configuration, patching and updates, and security.
IaaS - essentially renting the hardware in a cloud datacenter, but what to do with that hardware is up to you.
IaaS common scenarios
- Lift-and-shift migration: You’re standing up cloud resources similar to your on-prem datacenter, and then simply moving the things running on-prem to running on the IaaS infrastructure.
- Testing and development: You have established configurations for development and test environments that you need to rapidly replicate. You can stand up or shut down the different environments rapidly with an IaaS structure, while maintaining complete control.
PaaS
- the cloud provider maintains the physical infrastructure, physical security, and connection to the internet.
- in addition to IaaS provider also maintain the operating systems, middleware, development tools, and business intelligence services that make up a cloud solution.
- don’t have to worry about the licensing or patching for operating systems and databases.
- depending on the configuration, you or the cloud provider may be responsible for networking settings and connectivity within your cloud environment, network and application security, and the directory infrastructure.
PasS common scenarios
- Development framework: PaaS provides a framework that developers can build upon to develop or customize cloud-based applications. Cloud features such as scalability, high-availability, and multi-tenant capability are included, reducing the amount of coding that developers must do.
- Analytics or business intelligence: Tools provided as a service with PaaS allow organizations to analyze and mine their data, finding insights and patterns and predicting outcomes to improve forecasting, product design decisions, investment returns, and other business decisions.
SaaS
essentially renting or using a fully developed application
Example: Email, financial software, messaging applications, and connectivity software.
SaaS common scenarios
- Email and messaging.
- Business productivity applications.
- Finance and expense tracking.
Cloud concepts that support performance predictability
- Autoscaling
- Load balancing
- High availability
Benefits of using cloud services
- high availability and scalability
- reliability and predictability
- security and governance manageability
Azure Sovereign regions
- US Government (separate instance, separate portal, separate lifecycle)
- Azure China (+operated by a Chinese company)
3.
Number of azure public regions
60+
Types of support plans
- Basic
- DEVELOPER
- STANDARD
- PROFESSIONAL DIRECT
Support plan comparison: 24/7 ACCESS TO TECHNICAL SUPPORT BY EMAIL AND PHONE AFTER A SUPPORT REQUEST IS SUBMITTED
- Basic - not available
- Developer - Available during business hours by email only.
Support plan comparison: CASE SEVERITY AND RESPONSE TIME
- Basic - no
- Developer - Minimal business impact (Sev C): Within eight business hours
- Basic: Moderate business impact (Sev B): Within four hours / Critical business impact (Sev A): Within one hour
- Professional Direct: Minimal business impact (Sev C): within four business hours / Moderate business impact (Sev B): Within two hours / Critical business impact (Sev A): Within one hour
Support plan comparison: THIRD-PARTY SOFTWARE SUPPORT WITH INTEROPERABILITY AND CONFIGURATION GUIDANCE AND TROUBLESHOOTING
No for BASIC
