Correct Answer:

Explanation:

Verified Answer: 1) Create the Service Bus client; 2) create the queue processor/receiver; 3) register message and error handlers; 4) start the message processor.
Detailed Explanation: The processor depends on a namespace client/connection, so the client is created first.
Next, the queue-specific processor or receiver is created from that client. Message and error callbacks must be registered before processing starts so incoming messages and failures have defined handlers. Starting the processor is therefore the final step. Dead-lettering failed messages is an optional application settlement decision and is not a prerequisite for constructing and starting the processor.
Study Guide Alignment: Azure service integration: Service Bus, Event Grid, Azure Functions triggers
/bindings, and event-driven processing.
Official Microsoft Learn References: AI-200 Study Guide | Service Bus message transfers, locks, and settlement

Correct Answer:

Explanation:

Verified Answer: 1) Register the Event Grid resource provider; 2) create a custom topic; 3) create an event subscription.
Detailed Explanation: A newly provisioned subscription must have the Event Grid resource provider available before Event Grid resources can be created. The publisher needs a custom topic as the event-ingress resource, and routing to a downstream processor is then defined by an event subscription on that topic. The event subscription can include filters such as event type or data fields so that only high-confidence events reach the processor. Creating a partner topic or domain is unnecessary for the stated custom workflow.
Study Guide Alignment: Azure service integration: Service Bus, Event Grid, Azure Functions triggers
/bindings, and event-driven processing.
Official Microsoft Learn References: AI-200 Study Guide | Create an Event Grid custom topic or domain

Correct Answer:

Explanation:
* The code configures the tracer provider before any spans are created: Yes
* The configuration exports traces synchronously: No
* The configuration enables export to Azure Monitor: Yes
The first statement is Yes. The code calls trace.set_tracer_provider(TracerProvider()) before obtaining the tracer and before any span-creation operation occurs. In OpenTelemetry, retrieving a tracer by using trace.
get_tracer() does not itself create a span; spans are created later through methods such as start_span() or start_as_current_span().
The second statement is No. The code uses BatchSpanProcessor, which batches completed spans and exports them through a background processing mechanism rather than exporting every span synchronously on the application ' s execution path. OpenTelemetry documentation states that BatchSpanProcessor batches ended spans before sending them to the configured exporter, and the Python implementation uses a background thread for export processing.
The third statement is Yes. AzureMonitorTraceExporter is instantiated with an Azure Monitor/Application Insights connection string and passed to BatchSpanProcessor. That processor is then registered with the tracer provider. Microsoft provides this same pattern specifically for exporting OpenTelemetry traces to Azure Monitor/Application Insights.
Study Guide references: Azure Monitor OpenTelemetry; TracerProvider; BatchSpanProcessor; AzureMonitorTraceExporter; distributed tracing.

Correct Answer: A  🗳️

Correct Answer:

Explanation:
* Command: func init
* Parameter: --worker-runtime
Use func init to initialize a new Azure Functions project. Microsoft documents func init as the Azure Functions Core Tools command that creates the project structure in either the current directory or a specified project folder. The command is specifically intended for creating a new Functions application project, whereas func new creates an individual function from a template inside an already initialized project.
The --worker-runtime parameter specifies the language/runtime model for the Functions project. For example, Microsoft documents func init --worker-runtime python for Python projects and func init --worker- runtime dotnet-isolated for modern C#/.NET isolated-worker projects.
--language is not the primary parameter used to establish the Functions worker runtime in this scenario. It can be relevant to certain runtime combinations, such as Node.js, but the Core Tools project initialization examples for Python and C# rely on --worker-runtime. --target-framework is used to select a specific .NET target framework after the worker/runtime model is determined; it does not identify whether the project should be Python or C#.
Therefore, the correct combination is func init + --worker-runtime .
Study Guide references: Azure Functions Core Tools # func init; local Functions project creation; --worker- runtime; Python and .NET isolated worker projects.