Pure Storage Exam FBAP_002 Topic 3 Question 47 Discussion

Actual exam question for Pure Storage's FBAP_002 exam

Question #: 47
Topic #: 3

A customer is developing a AI workflow that Ingests sensor data to FlashBlade NFS from its cloud edge collection point for furthers analysis.

The customer's HPC cluster mounts NFS to train the data but S3 to label.

Which challenge will the architect experience with this design?

ANFS and S3 are NOT a shared namespace. ***

BNFS and S3 must use different data VIPs.

CNFS and S3 cannot be enabled concurrently.

DNFS and S3 cannot share export rules.

Show Suggested Answer

Suggested Answer: B

by Jimmie at Sep 15, 2024, 05:36 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Carissa

2 months ago

I'm guessing the architect is going to have a tough time with this one. Option A sounds like the most logical choice, unless they want to end up with a big ol' cluster of incompatible storage systems.

upvoted 0 times

Chauncey

26 days ago

Definitely, it's important to consider compatibility when setting up storage systems.

upvoted 0 times

...

Joanna

1 months ago

That's right, having separate namespaces for NFS and S3 could cause issues.

upvoted 0 times

...

Ira

1 months ago

Option A) NFS and S3 are NOT a shared namespace.

upvoted 0 times

...

Rolande

2 months ago

Haha, this is like trying to mix oil and water. NFS and S3 are about as compatible as cats and dogs. The architect better choose option A if they want to avoid a major migraine.

upvoted 0 times

...

Janine

2 months ago

Ah, the old NFS-S3 conundrum. I bet the architect is going to have a headache trying to make this work. Option A is definitely the way to go, unless they want to end up with a tangled mess of file paths and data silos.

upvoted 0 times

Vernell

2 months ago

Agreed, it's important to maintain clarity in the workflow.

upvoted 0 times

...

Britt

2 months ago

That's right, keeping them separate will avoid confusion.

upvoted 0 times

...

Kimberely

2 months ago

Option A) NFS and S3 are NOT a shared namespace.

upvoted 0 times

...

Keneth

2 months ago

But couldn't the architect just use different data VIPs for NFS and S3 to overcome this challenge?

upvoted 0 times

...

Jarod

2 months ago

I agree with Joseph, having different namespaces for NFS and S3 could cause issues.

upvoted 0 times

...

Joseph

2 months ago

I think the challenge will be that NFS and S3 are not a shared namespace.

upvoted 0 times

...

Devorah

3 months ago

Hmm, I think the correct answer is A. NFS and S3 are not a shared namespace, so the architect will face challenges in integrating the two. Trying to use both in the same workflow sounds like a recipe for disaster.

upvoted 0 times