1) What is the primary focus of cloud-native architecture? a) a) Optimization for fixed, high-cost infrastructure b) b) Enhancing manual effort to modify systems c) c) Achieving resilience and scale through automation and distributed processing d) d) Minimizing the use of cloud-based services 2) What is a key benefit of designing for automation in cloud-native systems? a) a) Reduced system resilience and performance b) b) Increased upfront investment with no long-term benefits c) c) Ability to repair, scale, and deploy systems faster than manual processes d) d) Dependency on manual intervention for routine tasks 3) What does the principle of statelessness emphasize in cloud-native architecture? a) a) Storing all user and system data in a centralized location b) b) Designing components to rely heavily on persistent storage c) c) Storing state data in distributed databases for easier access d) d) Designing components to be stateless wherever possible for easier scalability and management 4) What is the main consideration when deciding whether to adopt managed services in cloud-native architectures? a) a) Compatibility with open-source alternatives b) b) Strategic significance of the service c) c) Potential risk of being 'locked in' to a provider vs. operational overhead d) d) Availability of comprehensive documentation for the service 5) What approach does cloud-native architecture take towards security? a) a) Reliance on perimeter security with trusted and untrusted zones b) b) Application of authentication and trust between components, regardless of their location c) c) Emphasis on single-layer security measures d) d) Dependency on manual security checks for each component

Cloud Native: Principles, Applications, and Challenges

印刷
埋め込み

リーダーボード

表示スタイル

オプション

テンプレートを切り替える

自動保存: を復元しますか?