Back to Amazon CloudSearch

Language Support

5 minutes 5 Questions

Amazon CloudSearch provides support for multiple languages through its powerful text processing features. Built-in language-specific text analyzers allow the service to accurately interpret and index content in several languages, including English, French, German, Italian, Portuguese, and Spanish. …

Test mode:
Start practice test
AWS Certified Solutions Architect - Language Support Example Questions

Test your knowledge of Language Support

Question 1

A team needs to create an application with different language combinations supported by the Amazon Lex bot. What language combination is NOT supported by Amazon Lex?

Correct Answer: Japanese and Russian

As of now, Amazon Lex does not support Japanese and Russian language combinations. Other mentioned combinations like English with Spanish, Chinese, French, Italian, or Korean are supported by Lex.

Question 2

An e-commerce company uses AWS Lambda for its backend and needs to add multilingual (i18n) processing for international customers. The team is restricted to choosing from the following runtimes: Node.js, Python, or Java. Which Lambda runtime(s) can implement locale-aware processing using available libraries?

Correct Answer: Node.js, Python, or Java

All three listed AWS Lambda runtimes—Node.js, Python, and Java—support robust internationalization (i18n) and localization libraries and tooling. For example, Node.js can use libraries like i18next or Globalize, Python can use Babel and gettext, and Java can use ICU4J and ResourceBundle. Lambda imposes no restriction on performing locale-aware processing in these runtimes, so any of the three can implement multilingual support effectively.

Question 3

An organization is migrating a Node.js service to AWS Lambda. The service relies on a native C++ addon (.node and shared libraries) that must be compiled for the Lambda execution environment (Amazon Linux 2). Several Lambda functions will use this addon, and the team wants a reusable, versioned package of the native binaries without bundling them into each function’s deployment package. What is the best approach for this migration?

Correct Answer: Create an AWS Lambda layer that contains the precompiled Node.js native addon (.node) and any required C/C++ shared libraries compiled for the Lambda execution environment (Amazon Linux 2), and attach the layer to the functions.

Packaging the native C/C++ binaries and the Node.js native addon into an AWS Lambda layer provides a reusable, versioned artifact that can be attached to multiple functions. The binaries must be compiled for the Lambda execution environment (Amazon Linux 2) to ensure compatibility. This approach keeps function deployment packages smaller, centralizes updates to the native dependency, and avoids duplicating the same large binaries across many functions. Directly uploading the application with the native library can work, but it duplicates binaries in every function and complicates versioning and reuse. Uploading to Amazon S3 alone does not make the code executable in Lambda. Elastic Beanstalk is a different compute service and does not meet the requirement to run the workload on AWS Lambda.

More Language Support questions
17 questions (total)
Start 17 question test