Q: 16
From Azure Security Center, you need to deploy SecPol1.
What should you do first?
Options
Discussion
B . You gotta set the management group first, otherwise you can't assign SecPol1 to anything meaningful. Seen this step called out in a bunch of official guides and labs, pretty sure it's the right starting point.
Does anyone know if the question says there's already a management group? If so, would C (create an initiative) be next or are we missing something else in the requirements?
C/B? Tempting to pick C since initiatives bundle policies, but you can't assign anything without a management group first. B feels right, seen similar on practice but open if I'm missing a twist.
C here. Initiative brings policies together, so I'd pick that before thinking about the scope. Not totally sure though.
I thought C at first since initiatives bundle policies, but now not so sure. C
Had something like this in a mock. You always need to define the scope first, so creating an Azure Management group (B) makes the most sense here. Without that, there's nothing for your security policy to attach to at org level. Pretty sure B is correct but open to other thoughts if I missed a nuance.
B imo. You need the management group in place to define where SecPol1 goes. Option C is tempting but without a scope set first, you can't deploy. Seen similar setup in previous practice sets.
B for this one.
B tbh. Before you assign a security policy in Security Center, you need a management group so you have something to target at the right scope. Just setting up the policy before that wouldn't work as expected. Not 100% sure but that's how it's been in similar questions. Anyone disagree?
Be respectful. No spam.