Cloud Concepts practice questions

Answer: A) Operational Excellence

• AOperational Excellence is about delivering business value by running workloads effectively, gaining insight into operations, and continuously improving processes and procedures.
• BReliability focuses on a workload performing its function correctly and recovering from failure, not on operational processes.
• CThe Security pillar covers protecting data, systems, and assets, not running and improving operations.
• DPerformance Efficiency is about using resources efficiently as demand changes, not operations and process improvement.

Answer: A) Hybrid

• AA hybrid deployment integrates on-premises (or private cloud) infrastructure with public cloud resources, often connected over VPN or AWS Direct Connect.
• BAn all-in cloud deployment runs everything in the cloud with no on-premises component.
• CThat would mean no cloud resources at all, which isn't the case here.
• DMulti-region describes spreading a cloud deployment across AWS Regions, not combining cloud with on-premises.

Answer: A) Costs rise and fall with actual usage instead of being fixed at a peak-capacity level

• AVariable pricing means an unpredictable workload does not force paying year-round for its highest possible demand.
• BPay-as-you-go specifically removes the need for long-range capacity forecasting.
• COnly specific Free Tier allowances are free; pay-as-you-go itself still charges for usage.
• DOn-demand prices can change and usage-based charges vary by definition.

Answer: A) Security

• AThe Security pillar addresses identity and access management, detection, infrastructure and data protection, and incident response.
• BReliability is about a workload performing correctly and recovering from failure.
• CPerformance Efficiency is about using resources efficiently as demand changes.
• DCost Optimization is about avoiding unnecessary costs.

Answer: A) Sustainability

• AThe Sustainability pillar addresses reducing energy consumption and the carbon footprint of workloads, for example by right-sizing, using efficient instance types, and choosing Regions with lower impact.
• BCost Optimization is about avoiding unnecessary spend; it can correlate with efficiency but its goal is financial.
• CPerformance Efficiency is about using computing resources effectively to meet requirements as demand changes, not environmental impact.
• DReliability is about correct operation and recovery from failure.

Answer: A) Measured service (pay-as-you-go)

• AMeasured service means resource usage is metered and billed at a fine granularity, so customers pay only for what they consume.
• BResource pooling is the provider serving many customers from shared infrastructure; it's a different NIST characteristic.
• CElasticity is fast scaling with demand; metering and billing granularity is a separate property.
• DThat refers to services being available over the network from many client types.

Answer: A) Replatform (lift, tinker, and shift)

• AReplatforming makes a few targeted optimizations during migration — such as moving to a managed database — without changing the core application architecture.
• BPure rehosting moves everything unchanged; swapping in a managed database is a deliberate optimization beyond rehosting.
• CRefactoring substantially rewrites the application (e.g. to microservices), which this company avoided.
• DRetain means deliberately keeping an application where it is for now, not migrating it.

Answer: A) High availability through fault isolation across separate locations

Spreading a workload across Availability Zones and Regions removes single points of failure, so the application can keep running through an AZ-wide or Region-wide outage. That is the high availability benefit of the AWS Cloud.

• AAWS best practice is to spread workloads across Availability Zones and, where needed, Regions. This removes single points of failure and gives fault tolerance and high availability when a whole AZ or Region is affected.
• BElasticity means adding or removing capacity as demand changes. The design here is about surviving location failures, not following changes in load.
• CDuplicating a workload across AZs and Regions usually adds cost. AWS notes that multi-Region designs can involve extra complexity and cost, so lower prices aren't the benefit here.
• DAgility means being able to experiment and deliver faster. Spreading a workload across locations for failover improves resilience, not development speed.

Answer: A) Rehost (lift and shift)

Common migration strategies (the '7 Rs'): Rehost (lift and shift), Replatform (lift and reshape), Repurchase (move to a different product), Refactor, Retire, Retain, Relocate.

• ARehosting moves a workload to the cloud with no modification — the fastest strategy, often used to hit a data-center exit deadline before optimizing later.
• BRefactoring re-architects the application (e.g. into microservices or serverless), which involves significant code change.
• CRepurchasing replaces the application with a different product, typically a SaaS offering.
• DRetiring means decommissioning a workload that is no longer needed.

Answer: A) Automatically recover from failure, test recovery procedures, and scale horizontally

The Reliability pillar's design principles include automatically recovering from failure, testing recovery procedures, scaling horizontally to increase aggregate availability, stopping guessing capacity, and managing change through automation. The other options list principles from the Security, Cost Optimization and Performance Efficiency pillars.

• AAll three are listed design principles of the Reliability pillar. The pillar also includes stopping guessing capacity and managing change through automation.
• BThese are design principles of the Security pillar, not the Reliability pillar.
• CThese are design principles of the Cost Optimization pillar.
• DThese are design principles of the Performance Efficiency pillar.