Use the AWS Organizations console to remove the account from the source organization and accept the invitation from the target organization is correct because it lets you move the existing AWS account into the acquiring organization while preserving the account's resources, identities and configuration.

You remove the member account from the current organization and the destination organization sends an invitation which the account accepts. After acceptance the account becomes part of the new organization and its resources remain intact. Make sure you have the necessary management account permissions and review billing, service control policies and IAM roles as part of the move.

Create a new account in the target organization and replicate workloads with AWS Application Migration Service is wrong because it requires creating a separate account and performing full workload migration which increases effort and risk when a direct account transfer is supported.

Use AWS CloudFormation StackSets to relocate the account between organizations is incorrect because CloudFormation and StackSets manage resources inside accounts and they do not transfer account membership between organizations.

Create a new account in the target organization and share needed resources through AWS Resource Access Manager is not suitable because RAM only shares resources across accounts and does not change account ownership or organization membership so you would still have two accounts to manage.

Full AWS Practitioner Certification Question