DVA-C02 Application Auto Scaling Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Create DynamoDB table, then Define scaling policies for read and write, then Create scaling target, then Apply scaling policies

  Why it's wrong here

  While the DynamoDB table exists, defining scaling policies before creating the scaling target is incorrect. Scaling policies are rules *for* a specific scalable target. The PutScalingPolicy API call requires parameters like ResourceId, ScalableDimension, and ServiceNamespace, which are established and registered when the scaling target is created using RegisterScalableTarget. Therefore, the target must be registered with Application Auto Scaling before any policies can be successfully defined for it.

• ✓

  Create DynamoDB table, then Create scaling target, then Define scaling policies, then Apply scaling policies

  Why this is correct

  This sequence correctly outlines the necessary steps for configuring DynamoDB auto scaling. First, the DynamoDB table must be created as the foundational resource. Next, a scaling target for the table's read and write capacity must be registered with Application Auto Scaling. Only after the target exists can specific scaling policies, which define the rules for scaling, be successfully created and then applied to activate the automated capacity adjustments.

• ✗

  Define scaling policies, then Create scaling target, then Create DynamoDB table, then Apply scaling policies

  Why it's wrong here

  This order is fundamentally incorrect because both defining scaling policies and creating a scaling target require an existing DynamoDB table to reference. Application Auto Scaling operations, such as PutScalingPolicy or RegisterScalableTarget, depend on a valid ResourceId (the table's ARN) and ScalableDimension (read/write capacity) which are not available until the table has been provisioned. Attempting these steps prematurely would result in immediate API errors.

• ✗

  Create DynamoDB table, then Create scaling target, then Apply scaling policies, then Define scaling policies

  Why it's wrong here

  This sequence is illogical and technically invalid because scaling policies must be fully defined with their specific parameters, such as target utilization, minimum, and maximum capacity, before they can be applied or associated with a scaling target. Applying a policy implies referencing an existing, configured set of rules. Attempting to apply a non-existent or undefined policy would lead to an immediate error, as there would be no operational instructions for Application Auto Scaling to enforce.

Go deeper

Related to this question