ExamTopics Logo
Mail Us[email protected]
Menu
Microsoft Discussions
exam questions

Exam AZ-104 All Questions

View all questions & answers for the AZ-104 exam
Go to Exam

Exam AZ-104 topic 5 question 13 discussion

Actual exam question from Microsoft's AZ-104
Question #: 13
Topic #: 5
[All AZ-104 Questions]

HOTSPOT -
You have an Azure subscription that contains the resource groups shown in the following table.

RG1 contains the resources shown in the following table.

VM1 is running and connects to NIC1 and Disk1. NIC1 connects to VNET1.
RG2 contains a public IP address named IP2 that is in the East US location. IP2 is not assigned to a virtual machine.
For each of the following statements, select Yes if the statement is true. Otherwise, select No.
NOTE: Each correct selection is worth one point.
Hot Area:

Show Suggested Answer Hide Answer
Suggested Answer:
by fochistu at Dec. 1, 2020, 6 p.m.

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
Submit Cancel
NickyDee
Highly Voted 4 years, 7 months ago
Tested this in an identical lab: 1. YES. I was able to move the storage from RG1 to RG2, however it stayed in the West US region. 2. YES. I was able to move NIC1 from RG1 to RG2 which was associated with VM1 and VNET1 subnet1, however it stayed in the West US region. 3. NO. The location of IP2 did not change. However I was able to move LP2 from RG2 to RG1 as it isn't associated with any other resource, however it stayed in the East US region. All resources moved to the new resource groups, but the region did not change
upvoted 241 times
itgg11
3 years, 6 months ago
YYN. tested in lab
upvoted 11 times
...
rgullini
4 years, 4 months ago
Also tested, you are correct.
upvoted 18 times
silver_bullet666
3 years, 10 months ago
I also tested and was able to move the NIC attached to a running VM to a different RG. Took a while though!
upvoted 6 times
...
...
...
mlantonis
Highly Voted 4 years, 2 months ago
Correct Answer: Box 1: Yes You can move the Storage Account to RG2, however it stayed in the West US region. You cannot change the Region, you need to recreate the Storage Account. Box 2: Yes You can move move NIC1 to RG2 which was associated with VM1 and VNET1 subnet1, however it stayed in the West US region. You can move a NIC to a different RG or Subscription by selecting (change) next to the RG or Subscription name. If you move the NIC to a new Subscription, you must move all resources related to the NIC with it. If the network interface is attached to a virtual machine, for example, you must also move the virtual machine, and other virtual machine-related resources. Box 3: No You can move IP2 to RG1, as it isn't associated with any other resource, however it stayed in the East US region. The location will not change.
upvoted 159 times
AzureCrawler001
3 years, 1 month ago
mlantonis - can I buy you a beer or coffee?
upvoted 33 times
cosmicT73
6 months, 1 week ago
Lol :)
upvoted 1 times
...
Georgego
2 years, 7 months ago
machine learning Antonis is a gun!
upvoted 7 times
...
JohnnyChimpo
2 years, 6 months ago
Y-N Mlantonis' answer
upvoted 7 times
...
...
manortmar
4 years ago
"as it isn't associated with any other resource" really? According to the above explanation being associated shouldn't be a problem to move between RGs.
upvoted 3 times
...
mlantonis
4 years, 2 months ago
Note: Resources can be everywhere regardless of the resource group they belong to. The resource group is only a collection of metadata relative to the resources defined inside it. You can move a resource from one resource group to another group. The resources in a resource group can be located in different regions than the resource group. Reference: https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/overview
upvoted 41 times
...
...
Amir1909
Most Recent 1 year, 6 months ago
Yes Yes No
upvoted 2 times
...
SkyZeroZx
1 year, 7 months ago
Correct Answer: Box 1: Yes You can move the Storage Account to RG2, however it stayed in the West US region. You cannot change the Region, you need to recreate the Storage Account. Box 2: Yes You can move move NIC1 to RG2 which was associated with VM1 and VNET1 subnet1, however it stayed in the West US region. You can move a NIC to a different RG or Subscription by selecting (change) next to the RG or Subscription name. If you move the NIC to a new Subscription, you must move all resources related to the NIC with it. If the network interface is attached to a virtual machine, for example, you must also move the virtual machine, and other virtual machine-related resources. Box 3: No You can move IP2 to RG1, as it isn't associated with any other resource, however it stayed in the East US region. The location will not change.
upvoted 1 times
...
SgtDumitru
1 year, 8 months ago
Y/Y/N When moving NIC to different RG, you only move NIC's meta-data location, not NIC itself. NIC remains in same location where VM is located.
upvoted 1 times
...
marioZuo
2 years ago
we need to know if the public IP is a standard or a basic one. Standard IP will blocked RDP if now NSG on NIC.
upvoted 1 times
...
Josete1106
2 years ago
Y Y N is correct!
upvoted 1 times
...
Durden871
2 years, 5 months ago
Literally just tested this albeit backwards. RG1 - US East RG2 - US West Created Linux VM in RG1 My VM is up and running with the auto-created NIC attached, all in RG1. Validating....Taking awhile. This really does take awhile. It moved to the US West located RG2 without turning off or decommissioning the VM. The location of the NIC is in US East still. The correct answer is YYN.
upvoted 1 times
...
orionduo
2 years, 6 months ago
YYN You can move move NIC1 to RG2 which was associated with VM1 and VNET1 subnet1, however it stayed in the West US region. You can move a NIC to a different RG or Subscription by selecting (change) next to the RG or Subscription name. If you move the NIC to a new Subscription, you must move all resources related to the NIC with it. If the network interface is attached to a virtual machine, for example, you must also move the virtual machine, and other virtual machine-related resources.
upvoted 1 times
...
hitit
2 years, 10 months ago
Y-Y-N This is my test result.
upvoted 1 times
...
EmnCours
2 years, 11 months ago
Answer Y-Y-N
upvoted 1 times
...
Jayad
3 years, 4 months ago
I know many of you have tested moving the NIC to a different RG, but, is it a supported configuration ?
upvoted 1 times
...
Redimido
3 years, 6 months ago
1. YES - 2. YES - I tested it personally. It will work, although you will have to update your scripts (if you have any associated with the moved NIC) to use the new NIC's resourceID, as this one will change also. 3. NO
upvoted 1 times
...
JohnPhan
3 years, 9 months ago
Yes No - You can move HDInsight clusters to a new subscription or resource group. However, you can't move across subscriptions the networking resources linked to the HDInsight cluster (such as the virtual network, NIC, or load balancer). In addition, you can't move to a new resource group a NIC that is attached to a virtual machine for the cluster. No
upvoted 2 times
...
AubinBakana
3 years, 11 months ago
You can't just move the NIC, it's part of the VM.
upvoted 3 times
AubinBakana
3 years, 11 months ago
I am referring to NIC1 in RG1.
upvoted 1 times
...
...
Kamex009
3 years, 11 months ago
This question was asked on exam taken on 8/22/2021
upvoted 5 times
...
Kopy
4 years ago
"In addition, you can't move to a new resource group a NIC that is attached to a virtual machine for the cluster." https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/move-support-resources
upvoted 3 times
slsl
3 years, 7 months ago
Apply only to Microsoft.HDInsight no VMs
upvoted 1 times
...
...
Load full discussion...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel