Which option best suits the implementation of an Amazon RDS database instance instead of a NoSQL/non-relational database?

Answer options:

A.Where datasets are constantly evolving and cannot be confined to a static data schema.
B.Where vertical scaling of the database’s resources is not permissible and is seldom necessary.
C.In an organisation whose datasets are dynamic and document-based. 
D.In an organisation where only a finite number of processes query the database in predictable and well-structured Schemas.

Correct Answer – D
Amazon Relational databases service (RDS) is best suited in scenarios where the dataset and forms are consistent such that their data schema is persistently valid. It is best to deploy in an environment where the load can be anticipated and is somewhat finite. Amazon RDS engines include Amazon Aurora, MariaDB, PostgreSQL-
https://aws.amazon.com/rds/
Option A is INCORRECT because Amazon RDS engines are inappropriate in a scenario where datasets are constantly evolving and the data schema is flexible. NoSQL/non-relational databases fit this use case.
Option B is INCORRECT because Amazon Relational Database service engines will scale up with the increase in load. It is often necessary as the traffic patterns to the database increases.
Option C is INCORRECT because in a scenario where the datasets are dynamic and document-based, the use of JSON and not SQL is appropriate. Therefore non-relationals/NoSQL database engines such as Amazon DynamoDB are suitable.
https://aws.amazon.com/nosql/