Do property files containing encrypted properties have to have their filename end with '-secure.yaml' or '-secure.properties'?

• A. It is best practice, but not required.
• B. Yes; they must end with "-secure.yaml" or "-secure.properties".
• C. They must end with "-secure.yaml" only.
• D. They must end with "-secure.properties" only.

Answer: (A)

In MuleSoft, the secure properties feature uses a separate file to hold encrypted values, and using a filename that ends with -secure.yaml or -secure.properties is a strong convention to signal that the file contains encrypted data. This convention helps you and the tooling recognize and handle sensitive values properly, and many templates rely on it for automatic loading and organization.

But the runtime does not strictly require the filename to have the -secure suffix. You can configure the application to load encrypted properties from a different file or location as long as the system knows how to decrypt and inject those values. So the -secure naming is best practice for clarity and compatibility, not a hard requirement.