An enterprise customer support organization wants to modernize its multi-platform case routing system. The product owner defines the following business requirement and user story: "When a customer creates a high-priority support case in Salesforce, the platform must immediately detect the event, retrieve the full case record, translate non-English customer comments into English, standardize the payload into our canonical JSON format, and route the record to an internal issue-tracking service." You need to translate this business requirement into functional data flows and service integrations using Google Cloud services. Which integration architecture should you implement?

Create an Application Integration flow with a Salesforce Change Data Capture (CDC) trigger, a Connectors task to fetch the Case entity, a Translate - Text task for localization, and a Data Mapping task to transform variables for the destination endpoint.: ### What Google Cloud Application Integration Is **Application Integration** is an Integration Platform as a Service (iPaaS) solution in Google Cloud designed to visually orchestrate, automate, and connect enterprise SaaS applications, Google Cloud services, and custom internal APIs without requiring custom middleware code. ### How it meets the Functional Requirements To translate the business user story into specific functional components and data flows: - **Event Detection (Real-Time)**: The **Salesforce trigger** configured with **Change Data Capture (CDC)** on the `Case` object instantly captures case creation events as they occur in Salesforce. - **Entity Retrieval**: The integration maps the generated CDC record ID to a **Connectors task** targeting the Salesforce connection with an **Entities: Get** operation to pull the complete case payload. - **Language Translation**: A **Translate - Text task** receives the raw customer comment strings in its request parameters and outputs translated text, directly fulfilling the business localization requirement. - **Data Standardization**: A **Data Mapping task** applies transform functions and expressions to map input attributes and translated text into the required canonical target schema before passing the payload along conditional edges to the downstream ticketing service. ### Key Advantages and Capabilities - **No-Code/Low-Code Orchestration**: Connects disparate SaaS environments using pre-built triggers, tasks, and visual mapping canvases. - **Built-In Transformations**: Employs **Data Mapping** and **Data Transformer** tasks to standardize varied schemas and variable data types easily. - **Native Enterprise Connectors**: Manages authentication, connection pooling, and credential lifecycle securely across multi-cloud and SaaS platforms. - **Real-Time Responsiveness**: Event-driven architecture ensures zero-delay processing compared to scheduled batch polling. ### Why This Is Optimal This architecture directly maps each step of the business user story to purpose-built, managed cloud integration components. It eliminates the operational overhead of running custom server infrastructure while providing built-in error handling, schema mapping, and managed security.

StudyCerts

Translate Business Case Routing Functional Requirements | Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam! | StudyCerts

Professional Cloud Architect

Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam!

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Translate Business Case Routing Functional Requirements

Section: Identifying functional and non-functional requirements

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

An enterprise customer support organization wants to modernize its multi-platform case routing system. The product owner defines the following business requirement and user story:

"When a customer creates a high-priority support case in Salesforce, the platform must immediately detect the event, retrieve the full case record, translate non-English customer comments into English, standardize the payload into our canonical JSON format, and route the record to an internal issue-tracking service."

You need to translate this business requirement into functional data flows and service integrations using Google Cloud services.

Which integration architecture should you implement?

Implement an offloaded BigQuery data warehouse migration pipeline that syncs Salesforce records once daily, utilizes facade views for schema translation, and triggers Dataflow to load transformed rows into the ticketing platform.

Deploy a Cloud Dataflow streaming pipeline that reads Salesforce webhooks, uses a static singleton Map side-input to query the Cloud Translation API for each record, and executes GroupByKey transforms for external routing.

Create an Application Integration flow with a Salesforce Change Data Capture (CDC) trigger, a Connectors task to fetch the Case entity, a Translate - Text task for localization, and a Data Mapping task to transform variables for the destination endpoint.

Configure a Cloud Scheduler cron job to poll Salesforce via REST API every hour, write the payloads to Cloud Storage, and execute a Data Transformer Jsonnet task to translate text before schema validation.

Professional Cloud Architect

Translate Business Case Routing Functional Requirements

Related questions