Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
Question 21 of 129
Free Preview · 129 of 427 · questions 1–129 of 427 are free. Sign up free to sync your progress across devices.
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
why D???????????
Option B is the best, provides a solution that improves the maintainability of the Jenkins infrastructure by migrating it to a managed service like ECS, while also addressing the build artifact encryption requirement by utilizing the secure and default-encrypted storage of Amazon S3. Thinking in your deployment process in jenkins and change to codebuild, can be a difficult work to do. Change only the platform for ec2 to ecs you don't need to sustain patching and updates in ECS. And preserve your artifact on S3.
The answer is B Containerized Jenkins on ECS: By deploying Jenkins on Amazon ECS (Elastic Container Service), you can leverage containerized environments to easily scale and manage Jenkins. This reduces the operational overhead of patching and upgrading EC2 instances running Jenkins. Artifact Storage with Encryption:Storing build artifacts in Amazon S3 with default encryption enabled ensures that all files in the bucket are automatically encrypted at rest using either SSE-S3 or SSE-KMS. This complies with the requirement to protect intellectual property by ensuring encryption of artifacts. This approach ensures a fully managed and scalable solution for both Jenkins (containerized) and the artifact storage, aligning with best practices for security and compliance.