Network protection blocks malicious sites before users connect, so it's really the first defense layer. Automated stuff comes into play after something gets through. Pretty sure about D here.
D imo, but are they asking for the best characteristic or just any feature? If they're focused on persistence specifically, that rules out B and C since not all sensitivity labels enforce encryption or are limited to predefined categories.
Conditional Access policy is what you'd use for this, so C. It lets you target specific groups and require MFA on sign-in. Pretty sure the others can't do that directly. Someone correct me if that's off?
Option C is the one here since Conditional Access lets you enforce MFA just for certain groups. If the question wanted the broadest control (like tenant-wide), would that change anything or would C still apply?
Option A and D for sure. Azure Firewall operates at the VNet boundary so it protects virtual machines (A) and the network itself (D). E seems like a trap since SharePoint Online is SaaS, not IaaS, so Firewall can't protect it directly. Pretty straightforward unless I'm missing some edge case here.
Yeah, Azure Firewall works at the network layer so it protects resources inside VNets like virtual machines and the VNets themselves. It's not meant for things like Exchange or SharePoint. So A and D, unless I'm missing something.
B makes sense since it's about encrypting data that's stored, not data in transit. The other options are all about securing data moving over networks. Pretty sure B lines up with 'encryption at rest'. Agree?