MENU
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?
Suggested Answer: A
Get Premium Salesforce Certified MuleSoft Platform Integration Architect (Mule-Arch-202) Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
42 comments · newest first
IS
Isadora
11 months ago
Wait, can tokenization really work without recoding? That sounds too good to be true!
LE
Leoma
11 months ago
D is definitely a solid option, but I wonder if it’s as secure as A.
AF
Afton
12 months ago
C seems interesting, but isn't encryption a bit heavy for this?
TH
Theodora
12 months ago
I think B is too limited. We need both masking and tokenization for security.
CO
Corrinne
1 year ago
Sounds like A is the right choice! Masking and tokenization together make sense.
FR
Francine
1 year ago
I lean towards option D since it focuses on tokenization, but I'm a bit confused about how detokenization works in this context.
ST
Staci
1 year ago
I feel like field-level encryption could also be a valid approach, but I can't recall if it fits the requirement of not recoding the API implementations.
AR
Arlette
1 year ago
I think option A sounds familiar because it mentions both masking and tokenization, which we practiced in a similar question.
LA
Lashaunda
1 year ago
I remember we discussed tokenization and masking in class, but I'm not sure if both are needed for this question.
SE
Selene
1 year ago
Okay, I think I've got this. The key is using a tokenization policy in the API gateway to replace the sensitive data with tokenized values. Then you can apply a detokenization policy to convert it back, without having to recode the APIs. Option D seems like the best fit.
EL
Elouise
1 year ago
I'm not totally sure about this one. The question is asking for an approach that can both hide the data and convert it back, which seems tricky. I'll need to read through the options carefully and try to visualize how each one would work in practice.
ME
Melda
1 year ago
Ah, this is right up my alley! I've worked with API gateways before, and the key here is using a tokenization policy to mask the sensitive data. Then you can apply a detokenization policy to convert it back. Option D looks like the way to go.
GL
Gladys
1 year ago
Hmm, I'm a bit confused by the different options here. Tokenization, masking, encryption - which one is the right approach? I'll need to make sure I understand the differences between these techniques before I can decide.
DO
Dortha
1 year ago
This looks like a tricky one, but I think I can handle it. I'll need to carefully read through the options and think about the key requirements - hiding sensitive data, but being able to convert it back without recoding the APIs.
MO
Mozell
1 year ago
Okay, let's see. The key details here are the hand-drawn, incomplete screens that change when someone interacts with them. I think the term I'm looking for is a low-fidelity prototype.
RO
Roosevelt
1 year ago
I remember learning about this in class. I believe the correct answer is B, clinical cost centers. Those are the ones responsible for delivering direct patient care.
SH
Shad
1 year ago
Hmm, I'm not totally sure about this one. I know DNS has something to do with IP addresses, but I can't quite remember the specifics. I'll have to think this through carefully.
SE
Selma
1 year ago
I think maintaining custody of the electronic record with the business originator could be a good way to protect it. Not entirely sure though.
EL
Elly
1 year ago
I'm not entirely sure, but I think Sectoral makes the most sense since the question mentions the health market specifically. I'll go with that for now.
JE
Jennifer
2 years ago
I'm going with option D. Tokenization just makes sense for this use case. Plus, it's a lot easier than trying to implement a full encryption solution.
LI
Lino
2 years ago
Haha, I bet the API developers are hoping the answer is not C. Field-level encryption? That's way too much work!
KA
Kanisha
2 years ago
D) 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
CA
Caren
2 years ago
B) 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
MO
Moira
2 years ago
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
EM
Emmanuel
2 years ago
Option D is definitely the best choice here. Tokenization is a smart approach that allows you to mask sensitive information without having to modify the API implementations.
FA
Fabiola
2 years ago
Tokenization does sound like a secure method to protect sensitive information.
NO
Noah
2 years ago
I agree, option D seems like the most efficient way to handle sensitive data.
HI
Hildegarde
2 years ago
Tokenization does sound like a secure method to protect sensitive information.
TH
Theodora
2 years ago
Tokenization is definitely the way to go for securing sensitive information.
JE
Jesus
2 years ago
I agree, option D seems like the most efficient way to handle sensitive data.
JO
Jovita
2 years ago
I agree, option D is the most efficient way to hide sensitive data.
JE
Jeffrey
2 years ago
I agree, option D is the correct answer. Tokenization is a simple yet effective way to protect sensitive data while maintaining the overall functionality of the API.
GW
Gwen
2 years ago
Option D seems like the way to go. Tokenization is a great way to keep sensitive data secure without having to recode the API implementations.
UN
Una
2 years ago
C) 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
AS
Ashlyn
2 years ago
Masking sensitive values with tokenization policy seems like a secure way to handle sensitive data exchange.
FE
Fernanda
2 years ago
B) 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
AL
Alberta
2 years ago
That sounds like a good approach. Using both masking and tokenization can provide an extra layer of security for sensitive data exchange.
MA
Mabelle
2 years ago
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
GI
Gilberto
2 years ago
Option D seems like the way to go. Tokenization is a great way to keep sensitive data secure without having to recode the API implementations.
NA
Nathalie
2 years ago
I agree, using tokenization for sensitive data is a smart approach to maintain security.
CR
Cristina
2 years ago
Option D seems like the way to go. Tokenization is a great way to keep sensitive data secure without having to recode the API implementations.
KI
Kimbery
2 years ago
D) 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