MENU
You are building an API that will be used by Android and iOS apps The API must:
* Support HTTPs
* Minimize bandwidth cost
* Integrate easily with mobile apps
Which API architecture should you use?
Suggested Answer: A
Get Premium Professional Cloud Developer Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
31 comments · newest first
AL
Alease
10 months ago
I’m surprised MQTT is even an option here.
WI
Willard
10 months ago
SOAP? Really? That's so outdated.
JU
Jules
10 months ago
I think gRPC would be better for performance!
TA
Tandra
10 months ago
RESTful APIs are super common for mobile apps.
CA
Carma
11 months ago
REST is the way to go, no doubt about it!
FR
Fredric
11 months ago
MQTT could be a good option for minimizing bandwidth, but I don't know if it's as commonly used for APIs as RESTful ones.
MA
Magda
11 months ago
SOAP-based APIs seem outdated for mobile apps, right? I feel like they wouldn't integrate easily, but I can't recall the specifics.
HI
Hildred
11 months ago
I remember practicing with gRPC in class, and it seemed efficient for mobile apps, but I wonder if it really minimizes bandwidth costs compared to REST.
GA
Gary
12 months ago
I think RESTful APIs might be the best choice since they are widely used and easy to integrate with mobile apps, but I'm not entirely sure about the bandwidth aspect.
NO
Novella
12 months ago
I'm leaning towards gRPC-based APIs. The performance and bandwidth benefits could be really useful for this project.
SH
Shenika
12 months ago
RESTful APIs are the safest bet. They meet all the requirements and are a proven solution for mobile app integration.
TE
Tegan
1 year ago
SOAP-based APIs seem outdated for this use case. I'd go with either RESTful or gRPC-based APIs.
IS
Isadora
1 year ago
I'm not too sure about this one. MQTT or gRPC might be better options to minimize bandwidth and improve performance.
CH
Charisse
1 year ago
I think RESTful APIs would be the best choice here. They're widely used, well-supported, and integrate easily with mobile apps.
SH
Sherman
1 year ago
I prefer gRPC-based APIs because they are more efficient for mobile apps.
MO
Mona
1 year ago
But gRPC-based APIs can also minimize bandwidth cost and integrate easily with mobile apps.
VA
Valentin
1 year ago
SOAP-based APIs? Really? That's so 2000s. I'd go with gRPC or RESTful, no doubt about it.
BE
Belen
9 months ago
Both gRPC and RESTful have their perks!
LI
Lino
9 months ago
RESTful APIs are still solid for mobile apps.
BE
Bev
10 months ago
I agree! gRPC is way more efficient.
MA
Marcos
11 months ago
SOAP-based APIs? Really? That's so outdated.
SO
Sommer
1 year ago
I agree with Mary, RESTful APIs are widely used and support HTTPS.
GI
Gilberto
1 year ago
MQTT for APIs seems like an interesting option. It's great for minimizing bandwidth and could work well with the mobile apps.
AL
Aleta
1 year ago
A) RESTful APIs
MA
Mary
1 year ago
I think we should use RESTful APIs for this.
AN
Andra
1 year ago
I'm leaning towards RESTful APIs. They're widely supported, easy to use, and can handle HTTPS without much hassle.
CH
Chantell
1 year ago
A) RESTful APIs
LI
Lina
1 year ago
I think gRPC-based APIs would be the best choice here. It's lightweight, efficient, and integrates well with mobile apps.
GE
Geraldo
1 year ago
C) gRPC-based APIs
MA
Marnie
1 year ago
B) MQTT for APIs
CA
Carma
1 year ago
A) RESTful APIs