REST vs SOAP vs GraphQL comparison in Rest API - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to identify the protocol that uses XML messages and strict standards.

Rest API

The protocol that uses XML messages and strict standards is [1].

Drag options to blanks, or click blank then click option'

ASOAP

BREST

CGraphQL

DHTTP

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing REST with SOAP because both use HTTP.

SOAP uses XML messages and follows strict standards for messaging.

2fill in blank

medium

Complete the code to identify the API style that uses flexible queries to get only needed data.

Rest API

The API style that allows clients to request exactly the data they need is [1].

Drag options to blanks, or click blank then click option'

AGraphQL

BREST

CRPC

DSOAP

Attempts:

3 left

💡 Hint

Common Mistakes

Thinking REST allows flexible queries like GraphQL.

GraphQL lets clients specify exactly what data they want in a query.

3fill in blank

hard

Fix the error in the statement about REST's data format.

Rest API

REST APIs commonly use [1] as the data format for requests and responses.

Drag options to blanks, or click blank then click option'

AYAML

BXML

CHTML

DJSON

Attempts:

3 left

💡 Hint

Common Mistakes

Assuming REST uses XML like SOAP.

REST APIs most commonly use JSON because it is lightweight and easy to use.

4fill in blank

hard

Fill all three blanks to complete the comparison of REST and SOAP.

Rest API

REST is [1] and uses [2] for data, while SOAP is [3] and uses XML.

Drag options to blanks, or click blank then click option'

Astateless

Bstateful

CJSON

DHTTP

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up stateless and stateful concepts.

REST is stateless and commonly uses JSON, SOAP is stateful and uses XML.

5fill in blank

hard

Fill all three blanks to complete the GraphQL query example.

Rest API

query { [1] { [2] [3] } }

Drag options to blanks, or click blank then click option'

Auser

Bname

Cemail

Dposts

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'posts' instead of user fields.

This GraphQL query asks for the user's name and email fields.

Practice

1. Which API style allows clients to request exactly the data they need in a single query?

easy

A. FTP

B. REST

C. SOAP

D. GraphQL

Solution

1. Step 1: Understand GraphQL's data fetching

   GraphQL lets clients specify exactly which fields they want in a query, reducing over-fetching.

2. Step 2: Compare with REST and SOAP

   REST uses fixed endpoints and HTTP methods, SOAP uses strict XML messages, neither allows flexible data selection like GraphQL.

3. Final Answer:

   GraphQL -> Option D

4. Quick Check:

   Exact data request = GraphQL [OK]

Hint: GraphQL = precise data queries in one request [OK]

Common Mistakes:

• Confusing REST with GraphQL's flexible queries
• Thinking SOAP supports flexible data selection
• Choosing unrelated protocols like FTP

2. Which of the following is the correct HTTP method typically used by REST APIs to update a resource?

easy

A. PUT

B. POST

C. GET

D. CONNECT

Solution

1. Step 1: Recall REST HTTP methods

   REST commonly uses PUT to update or replace a resource at a URL.

2. Step 2: Differentiate from other methods

   GET retrieves data, POST creates new resources, CONNECT is for network tunnels, so only PUT updates.

3. Final Answer:

   PUT -> Option A

4. Quick Check:

   Update resource = PUT [OK]

Hint: PUT method updates resources in REST [OK]

Common Mistakes:

• Using GET to update data
• Confusing POST with update instead of create
• Selecting non-REST HTTP methods like CONNECT

3. Given the following GraphQL query, what data will the client receive?

{ user(id: "123") { name email } }

medium

A. {"user": {"name": "Alice"}}

B. {"user": {"name": "Alice", "email": "[e-mail]"}}

C. {"user": {"id": "123", "name": "Alice"}}

D. {"user": {"email": "[e-mail]"}}

Solution

1. Step 1: Analyze the GraphQL query fields

   The query requests the user's name and email fields for user with id "123".

2. Step 2: Determine expected response

   The response includes both requested fields inside the user object, matching {"user": {"name": "Alice", "email": "[e-mail]"}}.

3. Final Answer:

   {"user": {"name": "Alice", "email": "[e-mail]"}} -> Option B

4. Quick Check:

   Requested fields = name and email [OK]

Hint: GraphQL returns only requested fields in response [OK]

Common Mistakes:

• Expecting all user fields returned
• Missing one of the requested fields
• Confusing id field presence

4. You have a SOAP API call that fails due to incorrect message format. What is the most likely cause?

medium

A. Using GraphQL query syntax in the request

B. Missing HTTP GET method in the request

C. Using JSON instead of XML in the request body

D. Not specifying the resource URL correctly

Solution

1. Step 1: Understand SOAP message format requirements

   SOAP requires XML formatted messages strictly following its schema.

2. Step 2: Identify common format errors

   Sending JSON instead of XML breaks the SOAP message format, causing failure.

3. Final Answer:

   Using JSON instead of XML in the request body -> Option C

4. Quick Check:

   SOAP needs XML, not JSON [OK]

Hint: SOAP messages must be XML formatted [OK]

Common Mistakes:

• Using JSON payloads with SOAP
• Confusing HTTP methods for SOAP
• Mixing GraphQL syntax with SOAP

5. You need to design an API for a mobile app that requires minimal data usage and flexible queries. Which API style is best and why?

hard

A. GraphQL, because it lets clients request exactly the data they need

B. REST, because it uses simple URLs and HTTP methods

C. SOAP, because it uses strict XML for secure communication

D. FTP, because it transfers files efficiently

Solution

1. Step 1: Identify requirements for minimal data and flexible queries

   The app needs to reduce data usage and allow clients to specify data fields.

2. Step 2: Match API styles to requirements

   GraphQL allows clients to request only needed data in one query, minimizing data transfer and providing flexibility.

3. Final Answer:

   GraphQL, because it lets clients request exactly the data they need -> Option A

4. Quick Check:

   Minimal data + flexible queries = GraphQL [OK]

Hint: Choose GraphQL for flexible, minimal data queries [OK]

Common Mistakes:

• Choosing REST without flexible data selection
• Selecting SOAP despite heavy XML overhead
• Confusing FTP with API styles