Exam AWS Certified Solutions Architect - Associate SAA-C02 topic 1 question 54 discussion

A & D is correct. With RAM you cannot share the API Gateway, have look here: https://docs.aws.amazon.com/ram/latest/userguide/shareable.html With privatelink you can add the LB, thats the reason why LB is in the description and the API GW after the LB, another account and can than be used from the application.

A & E to me..

AWS PrivateLink works with Network Load Balancers (NLBs) and Application Load Balancers (ALBs)

A & D, Route to IP Addresses In order to address these use cases, Application Load Balancers can now route traffic directly to IP addresses. These addresses can be in the same VPC as the ALB, a peer VPC in the same region, on an EC2 instance connected to a VPC by way of ClassicLink, or on on-premises resources at the other end of a VPN connection or AWS Direct Connect connection.

The hardest limitation is that the peered networks must not have any IP address space overlap. In the case, we don't know if we can use VPC peering or not. But PrivateLink should work.

ad is correct

DE because they are transitive.

When you establish peering relationships between VPCs across different AWS Regions, resources in the VPCs (for example, EC2 instances and Lambda functions) in different AWS Regions can communicate with each other using private IP addresses, without using a gateway, VPN connection, or network appliance. The traffic remains in the private IP space. https://docs.aws.amazon.com/vpc/latest/peering/what-is-vpc-peering.html

E is a distractor! you cant share resources when 2 accounts are not consolidated to same organization. Hence A+D.

I´m with the people on this question

Which architectural improvements will result in the lowest NAT gateway costs? (Select two.) It is NOT asking for a combination. Just the possible options .. OR logic ... not AND logic.

A & E For A: A VPC peering connection is a networking connection between two VPCs that enables you to route traffic between them using private IPv4 addresses or IPv6 addresses. There is no charge to create a VPC peering connection. https://docs.aws.amazon.com/vpc/latest/peering/what-is-vpc-peering.html For E: AWS Resource Access Manager allows you to easily and securely share AWS resources with any AWS account or if you are part of AWS organizations, with organizational units (OUs), or your entire organization. There is no additional charge for using AWS RAM. Services with resources you can share using AWS RAM: Amazon VPC, S3, 53, Aurora, etc. For these case, share with the VPCs https://docs.aws.amazon.com/vpc/latest/peering/what-is-vpc-peering.html

My answer A&D

AE AWS Private link is used to expose a application service to 1000's of VPC. You need NLB on the applicaton service and a ENI on the customer VPC side. ( based on Stephane Maarek Lectures)

A, D for sure

A & D are correct

A and D. no need to have RAM because VPC peering and PrivateLink provide multi-accounts connections.