Your company plans to migrate all its network resources to Azure.
You need to start the planning process by exploring Azure.
What should you create first?
Click on the arrows to vote for the correct answer
A. B. C. D.A
The first thing you create in Azure is a subscription. You can think of an Azure subscription as an 'Azure account'. You get billed per subscription.
A subscription is an agreement with Microsoft to use one or more Microsoft cloud platforms or services, for which charges accrue based on either a per-user license fee or on cloud-based resource consumption.
Microsoft's Software as a Service (SaaS)-based cloud offerings (Office 365, Intune/EMS, and Dynamics 365) charge per-user license fees.
Microsoft's Platform as a Service (PaaS) and Infrastructure as a Service (IaaS) cloud offerings (Azure) charge based on cloud resource consumption.
You can also use a trial subscription, but the subscription expires after a specific amount of time or consumption charges. You can convert a trial subscription to a paid subscription.
Organizations can have multiple subscriptions for Microsoft's cloud offerings.
https://docs.microsoft.com/en-us/office365/enterprise/subscriptions-licenses-accounts-and-tenants-for-microsoft-cloud-offeringsTo start the planning process for migrating network resources to Azure, the first thing you should create is a subscription. A subscription is a logical container used to provision and manage resources in Azure. It provides a way to organize and separate billing, access control, and resource utilization across different environments or departments within an organization.
When you create a subscription, you can choose between two types: a free trial subscription, which provides a limited amount of Azure resources for free for 12 months, or a paid subscription, which allows you to pay for the resources you use.
Once you have a subscription, you can create a resource group, which is a logical container used to group related Azure resources together. You can use a resource group to manage and organize resources based on their lifecycle or a specific project. For example, you might create a resource group for a production environment, one for a development environment, and another for a testing environment.
After you create a resource group, you can create a virtual network, which is an isolated network environment that you can customize to meet your organization's specific needs. A virtual network allows you to securely connect resources deployed in Azure, including virtual machines, cloud services, and storage accounts. You can also connect your virtual network to on-premises networks using VPN or ExpressRoute connections.
Finally, you can create a management group, which is a logical container used to manage access, policies, and compliance across multiple subscriptions. You can use a management group to apply policies and governance across your organization, regardless of which subscription the resources are in.
In summary, when planning to migrate network resources to Azure, you should start by creating a subscription, followed by a resource group, a virtual network, and a management group.
In this scenario, you are asked to recommend a cloud deployment solution for several custom applications that will provide invoicing services to the company's customers. The solution you choose should be able to accommodate the installation of prerequisite applications and services for each application.
A. Software as a Service (SaaS): This cloud deployment model allows customers to access and use software applications hosted on a cloud provider's infrastructure. In this case, the applications would be fully managed and provided to the company as a service without the need for the company to manage any infrastructure. However, since the applications are pre-built and hosted by the cloud provider, there may be limitations on the customization and integration options for the company.
B. Platform as a Service (PaaS): This cloud deployment model provides a platform for customers to build, deploy, and manage their own applications without having to worry about the underlying infrastructure. In this case, the company would have the ability to install the prerequisite applications and services required for their custom invoicing applications on the PaaS platform. This would allow for greater flexibility and customization options than SaaS, but still offload much of the infrastructure management to the cloud provider.
C. Infrastructure as a Service (IaaS): This cloud deployment model provides virtualized computing resources, including servers, storage, and networking, as a service. In this case, the company would have full control over the virtual machines and infrastructure that their custom invoicing applications run on. This option would provide the greatest level of customization and control, but also requires the most infrastructure management from the company.
Based on the requirements of this scenario, the recommended cloud deployment solution would be B. Platform as a Service (PaaS). This would provide the company with the ability to install and manage the prerequisite applications and services required for their custom invoicing applications, while offloading much of the underlying infrastructure management to the cloud provider.