Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Palo Alto Networks Exam PSE-PrismaCloud Topic 5 Question 64 Discussion

Actual exam question for Palo Alto Networks's PSE-PrismaCloud exam
Question #: 64
Topic #: 5
[All PSE-PrismaCloud Questions]

A customer CSO has asked you to demonstrate how to identify all "Amazon RDS" resources deployed and the region that they are deployed in. What are two ways that Prisma Public Cloud can show the relevant information?(Choose two.)

Show Suggested Answer Hide Answer
Suggested Answer: B, D

Contribute your Thoughts:

Wayne
6 months ago
Candidate 6: I think A and D are the correct answers. Compliance reports and filtering on AWS resources seems like the way to go.
upvoted 0 times
...
Huey
6 months ago
Candidate 5: I agree with Candidate 4. Using RQL queries and filtering in the Asset dashboard should work.
upvoted 0 times
...
Leah
6 months ago
Candidate 4: I think both B and D are correct options. The Investigate tab and Asset dashboard should provide the needed information.
upvoted 0 times
...
Cherrie
6 months ago
Candidate 3: I'm not sure about B, but I think A might be correct because compliance reports can show deployed resources.
upvoted 0 times
...
Allene
7 months ago
Candidate 2: I agree with Candidate 1, but I also think D is a good option because the Asset dashboard specifically shows AWS resources.
upvoted 0 times
...
Mertie
7 months ago
Candidate 1: I think the answer is B because the Investigate tab allows you to write RQL queries.
upvoted 0 times
...
Timothy
7 months ago
I am not sure about option C. Configuring an Inventory report may not necessarily show all Amazon RDS resources deployed.
upvoted 0 times
...
Allene
7 months ago
I believe option B is a good choice as well. Writing an RQL query can provide specific information about Amazon RDS resources in different regions.
upvoted 0 times
...
Timothy
7 months ago
I agree with Option D also seems valid as filtering on AWS and selecting Amazon RDS should display the relevant resources.
upvoted 0 times
...
Mari
7 months ago
I think option A is correct because compliance reports usually show details about deployed resources.
upvoted 0 times
...
Charlie
8 months ago
Absolutely, the Asset dashboard in option D is perfect for this. Just filter by AWS services and you'll be able to see all your RDS instances and their locations. Easy peasy!
upvoted 0 times
...
Keneth
8 months ago
Yeah, B and D are definitely the way to go. I'm pretty sure the RQL query in option B would let you easily filter and view all the RDS resources and their regions.
upvoted 0 times
...
Afton
8 months ago
I agree with you on B and D. Generating a compliance report (A) seems a bit overkill for this task, and configuring an Inventory report (C) doesn't seem directly relevant to identifying Amazon RDS resources.
upvoted 0 times
Fairy
7 months ago
Great, I think we're all on the same page then.
upvoted 0 times
...
Grover
7 months ago
Let's focus on those two options to get the information we need.
upvoted 0 times
...
Luisa
8 months ago
We should go with B and D for sure.
upvoted 0 times
...
Jules
8 months ago
Exactly, configuring an Inventory report doesn't seem like the most direct way to identify Amazon RDS resources.
upvoted 0 times
...
Shoshana
8 months ago
Agree, generating a compliance report sounds like too much for this task.
upvoted 0 times
...
Lavonda
8 months ago
Yeah, writing an RQL query and using the Asset dashboard make sense.
upvoted 0 times
...
Ricki
8 months ago
I think B and D are the best options here.
upvoted 0 times
...
...
Wynell
8 months ago
Hmm, this is a tricky one. I'm not too familiar with Prisma Public Cloud, but I think B and D seem like the most straightforward options here.
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