Objective: use the access model as evidence
After the storage and responsibility lessons, distinguish a database’s data-access contract from its operating model and migration tooling. RDS supplies a managed relational database service. DynamoDB supports key-value and document models, does not support JOIN, and does support ACID transactions. Therefore “needs transactions” is not enough to choose RDS over DynamoDB. Ask whether the workload explicitly needs relational SQL/JOIN behavior or has a stated known-key/document access pattern. A requirement that is true for both options cannot uniquely distinguish them.
Worked example: a workshop’s records and lookup
Fictional teaching case: a workshop has relational enrollment records that existing SQL reports JOIN to event schedules. A separate lookup component reads a prepared participant document using a known key and does not need joins. Both components want reliable updates. First identify the reports’ explicit relational query requirement: RDS is the direct relational category to evaluate. Next identify the lookup’s key/document access requirement: DynamoDB is the relevant comparison category. Do not use transactions as the dividing line, because DynamoDB supports them too. Check the conclusion by removing the SQL JOIN requirement from the first component. That change would reopen the access-pattern evaluation; it would not prove that one model wins every database task.
Managed operations do not own every data decision
RDS reduces common operational work such as backups and software patching. The customer still tunes SQL queries and applies controls appropriate to data sensitivity and organizational requirements. These responsibilities need knowledge of the schema, workload, and legitimate readers. Selecting a managed relational engine therefore answers one operating-model question without completing every application decision. The same reasoning prevents the opposite error: customers are not expected to take over AWS physical infrastructure simply because some application duties remain theirs.
Migration is a process, not a compatibility certificate
DMS supports database migration and ongoing replication. A different-engine move also requires source-schema assessment/conversion and target-application validation. Data can arrive at a destination without every original query, feature, or business workflow behaving correctly there. Separate the transfer capability from proof of compatibility. The useful planning output names which schema and application checks are needed; a product selection by itself cannot supply those results. Do not promise universal automatic conversion or an unchanged application when the source evidence does not establish either.
Transfer check and check basis
Try this independent check: a fictional roster application has no JOIN requirement, but someone rejects DynamoDB solely because the application uses an ACID transaction. Is that rejection supported? Check basis: no; DynamoDB supports ACID transactions, so the access pattern and other explicit requirements still need comparison. Now consider a database move where a schema assessment succeeds but application queries have not been tested. The result is partial evidence, not complete compatibility approval. Attempt aws-clf-q-033–036 and cards aws-clf-card-25–27. In each explanation, name whether the reasoning concerns model fit, operational responsibility, or migration validation rather than treating all three as one choice.
Try it, then explain it.
Complete a short set without looking at the example. After each answer, explain which evidence or rule supports your decision and why the alternatives do not fit.
Sources & authorship
Original OpenExam explanations and examples. References support the concepts; they are not the source of copied questions. Independent educator review is pending.
What is AWS Database Migration Service? - AWS Database Migration ServiceWhat is Amazon DynamoDB? - Amazon DynamoDBWhat is Amazon Relational Database Service (Amazon RDS)? - Amazon Relational Database ServiceSecurity in Amazon RDS - Amazon Relational Database ServiceShared Responsibility Model - Amazon Web Services (AWS)