C (Lack of visibility and tracking): In cloud-native environments, organizations often struggle with monitoring and tracking workloads across dynamic, distributed, and multi-tenant architectures. Traditional visibility tools may not fully cover cloud-native assets like containers, serverless functions, or microservices, making it harder to detect threats and enforce policies.
D (Increased attack surface): Cloud-native architectures introduce many additional components—APIs, microservices, third-party integrations, and distributed data—which all expand the organization's overall attack surface. More entry points for attackers create additional security challenges compared to traditional on-prem environments.
Other options explained:
A: User roles can be managed with proper IAM systems.
B: Polymorphism refers to code behavior in programming, not a core security challenge in cloud-native design.
E: Credential validation is part of basic access control but not a top cloud-native challenge compared to visibility and attack surface expansion.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit