CLF-C02 Cloud Concepts Cloud Concepts Practice Questions

Elasticity is the cloud best practice of dynamically adjusting compute capacity up or down in response to demand, avoiding over-provisioning during low-traffic periods and under-provisioning during peaks, which directly reduces cost.

Build security in every layer is the Defense in Depth principle from the Security pillar of the Well-Architected Framework, which addresses threat protection rather than capacity management. Parallelizing tasks is a performance design principle that distributes workloads across multiple smaller components to increase throughput, not a mechanism for dynamically adjusting capacity to control costs. Adopting monolithic architecture consolidates all application components into a single tightly coupled unit, which is the opposite of a cloud best practice and does not support dynamic scaling.

The three recognized AWS cloud computing service models are IaaS, PaaS, and SaaS. Networking as a Service is not one of them and does not exist as a defined cloud computing model in the AWS framework.

Platform as a Service is one of the three recognized cloud computing models, providing customers with a managed platform for developing and deploying applications without managing the underlying infrastructure. Infrastructure as a Service is one of the three recognized cloud computing models, giving customers virtualized compute, storage, and networking resources they manage themselves. Software as a Service is one of the three recognized cloud computing models, delivering fully managed applications to end users over the internet without any infrastructure or platform management required.

Using loosely coupled components means each part of an application can scale, fail, and be updated independently without cascading failures to other components, which is the foundational AWS best practice for building resilient and scalable architectures.

Using tightly coupled components creates direct dependencies between parts of an application so that a failure or change in one component directly affects others, increasing the risk of cascading failures and making the system harder to scale and maintain independently. A monolithic design combines all components into a single unit that is difficult to scale or update independently, which is the opposite of the modular approach AWS recommends. Stateful components store session data locally on a specific instance, which prevents requests from being distributed freely across instances and undermines horizontal scaling and resilience.

When applications in the AWS Cloud communicate with a legacy application in a corporate data center, this is a hybrid architecture that combines on-premises and cloud resources in a single solution.

Cloud-native describes applications designed and built entirely to run in the cloud, with no dependency on on-premises infrastructure or legacy systems. Partner network refers to the AWS Partner Network, which is a program for technology and consulting companies that build solutions on AWS, and is not a deployment model. Infrastructure as a Service is a cloud service model that provides virtualized compute, storage, and networking resources, and does not describe the combination of cloud and on-premises components in a single architecture.

Distributing workloads across multiple Availability Zones ensures the application can continue operating if one AZ fails, embodying the design for failure principle, where the architecture anticipates and accommodates component failures.

Implement automation refers to reducing manual intervention through scripts and managed services, not to fault tolerance across zones. Design for agility refers to the ability to rapidly experiment and deploy, not to handling infrastructure failures. Implement elasticity refers to automatically scaling resources in response to demand, not to distributing workloads for fault tolerance.