Your architecture team has recommended the following for the VPCs in your AWS Account.
· A shared services VPC which would provide services to other VPCs
· A hosted VPC that will be accessible to the customer
· The hosted VPC will also interact with the shared services VPC.Which of the following should also be considered as part of the design?
Choose 3 answers from the options given below. Each answer is an independent design solution.

Answer options:

A.Ensure an AWS PrivateLink is available for accessing the Shared services VPC.B.Use VPC peering between the shared services VPC and other VPCs.
C.Setup communication via the Public IPs (or via the Internet) and ensure the right security measures are in place for inter-VPC communications.
D.Create a VPN between each VPC. Ensure the Virtual private gateway is in place for the other VPCs.

Answer - A, B and C
One option is to create an AWS PrivateLink that can access the services in the AWS shared VPC. 
You can create your own application in your VPC and configure it as an AWS PrivateLink-powered service (referred to as an endpoint service). Other AWS principals can create a connection from their VPC to your endpoint service using an interface VPC endpoint. You are the service provider, and the AWS principals that create connections to your service are service consumers.
And the other option is to make the VPC public. But the right security measures need to be put in place.
Option B is correct because, in VPC peering, it states that, You may want to use this spoke configuration when you have resources on a central VPC, such as a repository of services, that other VPCs need to access. The other VPCs do not need access to each others` resources. They only need access to resources on the central VPC. 
Option D is incorrect because this option should only be used for a transit VPC.For more information on VPC and Subnet sizing, please visit the below URL:
https://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/endpoint-service.html