Yeah, D and E make sense here because they're both focused on security standards at the logical level. Specifying SHA-2 for certs (D) directly addresses cryptographic policy, and E is about trust management processes between NSX managers. Pretty sure that's what the question wants since A/B/C are more about implementation. Agree?
Yeah it's D and E. Both map directly to policy compliance at the logical design level, like using SHA-2 certs and having a solid cert management process. The rest are more about implementation or sizing, not high-level security standards. Pretty sure on this but let me know if you see it differently.
I see why D and E fit, since they're about security standards at the logical design layer. Using SHA-2 for certs and keeping thumbprints updated both map to compliance requirements. Not 100% confident if B could sneak in but these seem strongest. Disagree?