nerdexam
Amazon

DOP-C02 · Question #214

A company is migrating from its on-premises data center to AWS. The company currently uses a custom on-premises Cl/CD pipeline solution to build and package software. The company wants its software…

The correct answer is B. Create an AWS Identity and Access Management Roles Anywhere trust anchor. Create an IAM D. For each public repository, create a CodeArutact repository that is configured with an external. To integrate on-premises CI/CD with AWS CodeArtifact and manage public dependencies with minimal operational overhead, use IAM Roles Anywhere for secure authentication and configure dedicated CodeArtifact repositories for each public upstream.

Submitted by salim_om· Mar 6, 2026SDLC Automation

Question

A company is migrating from its on-premises data center to AWS. The company currently uses a custom on-premises Cl/CD pipeline solution to build and package software. The company wants its software packages and dependent public repositories to be available in AWS CodeArtifact to facilitate the creation of application-specific pipelines. Which combination of steps should the company take to update the CI/CD pipeline solution and to configure CodeArtifact with the LEAST operational overhead? (Choose two.)

Options

  • AUpdate the C1ICD pipeline to create a VM image that contains newly packaged software. Use
  • BCreate an AWS Identity and Access Management Roles Anywhere trust anchor. Create an IAM
  • CCreate a new Amazon S3 bucket. Generate a presigned URL that allows the PutObject request.
  • DFor each public repository, create a CodeArutact repository that is configured with an external
  • ECreate a Codeartitact repository that is configured with a set of external connections to the public

How the community answered

(34 responses)
  • A
    15% (5)
  • B
    76% (26)
  • C
    3% (1)
  • E
    6% (2)

Why each option

To integrate on-premises CI/CD with AWS CodeArtifact and manage public dependencies with minimal operational overhead, use IAM Roles Anywhere for secure authentication and configure dedicated CodeArtifact repositories for each public upstream.

AUpdate the C1ICD pipeline to create a VM image that contains newly packaged software. Use

CodeArtifact is designed for software packages (e.g., npm, Maven, PyPI) rather than VM images, making this approach unsuitable for storing application-specific packages.

BCreate an AWS Identity and Access Management Roles Anywhere trust anchor. Create an IAMCorrect

AWS IAM Roles Anywhere provides a secure and low-overhead method for the on-premises CI/CD pipeline to authenticate to AWS services like CodeArtifact by assuming an IAM role using X.509 certificates.

CCreate a new Amazon S3 bucket. Generate a presigned URL that allows the PutObject request.

Using S3 with presigned URLs is a less integrated and higher-overhead approach for managing continuous package uploads compared to CodeArtifact's native package manager integrations and upstream capabilities.

DFor each public repository, create a CodeArutact repository that is configured with an externalCorrect

Creating a dedicated CodeArtifact repository configured with an external connection for each public repository allows CodeArtifact to fetch and cache public packages, centralizing dependency management efficiently and securely.

ECreate a Codeartitact repository that is configured with a set of external connections to the public

While a CodeArtifact repository can have multiple upstream connections, option D's approach of creating a CodeArtifact repository for *each* public upstream is a clearer and more common pattern for managing distinct public dependencies.

Concept tested: AWS CodeArtifact upstream configuration and on-premises to AWS authentication

Source: https://docs.aws.amazon.com/codeartifact/latest/ug/upstreams.html

Topics

#CodeArtifact#CI/CD Integration#AWS Roles Anywhere#Package Management

Community Discussion

No community discussion yet for this question.

Full DOP-C02 Practice