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 2 Question 77 Discussion

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

How can you use Prisma Public Cloud to identify Amazon EC2 instances that have been tagged as "Private?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

Gennie
2 months ago
Option A sounds like it could work, but creating an RQL config query seems a bit more complex than necessary for this task. C is the way to go, in my opinion.
upvoted 0 times
Meaghan
1 months ago
I also prefer option C, it's simple and efficient for finding the tagged instances.
upvoted 0 times
...
Youlanda
1 months ago
I think option A could work too, but option C is definitely easier to use for this specific task.
upvoted 0 times
...
Lai
1 months ago
I agree, option C is the most straightforward way to identify Amazon EC2 instances tagged as 'Private.'
upvoted 0 times
...
...
Cortney
2 months ago
Haha, I bet the exam writers were hoping we'd overthink this one. C is clearly the easiest way to get the job done. No need to get fancy with RQL or compliance reports.
upvoted 0 times
Laila
1 months ago
User 3: I always go for the straightforward approach, especially in exams.
upvoted 0 times
...
Lynda
1 months ago
Agreed, no need to complicate things when there's an easy solution.
upvoted 0 times
...
Paris
2 months ago
Yeah, C is definitely the simplest option.
upvoted 0 times
...
...
Lourdes
2 months ago
D is an interesting option, but a CIS compliance report is a bit overkill just to find tagged resources. I'd stick with the more targeted approach in C.
upvoted 0 times
Edna
29 days ago
True, that could be another effective way to identify resources with the specific tag.
upvoted 0 times
...
Carylon
1 months ago
I think creating an RQL config query in option A could also be a good approach.
upvoted 0 times
...
Tommy
1 months ago
Yeah, using the Asset Dashboard and filtering on tags is a straightforward method.
upvoted 0 times
...
Barrett
2 months ago
I agree, option C seems like a more efficient way to identify tagged resources.
upvoted 0 times
...
...
Yasuko
3 months ago
I think both A and C could be correct, but I would go with A because it directly targets resources with the tag 'Private.'
upvoted 0 times
...
Mickie
3 months ago
I disagree, I believe the correct answer is C) Open the Asset Dashboard, filter on tags: and choose 'Private.'
upvoted 0 times
...
Berry
3 months ago
I was thinking B, since a network query could reveal traffic patterns from instances with the 'Private' tag. That could provide additional context beyond just the tag itself.
upvoted 0 times
Lashanda
2 months ago
D) Generating a CIS compliance report could also provide valuable information.
upvoted 0 times
...
Pearline
2 months ago
C) Open the Asset Dashboard, filter on tags: and choose 'Private.'
upvoted 0 times
...
Tish
2 months ago
B) I agree, a network query could give more context on traffic patterns.
upvoted 0 times
...
Queen
2 months ago
A) Create an RQL config query to identify resources with the tag 'Private.'
upvoted 0 times
...
...
Callie
3 months ago
I think the answer is A) Create an RQL config query to identify resources with the tag 'Private.'
upvoted 0 times
...
Caitlin
3 months ago
Option C seems the most straightforward way to identify resources with the 'Private' tag. Filtering the Asset Dashboard is a simple and intuitive approach.
upvoted 0 times
Lonny
3 months ago
Filtering the Asset Dashboard is a simple and intuitive approach.
upvoted 0 times
...
Daniel
3 months ago
Option C seems the most straightforward way to identify resources with the 'Private' tag.
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