A municipal Functions application sets REGION=us-ashburn-1 for all handlers, but the GIS export function must use a different region key. How should that override be applied?
Select an answer to reveal the explanation.
Short Explanation
Shared application config is the default office policy; a function-level sticky note with the same key wins for that one desk. Override on the function instead of forking a whole new application.
Full Explanation
Oracle Functions configuration is layered: application-wide key-value pairs provide defaults for every function in the municipal application, while the same key set at function level overrides the application value for that function only. For GIS export that needs a different REGION than us-ashburn-1, set REGION on that function; other handlers keep the application default without forking the whole application.
Creating a second Functions application solely to change one configuration key adds operational sprawl and is unnecessary when function-level override exists. Dynamic group matching rules govern which resources receive IAM grants; they do not inject arbitrary region configuration keys at evaluation time. Putting conflicting keys only in the Docker image so runtime config is ignored fights the platform model—runtime configuration is meant to win for environment-specific values.
Exam caveat: understand precedence—function config overrides application config for matching keys; missing function keys fall back to the application. Operational check: verify REGION at application scope, add the override on the GIS function only, invoke both a default handler and the GIS handler, and confirm environment variables (or logged region clients) reflect application versus function values as intended.