Q: 7
DRAG DROP Your company plans to deploy an application to the following endpoints: • Ten virtual machines hosted in Azure. • Ten virtual machines hosted in an on-premises data center environment All the virtual machines have the- Azure Pipelines agent. You need to implement a release strategy for deploying the application to the endpoints. What should you recommend using to deploy the application to the endpoints? To answer, drag the appropriate components to the correct endpoint. Each component may be used once, more than once, or not at all. You may need to drag the split bar between panes or soon to view content NOTE: Each correct selection n worth one point. 
Drag & Drop
Discussion
Makes sense to use deployment groups for both the Azure and on-prem VMs here since all have the Pipeline agent. Management group/resource group don’t work across hybrid, and deployment group fits this setup. Pretty sure this is what Microsoft wants.
Ten Azure VMs: deployment group, On-prem VMs: deployment group. Resource group is tempting but only makes sense for Azure resources.
Both Azure and on-prem VMs: deployment group for each. That's what fits if all have agents, right?
Ten virtual machines hosted in Azure → A deployment group, Ten virtual machines hosted in an on-premises data center environment → A deployment group
Tired of the group naming in Azure DevOps, but yeah-deployment group for both Azure and on-prem VMs.
Makes sense to use deployment group for both Azure and on-prem VMs since they've all got the pipeline agent installed. Resource groups wouldn't cover the on-prem machines, and management/app roles don't handle deployment targeting. Pretty sure this is the right mapping. Anyone see it differently?
Ten virtual machines hosted in Azure → A deployment group
Ten virtual machines hosted in an on-premises data center environment → A deployment group
Ten virtual machines hosted in Azure → A deployment group
Ten virtual machines hosted in an on-premises data center environment → A deployment group
Seriously wish they'd stop mixing up all these 'groups', but it's deployment group for both endpoints here.
Ten Azure VMs -> deployment group, On-prem VMs -> deployment group. All have agents so both get grouped the same way here.
I don’t think deployment group is right for on-prem here. Resource group for both Azure and on-prem makes more sense to me.
Deployment group for Azure VMs, resource group for on-prem VMs.
Be respectful. No spam.
