"Principles of Cloud Native design - 12 Factor apps"

1. 1. What is the primary focus of Cloud Native Architecture?

• • A) Fixed infrastructure

• • B) Monolithic structures

• • C) Scalability, flexibility, and resilience

• • D) Low-cost development

2. 2. What does "Immutable Infrastructure" mean in cloud-native applications?

• • A) Ever-changing servers

• • B) Unpredictable deployment processes

• • C) Servers remain unchanged after deployment

• • D) Manual updates to infrastructure

3. 3. What are Microservices in the context of cloud-native applications?

• • A) Large, interconnected software components

• • B) Independent software components working together

• • C) Single, monolithic applications

• • D) Static elements of a cloud-native system

4. 4. What is the purpose of the 12 Factor Application principles?

• • A) Enhancing monolithic applications

• • B) Building large-scale infrastructure

• • C) Ensuring modularity and agility

• • D) Restricting scalability

5. 5. What does the "Dependencies" principle in a 12 Factor Application emphasize?

• • A) Implicit reliance on system-wide packages

• • B) Explicit declaration and isolation of dependencies

• • C) Avoidance of version control systems

• • D) Unspecified compatibility across environments

6. 6. How does cloud-native architecture handle application configuration?

• • A) Hard-coding configuration in the source code

• • B) Storing configuration in a centralized repository

• • C) Dynamic modifiability using environment variables

• • D) Relying on implicit system-wide configuration

7. 7. What is the recommended approach for handling logs in a cloud-native application?

• • A) Storing logs as constants in the code

• • B) Directing logs to a single, fixed location

• • C) Treating logs as event streams and writing to stdout and stderr

• • D) Ignoring log storage and analysis concerns.