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

Cisco 350-901 Exam - Topic 16 Question 87 Discussion

Posted by Sage on Nov 14, 2024 at 03:45 AM

Which transport layer protocol does gRPC use to retrieve telemetry information?

Suggested Answer: D

Get Premium 350-901 Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
40 comments · newest first
LE
Leonora 11 months ago
Really? I had no idea it wasn't just TCP!
LA
Larae 11 months ago
Nope, it's definitely HTTP/2.
LA
Lang 11 months ago
Wait, I thought it was TCP?
RI
Rima 11 months ago
Totally agree, it's all about that efficiency!
ME
Mee 12 months ago
gRPC uses HTTP/2 for transport.
MA
Markus 12 months ago
I definitely remember that gRPC is built on top of HTTP/2, so I’m leaning towards that as the answer.
SI
Sina 1 year ago
I’m a bit confused; I thought gRPC might use TCP, but I also recall something about HTTP/2 being important for its features.
LE
Levi 1 year ago
I remember practicing a question about gRPC and TCP, but I feel like HTTP/2 is the right answer here.
MA
Marguerita 1 year ago
I think gRPC uses HTTP/2 for its transport layer, but I’m not completely sure.
SY
Sylvie 1 year ago
I'm a bit confused here. I know gRPC is used for telemetry, but I'm not sure which transport layer protocol it uses. I'll have to guess and go with C, TCP, since that's a common transport protocol.
CO
Corrinne 1 year ago
Ah, I remember learning about this in class. gRPC is built on top of HTTP/2, which provides efficient and low-latency communication. So the answer is definitely D.
AL
Almeta 1 year ago
Hmm, I'm a bit unsure about this one. I know gRPC is a modern RPC framework, but I can't remember which transport protocol it uses. I'll have to think this through carefully.
DE
Delisa 1 year ago
I'm pretty sure gRPC uses HTTP/2 as the transport layer protocol, so I'll go with option D.
DA
Daren 2 years ago
That makes sense. HTTP/2 is known for its efficiency in handling multiple concurrent requests.
IS
Isadora 2 years ago
I think gRPC uses HTTP/2 because it is designed for low latency communication.
DA
Daren 2 years ago
D) HTTP/2
BR
Brinda 2 years ago
TCP? Really? That's so last year. I bet the correct answer is telepathy. Cutting-edge stuff, you know.
ED
Edna 2 years ago
↳ replying to Brinda
D) HTTP/2
TO
Torie 2 years ago
↳ replying to Brinda
C) TCP
NO
Noe 2 years ago
↳ replying to Brinda
B) SNMP
GE
Germaine 2 years ago
↳ replying to Brinda
A) SSH
EL
Elmer 2 years ago
D. HTTP/2, of course! Keeps it modern and efficient, just like my wardrobe choices.
KA
Kattie 2 years ago
↳ replying to Elmer
D. HTTP/2, of course! Keeps it modern and efficient, just like my wardrobe choices.
BE
Belen 2 years ago
↳ replying to Elmer
D) HTTP/2
SH
Sharee 2 years ago
↳ replying to Elmer
C) TCP
MI
Miriam 2 years ago
↳ replying to Elmer
B) SNMP
LO
Lonna 2 years ago
↳ replying to Elmer
A) SSH
LU
Ludivina 2 years ago
Hmm, gRPC huh? Guess they're going for the 'G' in 'Gotta Retrieve Protocols Correctly'.
ME
Meghann 2 years ago
↳ replying to Ludivina
Close, but gRPC actually uses HTTP/2 for telemetry information retrieval.
LA
Laurel 2 years ago
↳ replying to Ludivina
C) TCP
CH
Charisse 2 years ago
↳ replying to Ludivina
Actually, gRPC uses HTTP/2, not SNMP.
FR
Francoise 2 years ago
↳ replying to Ludivina
B) SNMP
CH
Christoper 2 years ago
↳ replying to Ludivina
Close, but gRPC specifically uses HTTP/2 for telemetry data.
KI
Kimbery 2 years ago
↳ replying to Ludivina
C) TCP
HA
Hannah 2 years ago
↳ replying to Ludivina
No, gRPC actually uses HTTP/2 for telemetry information.
GI
Gilma 2 years ago
↳ replying to Ludivina
That's correct. gRPC uses HTTP/2 to retrieve telemetry information.
AL
Alba 2 years ago
↳ replying to Ludivina
B) SNMP
TO
Tomas 2 years ago
↳ replying to Ludivina
That's correct! gRPC uses HTTP/2 to retrieve telemetry information.
MA
Matthew 2 years ago
↳ replying to Ludivina
D) HTTP/2
KA
Kattie 2 years ago
↳ replying to Ludivina
D) HTTP/2
0/2000 characters

Save Cancel