CCNA Genaiops Infrastructure Questions

Resource Tags applied to the Azure AI project resource let Cost Management attribute and filter spend per project, satisfying the requirement to track usage for a specific project. Tags propagate to billing records, enabling grouped cost reporting without deploying separate subscriptions.

Prompt Flow evaluation runs compute benchmark metrics against a dataset before deployment, satisfying the pre-promotion gate. Integrated as a pipeline step, they score the model's outputs and return results your CI/CD logic can act on, blocking promotion when thresholds fail. This directly meets the stem's requirement to evaluate performance prior to production release.

Evaluation in Azure AI Foundry supplies built-in metrics and evaluators that score model outputs for groundedness, relevance and fluency, satisfying the stem's requirement for developer assistance. It enables systematic, repeatable quality assessment across prompts and models, so teams can compare runs and catch regressions before deployment rather than relying on manual inspection.

Azure API Management policies apply retry logic at the gateway layer, so transient faults from multiple LLM services are absorbed before reaching Semantic Kernel. This delivers infrastructure-level resiliency without embedding retry code in agent orchestration, satisfying the requirement to handle frequent transient errors centrally.

The deployment SKU determines the underlying VM family and therefore which GPU hardware is provisioned. Selecting the correct SKU at deployment time is the mechanism that guarantees the required GPU type is allocated to the model.

Autoscale policies define the rules that translate monitored metrics into scaling actions, specifying thresholds, minimum and maximum replica counts, and cooldown periods. They are the decision layer that automates orchestration scaling, satisfying the stem's requirement.

Request latency measures end-to-end response time from the model, exposing throttling, cold starts or backend saturation. It is a critical health signal because degraded latency directly impacts user experience and can indicate capacity or dependency problems in the GenAI deployment.

The Model Catalog in Azure AI Foundry hosts pre-optimised models from Microsoft, Azure OpenAI and partners, letting developers deploy them to an endpoint with one click rather than configuring infrastructure, weights and serving stacks manually.

The Cognitive Services OpenAI User role grants the data-plane permission needed to call model deployments in Azure AI Foundry. Assigning it to the agent's managed identity at the resource or deployment scope is the correct fix for authentication failures caused by missing role assignments. This follows least privilege and matches how Foundry authorizes inference calls.

A System-Assigned Managed Identity is created automatically with the Azure resource and tied to its lifecycle, giving the AI project a credential in Microsoft Entra ID to authenticate to other Azure services without storing secrets.

Scaling the LLM deployment's instance count adds parallel compute capacity for inference, directly addressing the slow generation phase. Vector search already performs quickly, so the bottleneck lies in token generation, which the LLM deployment handles.

Tracking quota usage directly satisfies the governance requirement by exposing consumption against assigned limits for model deployments and compute. Microsoft Entra ID role assignments and Azure Policy enforce who may deploy, but quota telemetry reveals capacity exhaustion before it blocks workloads, enabling proactive requests for additional capacity or reallocation across the AI Foundry project.

The Quotas tab in Azure AI Foundry displays real-time token-per-minute usage against your assigned limits per model and deployment, directly satisfying the stem's need for the quickest quota check during a spike. It surfaces current consumption without requiring log queries or metric configuration, unlike Azure Monitor.

'Resource Not Available' indicates the target region lacks the compute capacity or quota to provision the requested model SKU. Capacity is region- and SKU-specific, so redeploying to another region or requesting a quota increase resolves the failure.

Azure AI Content Safety supplies the filtering layer, analysing prompts and completions for harmful categories such as violence, hate and self-harm. It integrates directly with Azure OpenAI deployments, satisfying the stem's requirement that LLM responses be filtered, unlike storage or identity components such as Microsoft Entra ID.

Keeping the project and its dependencies in one resource group satisfies the lifecycle-management constraint: resources share a single deployment, tagging, and deletion boundary, so the whole AI project can be provisioned, tracked, and removed atomically. Microsoft Entra ID governs access at that scope, simplifying permission cleanup when the project retires.

Throttling occurs when request rates or token consumption exceed the endpoint's assigned quota, so comparing current usage against quota limits identifies whether the limit is the cause. This diagnosis is the prerequisite step before requesting an increase or reducing call volume.

Azure AI Foundry's project Deployments blade is where each model deployment's instance count, model version and provisioning configuration are set. This satisfies the stem's requirement to define deployment settings, since configuration occurs at the deployment resource itself rather than in the model catalogue or a training compute target.

Provisioned throughput is billed for reserved capacity whether or not it is used, so running it at full capacity off-peak wastes money. Routing off-peak traffic to a pay-as-you-go deployment and scaling the provisioned deployment down preserves peak performance while lowering off-peak cost. This hybrid pattern matches the requirement of no peak-hour impact.

Endpoint availability status directly exposes whether the agent's target service endpoint is reachable, which is the prerequisite for any deployment handshake. When an agent deployment fails, an unreachable or unhealthy endpoint blocks registration before configuration is even evaluated, so checking availability isolates connectivity faults from authentication or policy issues.

Deleting unused model deployments directly eliminates idle compute charges, since provisioned throughput and hosted endpoints bill continuously regardless of traffic. This satisfies the cost-optimisation constraint by removing resources that consume quota and incur hourly fees without serving requests. Regular audits of deployment usage therefore reduce spend without affecting active inference workloads.

Azure AI Services networking settings include firewall controls that allow or deny traffic by IP address or CIDR range, plus private endpoint options. Restricting the Foundry project to specific addresses therefore uses these firewall rules rather than authentication or RBAC configuration.

Blue-Green runs two identical environments, routing live traffic to the stable slot while the updated prompt flow is validated in the idle slot. Swapping only after verification eliminates downtime, satisfying the stem's no-downtime constraint without exposing users to an untested flow.

Diagnostic Settings stream resource logs from each model endpoint into a Log Analytics Workspace, giving centralised, queryable retention across the organisation. This satisfies the audit requirement because logs persist beyond transient local storage and can be queried with KQL across subscriptions.

Asynchronous execution decouples tool invocation from the orchestration wait, letting the agent continue or poll rather than block on a synchronous response. This directly addresses the timeout constraint by removing the blocking call that exceeds the orchestration deadline for long-running tools.

Bicep is Microsoft's declarative domain-specific language for deploying Azure resources, giving idempotent, version-controlled templates that satisfy the IaC requirement for repeatable AI Foundry provisioning. It transpiles directly to ARM templates, so Foundry project resources deploy consistently across environments.

Azure Key Vault stores the secret centrally with access control and auditing, and the connection references it at runtime rather than embedding credentials in configuration. This satisfies the requirement to handle the secret securely, avoiding plaintext exposure in code or connection strings.

Prompt Flows provide the orchestration component within an Azure AI Foundry project, letting you chain prompts, models, and tools into executable flows. They are a first-class project asset, satisfying the stem's requirement to identify genuine project components.

Prompt Flow provides built-in versioning for prompt variants, letting teams iterate, compare and roll back prompt revisions within the AI Foundry workflow. It satisfies the requirement to manage prompt versioning centrally rather than through ad-hoc code or external repositories.

Horizontal Pod Autoscaling dynamically scales inference pods based on CPU, memory or custom metrics, absorbing variable agent workloads. It satisfies the scalability requirement by adding capacity during demand spikes without manual intervention, keeping orchestration responsive.

Provisioned Throughput Units reserve dedicated model capacity, converting the deployment from pay-as-you-go token limits to a guaranteed throughput allocation. This directly removes the shared-quota throttling the stem describes, since PTUs provide predictable, reserved inference capacity for that specific model rather than competing for pooled regional capacity.

Private Link gives the GenAI deployment a private endpoint, so inference traffic traverses the Microsoft backbone rather than the public internet. This satisfies the production requirement for network isolation, preventing data exposure during model prompts and responses.

Azure AI Search provides vector and hybrid retrieval indexes purpose-built for RAG, satisfying the stem's optimal retrieval performance constraint. Its native semantic ranking and integrated vectorisation deliver low-latency similarity search across indexed documents, unlike general-purpose stores that lack native vector indexing. Microsoft Entra ID secures access to the service.

API keys authenticate directly against an Azure AI Foundry project endpoint, satisfying the requirement for a valid project-level authentication method. The key is scoped to the project resource, so callers present it without needing a separate identity token exchange. This makes it one of the two supported mechanisms alongside Microsoft Entra ID.

Evaluation in Azure AI Foundry runs built-in and custom metrics against a model or prompt flow using test datasets, producing scored results. It is the feature that quantifies performance rather than merely deploying or monitoring the model.

App Configuration stores environment-specific key-values behind labels, so Dev, Test and Prod settings coexist in one store and are selected at runtime without code changes. This satisfies the stem's requirement for managing differing configuration across environments, and integrates with Microsoft Entra ID for access control.

Prompt Flow provides built-in evaluation flows that score outputs against metrics such as groundedness and relevance, plus batch testing across datasets. This satisfies the stem's orchestration benefit by embedding repeatable quality measurement directly into the pipeline, rather than requiring separate tooling to validate prompt variants before deployment.

The Connections configuration in Azure AI Foundry stores the endpoint, authentication credentials and access keys the agent uses when invoking an external tool. A missing, stale or mis-scoped connection entry prevents the tool call from authenticating, so it must be verified first.

Azure AI Developer grants permissions to build, deploy and test models within an Azure AI Foundry project without granting broader resource-management rights. This satisfies the stem's minimum-permission constraint for a developer deploying and testing a model.

Azure Key Vault stores the API key as a managed secret, and the AI Project Connection references it, so the agent retrieves credentials at runtime without hard-coding them. This satisfies the stem's requirement for secure storage within the project.

Diagnostic Logs stream request-level records, including content-filter verdicts, into Log Analytics. This satisfies the monitoring requirement by giving a queryable audit trail of flagged outputs, which is the evidence source that alerts and dashboards later consume.

The Prompt Flow CLI exposes commands for running and evaluating flows from a terminal, so pipeline tasks can invoke flow tests non-interactively. This satisfies the CI/CD automation requirement, whereas the visual studio interface requires manual interaction.

The Endpoints tab surfaces deployment connectivity state, including private endpoint and network configuration, so failures despite 'Succeeded' status are diagnosed there first. It satisfies the stem's need to check connectivity before investigating model or payload issues.

Azure Monitor with diagnostic logs streams per-request telemetry from model deployments, capturing latency and token usage metrics at the individual inference level. This satisfies the stem's real-time, granular monitoring requirement, since diagnostic logs expose request-level detail that aggregated platform metrics cannot provide.

Prompt Flow provides a visual designer for chaining prompts, Python code and LLM calls into executable flows, letting developers author, run and evaluate prompt-based workflows before deployment. This directly satisfies the question's requirement for building and testing prompt workflows in Azure AI Foundry.