Which of the following characteristics should you consider when deciding whether to deploy an application or service to a virtual machine 1 hardware requirements?

86.Choose the scenarios that need virtualization software.i.A client needs to run more than one operating system at a timeii.Software vendor needs to use virtual machines to ship entiresoftware configurationsiii.A user needs disks that can be arbitrarily frozen, woken up, copied,backed up, amd transported between hostsiv.A company needs an application to reduce hardware and electricitycosts.A.i, ii and iiiB.ii, iii and ivC.i, ii and ivD.i, ii, iii and iv

87.Which of the following characteristics should to consider when decidingwhether to deploy an application or service to a virtual machine?i.Hardware requirementsii.Software support and compatibilityiii.Licensingiv.Performance and resource requirements

Get answer to your question and much more

TUTORIALDFD4043 CLOUD COMPUTING88.You are a software tester that is testing a complex application that is runningwithin a single virtual machine. You have recently encountered a rare andintermittent software defect that developers have been unable to reproduceor troubleshoot in the past. Choose the steps should you take to allowdevelopers to recreate the issue?

Get answer to your question and much more

89.Choose which of the following virtualization management approaches canhelp organizations maintain optimal hardware resource utilization over time.i.Automatically reconfiguring virtual machines based on performancestatistics.ii.Deploying multiple copies of virtual machines to different host servers.iii.Automatically moving virtual machines based on changes to resourcerequirements.iv.Placing virtual machines on isolated virtual network switches.v.Storing virtual machines on a Storage Area Network (SAN)

Get answer to your question and much more

TUTORIALDFD4043 CLOUD COMPUTINGD.i and v90.Choose the effect of a server after it is being virtualized.A.A virtualized server uses less energy than a no-virtualized server.B.A virtualized server uses more storage space than a non-virtualizedserver.C.A virtualized server needs to run more than one operating system at atime that makes it performance being reduced.D.A virtualized server applications reduce the hardware workload andelectricity costs by 100 percent compared to non-virtualized server whichonly reduces hardware workload and electricity costs by 10 percent.91.Figure 3.0Apply the virtualization concept and identify the correct items for the virtualmachine shown in Figure 3.0.31

TUTORIALDFD4043 CLOUD COMPUTINGA.i. Virtual machineii. Operating systemiii. ISAB.i. Operating systemii. Virtual machineiii. ISAC.i. ISAii. Operating systemiii. Virtual machineD.i. Virtual machineii. ISAiii. Operating system

Upload your study docs or become a

Course Hero member to access this document

Upload your study docs or become a

Course Hero member to access this document

End of preview. Want to read all 53 pages?

Upload your study docs or become a

Course Hero member to access this document

Skip to main content

This browser is no longer supported.

Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.

Choose an Azure compute service

Azure offers many ways to host your application code. The term compute refers to the hosting model for the computing resources that your application runs on. The following flowchart will help you to choose a compute service for your application.

If your application consists of multiple workloads, evaluate each workload separately. A complete solution can incorporate two or more compute services.

Choose a candidate service

Use the following flowchart to select a candidate compute service.

Definitions:

• "Lift and shift" is a strategy for migrating a workload to the cloud without redesigning the application or making code changes. Also called rehosting. For more information, see Azure migration and modernization center.
• Cloud optimized is a strategy for migrating to the cloud by refactoring an application to take advantage of cloud-native features and capabilities.

The output from this flowchart is a starting point for consideration. Next, perform a more detailed evaluation of the service to see if it meets your needs.

This article includes several tables that can help you to make these tradeoff decisions. You might find that the initial candidate isn't suitable for your particular application or workload. In that case, expand your analysis to include other compute services.

Understand the basic features

If you're not familiar with the Azure service selected in the previous step, read the overview documentation to understand the basics of the service.

• Azure App Service. A managed service for hosting web apps, mobile app back ends, RESTful APIs, or automated business processes.
• Azure Spring Apps. A managed service designed and optimized for hosting Spring Boot apps.
• Azure Kubernetes Service (AKS). A managed Kubernetes service for running containerized applications.
• Azure Batch. A managed service for running large-scale parallel and high-performance computing (HPC) applications
• Azure Container Instances. The fastest and simplest way to run a container in Azure, without having to provision any virtual machines and without having to adopt a higher-level service.
• Azure Functions. A managed FaaS service.
• Azure Service Fabric. A distributed systems platform that can run in many environments, including Azure or on premises.
• Azure Virtual machines. Deploy and manage VMs inside an Azure virtual network.
• Azure Container Apps. A managed service built on Kubernetes, which simplifies the deployment of containerized applications in a serverless environment.
• Azure Red Hat OpenShift. A fully managed OpenShift cluster for running containers in production with Kubernetes.

Understand the hosting models

Cloud services, including Azure services, generally fall into three categories: IaaS, PaaS, or FaaS. (There's also SaaS, software-as-a-service, which is out of scope for this article.) It's useful to understand the differences.

Infrastructure-as-a-Service (IaaS) lets you provision individual VMs along with the associated networking and storage components. Then you deploy whatever software and applications you want onto those VMs. This model is the closest to a traditional on-premises environment, except that Microsoft manages the infrastructure. You still manage the individual VMs.

Platform-as-a-Service (PaaS) provides a managed hosting environment, where you can deploy your application without needing to manage VMs or networking resources. Azure App Service and Azure Container Apps are PaaS services.

Functions-as-a-Service (FaaS) goes even further in removing the need to worry about the hosting environment. In a FaaS model, you deploy your code and the service automatically runs it. Azure Functions is a FaaS service.

There's a spectrum from IaaS to pure PaaS. For example, Azure VMs can autoscale by using virtual machine scale sets. This automatic scaling capability isn't strictly PaaS, but it's the type of management feature found in PaaS services.

In general, there's a tradeoff between control and ease of management. IaaS gives the most control, flexibility, and portability, but you have to provision, configure and manage the VMs and network components you create. FaaS services automatically manage nearly all aspects of running an application. PaaS services fall somewhere in between.

CriteriaVirtual MachinesApp ServiceAzure Spring AppsService FabricAzure FunctionsAzure Kubernetes ServiceContainer InstancesAzure BatchAzure Container AppsAzure Red Hat OpenShift

Application composition	Agnostic	Applications, containers	Applications, microservices	Services, guest executables, containers	Functions	Containers	Containers	Scheduled jobs	Containers	Containers
Density	Agnostic	Multiple apps per instance via app service plan	Multiple apps per service instance	Multiple services per VM	Serverless 1	Multiple containers per node	No dedicated instances	Multiple apps per VM	Serverless	Multiple containers per node
Minimum number of nodes	1 2	1	2	5 3	Serverless 1	3 3	No dedicated nodes	1 4	Serverless	6 8
State management	Stateless or Stateful	Stateless	Stateless	Stateless or stateful	Stateless	Stateless or Stateful	Stateless	Stateless	Stateless or Stateful	Stateless or Stateful
Web hosting	Agnostic	Built in	Built in	Agnostic	Not applicable	Agnostic	Agnostic	No	Agnostic	Agnostic
Can be deployed to dedicated VNet?	Supported	Supported5	Supported	Supported	Supported 5	Supported	Supported	Supported	Supported	Supported
Hybrid connectivity	Supported	Supported 6	Supported	Supported	Supported 7	Supported	Not supported	Supported	Supported	Supported

Notes

1. If using Consumption plan. If using App Service plan, functions run on the VMs allocated for your App Service plan. See Choose the correct service plan for Azure Functions.
2. Higher SLA with two or more instances.
3. Recommended for production environments.
4. Can scale down to zero after job completes.
5. Requires App Service Environment (ASE).
6. Use Azure App Service Hybrid Connections.
7. Requires App Service plan or Azure Functions Premium plan.
8. 3 for master nodes, and 3 for worker nodes.

DevOps

CriteriaVirtual MachinesApp ServiceAzure Spring AppsService FabricAzure FunctionsAzure Kubernetes ServiceContainer InstancesAzure BatchAzure Container AppsAzure Red Hat OpenShift

Local debugging	Agnostic	IIS Express, others 1	Visual Studio Code, Intellij, Eclipse	Local node cluster	Visual Studio or Azure Functions CLI	Minikube, others	Local container runtime	Not supported	Local container runtime	Minikube, others
Programming model	Agnostic	Web and API applications, WebJobs for background tasks	Spring Boot, Steeltoe	Guest executable, Service model, Actor model, Containers	Functions with triggers	Agnostic	Agnostic	Command line application	Agnostic	Agnostic
Application update	No built-in support	Deployment slots	Rolling upgrade, Blue-green deployment	Rolling upgrade (per service)	Deployment slots	Rolling update	Not applicable		Revision management	Rolling update

Notes

1. Options include IIS Express for ASP.NET or node.js (iisnode); PHP web server; Azure Toolkit for IntelliJ, Azure Toolkit for Eclipse. App Service also supports remote debugging of deployed web app.
2. See Resource Manager providers, regions, API versions and schemas.

Scalability

CriteriaVirtual MachinesApp ServiceAzure Spring AppsService FabricAzure FunctionsAzure Kubernetes ServiceContainer InstancesAzure BatchAzure Container AppsAzure Red Hat OpenShift

Autoscaling	Virtual machine scale sets	Built-in service	Built-in service	Virtual machine scale sets	Built-in service	Pod auto-scaling1, cluster auto-scaling2	Not supported	N/A	Scaling rules4	Pod auto-scaling, cluster auto-scaling
Load balancer	Azure Load Balancer	Integrated	Integrated	Azure Load Balancer	Integrated	Azure Load Balancer or Application Gateway	No built-in support	Azure Load Balancer	Integrated	Azure Load Balancer or Application Gateway
Scale limit3	Platform image: 1000 nodes per scale set, Custom image: 600 nodes per scale set	30 instances, 100 with App Service Environment	500 app instances in Standard	100 nodes per scale set	200 instances per Function app	100 nodes per cluster (default limit)	20 container groups per subscription (default limit).	20 core limit (default limit).	5 Environments per region, 20 Container apps per environment, 30 Replicas per container app	60 nodes per cluster (default limit)

Notes

1. See Autoscale pods.
2. See Automatically scale a cluster to meet application demands on Azure Kubernetes Service (AKS).
3. See Azure subscription and service limits, quotas, and constraints.
4. See Set scaling rules in Azure Container Apps.

Availability

CriteriaVirtual MachinesApp ServiceAzure Spring AppsService FabricAzure FunctionsAzure Kubernetes ServiceContainer InstancesAzure BatchAzure Container AppsAzure Red Hat OpenShift

SLA	SLA for Virtual Machines	SLA for App Service	SLA for Azure Spring Apps	SLA for Service Fabric	SLA for Functions	SLA for AKS	SLA for Container Instances	SLA for Azure Batch	SLA for Azure Container Apps	SLA for Azure Red Hat OpenShift
Multi region failover	Traffic manager	Traffic manager	Traffic manager, Multi-Region Cluster	Azure Front Door	Traffic manager	Not supported	Not Supported		Not Supported	Not supported

For guided learning on Service Guarantees, review Core Cloud Services - Azure architecture and service guarantees.

Security

Review and understand the available security controls and visibility for each service

• App Service
• App Spring Apps
• Azure Kubernetes Service
• Batch
• Container Instances
• Functions
• Service Fabric
• Virtual machine - Windows
• Virtual machine - LINUX

Other criteria

CriteriaVirtual MachinesApp ServiceApp Spring AppsService FabricAzure FunctionsAzure Kubernetes ServiceContainer InstancesAzure BatchAzure Container AppsAzure Red Hat OpenShift

SSL	Configured in VM	Supported	Supported	Supported	Supported	Ingress controller	Use sidecar container	Supported	Ingress controller	Supported
Cost	Windows, Linux	App Service pricing	Azure Spring Apps pricing	Service Fabric pricing	Azure Functions pricing	AKS pricing	Container Instances pricing	Azure Batch pricing	Azure Container Apps pricing	Azure Red Hat OpenShift pricing
Suitable architecture styles	N-Tier, Big compute (HPC)	Web-Queue-Worker, N-Tier	Spring Boot, Microservices	Microservices, Event-driven architecture	Microservices, Event-driven architecture	Microservices, Event-driven architecture	Microservices, task automation, batch jobs	Big compute (HPC)	Microservices, Event-driven architecture	Microservices, Event-driven architecture

The output from this flowchart is a starting point for consideration. Next, perform a more detailed evaluation of the service to see if it meets your needs.

Consider limits and cost

Perform a more detailed evaluation looking at the following aspects of the service:

• Service limits
• Cost
• SLA
• Regional availability
• Compute comparison tables

Next steps

• Core Cloud Services - Azure compute options. This Microsoft Learn module explores how compute services can solve common business needs.

Feedback

Submit and view feedback for

Which is the main factor that determines the number of virtual machines?

Which of the following terms describes a situation in which many virtual machines are deployed without proper it our site?

Which of the following terms describe a situation in which many virtual machines are deployed?

Which of the following are the benefits of the vmware server virtualization solution choose three?