Whiz Labs Practice Test 1 Flashcards
B. No
Explanation:
Since rg-staging-2 has Read Only lock defined.
Read lock means that users can not make any chages/updates in the resource group
Read Lock is the same as applying reader role on the RG
Reader role allow only */Read operation, excluding move operation.
A. Yes
Explanation:
We can move resources from one resource group to another, and in this case the source resource group does not have any lock defined and receiving resource group has got delete lock, which stops from deleting resources
Delete lock on a resource group means that any resource which is contained by a resource group cannot be deleted
The idea behind delete lock is to avoid any resource deletion even by mistake.
A resource group can be deleted by a user by mistake, in case, there is no lock on the resource group
B. No
Explanation:
Moving a resource from one resource group results in metadata changes, and it does not have any effect on resources
Both rg-staging1 and rg-production-4 do not have any locks
But we still cannot move App Service resources from resource group rg-staging-1 to the target resource group ‘rg-production-4’ because it already contains web resources
The destination resource group must not have any existing App Service Resources. App Service resources include Web Apps, App Service plans etc
A company has an Azure subscription named whizlabstaging.
They also have a resource group named whizlabs-rg. The resource group has an internal load balancer named whizlab-internal and a public load balancer named whizlab-public
They want to give a user named whizlabusr permissions to configure both load balancers
The solution must follow the principle of least privilege
Which role would you assign the user to allow the addition of a backend pool to the load balancer “whizlab-internal”
A. Contributor Role on whizlab-internal
B. Network Contributor role on whizlab-internal
C. Network Contributor role on whizlabs-rg
D. Owner role on whizlab-internal
C. Network Contributor role on whizlabs-rg
Explanation:
To provide the ability to add the backend pool, whizlabusr must have the read access to the details of the virtual machine and network
For this reason, the user should be assigned a network contributor role within the resource group. In this role, whizlabusr will have the read access to the VM and full access to the groups network resources.
The other options are invalid since they would only provide access to the load balancer itself. They will not provide access to the other resources such as the virtual machines that needed to be added to the backend pool
no
A. Yes
Explanation:
Since whizlabuser1 user has the role of Cloud Device Admin and is a Group Owner, the user would be able to add registered or joined devices to the group
A. Yes
Explanation:
Since whizlabuser2 holds the role of User Administrator, they can update the membership of any assigned group, regardless of whether they are owner of the group or not because of the role associated with. They can add users, devices to any assigned group in Azure AD
B. No
Explanation:
Since the group is Dynamic in nature, you wont be able to add user or devices manually. Device whizlabvm2 shall be governed by Rules and automatically removed or added dynamically
A. Ensure the virtual machines are created in the different regions
B. Ensure the virtual machines are created in the same resource group
C. Ensure the virtual machines are created in the same virtual network
D. Ensure the virtual machines are created in the same availability set or virtual machine scale set
D. Ensure the virtual machines are created in the same availability set or virtual machine scale set
Explanation:
You look at the comparison between the Standard and Basic Load Balancer in the Microsoft documentation. It clearly mentions that the virtual machines need to be part of an availability set or virtual machine scale set
C. Ensure the virtual machines are created in the same virtual network
Explanation:
You look at the comparison between the Standard and Basic Load Balancer in the Microsoft documentation. It clearly mentions that that virtual machines need to be part of a single virtual network
A. An application gateway that uses the Standard tier
B. An application gateway that uses the WAF tier
C. A network security group
D. An internal load balancer
E. A public load balancer
D. An internal load balancer
Explanation:
3 tier architecture shown below will help us to answer question number 11 and number 12
IN Question 11, the Business Logic Tier has the requirement of NOT being accessible from the Internet. Hence, we should spin up an internal load balancer with private IP
Hence the correct answer is D and all other answers are wrong.
A. An application gateway that uses the standard tier
B. An application gateway with WAF
C. A network security group
D. Internal Load Balancer
E. Public Load Balancer
B. An application gateway with WAF
Explanation:
To protect web servers against SQL injection attacks, one can use the WAF feature
Application gateway has the option to provide a WAF.
A. Yes
Explanation:
In order to attach a network interface to a virtual machine, it must be created in the same region as the virtual machine. It also is a part of the same virtual network hosting the virtual machine.
Hence, the requirements for ensuring the network interface can be attached to the virtual machine are met
A. Yes
First, we need to understand the difference between data and metadata. Metadata is not the actual data, but additional useful ifnormation about the data. A resource group contains metadata regarding Azure resources, not the actual resources
A resource group contains the list of resources and some additional useful info like the region in which resources exist, components of each resource, etc… In view of this, a resource group and actual resources contained by the resource group can be in a different region.
The basic constraint here is that a VM and all its components should be in the same network and in the same region
B. No
Explanation:
In order to attach a network interface to a virtual machine, it must be created in the same region as the virtual machine. It also must be part of the same virtual network hosting the virtual machine
Here the virtual machine is in the West US region and the network interface is being created in the Central US region
A. whizlabvm1 only
B. whizlabvm1 and whizlabfiledata only
C. whizlabvm1 and whizlabdbonly
D. whizlabvm1, whizlabstore1 and whizlabdb
E. whizlabvm1, whizlabdata, whizlabfiledata and whizlabdb
A. whizlabvm1 only
Explanation:
Here the recovery services vault (whizlabvault1) is located in the Central US region. This means that only resources in this region can be backed up in the recovery services vault. And for this, we have only the virtual machine location in this region
B. whizlabfiledata only
Explanation:
In Azure recovery service vault (RSV), we can backup only those resources, which are in the same region as of RSV.
In the current scenario the RSV( whizlabvault2) region is west us. Storage account whizlabstore1 is also in the same region.
Whizlabstore1 have two resources - a blob container named whizlabdata and a file share named whizlabfiledata
Azure blob data cannot be backed up in RSV as it requires a backup vault. In RSV, the Azure file share can be backed up. There are no other resources in the same region other than these two
D. whizlabuser1 and whizlabusr2
Explanation:
When a device is joined to Azure AD, the user who joins the computer to the domain is added as the local administrator.
Also, the Global Admin will be added as an administrator to the system
You need to increase the number of CPU cores and memory for running Azure Container INstance
What steps do you take to carry out this task?
A. Stop the ACI
B. Redeploy the ARM ACI deployment template
C. In the Azure portal, select the Scale Up for ACI container
D. Update Dockerfile
E. Delete the ACI
B. Redeploy the ARM ACI deployment template
E. Delete the ACI
Explanation:
Unfortunately, Azure does not allow you to scale Azure Container Instances. You need to delete the current ACI and create a new instance with the new resource requirements. The most convenient way is to reuse the ARM template from the previous ACI deployment. You can find the template under the Deployments section on the ACIs resource group blade. When you select the deployment template and click on the Redeploy button on the top bar, the Azure portal opens the Customer deployment screen.
Here you click on the Edit Parameters and can change the number of CPU cores, memory and restart policy.
If you have not deleted the previous ACI and keep the same name for the new instance, you will get a deployed failed error when you click on the Create button
You create an ACI multi container group.
Please select all correct statements about the ACI group
A. ACI group is similar to the AKS node
B. Containers in the ACI group share the same resources
C. You can add new containers to the already running ACI group
D. You can select different VM sizes for each container in a group
E. ACI group can include the init containers
F. You can create multi container ACI groups on Linux only
B. Containers in the ACI group share the same resources
E. ACI group can include the init containers
F. You can create multi container ACI groups on Linux only
Explanation:
You can create the groups of the ACI containers. These ACI groups are similar to AKS pods. The group is a collection of containers that runs or schedules on the same host machine. It shares the hosts resources, local network and storage volumes. You can deploy the multi container group only on Linux using ARM templates, YAML, or Docker Compose
Option B is correct because the containers in the ACI group share the same resources of the host machine. The containers share not only the same resources but also local network and storage volumes
Option E is correct because the ACI group can include the init containers. This container type prepares the run of your application. They set up accounts, databases or running scripts. Only after the init containers finish their jobs, the application containers start
Option F is correct because you can create multi container ACI groups on Linux only
Option A is incorrect because the ACI group is similar to the AKS pods but not to the AKS nodes
Option C is incorrect because you need to delete the old ACI group and create a new one with additional containers. Usually, you can deploy a multi container group using ARM templates or YAML scripts. The Docker Compose can also be used
Option D is incorrect because the ACI multi container group shares the same host machine and you cannot dedicate any VMs to a particular container