A company is consolidating many standalone AWS accounts into a multi-account architecture and will create new accounts for business units. The company needs centralized authentication to these accounts using its corporate directory. Which combination of actions should a solutions architect recommend? (Choose two.)

To consolidate accounts and enable centralized authentication, the architect should recommend creating a new organization in AWS Organizations with all features enabled. This allows for centralized management and billing across all accounts, including the new ones created for business units. AWS Organizations is fundamental for multi-account strategies. Next, to provide centralized authentication using the corporate directory, the architect should set up AWS IAM Identity Center (AWS Single Sign-On) within this organization. IAM Identity Center can then be configured to integrate with the company's existing corporate directory service (e.g., Active Directory, Okta, Azure AD), allowing users to sign in once and access all assigned AWS accounts and applications. Incorrect options: Amazon Cognito identity pools are primarily for customer-facing applications, not for centralizing corporate AWS account access. While SCPs are used with Organizations, they manage permissions, not authentication. AWS Directory Service is a component, but IAM Identity Center is the service for centralizing SSO. AWS Organizations does not directly handle authentication; it integrates with services like IAM Identity Center for this purpose.