DRAG DROP You need to configure the Subcontract Docs extension to translate the fields. Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order. 
Yeah, makes sense to start by enabling the translation feature first (E), then build to get the Translations folder (F), and finally translate the .xlf file (G). That's the usual sequence for multi-language support in AL extensions. Pretty sure that's how it works in real projects but open to correction.
Had something like this in a mock, and the correct sequence went: add TranslationFile to app.json, build with AL: Package, then translate the .xlf file. That aligns with standard AL multilanguage setup. Pretty sure that's right but happy for corrections if someone spots an edge case.