Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Cisco Exam 300-535 Topic 9 Question 40 Discussion

Actual exam question for Cisco's 300-535 exam
Question #: 40
Topic #: 9
[All 300-535 Questions]

An engineer must change from using NETCONF for streaming telemetry to telemetry data using gRPC framework because NETCONF uses XML for message and payload encoding. Which two messages and payload encodings does gNMI use? (Choose two.)

Show Suggested Answer Hide Answer
Suggested Answer: A, C

Contribute your Thoughts:

Melda
1 months ago
Wait, they're not using carrier pigeons for telemetry data? Clearly, this engineer needs to brush up on their ancient communication methods.
upvoted 0 times
Moon
17 days ago
gNMI uses protobuf payload and JSON payload for message and payload encoding.
upvoted 0 times
...
Helaine
22 days ago
Carrier pigeons would definitely be a unique choice for telemetry data!
upvoted 0 times
...
...
Miesha
1 months ago
C and D, my friend. Protobuf and JSON are the way to go. Unless, of course, the engineer is secretly a fan of ancient hieroglyphics, in which case, I'd recommend a career change.
upvoted 0 times
Beula
5 days ago
C and D are definitely the way to go. Protobuf and JSON make life so much easier.
upvoted 0 times
...
Truman
18 days ago
Agreed, gNMI with JSON is definitely the way to go for streaming telemetry.
upvoted 0 times
...
Candida
19 days ago
E) gNMI notifications with JSON
upvoted 0 times
...
Frederica
22 days ago
Absolutely, protobuf and JSON are much more efficient than XML.
upvoted 0 times
...
Roselle
23 days ago
D) JSON payload
upvoted 0 times
...
Sheridan
1 months ago
C) protobuf payload
upvoted 0 times
...
...
Latanya
2 months ago
Ah, the age-old debate of NETCONF vs. gRPC. Personally, I prefer the elegance of protobuf and the flexibility of JSON. Who needs XML when you can have the best of both worlds?
upvoted 0 times
Renato
13 days ago
Yes, gNMI notifications with JSON provide a more streamlined approach to telemetry data.
upvoted 0 times
...
Ezekiel
16 days ago
I think gNMI uses protobuf payload and gNMI notifications with JSON.
upvoted 0 times
...
Craig
1 months ago
I agree, protobuf and JSON are much more efficient than XML.
upvoted 0 times
...
...
Luis
2 months ago
I'm pretty sure gNMI uses protobuf and JSON, not XML. That would just be redundant and inefficient. Unless the engineer is stuck in the 90s, in which case, my condolences.
upvoted 0 times
...
Carissa
2 months ago
Protobuf and JSON payload are the two correct encodings for gNMI, not XML. NETCONF is definitely old school, but at least it's better than using a stone tablet and chisel.
upvoted 0 times
Felicia
20 hours ago
I think gNMI uses protobuf and JSON payload encodings.
upvoted 0 times
...
Shayne
2 days ago
I agree, NETCONF is definitely outdated.
upvoted 0 times
...
Truman
3 days ago
It's good to know that gNMI is more modern than NETCONF.
upvoted 0 times
...
Caprice
6 days ago
Yes, gNMI does use protobuf and JSON for message and payload encoding.
upvoted 0 times
...
Edda
27 days ago
I think gNMI uses protobuf and JSON payload encodings.
upvoted 0 times
...
Olga
2 months ago
Yeah, XML feels like a relic from the past compared to protobuf and JSON.
upvoted 0 times
...
Gracia
2 months ago
I agree, NETCONF is definitely outdated.
upvoted 0 times
...
James
2 months ago
I agree, protobuf and JSON are much more efficient than XML.
upvoted 0 times
...
...
Yun
2 months ago
I'm not sure about gNMI, but I think protobuf payload and JSON payload make sense for streaming telemetry.
upvoted 0 times
...
Hester
3 months ago
I agree with Craig. gNMI uses protobuf payload and JSON payload for message and payload encoding.
upvoted 0 times
...
Craig
3 months ago
I think gNMI uses protobuf payload and JSON payload.
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