DOP-C02 Question 47
Select 3Your organization is using AWS CodeArtifact to manage and store software packages for application development. Several teams are sharing a repository, and you are tasked with ensuring secure access to the artifacts while maintaining operational efficiency. What steps should you take to meet these requirements?
- A
Use AWS IAM policies to grant specific permissions to each team for their respective package namespaces.
- B
Enable cross-account access to the repository by setting the repository's permissions to 'public'.
- C
Implement encryption at rest using AWS KMS and ensure all package uploads are encrypted.
- D
Use a lifecycle policy to automatically delete unused artifacts after a specified retention period.
- E
Create a managed policy that grants 'Admin' access to all team members for unrestricted artifact management.
Show answer and explanation
Correct answers: A, C, D
Explanation
Secure management of artifacts in AWS CodeArtifact involves applying the principle of least privilege using IAM policies, ensuring encryption at rest to protect sensitive data, and implementing lifecycle policies to maintain operational efficiency. Avoiding insecure practices, such as making repositories public or granting overly broad permissions, is critical to maintaining a secure artifact management system.
- A. Correct.
Correct: Using AWS IAM policies to grant granular permissions ensures that teams can only access their specific package namespaces, improving security and access control.
- B. Incorrect.
Incorrect: Setting repository permissions to 'public' exposes it to unauthorized access, which is a violation of secure artifact management best practices.
- C. Correct.
Correct: Enabling encryption at rest using AWS KMS ensures that artifacts are stored securely and comply with industry standards for data protection.
- D. Correct.
Correct: Implementing a lifecycle policy helps manage storage costs and operational efficiency by automatically cleaning up unused artifacts.
- E. Incorrect.
Incorrect: Granting 'Admin' access to all team members violates the principle of least privilege and introduces unnecessary security risks.