What should the solutions architect do next in the new management account?
Have the R&D AWS account be part of both organizations during the transition.
Invite the R&D AWS account to be part of the new organization after the R&D AWS account has left the prior organization.
Create a new R&D AWS account in the new organization. Migrate resources from the prior R&D AWS account to the new R&D AWS account.
Have the R&D AWS account join the new organization. Make the new management account a member of the prior organization.
Explanations:
An AWS account can only be a member of one organization at a time. Therefore, it is not possible for the R&D AWS account to be part of both organizations simultaneously.
This option is correct because the R&D AWS account must first leave the prior organization before it can be invited to the new organization. This aligns with the process of moving an AWS account from one organization to another.
This option suggests creating a new AWS account in the new organization and migrating resources, which is not necessary unless there are specific requirements for starting from a new account. The existing R&D account should be transferred.
The R&D AWS account cannot join the new organization while the management account is still part of the previous organization. The R&D account must leave the old organization first before joining the new one.
I outline that the answer is:
Invite the R&D AWS account to be part of the new organization after the R&D AWS account has left the prior organization.
I opine that the answer is:
Invite the R&D AWS account to be part of the new organization after the R&D AWS account has left the prior organization.