IT has implemented a new poet identification code, and they would like to be able to analyze cloud consumption based upon this code. What features would you use in Cloud Provisioning and Governance to implement this request? (Choose two.)
I'm a bit confused about the options. I feel like creating a Cloud Script could be useful, but I can't recall how it directly relates to the poet identification code.
I think adding a new Project Tag to the Tag Definitions could help track cloud consumption effectively, but I'm not entirely sure about the second option.
Hmm, I'm not sure about the "Add new parameter to the CAPI interface" option. Does that actually relate to the cloud provisioning and governance features they're asking about? I'm leaning towards A and B as the best choices here.
I feel pretty confident about this one. The two features I would choose are A) Add a new Project Tag to the Tag Definitions and B) Create a Resource Pool associated to the projects table. That should give IT the ability to track cloud consumption based on the new poet identification code.
I'm a little confused on the difference between creating a Cloud Script and manually creating a new variable. Are those both viable options, or is one of them not the best approach for this scenario?
Okay, let me think this through. Adding a new Project Tag to the Tag Definitions seems like a good option to associate the poet ID with the cloud resources. And creating a Resource Pool associated to the projects table could also help with the analysis.
Hmm, this looks like it's testing our understanding of cloud provisioning and governance features. I think the key is to identify the two features that would allow us to analyze cloud consumption based on the new poet identification code.
I'm with the majority on this one - A and C are the way to go. Though I have to wonder, did the poet identification code come from a poetry contest in the office? Maybe the winner gets a free month of cloud credits.
A and C all the way! Though I have to say, the poetry-loving IT team must be really into their craft. Hopefully, they're not writing haikus in the cloud provisioning scripts.
D and E are just weird choices. Why would you manually create a variable when you can use a tag? And the CAPI interface is for a different purpose. A and C are the winners here.
I'm not sure about creating a Resource Pool or adding a new parameter to the CAPI interface. Those feel a bit overkill for this requirement. I'd go with A and C.
A and C seem like the most logical choices here. Adding a new Project Tag to track the poet identification code, and creating a Cloud Script to automate the analysis of cloud consumption based on that tag.
A and C would definitely be the way to go. The Project Tag would help track the poet identification code, and the Cloud Script would automate the analysis.
Cordell
3 months agoVan
4 months agoTom
4 months agoZena
4 months agoLatosha
4 months agoBok
5 months agoCrissy
5 months agoSharika
5 months agoVan
5 months agoMarjory
5 months agoHoa
5 months agoEliz
5 months agoKristofer
5 months agoValentine
5 months agoEllsworth
10 months agoDonte
8 months agoAlecia
8 months agoMila
9 months agoCory
9 months agoRhea
9 months agoSherly
10 months agoRuby
9 months agoNorah
9 months agoGenevive
9 months agoJerry
9 months agoCassandra
9 months agoDawne
9 months agoAntonio
9 months agoYesenia
9 months agoTegan
9 months agoTwanna
11 months agoFelicitas
9 months agoSuzan
9 months agoLonna
9 months agoLelia
9 months agoAlisha
11 months agoBritt
11 months agoDonte
10 months agoEvangelina
10 months agoPeggie
11 months agoDelila
11 months agoNelida
11 months ago