You are choosing an embedding strategy for a RAG solution. Documents range from 2 to 200 pages. You need to preserve semantic coherence while staying within embedding model token limits. What should you do?

• A. Embed each entire document as a single vector
• B. Chunk documents into smaller overlapping segments before embedding
• C. Use only document titles for embedding
• D. Convert documents to images and use image embeddings

Explanation: Only visible for ITCertMagic members. You can sign-up / login (it's free).

Drag and Drop Question
You are deploying an Azure Function app that retrieves secrets from Key Vault by using a managed identity.
The deployment must ensure that identity and secret configuration are in place before the function code is deployed.
You need to deploy the function app securely.
In which order should you perform the actions? To answer, move all actions from the list of actions to the answer area and arrange them in the correct order.

Explanation:
Step 1: Create the function app
You must first provision the underlying Azure Functions infrastructure before you can bind an identity or configuration settings to it.
Step 2: Assign a managed identity to the function app
Turning on the managed identity (such as a system-assigned identity) creates a distinct security principal in Microsoft Entra ID for the resource.
Step 3: Grant access to Key Vault
Use the managed identity's principal ID to create an access policy or RBAC role assignment in Key Vault, allowing the app to read secrets.
Step 4: Add Key Vault references to application settings.
Configure the Function App's application settings to point to the Key Vault secret URIs (@Microsoft.KeyVault(...)), which can now be securely resolved by the identity.
Step 5: Deploy the function code
Finally, deploy the application code. This ensures that when the code initializes and executes, all environment variables and secrets are already active and accessible, preventing application startup failures.
Reference:
https://learn.microsoft.com/en-us/azure/app-service/app-service-key-vault-references

Drag and Drop Question
You plan to create a Docker image that runs an ASP.NET Core application named ContosoApp.
You have a setup script named setupScript.ps1 and a series of application files including ContosoApp.dll.
You need to create a Dockerfile document that meets the following requirements:
- Call setupScript.ps1 when the container is built.
- Run ContosoApp.dll when the container starts.
The Dockerfile document must be created in the same folder where ContosoApp.dll and setupScript.ps1 are stored.
Which five commands should you use to develop the solution? To answer, move the appropriate commands from the list of commands to the answer area and arrange them in the correct order.

Explanation:
Step 1: FROM microsoft/aspnetcore:latest
Sets the base image for the container.
Base First: You must always declare the base image (FROM) before running any other commands.
Step 2: WORKDIR /apps/ContosoApp
Creates and sets the working directory inside the container.
Directory and Copy: You need to set the working directory (WORKDIR) before copying files (COPY) so Docker knows exactly where to put them.
Step 3: COPY ./ .
Copies the application files and script from your local folder into the working directory.
Step 4: RUN powershell ./setupScript.ps1
Executes the script during the image build process.
Build vs. Run: The RUN command happens while building the image, so the script completes its setup before the final image is saved. The CMD instruction does not execute anything during the build; it simply configures the starting point for when the container is actually launched.
Step 5: CMD ["dotnet", "ContosoApp.dll"]
Defines the default command to run your application when the container starts.
Reference:
https://azuretar.com/using-startup-command-to-pass-command-line-arguments-to-azure-app-service-for-linux/

You store embeddings in Redis by using keys formatted as doc:(id). Some embeddings are accessed frequently. Others are rarely used.
You need to implement a caching strategy that keeps only frequently accessed embeddings in memory.
What should you use?

• A. allkeys-lru
• B. EXPIRE command
• C. time-window expiration
• D. volatile-ttl

Explanation: Only visible for ITCertMagic members. You can sign-up / login (it's free).

Drag and Drop Question
You are developing several microservices to run on Azure Container Apps.
The microservices must allow HTTPS access by using a custom domain.
You need to configure the custom domain in Azure Container Apps.
In which order should you perform the actions? To answer, move all actions from the list of actions to the answer area and arrange them in the correct order.

Explanation:
Step 1: Enable ingress
You must first expose your container app to external traffic to generate the default fully qualified domain name (FQDN) needed for DNS mapping.
Step 2: Add DNS records to the domain provider
Log into your domain registrar to create the required TXT (for verification) and CNAME/A records pointing to your container app.
Step 3: Validate the custom domain name
Azure checks your DNS records to confirm that you actually own the domain before allowing it to be linked.
Step 4: Add the custom domain name
Once validation passes, you officially add and register the custom domain name within the Azure Container App configuration.
Step 5: Bind the certificate
Finally, bind an SSL/TLS certificate to the custom domain to secure the connection and enable HTTPS access.
Reference:
https://learn.microsoft.com/en-us/azure/container-apps/ingress-overview