API Gateways and Reverse Proxies PDF

Add the following multiple choice questions and answers and explanations verbatim (DO NOT change the given wording). ========================================== New Question 1: "Which of the following best describes API orchestration in the context of an API Gateway?" Choice A: "Managing the load ac...

Add the following multiple choice questions and answers and explanations verbatim (DO NOT change the given wording). ========================================== New Question 1: "Which of the following best describes API orchestration in the context of an API Gateway?" Choice A: "Managing the load across multiple servers" Choice B: "Combining multiple API calls into a single response" Choice C: "Encrypting data before sending to backend services" Choice D: "Caching API responses to improve performance" Correct answer: B Explanation: "Combining multiple API calls into a single response API orchestration involves coordinating multiple API calls and aggregating their results into a single response, which is a functionality typically handled by an API Gateway." ========================================== New Question 2: "What is a potential trade-off when implementing an API Gateway in a microservices architecture?" Choice A: "Increased security due to hiding backend servers" Choice B: "Simplified client interactions through a single entry point" Choice C: "Potential performance overhead due to centralized processing" Choice D: "Enhanced caching capabilities to improve response times" Correct answer: C Explanation: "Potential performance overhead due to centralized processing Implementing an API Gateway introduces a centralized point where all requests are processed, which can lead to performance overhead if not properly managed." ========================================== New Question 3: "In a microservices architecture, why might an organization choose to use both an API Gateway and a Reverse Proxy?" Choice A: "To manage both application-specific routing and general traffic management" Choice B: "To duplicate functionalities for redundancy" Choice C: "To handle client authentication twice for increased security" Choice D: "To simplify the architecture by using multiple entry points" Correct answer: A Explanation: "To manage both application-specific routing and general traffic management Using both an API Gateway and a Reverse Proxy allows an organization to handle application-specific routing (via the API Gateway) while also managing general traffic and security concerns (via the Reverse Proxy)." ========================================== New Question 4: "How does the complexity of an API Gateway compare to that of a Reverse Proxy?" Choice A: "API Gateways are generally simpler than Reverse Proxies" Choice B: "API Gateways and Reverse Proxies have similar levels of complexity" Choice C: "API Gateways are generally more complex due to additional features like request transformation and orchestration" Choice D: "Reverse Proxies offer more features, making them more complex than API Gateways" Correct answer: C Explanation: "API Gateways are generally more complex due to additional features like request transformation and orchestration API Gateways provide more sophisticated functionalities tailored for managing microservices, making them more complex compared to Reverse Proxies which focus on network-level tasks." ========================================== New Question 5: "What architectural consideration should be taken into account when deploying an API Gateway to ensure high availability?" Choice A: "Deploying multiple instances of the API Gateway to avoid a single point of failure" Choice B: "Using a single, powerful server to handle all API Gateway tasks" Choice C: "Avoiding the use of caching mechanisms within the API Gateway" Choice D: "Implementing SSL termination only at the API Gateway" Correct answer: A Explanation: "Deploying multiple instances of the API Gateway to avoid a single point of failure To ensure high availability, multiple instances of the API Gateway should be deployed so that if one instance fails, others can continue to handle requests, thus avoiding a single point of failure." ========================================== New Question 6: "At which network layer do API Gateways primarily operate compared to Reverse Proxies?" Choice A: "API Gateways operate at the application layer, while Reverse Proxies operate at the network layer" Choice B: "API Gateways operate at the physical layer, while Reverse Proxies operate at the transport layer" Choice C: "Both API Gateways and Reverse Proxies operate exclusively at the application layer" Choice D: "API Gateways operate at the data link layer, while Reverse Proxies operate at the application layer" Correct answer: A Explanation: "API Gateways operate at the application layer, while Reverse Proxies operate at the network layer API Gateways manage application-specific traffic and protocols at the application layer, whereas Reverse Proxies handle network-level concerns." ==========================================