just passed yesterday 30-05-23, around 75% of the exam came from here, some with light changes.

Great work made it to the last question. Goodluck to you all

let me know for most of questions that system answer are correct or comment answer are correct?

https://docs.amazonaws.cn/en_us/athena/latest/ug/connect-to-a-data-source.html

key word is most operational effective => D requires no coding

I'll go with D as ABC looks too much work or irrelevant. Although not sure how AFQ actually achieves the read without impacting performance.

Not A - Pipe Resolvers require coding, would not consider that 'operationally efficient' Not B - CloudFront caches web content at the edge, not DynamoDB query results for apps Not C - Neither API Gateway or Lambda have anything to do with DynamoDB performance D - Can do exactly that

I am not an expert but I used Bing+Gemini+Chatgbt=AAA

multiple database tables = AppSync pipeline resolvers

For an operationally efficient solution that minimizes impact on baseline performance in a microservice-based serverless web application retrieving data from multiple DynamoDB tables, Amazon CloudFront with Lambda@Edge functions (Option B) is often the most suitable choice

D is correct. There is contruction of how to retrive data from DynamoDB with Anthena https://docs.aws.amazon.com/athena/latest/ug/connect-to-a-data-source.html

The Answer is A. Some use case for AWS AppSync is Unified data access. Consolidate data from multiple databases, APIs, and microservices in a single network call, from a single endpoint, abstracting backend complexity. https://aws.amazon.com/pm/appsync/?trk=e37f908f-322e-4ebc-9def-9eafa78141b8&sc_channel=ps&ef_id=Cj0KCQjwmvSoBhDOARIsAK6aV7jtg2I6jyXBH6_uUOKRrRoLmXQxaGbwYBP0aO1-RmauWW55DuXSGTMaAnT9EALw_wcB:G:s&s_kwcid=AL!4422!3!647301987556!e!!g!!aws%20appsync!19613610159!148358960849

B - seems more operationally efficient A: example to make use of GraphQL with multi DynamoDB tables https://www.youtube.com/watch?v=HSDKN43Vx7U but it seems not the most operationally efficient to set it up D: it can be useful when needs to join multi DynamoDB tables But also "querying DynamoDB using Athena can be slower and more expensive than querying directly using DynamoDB" refer to https://medium.com/@saswat.sahoo.1988/combine-the-simplicity-of-sql-with-the-power-of-nosql-pt-2-cff1c524297e

A is correct. https://aws.amazon.com/blogs/mobile/appsync-pipeline-resolvers-2/

https://aws.amazon.com/pm/appsync/?trk=66d9071f-eec2-471d-9fc0-c374dbda114d&sc_channel=ps&ef_id=CjwKCAjww7KmBhAyEiwA5-PUSi9OTSRu78WOh7NuprwbbfjyhVXWI4tBlPquEqRlXGn-HLFh5qOqfRoCOmMQAvD_BwE:G:s&s_kwcid=AL!4422!3!646025317347!e!!g!!aws%20appsync!19610918335!148058250160

I like D) the most. D. Amazon Athena Federated Query with a DynamoDB connector. I don't like A) since this is not a GraphQL query. I don't like B). Since Query multiple tables in DynamoDB from Lambda may not be efficient.

A. AppSync reduces operational effort, you only need to know GraphQL, AppSync provides caching ability to reduce loads on source B. Also provide caches through CloudFront, but require writing more 'low-level' codes on Lambda D. Requires a Lambda to create connection to DynamoDB source, also no caching