A company has five organizational units (OUs) as part of its organization in AWS Organizations. Each OU correlates to 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?

AWS accounts can only be members of one organization at a time. Therefore, the R&D AWS account must first leave the original organization before it can be invited to join the new organization. This ensures a clean separation and proper management within the new organizational structure. "Have the R&D AWS account be part of both organizations during the transition" is incorrect because an AWS account cannot simultaneously belong to two organizations. "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" is an unnecessarily complex and resource-intensive approach. Migrating resources can be time-consuming and introduce potential downtime. "Have the R&D AWS account join the new organization. Make the new management account a member of the prior organization" is incorrect because a management account cannot be a member account of another organization.