AWS Certified Professional DOP-C02 Reddit Questions

AWS CodeArtifact is a fully managed artifact repository service that supports popular package formats and can proxy downstream public repositories securely. It integrates seamlessly with both AWS Cloud and on-premises environments and stores artifacts in highly durable object storage (Amazon S3). CodeArtifact encrypts data at rest and in transit by default.

Because there is currently no routing between the on-premises data center and AWS, establishing a third-party software VPN appliance for connectivity provides secure communication without requiring complex AWS Direct Connect or multiple VPN setups.

This solution can be deployed quickly (within two weeks), is highly available, and meets encryption requirements. Using CodeArtifact eliminates the need to maintain third-party artifact servers, reducing operational overhead and improving reliability.

Options B, C, and D introduce higher complexity with AWS Direct Connect or multiple VPN connections and third-party software that increases deployment time and operational burden, which is against the requirement for rapid deployment and high operational efficiency.

Reference from AWS Official Documentation:

AWS CodeArtifact Overview:"CodeArtifact is a fully managed artifact repository service that makes it easy for organizations to securely store, publish, and share software packages used in their software development process."(AWS CodeArtifact Documentation)

Encryption in AWS CodeArtifact:"CodeArtifact encrypts data at rest and in transit by default."(AWS CodeArtifact Security)

VPN Appliance Deployment:"Software VPN appliances are commonly used for secure, encrypted connectivity between on-premises data centers and AWS."(AWS VPN Options)

This hook runs before the new application version is installed on the replacement instances. This is the best place to run the script because it ensures that the license file is downloaded and installed before the replacement instances start to handle request traffic. If you use any other hook, you may encounter errors or inconsistencies in your application.

because of "as few maintenance tasks as possible on the underlying infrastructure". Fargate does that better than "one centralized application server"

To meet the requirements of deploying a workload on several hundred EC2 instances with least-privilege permissions and temporary security credentials, the company should use an IAM role and an instance profile. An IAM role is a way to grant permissions to an entity that you trust, such as an EC2 instance. An instance profile is a container for an IAM role that you can use to pass role information to an EC2 instance when the instance starts. By using an IAM role and an instance profile, the EC2 instances can automatically receive temporary security credentials from the AWS Security Token Service (STS) and use them to access the S3 buckets. This way, the company does not need to manage or rotate any long-term credentials, such as IAM users or access keys.

To use an IAM role and an instance profile, the company should create an IAM role that has the appropriate permissions for S3 buckets. The permissions should allow the EC2 instances to read from the source S3 bucket and write to the destination S3 bucket. The company should also create a trust policy for the IAM role that specifies that EC2 is allowed to assume the role. Then, the company should add the IAM role to an instance profile. An instance profile can have only one IAM role, so the company does not need to create multiple roles or profiles for this scenario.

Next, the company should update the launch template to include the IAM instance profile. A launch template is a way to save launch parameters for EC2 instances, such as the instance type, security group, user data, and IAM instance profile. By using a launch template, the company can ensure that all EC2 instances in the Auto Scaling group have consistent configuration and permissions. The company should specify the name or ARN of the IAM instance profile in the launch template. This way, when the Auto Scaling group launches new EC2 instances based on the launch template, they will automatically receive the IAM role and its permissions through the instance profile.

The other options are not correct because they do not meet the requirements or follow best practices. Creating an IAM user and generating a secret key and token is not a good option because it involves managing long-term credentials that need to be rotated regularly. Moreover, embedding credentials in user data is not secure because user data is visible to anyone who can describe the EC2 instance. Creating a trust anchor and profile is not a valid option because trust anchors are used for certificate-based authentication, not for IAM roles or instance profiles. Modifying user data to use a new secret key and token is also not a good option because it requires updating user data every time the credentials change, which is not scalable or efficient.

1: AWS Certified DevOps Engineer - Professional Certification | AWS Certification | AWS

2: DevOps Resources - Amazon Web Services (AWS)

3: Exam Readiness: AWS Certified DevOps Engineer - Professional

IAM Roles for Amazon EC2 - AWS Identity and Access Management

Working with Instance Profiles - AWS Identity and Access Management

Launching an Instance Using a Launch Template - Amazon Elastic Compute Cloud

Temporary Security Credentials - AWS Identity and Access Management