Exam AWS Certified Solutions Architect - Professional SAP-C02 topic 1 question 324 discussion

The database must be able to scale based on demand, so Provisioned IOPS volume is out because they will be throttled. A and D are out. EC2 hosted in a private subnet without an internet connection, have to use VPC Endpoint, for DynamoDB, it must be Gateway VPC endpoint. B is the answer.

D is right option. Instance endpoint is for connecting specific instance (primary or replica) and not recommended.

The database must be able to scale based on demand - DocumentDB can be scaled on demand just not automatically and with small downtime; There is no requirement for AUTO scaling. Also MangoDB not always can be migrated to DynamoDB in other hand both support JSON; So if you think about proper auto scaling its - B, you should use Dynamo DB with GW endpoint, but also you will have pain in the a** to migrate it from MongoDB to DynamoDB; if you need only to have functionality scale on demand even with provisioned IOPS its - D, and DocumentDB fully support MongoDB ir easy to migrate.

B is not correct because DynamoDB is not MongoDB-compatible. The legacy application expects a MongoDB API, so using DynamoDB would require significant application changes. Option D (Amazon DocumentDB with cluster endpoint) natively supports MongoDB, allows private subnet access, encrypted connections, and scales automatically.

Option C Gateway endpoint uses internet connection Interface endpoint can be used with dynamodb: https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/privatelink-interface-endpoints.html#types-of-vpc-endpoints-for-ddb

Need a Mongo compatible DB

There is no concept of provision IOPS for DocumentDB , it uses cluster storage so option D (The verbiage ) is incorrect .

MongoDB (document DB) and DynamoDB (key-value) are different. The question says the app uses MongoDB *as* a key-value store, which is odd. Migrating to DynamoDB means data model changes. Options A and D include Provisioned IOPS, which is pricey, but the question doesn't mention cost optimization. AWS says DocumentDB scales, so PIOPS likely fits the "scale on demand" requirement. I lean towards D. If key-value is all that matters, you could use DynamoDB, but that means app changes. With AWS PrivateLink for DynamoDB, B and C are basically the same, making them invalid. So, D seems best, but it's not a slam dunk.

Should be D Document DB is good for MongoDB Manual Scale limit to 15 read replica is not the issue. DynamoDB is not good compatible with MongoDB .... So, what's next if Dynamo is not support Mongo

There seems to be a typo in the answer. The correct answer is DocumentDB with VPC endpoint, making "C" the right choice.

Should be option C. While gateway endpoints can be secured, they still expose the database to the internet, albeit indirectly. DynamoDB can use Interface VPC endpoint to connect to DynamoDB Tables.

B is correct Using a gateway VPC endpoint for DynamoDB (option B) does provide secure communication between your VPC and DynamoDB, and it meets the company's requirement for encrypted connectivity. In fact, using a gateway VPC endpoint can help you achieve several benefits, including: Securely communicate with DynamoDB without exposing your EC2 instances to the public internet Encrypt all outgoing traffic from your VPC to DynamoDB Meet security compliance requirements by controlling access to DynamoDB

Just summarizing from comments :) A and D out because provisioned IOPS is not considered scalable. C is out because DynamoDB only works with gateway vpc endpoint. B works, because MongoDB only used as key value store, it make sense to replace it with DynamoDB with little impact to the requirements.

The key here is Can you use Amazon Dynamodb to replace a MongoDB used as a key-value database and the answer is YES! Amazon DynamoDB supports interface VPC endpoints (AWS PrivateLink). This allows you to securely connect to DynamoDB from your VPC without the need for an internet gateway, NAT device, VPN connection, or AWS Direct Connect connection.

D. This is the correct answer. Amazon DocumentDB (with MongoDB compatibility) meets the requirements: 1. It can be hosted in a private subnet without an internet connection, as required by the technical guidelines. 2. Connectivity between the application and the database can be encrypted, as stated in the requirements. 3. Amazon DocumentDB can scale based on demand, which is another requirement mentioned in the question. 4. The use of the cluster endpoint to connect to Amazon DocumentDB is the appropriate approach, as it provides a single, highly available endpoint for the database cluster. Therefore, option D is the solution that best meets the given requirements.

DynamoDB isn't compatible withMongo

EC2 has no such concept called `cluster endpoint`. has to be B