Practice Test GeeksCCP - Certified Cloud Practitioner Practice Test
← All CCP Flashcard Decks

AWS Cloud Architecture and Design Principles Flashcards

6 cards from real CCP practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.

Read the first 6 AWS Cloud Architecture and Design Principles flashcards as text

  1. What does 'elasticity' mean in the context of AWS cloud computing?

    Answer: Automatically scaling resources up or down to match current demand

    Elasticity refers to the ability to automatically provision and de-provision resources to precisely match demand, avoiding both under- and over-provisioning.

  2. Which AWS service enables you to model and provision infrastructure as code using templates?

    Answer: AWS CloudFormation

    AWS CloudFormation lets you define your entire infrastructure in JSON or YAML templates and provision it consistently and repeatedly.

  3. Which design principle recommends replacing failed components automatically rather than fixing them in place?

    Answer: Treat servers as cattle, not pets

    The 'cattle not pets' principle means servers are disposable and interchangeable — when one fails, it's replaced automatically rather than manually nursed back to health.

  4. What is the benefit of using multiple AWS Regions for a global application?

    Answer: Reduced latency for users in different geographic locations and improved disaster recovery

    Deploying in multiple Regions reduces latency for globally distributed users and provides geographic redundancy for disaster recovery purposes.

  5. Which AWS Well-Architected pillar focuses on using cloud resources efficiently to deliver business value?

    Answer: Performance Efficiency

    The Performance Efficiency pillar focuses on using computing resources efficiently and maintaining that efficiency as demand changes and technologies evolve.

  6. What does 'infrastructure as code' (IaC) mean in cloud architecture?

    Answer: Defining and managing infrastructure through machine-readable configuration files

    Infrastructure as Code means defining your servers, networks, and services in code files (like CloudFormation templates), enabling repeatable, version-controlled deployments.