Some options, depending on the user experience you want to provide (no judgements here about what's better for your situation due to lack of details):

"old school" - (no JavaScript) necessarily reloads a page or URL in the web browser (either same page or in a new tab or window)

• direct link to the static file
• an actual download link that sends a GET request (via traditional hyperlink "click") to an endpoint (URL) that has the paramaters baked into the URL itself, that then invokes your business logic on the server to return whatever file you wish
• traditional HTML <form></form> with "radio" buttons, which when it is submitted sends a GET or POST ("method") request to the "action" with the form element values; then results in the browser loading the "action" URL - this could be the same "page" or a different "page" altogether

"modern" - requests are made in the "background" (asynchronously) and the page the user is on doesn't "reload" (requires JavaScript)

• form with radio buttons (or other elements), but "submit" issues the asynchronous request via JavaScript; the page is not reloaded
• a hyperlink, where "onclick" triggers the async JavaScript request

Depends on what you what. The general answer to, can it be done, is yes. Best for you to decide how you want the user to interact with the page and what you want them to "see" when whatever kind of element you want is clicked - hyperlink, form "submit" button, dog picture, etc. Decide that and you might get some much better information.