さらに、CertShiken DP-420ダンプの一部が現在無料で提供されています：https://drive.google.com/open?id=1Zlub6KX_mwRpIGVlHNPDQCFeplk_azho
CertShikenのMicrosoftのDP-420試験トレーニング資料は高度に認証されたIT領域の専門家の経験と創造を含めているものです。私たちのIT専門家は受験生のために、最新的なMicrosoftのDP-420問題集を提供します。うちの学習教材の高い正確性は言うまでもありません。受験生が最も早い時間で、一回だけでMicrosoftのDP-420認定試験に合格できるために、CertShikenはずっとがんばります。
Azure Cosmos DB は、ミッションクリティカルなアプリケーションに適した、グローバルに分散したマルチモデルデータベースサービスです。高可用性、低レイテンシー、シームレスなスケーラビリティを提供し、クラウドネイティブアプリケーションの理想的な選択肢となっています。DP-420 認定試験では、コンテナの設計と実装、パーティショニング戦略の設計と実装、および Azure Cosmos DB のパフォーマンスの最適化などのトピックをカバーしています。
DP-420認定試験を受験したいですか。DP-420認証資格を取得したいですか。試験に準備する時間が足りないあなたは、どうやって試験に合格できますか。しようがないわけではないです。短時間の準備でも楽に試験に合格することができるようになりますよ。それでは、どのようにすればそれを達成できますか。実は方法がとても簡単です。すなわちCertShikenのDP-420問題集を利用して試験の準備をすることです。
試験は、Cosmos DB を使用したデータアクセスパターンの設計と実装、パーティショニング戦略の設計と実装、グローバル分散の設計と実装、災害復旧とデータ同期の設計と実装など、さまざまなトピックでの候補者の知識とスキルをテストします。試験はまた、Cosmos DB を使用したサーバーレスおよびコンテナベースのアプリケーションの開発と実装における候補者の知識とスキルもテストします。
質問 # 174
You plan to create an Azure Cosmos DB database named db1 that will contain two containers. One of the containers will contain blog posts, and the other will contain users. Each item in the blog post container will include:
* A single blog post
* All the comments associated to the blog post
* The names of the users who created the blog post and added the comments.
You need to design a solution to update usernames m the user container without causing data integrity issues.
The solution must minimize administrative and development effort. What should you include in the solution?
To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
正解：
解説：
Explanation:
質問 # 175
You are implementing an Azure Data Factory data flow that will use an Azure Cosmos DB (SQL API) sink to write a dataset. The data flow will use 2,000 Apache Spark partitions.
You need to ensure that the ingestion from each Spark partition is balanced to optimize throughput.
Which sink setting should you configure?
正解：D
解説：
Batch size: An integer that represents how many objects are being written to Cosmos DB collection in each batch. Usually, starting with the default batch size is sufficient. To further tune this value, note:
Cosmos DB limits single request's size to 2MB. The formula is "Request Size = Single Document Size * Batch Size". If you hit error saying "Request size is too large", reduce the batch size value.
The larger the batch size, the better throughput the service can achieve, while make sure you allocate enough RUs to empower your workload.
Reference: https://docs.microsoft.com/en-us/azure/data-factory/connector-azure-cosmos-db
質問 # 176
You are developing an application that will connect to an Azure Cosmos DB for NoSQL account. The account has a single readme region and one agonal read region. The regions are configured for automatic failover.
The account has the following connect strings. (Line numbers are included for reference only.)
For each of the following statements, select Yes if the statement is true. otherwise, select No.
NOTE: Each correct selection is worth one point.
正解：
解説：
Explanation:
If the primary write region fails, applications that write to the database must use a different connection string to continue to use the service. = NO You do not need to use a different connection string to continue to use the service if the primary write region fails. This is because Azure Cosmos DB supports automatic failover, which means that it will automatically switch the primary write region to another region in case of a regional o utage 2 . The application doe s not need to change the connection string or specify the failover priority 3 . The connection string contains a list of all the regions associated with your account, and Azure Cos mos DB will route the requests to the appropriate region based on the availability and latency 1 .
The primary Read-Only SQL Connection String and the Secondary Read-Only SQL Connection String will connect to different regions from an application running in the East US Azure region = Yes The primary read-only SQL connection string and the secondary read-only SQL connection string will connect to different regions from an application running in the East US Azure region. This is because the primary read-only SQL connection string contains the endpoint for the East US region, which is the same as the primary write region. The secondary read-only SQL connection string contains the endpoint for the West US region, which is the additional read region. Therefore, if an application running in the East US Azure region uses these connection strings, it will connect to different regions depending on which one it chooses.
Applications can choose from which region by setting the PreferredLocations property within their connection properties = Yes Applications can choose from which region by setting the PreferredLocations property within their connection properties. This property allows you to specify a list of regions that you prefer to read from based on their proximity to your application 2 . Azure Cosmos DB will route the requests to the appropriate region based on the availability and latency 1 . You can also set the ApplicationRegion property to the region where your application is deployed, and Azure Cosmos DB will automatically populate the PreferredLocations property based on the geo-proximity from that location 1 .
質問 # 177
You have a container named container1 in an Azure Cosmos DB for NoSQL account named account1.
You configure container1 to use Always Encrypted by using an encryption policy as shown in the C# and the Java exhibits. (Click the C# tab to view the encryption policy in C#. Click the Java tab to see the encryption policy in Java.)
For each of the following statements, select Yes if the statement is true. Otherwise, select No.
NOTE: Each correct selection is worth one point.
正解：
解説：
Explanation
According to the Azure Cosmos DB documentation1, Always Encrypted is a feature designed to protect sensitive data, such as credit card numbers or national identification numbers, stored in Azure Cosmos DB.
Always Encrypted allows clients to encrypt sensitive data inside client applications and never reveal the encryption keys to the database.
To use Always Encrypted, you need to define an encryption policy for each container that specifies which properties should be encrypted and which data encryption keys (DEK) should be used. The DEKs are stored in Azure Cosmos DB and are wrapped by customer-managed keys (CMK) that are stored in Azure Key Vault.
Based on the encryption policy shown in the exhibits, the creditcard property is encrypted with a DEK named dek1, and the SSN property is encrypted with a DEK named dek2. Both DEKs are wrapped by a CMK named cmk1.
To answer your statements:
You can perform a query that filters on the creditcard property = No. This is because the creditcard property is encrypted and cannot be used for filtering or sorting operations1.
You can perform a query that filters on the SSN property = No. This is also because the SSN property is encrypted and cannot be used for filtering or sorting operations1.
An application can be allowed to read the creditcard property while being restricted from reading the SSN property = Yes. This is possible by using different CMKs to wrap different DEKs and applying access policies on the CMKs in Azure Key Vault. For example, if you use cmk2 to wrap dek2 instead of cmk1, you can grant an application access to cmk1 but not cmk2, which means it can read the creditcard property but not the SSN property2.
質問 # 178
You plan to deploy two Azure Cosmos DB Core (SQL) API accounts that will each contain a single database.
The accounts will be configured as shown in the following table.
How should you provision the containers within each account to minimize costs? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
正解：
解説：
Explanation:
Box 1: Serverless capacity mode
Azure Cosmos DB serverless best fits scenarios where you expect intermittent and unpredictable traffic with long idle times. Because provisioning capacity in such situations isn ' t required and may be cost-prohibitive, Azure Cosmos DB serverless should be considered in the following use-cases:
Getting started with Azure Cosmos DB
Running applications with bursty, intermittent traffic that is hard to forecast, or low ( < 10%) average-to-peak traffic ratio Developing, testing, prototyping and running in production new applications where the traffic pattern is unknown Integrating with serverless compute services like Azure Functions Box 2: Provisioned throughput capacity mode and autoscale throughput The use cases of autoscale include:
Variable or unpredictable workloads: When your workloads have variable or unpredictable spikes in usage, autoscale helps by automatically scaling up and down based on usage. Examples include retail websites that have different traffic patterns depending on seasonality; IOT workloads that have spikes at various times during the day; line of business applications that see peak usage a few times a month or year, and more. With autoscale, you no longer need to manually provision for peak or average capacity.
Reference:
https://docs.microsoft.com/en-us/azure/cosmos-db/serverless
https://docs.microsoft.com/en-us/azure/cosmos-db/provision-throughput-autoscale#use-cases-of-autoscale
質問 # 179
......
DP-420テスト内容: https://www.certshiken.com/DP-420-shiken.html
2026年CertShikenの最新DP-420 PDFダンプおよびDP-420試験エンジンの無料共有：https://drive.google.com/open?id=1Zlub6KX_mwRpIGVlHNPDQCFeplk_azho