A company has multiple lines of business (LOBs) that roll up to the parent company. The company has asked its solutions architect to develop a solution with the following requirements: - Produce a…

Creating a separate organization for each LOB would prevent consolidated billing across all LOBs and result in multiple invoices, contradicting the requirement for a single invoice.

Creating a single organization in the parent account and inviting each LOB account enables consolidated billing and allows for centralized management and application of policies across all accounts, addressing the single invoice and cost breakdown requirements.

Service quotas (limits) restrict resource creation at a usage level, not at a policy level for enabling/disabling services or features, and are not the primary tool for implementing governance policies on what services are permitted.

Creating an Service Control Policy (SCP) that allows only approved services and features and applying it to the LOB organizational units (OUs) or accounts restricts what LOB accounts can provision, even if they have full administrator permissions within their account, thus enforcing governance.

While enabling consolidated billing is part of the solution, merely linking accounts through consolidated billing does not provide the capability to restrict services and features based on governance policies; AWS Organizations is needed for that.