You are an AWS Solutions Architect in a financial company. The company recently started working on migrating legacy applications to AWS. You planned to use a new AWS Organization to manage all AWS accounts so that you can easily configure accounts, assign organizational units, configure security policies, etc. Which methods are valid for you to add accounts to the Organization? (Select TWO.)

Answer options:

A.In the AWS Organization console, create accounts within your organization.
B.Use AWS CLI request-join-to-organization for other AWS accounts to join the Organization. After the Organization owner accepts the requests, the accounts will join successfully.
C.For other accounts, use root accounts to login to the AWS Organization console, create requests to the Organization owner to join the organization.
D.In the root account of the Organization, create invitations to other accounts and wait for them to accept the invitations.
E.For other accounts, create a cross-account IAM role that allows the operation of add-account-to-organization for the resource of the AWS Organization ARN. Use an IAM user to assume the IAM role and send an API call to add the account to the Organization.

Correct Answer – A, D
There are two methods to add accounts to the AWS Organization either by creating new accounts within an Organization or creating invitations. Please refer to
https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_accounts_invites.html
and
https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_accounts_create.html.
Option A is CORRECT because the user can create a new account that is part of the Organization.
Option B is incorrect because other accounts can not create requests to join the Organization. There is no CLI request-join-to-organization as well.
Option C is incorrect because, in the AWS console, users cannot create requests to join an Organization. However, they can accept invitations.
Option D is CORRECT because this can be done through the AWS console, CLI, or API.
Option E is incorrect because the cross-account IAM role is not required in this scenario. Also, there is no API call to add to an organization for other accounts.