exam questions

Exam AWS Certified Security - Specialty All Questions

View all questions & answers for the AWS Certified Security - Specialty exam

Exam AWS Certified Security - Specialty topic 1 question 415 discussion

Exam question from Amazon's AWS Certified Security - Specialty
Question #: 415
Topic #: 1
[All AWS Certified Security - Specialty Questions]

A company is running internal microservices on Amazon Elastic Container Service (Amazon ECS) with the Amazon EC2 launch type. The company is using Amazon Elastic Container Registry (Amazon ECR) private repositories.

A security engineer needs to encrypt the private repositories by using AWS Key Management Service (AWS KMS). The security engineer also needs to analyze the container images for any common vulnerabilities and exposures (CVEs).

Which solution will meet these requirements?

  • A. Enable KMS encryption on the existing ECR repositories. Install Amazon Inspector Agent from the ECS container instances’ user data. Run an assessment with the CVE rules.
  • B. Recreate the ECR repositories with KMS encryption and ECR scanning enabled. Analyze the scan report after the next push of images.
  • C. Recreate the ECR repositories with KMS encryption and ECR scanning enabled. Install AWS Systems Manager Agent on the ECS container instances. Run an inventory report.
  • D. Enable KMS encryption on the existing ECR repositories. Use AWS Trusted Advisor to check the ECS container instances and to verily the findings against a list of current CVEs.
Show Suggested Answer Hide Answer
Suggested Answer: B 🗳️

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
ryogoku
Highly Voted 2 years, 4 months ago
Selected Answer: B
B because: 1. ECR supports image scanning by default. No need to install anything: https://docs.aws.amazon.com/inspector/latest/user/enable-disable-scanning-ecr.html It is not possible to change ECR encryption after repository is created: https://aws.amazon.com/blogs/containers/introducing-amazon-ecr-server-side-encryption-using-aws-key-management-system/
upvoted 13 times
AzureDP900
2 years, 2 months ago
Agreed
upvoted 2 times
...
...
Nuha_23
Most Recent 1 year, 8 months ago
Selected Answer: B
The answer is B. A&D are out : we can not Enable KMS encryption on the existing ECR repositories "For Encryption settings, this is a view only field as the encryption settings for a repository can't be changed once the repository is created." C is wrong : There is no SSM agent for CVE more information : https://docs.aws.amazon.com/AmazonECR/latest/userguide/repository-create.html https://docs.aws.amazon.com/AmazonECR/latest/userguide/repository-edit.html
upvoted 1 times
...
Green53
1 year, 10 months ago
Selected Answer: B
You can't enable KMS on ECR after creation, so rule out A. You don't need Systems Manager Agent (or Inspector) to scan images, rules out C. D is incorrect, this isn't what Trusted Advisor is for. That leaves B.
upvoted 1 times
...
Toptip
1 year, 11 months ago
Selected Answer: B
i think B is correct
upvoted 1 times
...
Tofu13
1 year, 11 months ago
Selected Answer: B
Basic scanning is the default for ECR. U can use enhanced scanning which uses Inspector. https://docs.aws.amazon.com/AmazonECR/latest/userguide/image-scanning.html https://docs.aws.amazon.com/AmazonECR/latest/userguide/image-scanning.html
upvoted 1 times
...
c73bf38
2 years, 1 month ago
Selected Answer: B
The KMS encryption settings cannot be changed or disabled after the repository is created.
upvoted 3 times
...
createchange
2 years, 2 months ago
Selected Answer: B
A cannot be true. Inspector installed on the EC2 instance would not perform container image scanning. You can utilize native ECR functionality for both encryption and container scanning.
upvoted 1 times
...
Leonardocp33
2 years, 4 months ago
Selected Answer: B
A and D is out because encryption cannot be changed after create the repository. B is the correct answer because ECR and inspector has a automatic process for scanning CVE https://docs.aws.amazon.com/AmazonECR/latest/userguide/image-scanning.html
upvoted 1 times
...
Smartphone
2 years, 4 months ago
Answer is B. For the the CVEs report of ECR container, it needs to be activated and configured the scanning settings at ECR console. In background, AWS Inspector scans the images. For scanning, not required to installed any agent.. https://docs.aws.amazon.com/inspector/latest/user/enable-disable-scanning-ecr.html
upvoted 1 times
...
Teknoklutz
2 years, 4 months ago
Selected Answer: B
Basic scanning—Amazon ECR uses the Common Vulnerabilities and Exposures (CVEs) database from the open-source Clair project. With basic scanning, you configure your repositories to scan on push or you can perform manual scans and Amazon ECR provides a list of scan findings.
upvoted 4 times
...
Kevin24
2 years, 4 months ago
Selected Answer: A
CVE Scanning is mentioned only in A
upvoted 1 times
ryogoku
2 years, 4 months ago
Not A and not D, because as per article below you can see that ECR repository encryption cannot be changed after it is created. https://aws.amazon.com/blogs/containers/introducing-amazon-ecr-server-side-encryption-using-aws-key-management-system/
upvoted 3 times
...
...
Blueocean
2 years, 4 months ago
While the AWS Inspector seems better for CVE, and Option A could have been option, the fact that encryption cannot be enabled for existing repository rules this out. The best option remaining is Option C
upvoted 1 times
...
amcloud
2 years, 4 months ago
Selected Answer: B
B - https://docs.aws.amazon.com/AmazonECR/latest/userguide/image-scanning.html
upvoted 4 times
...
Phongsanth
2 years, 4 months ago
Selected Answer: C
The KMS encryption setting cannot be changed or disabled after the repository is created. see the image step in this link https://aws.amazon.com/blogs/containers/introducing-amazon-ecr-server-side-encryption-using-aws-key-management-system/
upvoted 2 times
...
Balki
2 years, 4 months ago
Selected Answer: C
It should be C. We cannot change KMS encryption on an ECR image. You can try it yourself in AWS Console. We can detect CVE through SM. https://aws.amazon.com/about-aws/whats-new/2020/10/now-use-aws-systems-manager-to-view-vulnerability-identifiers-for-missing-patches-on-your-linux-instances/
upvoted 4 times
...
piter8111
2 years, 4 months ago
Selected Answer: B
The KMS encryption settings cannot be changed or disabled after the repository is created.
upvoted 3 times
...
tainh
2 years, 5 months ago
Selected Answer: A
A is correct https://docs.aws.amazon.com/inspector/v1/userguide/inspector_cves.html
upvoted 2 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...
exam
Someone Bought Contributor Access for:
SY0-701
London, 1 minute ago