A Foundry project must not be reachable from the internet. What do you set up?
Why B is the answer
Private networking
Private networking controls reachability. Filters act on content.
In detail
- Private networking takes the project off the public internet.
- Test from outside to confirm.
Use case
An illustrative scenario, not a real incident.
A regulated firm blocks public access to its Foundry project with private networking.
See it in different ways
flowchart LR A["Foundry project"] --> B["Managed identity"] A --> C["RBAC roles"] A --> D["Private networking"]
sequenceDiagram participant D as Developer participant G as GitHub participant A as GitHub Actions participant Z as Azure D->>G: Merges a Bicep change G->>A: Starts the workflow A->>Z: Signs in with OpenID Connect A->>Z: Deploys to dev, test and prod
flowchart TD
Q{"Where is the caller?"}
Q -->|"Inside the network"| A0["Allowed"]
Q -->|"On the internet"| A1["Blocked"]Key point: Private networking blocks internet access.
Why the other options are wrong
- A. Content filters
- Filters check content.
- C. Prompt variants
- Variants are for prompts.
- D. A second model deployment
- A second deployment does not change the network.

