A city platform team must document how the 311 web app connects to its Foundry project. Which setup concern is central?
Select an answer to reveal the explanation.
Short Explanation
The 311 site has to know which Foundry project to dial—like putting the right radio channel on the console. Document and configure that connection; tweaking the observability workspace and retention policy won’t give you the project link you need.
Full Explanation
A city platform team documenting how the 311 web app connects to its Foundry project must center on documenting and configuring connection settings to the Foundry project endpoint and credentials pattern. Applications consume Foundry through explicit project connectivity—endpoint, authentication, and environment—not through the Foundry project observability workspace and retention policy. Setup documentation should make that connection reproducible for operators and future platform staff.
Documenting and configuring the 311 app’s connection settings to the Foundry project observability workspace and retention policy fails because configuring monitoring and log retention does not establish API connectivity or the credentials pattern to Foundry. Documenting and configuring the 311 app’s connection settings to the Foundry project prompt registry and filter policy fails because managing prompts and filter policy does not establish the connection settings or credentials pattern the 311 app needs to reach Foundry. Documenting and configuring the 311 app’s connection settings to the Foundry project agent pool and release pipeline fails because agent pool and pipeline settings describe build infrastructure, not the runtime endpoint and credentials pattern the 311 app needs to reach Foundry.
Exam caveat: connection documentation covers the Foundry endpoint and credentials pattern itself—not observability workspace and retention policy, and not prompt registry and filter policy, which are observability and prompt-governance concerns rather than the connectivity contract. Operational check: from a staging 311 build, resolve the documented Foundry endpoint, authenticate with the approved pattern, complete a test call, and confirm the connection lives in documented settings rather than observability workspace and retention policy, prompt registry and filter policy, or agent pool and release pipeline settings.
Prefer to study offline? Printable PDF study book + test engine ($7.50, unofficial). These questions stay free here.