Câu 14: Salesforce Certified MuleSoft Integration Architect I

A leading eCommerce giant will use MuleSoft APIs on Runtime Fabric (RTF) to process customer orders. Some customer-sensitive information, such as credit card information, is required in request payloads or is included in response payloads in some of the APIs. Other API requests and responses are not authorized to access some of this customer-sensitive information but have been implemented to validate and transform based on the structure and format of this customer-sensitive information (such as accounts IDs, phone numbers, and postal codes). What approach configures an API gateway to hide sensitive data exchanged between API consumers and API implementations, but can convert tokenized fields back to their original value for other API requests or responses, without having to recode the API implementations?

1. A. Create both masking and tokenization formats and use both to apply a tokenization policy in an API gateway to mask sensitive values in message payloads with **** characters, and apply a corresponding detokenization policy to return the original values to other APIs.
2. B. Use a field-level encryption policy in an API gateway to replace sensitive fields in message payload with encrypted values, and apply a corresponding field-level decryption policy to return the original values to other APIs.
3. C. Create a tokenization format and use it to apply a tokenization policy in an API gateway to replace sensitive fields in message payload with similarly formatted tokenized values, and apply a corresponding detokenization policy to return the original values to other APIs — đáp án hiện tại
4. D. Create a masking format and use it to apply a tokenization policy in an API gateway to mask sensitive values in message payloads with **** characters, and apply a corresponding detokenization policy to return the original values to other APIs.