Hard practice exam 1

Explanation

Answer: B and E. Retire decommissions or archives an application, and retain deliberately leaves it in the source environment; in both cases no application is migrated to AWS in that wave, though for opposite reasons. Replatform, described as "lift, tinker, and shift," moves the workload while introducing some optimization to operate more efficiently, reduce cost, or exploit cloud capabilities, with the application itself broadly untouched.

• A. Software as a service carries subscription costs, and repurchasing also brings data migration, integration rework, and retraining. It is not automatically cheaper.
• C. A portfolio is assessed application by application, and a realistic migration mixes several strategies across the estate.
• D. Refactoring is the most complex and effort-intensive strategy. For large migrations AWS suggests rehosting, relocating, or replatforming first, then modernizing after the migration is complete.

Explanation

Answer: D. Migration Evaluator builds a data-driven business case for migrating to AWS. It takes a snapshot of the existing on-premises footprint using an agentless collector, identifies over-provisioned servers, and presents projected AWS costs, including cost comparisons of bringing existing licenses versus buying licenses from AWS. That licensing comparison is the detail that distinguishes it here.

• A. AWS Migration Hub tracks migration progress across tools. It reports on execution once a migration is underway.
• B. AWS Application Migration Service replicates and cuts over source servers to AWS. It performs the migration rather than justifying it.
• C. AWS Control Tower automates the setup and governance of a multi-account landing zone. It has no costing or business case function.

Explanation

Answer: B and E. AWS CAF organizes its foundational capabilities into six perspectives: business, people, and governance address strategy, culture, and control, while platform, security, and operations address building, protecting, and running the environment. The framework is used to find where capability is missing and where organizational dependencies lie, most explicitly in the align phase, so those gaps can be closed before they stall delivery.

• A. The framework is designed to be used from the earliest envision phase onward, well before any workload moves.
• C. Portfolio assessment against the migration strategies remains necessary. AWS CAF addresses organizational readiness; the strategy assessment addresses what happens to each application.
• D. AWS CAF describes capabilities and outcomes, not a mandated service adoption sequence. Which services an organization uses depends on its own workloads and goals.

Explanation

Answer: A. The purchase price is sunk, but the ongoing operating model is not. Facilities costs such as space, power, cooling, racks, uninterruptible power supplies, and physical security continue, as do network services, maintenance contracts, and the staff time spent operating the estate. At end of life the hardware must be replaced, which restarts the capital cycle.

• B. Age affects how soon a refresh is due, but a new server also consumes power, cooling, space, and support from the day it is installed.
• C. Depreciation reflects the consumption of an asset's value over its life and is a genuine cost in any honest comparison.
• D. Licensing is one ongoing cost among several, and citing it alone still leaves the facilities, network, maintenance, and refresh costs unaccounted for.

Explanation

Answer: C. Cloud value is not only the invoice. Cost optimization is defined as delivering business value at the lowest price point, and the pillar's "measure overall efficiency" principle asks for the business output of a workload to be compared against the cost of delivering it. Faster release cycles can bring revenue forward and reduce the cost of a wrong bet, and those effects can be estimated and weighed against a 12 percent saving.

• A. Agility is routinely quantified through revenue brought forward, reduced cost of failed experiments, and staff time recovered. The estimate is imprecise, not impossible.
• B. Judging only the bill would favor never shipping anything, since the cheapest workload is one that does nothing. Value must appear on the other side of the ratio.
• D. Agility is valuable but not unconditionally dominant. For a stable, low-change workload a durable cost reduction may well be worth more.

Explanation

Answer: A. The two levers act on different factors of the same equation. Rightsizing reduces the quantity of resource-hours consumed by fitting the resource to the workload. A commitment reduces the price per resource-hour in exchange for a usage pledge. Applying rightsizing first is important, because a commitment made against an oversized baseline locks in the excess.

• B. AWS provides recommendations but does not resize customer resources on its own, and commitments are purchased directly rather than through a support case.
• C. Both apply broadly. Storage can be rightsized by class and volume size, and commitment models cover compute and several other service families.
• D. This is inverted. Rightsizing is a configuration change with no term, whereas commitments carry a fixed one-year or three-year term.

Explanation

Answer: D. Buying four years of growth up front is precisely the fixed expense the cloud model replaces. Cloud storage grows as data is written and is charged on what is stored, so the money for year four's capacity stays in the business until year four, and a forecast that turns out to be wrong costs nothing.

• A. Spare capacity is not fault tolerance. Fault tolerance comes from redundant components and the ability to keep operating when one fails.
• B. Some storage software is licensed by capacity, but licensing is not what makes buying three times the needed capacity wasteful. The waste is the timing of the purchase.
• C. Volume discounts may reduce the unit price of the array, but a discount on capacity that sits empty for four years is still money spent early for no return.

Explanation

Answer: A. The saving comes from the shape of the demand. An intermittent workload leaves EC2 instances idle between runs, and idle instances are billed at the same rate as busy ones. With a serverless model the charge is tied to invocations and execution duration, so the gap between runs costs nothing. This is the consumption model applied to a workload whose utilization is naturally low.

• B. Serverless services are billed on usage, not at a flat monthly rate. Predictability comes from understanding the workload, not from a fixed fee.
• C. Execution speed depends on the code, the runtime, and the resources allocated. Serverless is not inherently faster, and cold starts can add latency.
• D. Data transfer and storage are charged normally. Only the compute model changes.

Explanation

Answer: A. Automation works on both sides of the bill. It reduces the operational effort spent on repetitive tasks, freeing people for higher-value work, and it applies cost-saving actions reliably: scaling in when demand falls, stopping non-production environments outside working hours, and expiring data on schedule. Manual equivalents are performed inconsistently or forgotten entirely.

• B. Automation changes exactly what is consumed, because scaling and shutdown decisions determine how many resource-hours are billed.
• C. Well-designed automation reduces consumption by removing idle capacity. Uncontrolled provisioning is a governance failure, not a property of automation.
• D. The benefit is reallocation of effort rather than headcount reduction. Teams typically redirect that time toward architecture, security, and product work.

Explanation

Answer: A. The same self-service that makes the cloud fast also makes it easy to leave things running. Without attribution, ownership, and regular review, forgotten test environments, detached volumes, unused snapshots, and instances sized for a load test quietly accumulate. This is why cost optimization treats cloud financial management as an ongoing organizational capability, supported by analyzing and attributing expenditure to the teams that own it.

• B. AWS has repeatedly reduced prices over the life of the platform rather than applying automatic annual increases.
• C. There is no differential rate based on how a workload arrived. Charges depend on the resources consumed.
• D. Consumption-based charges follow consumption. A flat workload with disciplined cleanup produces a flat bill.