Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Amazon Exam PAS-C01 Topic 5 Question 39 Discussion

Actual exam question for Amazon's PAS-C01 exam
Question #: 39
Topic #: 5
[All PAS-C01 Questions]

A company is planning to migrate its SAP workloads to AWS. The company will use two VPCs One VPC will be for production systems and one VPC will be for non-production systems. The company will host the non-production systems and the primary node of all the production systems in the same Availability Zone.

What is the MOST cost-effective way to establish a connection between me production systems and the non-production systems?

Show Suggested Answer Hide Answer
Suggested Answer: C

VPC endpoints to ensure that traffic to and from the CloudWatch and EC2 services stays within the VPC. Additionally, an IAM policy is created to grant access to only the necessary actions, such as DescribeInstances and GetMetricStatistics, for all EC2 resources. This approach will provide secure monitoring of the SAP system while maximizing security and ensuring support from both SAP and AWS.

https://docs.aws.amazon.com/sap/latest/general/data-provider-req.html#vpc-endpoints


Contribute your Thoughts:

Sherell
2 months ago
Ah, the age-old cloud architecture conundrum: 'How many layers of complexity can I add to this?' Option B is the clear winner here.
upvoted 0 times
Gracia
2 days ago
Yeah, setting up VPC peering and adding the appropriate routes is the most straightforward approach in this scenario.
upvoted 0 times
...
Arthur
5 days ago
I agree, VPC peering is the most cost-effective solution for connecting the production and non-production systems.
upvoted 0 times
...
Glendora
8 days ago
Option B is definitely the way to go. Keep it simple with a VPC peering connection.
upvoted 0 times
...
...
Major
2 months ago
Option B is the way to go. Why complicate things with a transit gateway or VPN when VPC peering does the job nicely?
upvoted 0 times
Evan
12 days ago
True, but for cost-effectiveness, VPC peering seems like the best option in this scenario.
upvoted 0 times
...
Jamal
17 days ago
True, but for now, simplicity is key. We can always reevaluate later.
upvoted 0 times
...
Dorothy
20 days ago
But wouldn't using a transit gateway be more scalable in the long run?
upvoted 0 times
...
Lewis
26 days ago
But wouldn't a transit gateway provide more flexibility for future growth?
upvoted 0 times
...
Carylon
1 months ago
I agree, VPC peering is simple and cost-effective.
upvoted 0 times
...
Romana
1 months ago
I agree, VPC peering is simple and effective for connecting the production and non-production systems.
upvoted 0 times
...
...
Dyan
2 months ago
I'm leaning towards Option B as well. VPC peering is a native AWS service that doesn't require additional hardware or configurations like the other options.
upvoted 0 times
Tommy
8 days ago
It's good to know that we're all on the same page with choosing Option B for the connection between the VPCs.
upvoted 0 times
...
Mozell
9 days ago
I agree, VPC peering is definitely the most convenient option for this scenario.
upvoted 0 times
...
Essie
11 days ago
Yeah, VPC peering seems like the most straightforward solution for connecting the VPCs.
upvoted 0 times
...
Skye
21 days ago
I think Option B is the way to go. It's simple and cost-effective.
upvoted 0 times
...
...
Jesus
2 months ago
Option B seems the most straightforward and cost-effective way to connect the production and non-production VPCs. VPC peering is a simple and reliable solution for this use case.
upvoted 0 times
...
Lemuel
3 months ago
I'm not sure, but I think setting up an AWS Direct Connect connection might be more reliable for production systems.
upvoted 0 times
...
Hermila
3 months ago
I agree with Werner. Transit Gateway can help in simplifying network connectivity and reducing costs.
upvoted 0 times
...
Werner
3 months ago
I think the most cost-effective way is to create an AWS Transit Gateway.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77