Your team is currently working on source code that’s defined in a Subversion repository. The company has just started using AWS tools for their CI/CD process and has now mandated that source code be migrated to AWS CodeCommit. Which of the following steps would you perform to fulfill this requirement? Choose 2 answers from the options given below.

Answer options:

A.Migrate the code as it is to the AWS CodeCommit Repository.
B.Migrate the code to a Git Repository first.
C.Migrate Git code to AWS Code Commit.
D.Ensure to clone the current repository from Subversion before committing it directly to AWS CodeCommit.

Answer – B and C
The AWS Documentation mentions the following.
Migrate to AWS CodeCommit.
You can migrate a Git repository to an AWS CodeCommit repository in many ways: by cloning it, mirroring it, migrating all or just some of the branches, and so on. You can also migrate local, unversioned content on your computer to AWS CodeCommit.
The following topics demonstrate some of the ways you can choose to migrate a repository. Your steps may vary, depending on your repository type, style, or complexity and the decisions you make about what and how you want to migrate. For very large repositories, you might want to consider migrating incrementally.
Note
You can migrate to AWS CodeCommit from other version control systems, such as Perforce, Subversion, or TFS, but you will have to migrate to Git first.
Options A and D are incorrect since you need to migrate the repository to Git first.
For more information on migrating a repository, please refer to the below URL-
https://docs.aws.amazon.com/codecommit/latest/userguide/how-to-migrate-repository.html