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

Nutanix Exam NCP-MCA Topic 1 Question 77 Discussion

Actual exam question for Nutanix's NCP-MCA exam
Question #: 77
Topic #: 1
[All NCP-MCA Questions]

A developer has created a variable type that should be used for all deployments. However, when an administrator is creating a blueprint, the variable is not available.

How can the developer resolve this issue?

Show Suggested Answer Hide Answer
Suggested Answer: B

To make a custom variable type available for all deployments, the developer should publish the variable type to the Marketplace. By publishing it to the Marketplace, the variable type becomes accessible to all administrators and users across different projects, ensuring consistency and reusability.


Nutanix Calm documentation on Publishing to Marketplace.

Nutanix Best Practices for Variable Management.

Contribute your Thoughts:

Yvonne
2 days ago
I'm just picturing the admin's face when they realize the variable type is missing. Option B - the dRodneyloper's secret weapon against admin frustration!
upvoted 0 times
...
Rodney
14 days ago
Ah, the age-old struggle between dRodneylopers and admins. Option B is clearly the most diplomatic choice. Plus, it'll save us all a headache down the line.
upvoted 0 times
Ramonita
2 days ago
A: Add the administrator to the Project Admin role.
upvoted 0 times
...
...
Janna
17 days ago
I think adding the administrator to the Developer role might also work to resolve the issue.
upvoted 0 times
...
Dalene
18 days ago
I believe publishing the variable type to Marketplace could also be a good option.
upvoted 0 times
...
Aretha
22 days ago
As a developer, I'm always looking for the most efficient solution. B is definitely the way to go here. No need to mess around with role assignments and all that jazz.
upvoted 0 times
Carlton
3 days ago
B) Publish the variable type to Marketplace.
upvoted 0 times
...
...
Deja
1 months ago
I agree with Emily, sharing the variable type with the Project seems like the best solution.
upvoted 0 times
...
Emily
1 months ago
I think the developer should share the variable type with the Project.
upvoted 0 times
...
Micaela
1 months ago
Sharing the variable type with the Project is a good solution, but B is just more elegant. Why not make it accessible to everyone from the get-go?
upvoted 0 times
Sharika
8 days ago
Sharing the variable type with the Project is a good solution, but B is just more elegant. Why not make it accessible to everyone from the get-go?
upvoted 0 times
...
Charlette
11 days ago
B) Publish the variable type to Marketplace.
upvoted 0 times
...
Taryn
14 days ago
A) Add the administrator to the Project Admin role.
upvoted 0 times
...
...
Kaycee
2 months ago
Hmm, I'm not sure adding the admin to the Developer role is the best idea. That might give them a bit too much power, don't you think? D looks like the safer bet.
upvoted 0 times
Vernell
22 days ago
Definitely, sharing the variable type with the Project seems like the best solution.
upvoted 0 times
...
Jin
23 days ago
Yeah, D seems like a safer option to share the variable type with the Project.
upvoted 0 times
...
Amina
24 days ago
I agree, giving the admin too much power could cause issues.
upvoted 0 times
...
...
German
2 months ago
Option B seems like the way to go. Publishing the variable type to Marketplace makes it available for all admins to use. Easy peasy!
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77