Yep, C is the way to go. CodePipeline handles the whole CI/CD process, not just infra or tests by themselves. With API Gateway stages, CloudFormation for IAC and CodeBuild for integration testing, everything’s covered end to end. Pretty sure that’s what AWS expects but let me know if anyone disagrees.
Q: 10
A company has a serverless application that uses Amazon API Gateway and AWS Lambda functions to
expose a RESTful API. The company uses a continuous integration and continuous delivery (CI/CD)
workflow to deploy the application to multiple environments. The company wants to implement
automated integration tests after deployment.
A developer needs to set up the necessary infrastructure and processes to automate the deployment
and integration tests for the serverless application.
Options
Discussion
C . Had something like this in a mock, CodePipeline is key for full CI/CD and integration tests across environments.
Nah, I think C. B is tempting but doesn't include full CI/CD orchestration with CodePipeline, which the question hints at for automation.
Gotta be C for this scenario.
Serverless CI/CD automation questions like this usually show up in practice tests and the official AWS study guide, worth reviewing both.
Pretty sure C is right since CodePipeline gives you full CI/CD automation, not just infra. I checked some practice exams and official guide, both show this pattern as best practice for serverless apps. Correct me if I'm missing something with B or D.
B for me, since CloudFormation plus CodeBuild seems solid for infra and test automation. Official docs and practice exams mention this combo a lot. I might be missing something subtle about orchestration though, open to corrections.
C tbh, because CodePipeline actually manages the whole CI/CD flow here, not just infra setup. B misses the orchestration bit and that's pretty key for proper automated deployment + testing after deploys to each API Gateway stage. I think C matches real exam setups I've seen but open if someone thinks B actually covers CI/CD end-to-end.
C vs B. Pretty sure C is better since CodePipeline ties the whole CI/CD flow together, not just infra or tests. B skips the orchestration part, which is kind of a trap here. Correct me if I'm missing a catch.
A for sure. SQS acts as a buffer so sudden spikes get smoothed before Lambda tries writing to DynamoDB. Seen similar in other AWS exam practice sets, so pretty confident here. Let me know if you read it differently.
Be respectful. No spam.
Question 10 of 35