BlackFriday 2024! 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 10 Question 29 Discussion

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

An SAP solutions architect is using AWS Systems Manager Distributor to install the AWS Data Provider for SAP on production SAP application servers and SAP HANA database servers The SAP application servers and the SAP HANA database servers are running on Red Hat Enterprise Linux.

The SAP solutions architect chooses instances manually m Systems Manager Distributor and schedules installation. The installation fails with an access and authorization error related to Amazon CloudWatch and Amazon EC2 instances. There is no error related to AWS connectivity.

What should the SAP solutions architect do to resolve the error?

Show Suggested Answer Hide Answer
Suggested Answer: C

It's likely that the instances currently lack the necessary permissions to interact with CloudWatch and EC2. By creating an IAM role with the appropriate permissions and attaching it to the instances, the SAP solutions architect can grant the necessary permissions to the instances to complete the installation.

https://docs.aws.amazon.com/sap/latest/general/data-provider-troubleshooting.html


Contribute your Thoughts:

Aleisha
5 months ago
I see your point, Mitsue. However, I believe the best approach would be D) Wait until Systems Manager Agent is fully installed and then use Patch Manager for installation.
upvoted 0 times
...
Mitsue
5 months ago
I would go with B) Download the AWS Data Provider for SAP installation package from AWS Marketplace and use an operating system super user to install it manually.
upvoted 0 times
...
Graciela
5 months ago
I agree with Elliott. It makes sense to set up the correct permissions for CloudWatch and EC2 instances.
upvoted 0 times
...
Elliott
5 months ago
I think the correct answer is C) Create an IAM role Attach the appropriate policy to the role Attach the role to the appropriate EC2 instances
upvoted 0 times
...
Raina
5 months ago
I would go with option C - creating an IAM role seems like the most logical step to resolve the error.
upvoted 0 times
...
Melvin
5 months ago
But what if the issue is related to Amazon CloudWatch and EC2 instances? I still think installing the CloudWatch agent is the best solution.
upvoted 0 times
...
Rachael
5 months ago
I disagree, I believe creating an IAM role and attaching it to the EC2 instances is the way to go.
upvoted 0 times
...
Melvin
6 months ago
I think the architect should install the CloudWatch agent first.
upvoted 0 times
...
Yolande
7 months ago
Haha, good one! But seriously, I think C is the right answer here. The IAM role is the most straightforward solution to the access and authorization problem.
upvoted 0 times
Nidia
7 months ago
So, it looks like C is indeed the correct answer in this scenario.
upvoted 0 times
...
Kip
7 months ago
But attaching the IAM role to the EC2 instances is crucial for access.
upvoted 0 times
...
Lashonda
7 months ago
Downloading the installation package could be a good step as well.
upvoted 0 times
...
Leatha
7 months ago
Installing the CloudWatch agent might not directly solve the issue.
upvoted 0 times
...
Regenia
7 months ago
It would definitely help in resolving the access and authorization error.
upvoted 0 times
...
Jame
7 months ago
I agree, creating an IAM role seems like the best option.
upvoted 0 times
...
...
Cherry
7 months ago
I agree with Rolland. The error message clearly indicates an access and authorization issue, so the IAM role is the way to go. Plus, it's a best practice to use managed IAM roles instead of hardcoding credentials.
upvoted 0 times
...
Torie
7 months ago
Hmm, I'm not so sure. What if the CloudWatch agent is not properly installed? Maybe we should try A first, just to be safe, and then move on to the IAM role if that doesn't work.
upvoted 0 times
...
Rolland
7 months ago
This question seems pretty straightforward. The issue is with access and authorization, likely related to the IAM permissions. I think the answer is C - we need to create an IAM role with the appropriate policy and attach it to the EC2 instances.
upvoted 0 times
...

Save Cancel