AWS Certified Developer - Associate Practice Mode

Community Discussion

Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.

• Chose A1

  Correct — Title (PK) + release year (SK) supports both "get by title+year" and "get all by title" queries. GSI with genre as PK covers "get all by genre". Flexible schema handles inconsistent cast/crew attributes natively in DynamoDB.

• Chose A2

  B) Eliminated - No efficient way to query by title + release year since the primary key is genre + release year, and the GSI only has the title C) Eliminated - Adding new columns for properties like assistant director or animal trainer becomes cumbersome and violates flexibility. D) Eliminated - JSON in RDS is harder to query

• Chose A2

  keyword: (title + release year), title, genre, each film has differential cast and crew => Discard C,D: when it store film by structure && option C must scan all data that is not primary key(title), seem be not flexible && option D is horrible way, when storing data as json structure, take time to extract this json ==> discard B: querry (title + release year) must scan all item without combining them in primary key(partition key and sort key) at primary table or GSI