How is the encrypted portion of a secure property represented in YAML-style syntax?

Prepare for the MuleSoft Developer 2 Certification Exam. Access practice quizzes featuring flashcards and multiple choice questions with explanations. Get confident and ready for your certification success!

Multiple Choice

How is the encrypted portion of a secure property represented in YAML-style syntax?

Explanation:
The idea being tested is signaling encrypted data in YAML by using a tag. In YAML, you can mark a value with a type tag that starts with an exclamation mark, indicating this scalar should be treated as a special type — in this case, encrypted data. Representing the password as a tagged scalar, like password: ![encrypted string], communicates to the parser or runtime that this value is not just plain text but an encrypted value that should be handled accordingly (e.g., decrypted when used). The other options fail because they either treat the value as a plain string (with quotes or not) or store a literal placeholder like [encrypted], which provides no indication to tooling that the data is encrypted.

The idea being tested is signaling encrypted data in YAML by using a tag. In YAML, you can mark a value with a type tag that starts with an exclamation mark, indicating this scalar should be treated as a special type — in this case, encrypted data. Representing the password as a tagged scalar, like password: ![encrypted string], communicates to the parser or runtime that this value is not just plain text but an encrypted value that should be handled accordingly (e.g., decrypted when used).

The other options fail because they either treat the value as a plain string (with quotes or not) or store a literal placeholder like [encrypted], which provides no indication to tooling that the data is encrypted.

Subscribe

Get the latest from Passetra

You can unsubscribe at any time. Read our privacy policy