Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
Question 18 of 108
Free Preview · 108 of 359 · questions 1–108 of 359 are free. Sign up free to sync your progress across devices.
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
The correct answer is C. gRPC-based APIs because it uses Protocol Buffering (protobuf), a binary format that significantly reduces payload size and minimizes bandwidth costs compared to JSON or XML. Additionally, gRPC automatically generates strongly-typed client SDKs, making it integrate easily with mobile apps on both Android and iOS while natively supporting HTTPS (via HTTP/2).
Both A and C are suitable solution but since it reads minimise bandwidth cost, I'd go with C
For an API designed for mobile apps with the requirements you've outlined, a RESTful API architecture is the most suitable choice. Here's why: RESTful API Advantages: HTTPs Support: REST APIs are built on top of HTTP, making HTTPS integration seamless. Bandwidth Minimization: REST APIs are designed for efficient data transfer. They use standard HTTP methods (GET, POST, PUT, DELETE) for CRUD operations, minimizing the amount of data sent over the network. Easy Mobile Integration: REST APIs are widely understood and supported by mobile development frameworks (like Android's Retrofit and iOS's Alamofire). They use JSON as a standard data format, which is easily parsed by mobile apps.