I'm going to go with option B. Registering the service sounds like the key step to make it available to Python-based consumer apps. Plus, who doesn't love a good 'register' endpoint?
Hmm, I'm a bit puzzled. Why would I need to configure the service using the /pxgrid/ise/config/profiler endpoint? That doesn't seem directly related to exposing functionality to consumer applications.
I'm leaning towards option D since it mentions the /pxgrid/ise/pubsub endpoint, which sounds like the right place to expose the service. But I'll double-check the documentation to be sure.
Answer B seems straightforward, but I want to make sure I understand the context. Does this have to do with exposing a Python-based application on the Cisco pxGrid platform?
Tonette
27 days agoDaniel
28 days agoDeane
3 days agoIola
10 days agoLaurel
13 days agoStephaine
16 days agoSimona
1 months agoMitzie
3 days agoAmina
14 days agoMarylou
19 days agoViola
2 months agoDetra
9 days agoKeva
13 days agoBlair
16 days agoJanessa
2 months agoTonette
2 months agoGlenna
1 months agoVivan
2 months agoAdell
2 months agoVerda
2 months ago