Q38Design Secure Architectures
A company has five organizational units (OUs) in AWS Organizations. Each OU corresponds to one of the five businesses that the company owns. The company's research and development (R&D) business is separating from the company and will need its own organization. A solutions architect creates a separate new management account for this purpose. What should the solutions architect do next in the new management account?
← → navigate · a answer
Community votes
Discussion · 16
B 9
An account can only join another org when it leaves the first org.
A is wrong as it's not possible
C that's a new account so not really a migration
D The R&D department is separating from the company so you don't want the OU to join via nesting
B 7
B as exactly described here: https://repost.aws/knowledge-center/organizations-move-accounts
B 7
In either case, perform these actions for each member account:
- Remove the member account from the old organization.
- Send an invite to the member account from the new organization.
- Accept the invite to the new organization from the member account.
https://repost.aws/knowledge-center/organizations-move-accounts
B 4
account can leave current organization and then join new organization.
B 4
https://aws.amazon.com/blogs/mt/migrating-accounts-between-aws-organizations-with-consolidated-billing-to-all-features/
3
B
https://aws.amazon.com/blogs/mt/migrating-accounts-between-aws-organizations-with-consolidated-billing-to-all-features/
B 3
https://repost.aws/knowledge-center/organizations-move-accounts
Remove the member account from the old organization.
Send an invite to the member account from the new organization.
Accept the invite to the new organization from the member account.
B 2
Option B: Invite the R&D AWS account to be part of the new organization after the R&D AWS account has left the prior organization is the appropriate approach. This option ensures that the R&D AWS account transitions smoothly from the old organization to the new one. The steps involved are:
Remove the R&D AWS account from the existing organization: This is done from the existing organization’s management account.
Invite the R&D AWS account to join the new organization: Once the R&D account is no longer part of the previous organization, it can be invited to and accepted into the new organization.
C 2
Creating a brand new AWS account in the new organization (Option C) allows for a clean separation and migration of only the necessary resources from the old account to the new.
B 2
As per this document, B is clearly the answer.
https://repost.aws/knowledge-center/organizations-move-accounts#:~:text=In%20either%20case%2C-,perform%20these%20actions,-for%20each%20member
2
What kind of "data lose" would happen when you change the account to a new organization? And why should you migrate ALL RESOURCES of the account to a new account?
2
"A clean separation" is already existing, they have their own account. "Migration of only the necessary resources from the old account to the new" is not asked for. They have an account in an existing organization, they need their own organization, thus move the existing account to a new organisation (B), done.
2
Says who?
1
C is better. first migrate , then delete. avoid the data lose.
C 1
C is better. first migrate , then delete. avoid the data lose.
C 1
When separating a business unit from an AWS Organizations structure, best practice is to:
Create a new AWS account dedicated for the business unit in the new organization
Migrate resources from the old account to the new account
Remove the old account from the original organization
This allows a clean break between the organizations and avoids any linking between them after separation.