Nutanix NCP-US Exam - Topic 1 Question 47 Discussion

Actual exam question for Nutanix's NCP-US exam

Question #: 47
Topic #: 1

After configuring Smart DR, an administrator is unable see the policy in the Policies tab. The administrator has confirmed that all FSVMs are able to connect to Prism Central via port 9440 bidirectional.

What is the possible reason for this issue?

AThe primary and recovery file servers do not have the same protocols.

BPort 7575 should be open for all External/Client IPS of FSVMs on the Source and Target cluster.

CThe primary and recovery file servers do not have the same version.

DPort 7575 should be open for all Internal/Storage IPs of FSVMs on the Source and Target.

Show Suggested Answer

Suggested Answer: A

File Analytics is a feature that provides insights into the data stored in Files, such as file types, sizes, owners, permissions, and access patterns. File Analytics also provides security against ransomware attacks by scanning files for ransomware in real time and providing notification in the event of a ransomware attack.File Analytics can detect ransomware based on file extensions, file signatures, or third-party solutions2. Reference: Nutanix File Analytics Administration Guide2

by Alethea at Mar 04, 2025, 10:59 PM

Limited Time Offer

25%

Off

Get Premium NCP-US Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Lacey

6 months ago

Just to clarify, is port 7575 really required for Internal/Storage IPs?

upvoted 0 times

...

Karol

6 months ago

I doubt it's the protocols, seems unlikely to cause this.

upvoted 0 times

...

Angella

6 months ago

Wait, are we sure it's not a version mismatch? Option C could be it.

upvoted 0 times

...

Kenia

7 months ago

Definitely agree with that, had the same issue before!

upvoted 0 times

...

Hershel

7 months ago

I think it might be option B, port 7575 needs to be open.

upvoted 0 times

...

Adela

7 months ago

I’m leaning towards the idea that port 7575 needs to be open for internal IPs, but I might be mixing it up with another scenario we practiced.

upvoted 0 times

...

Geoffrey

7 months ago

The version mismatch between the primary and recovery file servers sounds familiar. I feel like that could definitely cause issues with visibility.

upvoted 0 times

...

Angella

7 months ago

I think I saw a practice question about needing to open port 7575 for communication, but I can't recall if it was for internal or external IPs.

upvoted 0 times

...

Christa

8 months ago

I remember something about the protocols needing to match, but I'm not sure if that's the main issue here.

upvoted 0 times

...

Loren

8 months ago

Ah, I see. This seems to be a common issue with Smart DR. My guess is that the port 7575 configuration is the culprit. I'd recommend checking that the port is open for the correct IP addresses on both the source and target clusters.

upvoted 0 times

...

Avery

8 months ago

I think the key here is to focus on the file server configuration. The question mentions that the administrator is unable to see the policy, so it's likely related to the file server setup. I'd start by double-checking the protocol and version compatibility.

upvoted 0 times

...

Teresita

8 months ago

I'm a bit confused here. If the FSVMs can connect to Prism Central, then the port 9440 connectivity seems to be working. Maybe it's something to do with the protocols or the port 7575 configuration.

upvoted 0 times

...

Latanya

8 months ago

Okay, let's see. The administrator has confirmed connectivity to Prism Central, so that's not the issue. I'm wondering if it could be a version mismatch between the primary and recovery file servers.

upvoted 0 times

...

Cassandra

8 months ago

Hmm, this one seems tricky. I'll need to carefully review the information provided and think through the possible reasons.

upvoted 0 times

...

Rolland

1 year ago

I'm leaning towards D. If the internal/storage IPs aren't open, then the FSVM communication is going to be blocked, and that could definitely cause the policy to not show up.

upvoted 0 times

...

Lashon

1 year ago

Ha! Gotta love these networking questions. I bet the real issue is that one of the admins forgot to disable the firewall on their toaster. Classic!

upvoted 0 times

Clorinda

11 months ago

Check if the policies are properly configured.

upvoted 0 times

...

Julio

12 months ago

Could be a network configuration issue.

upvoted 0 times

...

Cheryll

12 months ago

Maybe there is a firewall blocking the connection.

upvoted 0 times

...

Paris

1 year ago

I'm not sure about this one. Are the primary and recovery file servers really supposed to have the same version? I thought that was just for the FSVM itself.

upvoted 0 times