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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Palo Alto Networks XDR-Engineer Exam - Topic 4 Question 1 Discussion

[Cortex XDR Agent Configuration]Multiple remote desktop users complain of in-house applications no longer working. The team uses macOS with Cortex XDR agents version 8.7.0, and the applications were previously allowed by disable prevention rules attached to the Exceptions Profile "Engineer-Mac." Based on the images below, what is a reason for this behavior?
A) Endpoint IP address changed from 192.168.0.0 range to 192.168.100.0 range
B) The Cloud Identity Engine is disconnected or removed
C) XDR agent version was downgraded from 8.7.0 to 8.4.0
D) Installation type changed from VDI to Kubernetes

Palo Alto Networks XDR-Engineer Exam - Topic 4 Question 1 Discussion

Actual exam question for Palo Alto Networks's XDR-Engineer exam
Question #: 1
Topic #: 4
[All XDR-Engineer Questions]

[Cortex XDR Agent Configuration]

Multiple remote desktop users complain of in-house applications no longer working. The team uses macOS with Cortex XDR agents version 8.7.0, and the applications were previously allowed by disable prevention rules attached to the Exceptions Profile "Engineer-Mac." Based on the images below, what is a reason for this behavior?

Show Suggested Answer Hide Answer
Suggested Answer: A

by Roslyn at Jun 12, 2025, 08:43 PM

Limited Time Offer

25%

Off

Get Premium XDR-Engineer Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Louis
9 months ago
Downgrading the XDR agent might also cause problems.
upvoted 0 times
...
Martha
9 months ago
Not sure about that, seems a bit off to me.
upvoted 0 times
...
Nilsa
9 months ago
Definitely agree, that makes sense!
upvoted 0 times
...
Beckie
10 months ago
Wait, could it really be the Cloud Identity Engine?
upvoted 0 times
...
Macy
10 months ago
I think the IP address change could be the issue.
upvoted 0 times
...
Marcelle
10 months ago
Changing the installation type sounds familiar, but I can't remember if that would directly affect the applications. It feels like it could be a factor.
upvoted 0 times
...
Rozella
10 months ago
I vaguely recall a practice question about downgrading the XDR agent version. Could that really impact the exceptions profile?
upvoted 0 times
...
Reta
11 months ago
I think we discussed the Cloud Identity Engine in class. If it's disconnected, it might cause problems with user authentication, right?
upvoted 0 times
...
Marti
11 months ago
I remember something about how changes in IP address could affect application access, but I'm not sure if that's the main issue here.
upvoted 0 times
...
Patrick
11 months ago
The Kubernetes installation type is an interesting possibility. I'll need to understand how that might impact the in-house applications and their interaction with the Cortex XDR agent.
upvoted 0 times
...
Glenna
11 months ago
Based on the version information, I'm wondering if there was an agent downgrade that caused the compatibility issues. I'll look into the release notes to see if that could be the explanation.
upvoted 0 times
...
Kiley
11 months ago
I'm a bit confused by the mention of the Cloud Identity Engine. I'll need to research that component and how it might be related to the application problems.
upvoted 0 times
...
Flo
11 months ago
Hmm, the IP address change seems like the most obvious culprit here. I'll double-check the network configuration details to see if that's the case.
upvoted 0 times
...
Claudia
12 months ago
This looks like a tricky one. I'll need to carefully review the information provided and the possible answers to determine the most likely reason for the application issues.
upvoted 0 times
...
Harrison
1 year ago
I'm going to go with the IP address change. It's the most straightforward explanation, and the 'Engineer-Mac' Exceptions Profile should have protected the apps from any other changes.
upvoted 0 times
Wei
1 year ago
B) The Cloud Identity Engine is disconnected or removed
upvoted 0 times
...
Wei
1 year ago
A) Endpoint IP address changed from 192.168.0.0 range to 192.168.100.0 range
upvoted 0 times
...
...
Anglea
1 year ago
Installation type changing from VDI to Kubernetes? That's a bit of a stretch, don't you think? I bet the IT team is just having a 'Kubernetes day' and trying to blame it on that.
upvoted 0 times
...
Jaime
1 year ago
Downgrading the XDR agent version from 8.7.0 to 8.4.0 would be my guess. Those version changes can sometimes break compatibility with certain apps.
upvoted 0 times
...
Barbra
1 year ago
Hmm, the Cloud Identity Engine being disconnected or removed could definitely cause this problem. I wonder if the IT team forgot to update the configuration after making that change.
upvoted 0 times
...
Georgene
1 year ago
The endpoint IP address change from 192.168.0.0 to 192.168.100.0 range seems like the most likely reason. The applications were previously allowed by the Exceptions Profile, so that shouldn't be the issue.
upvoted 0 times
Janae
1 year ago
B) The Cloud Identity Engine is disconnected or removed
upvoted 0 times
...
Lizbeth
1 year ago
A) Endpoint IP address changed from 192.168.0.0 range to 192.168.100.0 range
upvoted 0 times
...
...
Remedios
1 year ago
But what about the endpoint IP address change? Could that be a factor too?
upvoted 0 times
...
Dierdre
1 year ago
I agree with Brianne, that could definitely cause the issue.
upvoted 0 times
...
Brianne
1 year ago
I think the reason could be the XDR agent version downgrade.
upvoted 0 times
...

Save Cancel