Building Custom NLP Models with AutoML Natural Language

PMLE By islever Editorial Last updated

Building AI solutions using Google Cloud AI APIs or foundational models.

Short answer

B Use AutoML Natural Language to extract custom entities for classification.

Question

You work for a large technology company that wants to modernize their contact center. You have been asked to develop a solution to classify incoming calls by
product so that requests can be more quickly routed to the correct support team. You have already transcribed the calls using the Speech-to-Text API. You want
to minimize data preprocessing and development time. How should you build the model?
  1. Use the AI Platform Training built-in algorithms to create a custom model.
  2. Use AutoMlL Natural Language to extract custom entities for classification. Correct Answer
  3. Use the Cloud Natural Language API to extract custom entities for classification.
  4. Build a custom model to identify the product keywords from the transcribed calls, and then run the keywords through a classification algorithm.

Key Takeaways

The question tests the distinction between pre-trained APIs (which lack custom capability) and AutoML services (which offer customization with low-code efficiency). The trap is assuming standard NLP APIs can handle domain-specific categories.

To classify call transcripts by specific products with minimal effort, use AutoML Natural Language. This service enables custom entity extraction and classification without the heavy preprocessing required by custom training pipelines.

Common mistake: Candidates often choose Option C because it seems simpler. However, the Cloud Natural Language API cannot extract 'custom' entities; it only recognizes standard types like people or places. Choosing C ignores the requirement to identify specific company products.

Expert Analysis

The scenario requires classifying incoming calls by product to route them correctly. The key constraints are minimizing data preprocessing and development time, with transcription already completed.

Option C suggests using the Cloud Natural Language API to extract custom entities. This is technically incorrect because the Cloud Natural Language API provides pre-trained entity types (such as Person, Organization, Location) but does not support training or extracting 'custom' entities specific to a company's product catalog. As noted in community discussions, this option contains a factual error regarding the API's capabilities.

Option A involves AI Platform Training built-in algorithms, which typically require significant manual feature engineering, code implementation, and hyperparameter tuning, violating the constraint to minimize development time.

Option D proposes building a custom model for keywords and then running a classification algorithm. This approach is overly complex and contradicts the goal of speed and simplicity compared to managed services.

Option B, AutoML Natural Language, is the correct choice. It allows users to train custom text classification models (or extract custom entities) using labeled data with minimal coding and preprocessing. Since the transcripts exist, they can be easily uploaded as labeled examples. AutoML handles the underlying infrastructure and model selection, significantly reducing development time while providing the necessary customization to identify specific products that generic APIs miss.

Official Reference

https://cloud.google.com/natural-language/docs/automl

This link opens the official vendor documentation in a new tab.

Exam Strategy

When questions mention 'minimize development time' and 'custom' requirements, prioritize AutoML services over both raw API usage and custom training scripts. Check options carefully for technical inaccuracies, such as claiming an API supports features it explicitly excludes (like custom entities in standard NLP APIs).

Frequently Asked Questions

Can the Cloud Natural Language API extract custom entities?

No, the Cloud Natural Language API extracts only pre-defined entity types like persons, organizations, and locations. It cannot be trained on custom labels.

Why is AutoML better than custom training for this scenario?

AutoML requires less code and no manual feature engineering. It automates model selection and training, fitting the 'minimize development time' constraint better than custom scripting.

More PMLE FAQ →

Community Votes

B
67%
C
33%

67% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 30 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 30

  1. chohan 👍 25
    Should be B -> minimize data preprocessing and development time
  2. giaZ 👍 11
    If anything, C is wrong because it tells you something that is not true: extract custom entities with Natural Language API it's not possible. That is something you can do only with AutoML. Look at this comparison table: https://cloud.google.com/natural-language#section-6 That's how they subtly point you at answer B.
  3. sensev 👍 7
    Agree its B. A and D is incorrect since it requires more development time. C is also incorrect since the product is company specific and might not be well recognized by Cloud Natural Language API.
  4. baimus 👍 6
    I'm leaning towards C over B here. The question is underlining that minimal development time is required, and C is even less than B. If the information is really domain specific, then you'd need B, but it's not clear what products the company sells, so we don't have enough info to say it's too domain specific for C.
  5. mmona19 👍 4
    B- automl custom classification and entity is going to help with minimum effort.
Show 25 more comments
  1. ggorzki 👍 4 Answered B
    AutoML Natural Language - custom entities, with least development time
  2. pico 👍 3 Answered C
    Key Differences: Approach: Option B (AutoML Natural Language) involves using an AutoML service to train a custom NLP model, while Option C (Cloud Natural Language API) relies on a pre-built NLP API. Control and Customization: Option B gives you more control and customization over the training process, as you train a model specific to your needs. Option C offers less control but is quicker to set up since it uses a pre-built API. Complexity: Option B might require more technical expertise to set up and configure the AutoML model, while Option C is more straightforward and user-friendly. In summary, both options allow you to extract custom entities for classification, but Option B (AutoML) involves more manual involvement in training a custom model, while Option C (Cloud Natural Language API) provides a simpler, pre-built solution
  3. billyst41 👍 3 Answered B
    From Gemini: Can you extract custom entities from the cloud natural language API? No, you cannot train the Cloud Natural Language API to extract custom entities. The Natural Language API is a pre-trained model that can only extract a fixed set of entity types, such as people, organizations, and locations
  4. 21c17b3 👍 3
    I'm voting C here!
  5. pico 👍 2
    you can still use Option C (Cloud Natural Language API) even when the solution needs to classify incoming calls by company-specific products rather than general products. The Cloud Natural Language API can be customized to handle company-specific entities and classifications effectively.
  6. NamitSehgal 👍 2
    Should be B Basic classification, entity extraction, and sentiment analysis are available through the Cloud Natural Language API. AutoML Natural Language enables you to define custom classification categories, entities, and sentiment scores that are relevant to your application.
  7. theseawillclaim 👍 2 Answered C
    I think it's C. Natural Language API supports entity extraction, is pre-trained and comes off as a SaaS that you just pay per use. Considering you have already used STT on your data, I see no reason to use AutoML in this case.
  8. neohanju 👍 2
    I thought the answer is B too. However, after carefully reading the question and answers again, B produces entities for classification only, not a classification result. So, A and D are only candidates and A is better.
  9. Mohamed_Mossad 👍 2 Answered B
    "minimize data preprocessing and development time" answer will be limited to B,C will choose C as Natural Language API does not handle custom operation
  10. e407344 👍 2 Answered C
    "AutoML Natural Language" is the old name of the service. Now everything is unified under Vertex AI → AutoML training
  11. ralf_cc 👍 2
    AutoML only has classification and regression
  12. misya 👍 2 Answered C
    Cloud NLP API no require custom training
  13. PhilipKoku 👍 2 Answered C
    C) Cloud NLP API
  14. M25 👍 2 Answered B
    Went with B
  15. mayankblitzster 👍 1 Answered B
    A. Use AI Platform Training built-in algorithms Requires more manual setup, preprocessing, and model tuning—not ideal for minimizing development time. C. Use Cloud Natural Language API to extract custom entities The Cloud Natural Language API is for pre-trained entity types (e.g., locations, organizations), not custom classification. D. Build a custom model to identify product keywords and classify This is a manual and time-consuming approach, contrary to the goal of minimizing development time.
  16. taylz876 👍 1 Answered B
    B - Sorting calls by your company's own products is a custom task, since your product names and categories aren't something a generic model knows. AutoML Natural Language lets you train a custom text model on your labeled transcripts, with no code and almost no preprocessing. Since you've already transcribed the calls, you can use that text directly, which meets "minimize data preprocessing and development time." Today this lives in Agent Platform as AutoML text (formerly Vertex AI).
  17. gvk1 👍 1 Answered C
    This is direct question from this doc: https://medium.com/@pysquad/ai-infused-empowerment-harnessing-business-potential-with-google-clouds-nlp-api-in-python-b4fcb9fea1a3. "Automated Ticket Classification: Categorize and prioritize support tickets for efficient handling."
  18. YushiSato 👍 1
    It seems to me that if there is a product name that needs to be learned in AutoML Natural Language, there is a possibility that it cannot be transcribed into text by the Speech-to-Text API in the first place.
  19. b7ad1d9 👍 1 Answered B
    These are custom product names that need to be extracted from the text. AutoML is the right option. Cloud NL API is for understanding general purpose of text like sentiment etc. It doesn't qute fit here
  20. John_Pongthorn 👍 1 Answered B
    AutoML is appropriate to classify incoming calls by product (Custom) to be routed to the correct support team. Cloud Natural Language API is for general case (not particular business)
  21. julliet 👍 1
    you have to classify company products, which are custom classes
  22. 8c200dd 👍 1 Answered B
    C is for sentiment analysis, and it's more generic.
  23. David_ml 👍 1
    no. if you need custom entities you don't use APIs
  24. PKookNN 👍 1 Answered B
    focus on minimize dev time so AutoML
  25. lucaluca1982 👍 1 Answered C
    why not C?

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

How to Minimize Development Time for Weekly TensorFlow Retraining in Vertex AI?

S-grade

How to Handle Categorical Features in BigQuery ML for Fast Deployment?

S-grade

How to preprocess BigQuery data for TensorFlow?

S-grade

How to Track Model and Prediction Lineage in Vertex AI?

S-grade

Practice All PMLE Questions

Access 65 questions with complete answers and detailed explanations.

View Full PMLE Practice Test →

← Back to PMLE Study Guide