A: Implementing the change feed processor.
The point of entry is always the monitored container, from a Container instance you call GetChangeFeedProcessorBuilder.
C: You define the compute instance name or unique identifier with WithInstanceName, this should be unique and different in each compute instance you are deploying.
F: The lease container: The lease container acts as a state storage and coordinates processing the change feed across multiple workers. The lease container can be stored in the same account as the monitored container or in a separate account.
Reference:
https://docs.microsoft.com/en-us/azure/cosmos-db/sql/change-feed-processor

The below table demonstrates which API supports server-side latency metrics (Direct vs Gateway):

Option A is correct. SQL API supports both Server-Side Latency Direct as well as Server-Side Latency Gateway.
Option B is incorrect. MongoDB supports only Server-Side Latency Gateway.
Option C is incorrect. Cassandra supports only Server-Side Latency Gateway.
Option D is incorrect. Gremlin supports does not support Server-Side Latency Direct.
Option E is correct. Table supports both Server-Side Latency Direct as well as Server-Side Latency Gateway.
Reference:
https://docs.microsoft.com/en-us/azure/cosmos-db/monitor-server-side-latency

Explanation:
Box 1: No
The same connection string can still be used.
Azure Cosmos DB Core read write region connection strings
Azure Cosmos DB "primary write region" failover "connection string"
Box 2: No
The AccountEndpoint for both are the same.
Box 3: Yes
The ConnectionPolicy.PreferredLocations property gets and sets the preferred locations (regions) for geo-replicated database accounts in the Azure Cosmos DB service. For example, "East US" as the preferred location.
When EnableEndpointDiscovery is true and the value of this property is non-empty, the SDK uses the locations in the collection in the order they are specified to perform operations, otherwise if the value of this property is not specified, the SDK uses the write region as the preferred location for all operations.
Reference:
https://docs.microsoft.com/en-us/dotnet/api/microsoft.azure.documents.client.connectionpolicy.preferredlocations

To identify the number of request units (RUs) consumed by each query using the Azure Cosmos DB .NET SDK (specifically v2 API / DocumentClient syntax implied by your choices), you should use IDocumentQuery and FeedResponse.
ResourceResponse: In the legacy Azure Cosmos DB .NET SDK (v2), query and item operations return a ResourceResponse<T> object. This object contains a RequestCharge property that explicitly yields the number of RUs consumed by the database operation.
IDocumentQuery: When you perform asynchronous pagination or streaming of SQL query results in the v2 .NET SDK, the IDocumentQuery<T> interface is implemented. This interface exposes properties and response fields that catch execution metrics-including total request charges-as you iterate through your data feed.
Reference:
https://learn.microsoft.com/sv-se/azure/cosmos-db/find-request-unit-charge