Q: 8
You are customizing Business Central by using Visual Studio Code. You create a project that will
extend Business Central. The AL extension contains JSON files, which are automatically generated
and are used to store configuration data
For testing purposes, you plan to add the following changes to the files:
• Specify that page 21 must be opened after publishing.
• Enable debugging
• Disable the capability to download the source code
You need to add the configurations to the JSON files.
Which two configurations should you add? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point.
Options
Discussion
C and E imo. The
startupObjectId and resourceExposurePolicy settings controlling debugging/source download are meant to be in app.json, not launch.json. Launch.json is more for session-specific stuff, so these config changes have a lasting effect in app.json. Pretty sure that's what MS docs say too, but open to other views.Always get confused by where these resourceExposurePolicy configs go. Pretty sure C and E this time.
Maybe B and C. Launch.json is usually where you set up startup object and enable debugging when testing in VS Code, so I thought you'd configure those there. The resourceExposurePolicy can appear in both, so that's why I'm not 100% sure. Official docs or some hands-on lab would help clarify this one for me. Disagree?
B , because launch.json also handles debugging and object to start, but maybe I'm missing something with where resourceExposurePolicy is used.
Nah, not B. The resource exposure policy with allowDebugging and allowDownloadingSource set goes in app.json, so C and E.
Its B and D
I don't think it's B. C and E are correct since only app.json controls both startupObjectId and resourceExposurePolicy in a deployed extension. Launch.json is just for debugging configs, easy trap.
C/E. Only app.json controls startupObjectId and resourceExposurePolicy for live extensions, not launch.json. Pretty sure that's what they're after here.
I’d say C and E, since only app.json stores those persistent extension settings. Launch.json's configs would be ignored for these requirements.
I don’t think it’s B. C and E since launch.json is just for local debug, not real config.
Be respectful. No spam.
