Build Windows Containers for AWS CodeBuild and AWS CodePipeline Integration
Question
As a developer, you have to build Windows containers to use with AWS CodeBuild and integrate it into AWS CodePipeline and push the resulting containers to Amazon ECR.
You might consider custom Docker images.
What assertions are true in this scenario? (Select TWO).
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D. E.Correct Answers: A, D.
There are custom action timeouts whose default maximum execution time for AWS CodePipeline is one hour.
It can be requested to increase the limit through the AWS Service Quotas console.
AWS CodeBuild downloads a new copy of the Docker image for each build job.
Incorrect Answers:
Option B is incorrect because AWS CodeBuild does not cache Docker images to avoid downloading new copies.
Instead, a new copy of the Docker image for each build job is downloaded.
Option C is incorrect because AWS CodeBuild supports Windows builds in some AWS Regions.
Option E is incorrect because even though you can work around AWS Region limitations with Windows Servers through Amazon EC2 instances, the downside of this approach is additional management burden -neither AWS CodeBuild nor AWS CodePipeline support Amazon EC2 instances directly.
References:
https://go.aws/2M1RcZ1In this scenario, as a developer, you are required to build Windows containers using AWS CodeBuild and integrate them into AWS CodePipeline. You also need to push the resulting containers to Amazon ECR. You may consider using custom Docker images for this process.
The following assertions are true in this scenario:
B. AWS CodeBuild caches Docker images to avoid downloading new copies each build job, which reduces the time for large Docker images. This assertion is true. AWS CodeBuild caches Docker images to avoid downloading new copies each build job. This helps in reducing the time taken to build large Docker images.
C. AWS CodeBuild fully supports Windows builds in all AWS Regions. This assertion is true. AWS CodeBuild supports Windows builds in all AWS Regions. This means that you can use AWS CodeBuild to build Windows containers in any AWS Region.
The following assertions are false in this scenario:
A. The default maximum execution time for CodePipeline custom actions is one hour. If your build jobs require more than an hour, you need to request a limit increase for custom actions. This assertion is false. The default maximum execution time for CodePipeline custom actions is actually 4 hours, not one hour. However, if your build jobs require more than 4 hours, you will need to request a limit increase for custom actions.
D. AWS CodeBuild has to download a new copy of the Docker image for each build job, which may take longer time for large Docker images. This assertion is false. As mentioned earlier, AWS CodeBuild caches Docker images to avoid downloading new copies each build job. Therefore, it does not have to download a new copy of the Docker image for each build job.
E. Any limitations with Windows Server containers can be addressed by using Amazon EC2 instances. AWS CodeBuild and AWS CodePipeline support Amazon EC2 instances directly. This assertion is false. While AWS CodeBuild and AWS CodePipeline do support Amazon EC2 instances directly, using Amazon EC2 instances does not address any limitations with Windows Server containers. Instead, using Amazon EC2 instances would be an alternative to using AWS CodeBuild and AWS CodePipeline for building and deploying applications.
