Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25

- Free Preparation Discussions

Pure Storage Portworx-Enterprise-Professional Exam - Topic 1 Question 6 Discussion

Actual exam question for Pure Storage's Portworx-Enterprise-Professional exam

Question #: 6
Topic #: 1

[All Portworx-Enterprise-Professional Questions]

When upgrading Portworx on Kubernetes using the Operator, what step must the administrator take if using the px-versions configmap?

ACreate a new namespace for the configmap.

BUpdate the version manifest.

CDelete the existing configmap.

Show Suggested Answer

Suggested Answer: B

Comprehensive and Detailed Explanation From Exact Extract:

During Portworx upgrades via the Kubernetes Operator, if the deployment uses a px-versions ConfigMap to manage available Portworx versions, the administrator must update the version manifest within this ConfigMap to include the new version. This update informs the Operator of the target version for upgrades and ensures that the correct container images are pulled and deployed. Simply creating a new namespace or deleting the ConfigMap is insufficient and can cause upgrade failures or inconsistent version deployments. The Portworx Operator upgrade documentation emphasizes updating the px-versions ConfigMap manifest as a necessary step in orchestrated upgrades, enabling controlled, predictable version management within Kubernetes clustersPure Storage Portworx Upgrade Guidesource.

by Iesha at Aug 12, 2025, 02:09 PM

Limited Time Offer

25%

Off

Get Premium Portworx-Enterprise-Professional Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Lettie

8 months ago

Just updating the manifest is the way to go!

upvoted 0 times

...

Shantell

8 months ago

Deleting the configmap sounds risky.

upvoted 0 times

...

Goldie

9 months ago

You need to update the version manifest.

upvoted 0 times

...

Freeman

9 months ago

Totally agree, that's the right step!

upvoted 0 times

...

Vernice

9 months ago

Wait, are you sure about that?

upvoted 0 times

...

Crissy

9 months ago

I’m leaning towards creating a new namespace, but that seems a bit off for an upgrade process.

upvoted 0 times

...

Tyra

9 months ago

This question feels familiar; I think we practiced a similar one where updating the configmap was necessary.

upvoted 0 times

...

Melda

10 months ago

I remember something about needing to delete the existing configmap before upgrading, but I can't recall the exact details.

upvoted 0 times

...

Ettie

10 months ago

I think we might need to update the version manifest, but I'm not entirely sure if that's the only step involved.

upvoted 0 times

...

Loren

10 months ago

The key here is that we're using the px-versions configmap during the Portworx upgrade. That means we'll need to update the version manifest, so I'm going with B. Deleting the configmap doesn't seem quite right to me.

upvoted 0 times

...

Sylvie

10 months ago

I'm a little confused on this one. Do we really need to delete the configmap? Wouldn't it be better to just create a new namespace for it? I'm leaning towards A, but I'm not 100% sure.

upvoted 0 times

...

Jaclyn

11 months ago

Okay, let's see. If we're upgrading Portworx using the Operator, and we're using the px-versions configmap, then we'll need to delete the existing one before updating. That makes sense to me. I'm going with C.

upvoted 0 times

...

Hyman

11 months ago

Hmm, I'm not totally sure about this one. I know we need to update the Portworx version, but I'm not familiar with the px-versions configmap. I'll have to think this through carefully.

upvoted 0 times

...

Kristofer

11 months ago

This one seems pretty straightforward. I think the answer is C - delete the existing configmap.

upvoted 0 times

...