NetApp Exam NS0-593 Topic 7 Question 52 Discussion

Actual exam question for NetApp's NS0-593 exam

Question #: 52
Topic #: 7

A user reports that a colleague saved a file called Test.txt from a UNIX system to a multiprotocol volume. When opening the file later from a Windows system, it was not the file that they wanted. The file that they wanted was named TEST~1.TXT.

Which statement explains this behavior?

AUNIX name mapping updated the filename.

BA Snapshot copy preserved two versions of the file.

CWindows Volume Shadow Copy Service stored an older version of the file.

DCase Insensitivity of SMB clients caused the file to be displayed with a different name.

Show Suggested Answer

Suggested Answer: D

= The multiprotocol volume allows clients to access files using both NFS and SMB protocols. The NFS protocol is case-sensitive, meaning that Test.txt and TEST~1.TXT are two different files. The SMB protocol is case-insensitive, meaning that it treats uppercase and lowercase letters as the same when searching for a file. Therefore, when the user opened the file from a Windows system using SMB, the system could not distinguish between Test.txt and TEST~1.TXT and displayed one of them arbitrarily. This could lead to confusion and data loss if the user modified or deleted the wrong file.Reference=Client protocols;Multiprotocol NAS in NetApp ONTAP Overview and Best Practices, page 30-31.

by Ryan at Aug 05, 2024, 09:41 AM

Limited Time Offer

25%

Off

Get Premium NS0-593 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Hildred

4 months ago

I don't think so, I believe D is the correct answer because of how SMB clients handle file names.

upvoted 0 times

...

Francisca

4 months ago

But could it also be A, with UNIX name mapping updating the filename?

upvoted 0 times

...

Renay

4 months ago

I agree with Gerald, the case insensitivity of SMB clients can cause this issue.

upvoted 0 times

...

Gerald

4 months ago

I think the answer is D.

upvoted 0 times

...

Lovetta

4 months ago

I'm not sure, but I think B could also be a possibility.

upvoted 0 times

...

Moira

5 months ago

I agree with Kate, the case insensitivity of SMB clients can cause this issue.

upvoted 0 times

...

Melvin

5 months ago

Haha, the good old Test.txt vs TEST~1.TXT debacle. Gotta love those case-sensitive UNIX systems and their playful name conversions.

upvoted 0 times

Mayra

4 months ago

I know, it can be so confusing sometimes!

upvoted 0 times

...

Meaghan

5 months ago

D) Case Insensitivity of SMB clients caused the file to be displayed with a different name.

upvoted 0 times

...

Danica

5 months ago

A) UNIX name mapping updated the filename.

upvoted 0 times

...

Kate

5 months ago

I think the answer is D.

upvoted 0 times

...

Mozell

5 months ago

Hmm, interesting. I wonder if they tried 'dir /x' in Windows to see the 8.3 filename? That might have given them a clue.

upvoted 0 times

...

Erinn

5 months ago

Ah, the age-old problem of UNIX and Windows file name compatibility. I'd have to go with option D on this one - the case insensitivity of SMB clients is the likely culprit here.

upvoted 0 times