最新MuleSoft-Integration-Associate日本語合格保証試験問題集には正確で最新な問題があります
MuleSoft-Integration-Associate日本語試験ブレーン問題集で学習注釈と理論
質問 # 23
API 認証に API キーのみを使用するのではなく、OAuth 2.0 クライアント資格情報とアクセス トークンを使用する利点は何ですか?
- A. クライアントIDが漏洩した場合、APIキーと交換できる
- B. アクセストークンが侵害された場合、APIキーと交換できます
- C. アクセストークンが侵害された場合、クライアント資格情報を再発行する必要はありません。
- D. クライアントシークレットが侵害された場合、クライアント資格情報を再発行する必要はありません。
正解：C
解説：
OAuth 2.0 provides a more secure and flexible way of handling API authentication compared to API keys.
Here's a detailed explanation of the advantage mentioned:
* OAuth 2.0 Client Credentials Grant:
* How It Works: In this flow, a client application uses its client ID and client secret to obtain an access token from the authorization server.
* Access Tokens: These tokens are short-lived and used to authenticate API requests.
* Security Advantages:
* Token Compromise: If an access token is compromised, it only grants limited access because it has a short lifespan and can be easily revoked.
* Client Credentials: The client credentials (client ID and secret) are not exposed during API calls, reducing the risk of them being compromised.
* Token Refresh: New tokens can be obtained without exposing the client credentials again.
* Comparison with API Keys:
* API Keys: If an API key is compromised, it often provides long-term access without expiration.
Revoking the API key impacts all users or applications using it.
* OAuth Tokens: Compromised tokens can be individually revoked without needing to change the client credentials, minimizing disruption.
References
* OAuth 2.0 Framework: OAuth 2.0
* MuleSoft Security Best Practices: API Security
質問 # 24
どの Exchange アセット タイプが RAML または OAS 形式の完全な API 仕様を表していますか?
- A. REST API
- B. コネクタ
- C. API 仕様フラグメント
- D. SOAP API
正解：A
解説：
In Anypoint Exchange, a REST API asset represents a complete API specification in RAML (RESTful API Modeling Language) or OAS (OpenAPI Specification) format. Here's a detailed explanation:
* REST APIs:
* Definition: REST APIs are application programming interfaces that adhere to the principles of REST, allowing interaction with RESTful web services.
* Specifications: Typically defined using RAML or OAS to describe the API's endpoints, methods, request/response structures, and security protocols.
* Asset Types in Anypoint Exchange:
* REST APIs: Represent the full API specification, including all necessary details for developers to understand and use the API.
* SOAP APIs: Define APIs following the SOAP protocol, often using WSDL.
* Connectors: Provide pre-built connectivity to various systems and services.
* API Spec Fragments: Reusable pieces of an API specification, such as data types or security schemes, that can be included in full API specifications.
* Usage:
* Discoverability: Developers can easily discover, review, and reuse these API specifications in their projects.
* Documentation: Provides comprehensive documentation generated from the API specification, ensuring consistency and clarity.
References
* MuleSoft Documentation: REST APIs in Exchange
* RAML and OAS:RAML,OpenAPI
質問 # 25
MuleSoft によると、2 つのシステム間の通信に使用される方法、形式、プロトコルを説明するシステム統合用語はどれですか?
- A. インタラクション
- B. メッセージ
- C. コンポーネント
- D. インターフェース
正解：D
解説：
In system integration, the term "interface" describes the method, format, and protocol used for communication between two systems. Here's a detailed explanation:
* Interface:
* Definition: An interface defines the point of interaction between two systems, specifying how data is exchanged, including the communication method, data format, and protocol.
* Components: Typically includes API endpoints, data formats (e.g., JSON, XML), communication protocols (e.g., HTTP, HTTPS), and authentication mechanisms.
* Importance:
* Standardization: Ensures that different systems can communicate effectively by adhering to predefined standards and protocols.
* Interoperability: Facilitates seamless interaction and data exchange between disparate systems, enhancing overall integration.
* Examples:
* RESTful APIs: Define interfaces using HTTP/HTTPS and data formats like JSON or XML.
* SOAP Web Services: Use XML-based messages and protocols such as HTTP or HTTPS for communication.
References
* MuleSoft Documentation: System Integration Concepts
* Interface Design: API Interface
質問 # 26
組織は、クロスセルの機会を増やし、見込み客データをより適切に追跡するために、エンタープライズ ソフトウェア システムを調達する必要があります。
典型的な目的や意図された目的で使用される場合、これらのコア機能を持つエンタープライズ ソフトウェアのカテゴリはどれですか?
- A. 企業間取引 (B2B)
- B. サプライ チャネル管理 (SCM)
- C. 顧客関係管理 (CRM)
- D. IT サービス管理 (ITSM)
正解：C
解説：
Customer Relationship Management (CRM) systems are designed to manage an organization's interactions with current and potential customers. Here's a detailed explanation:
* Core Capabilities:
* Cross-Selling Opportunities: CRM systems track customer interactions, preferences, and purchasing history, helping businesses identify opportunities for cross-selling and upselling.
* Prospect Data Management: CRM systems manage prospect information, track leads, and nurture relationships through the sales funnel.
* Typical Use:
* Sales Management: Helps sales teams manage and analyze customer interactions and data throughout the customer lifecycle.
* Marketing Automation: Assists in automating marketing campaigns, segmenting customer lists, and tracking campaign effectiveness.
* Customer Service: Provides tools for managing customer support cases, improving customer satisfaction, and retaining customers.
References
* CRM Overview: What is CRM?
* Benefits of CRM: Why CRM Matters
質問 # 27
組織の IT チームは、API プロキシを使用して必要な認証および承認ポリシーを適用することにより、統合ソリューション内のすべての内部 API を保護する必要があります。他のすべての関連要因が同じである場合、チームはこれらの要件を満たすために、意図された目的で使用するときにどの統合テクノロジを選択する必要がありますか?
- A. 統合プラットフォーム・アズ・ア・サービス (iPaaS)
- B. ロボティックプロセスオートメーション (RPA)
- C. 電子データ交換 (EDI)
- D. API 管理 (APIM)
正解：D
解説：
Securing internal APIs within an integration solution is critical for protecting sensitive data and ensuring proper access controls. The use of API proxies to apply authentication and authorization policies is a best practice in API security. Here's a detailed explanation:
* API Management (APIM):
* Purpose: API Management platforms are designed specifically to manage, secure, and monitor APIs. They provide tools for designing, publishing, securing, and analyzing APIs.
* Key Features:
* Security: APIM platforms offer robust security features such as OAuth, JWT, API keys, and IP whitelisting to authenticate and authorize API consumers.
* API Proxies: They allow the creation of API proxies which act as intermediaries between the client and the backend service. This enables enforcing security policies without modifying the backend API.
* Implementation:
* Authentication and Authorization Policies: Using APIM, the IT team can easily configure policies for authentication (e.g., OAuth 2.0) and authorization to control access to APIs.
* Policy Enforcement: These policies are enforced at the API proxy level, ensuring that only authenticated and authorized requests reach the backend services.
* Monitoring and Analytics: APIM platforms provide detailed analytics and monitoring capabilities to track API usage, detect anomalies, and ensure compliance.
References
* MuleSoft Documentation: API Security
* API Management Overview: What is API Management
質問 # 28
APIクライアントは、値を含むAcceptヘッダーを使用してAPIゲートウェイにHTTPリクエストを送信します。
「アプリケーション/json」
クライアントが要求したデータ形式でのこのリクエストに対する有効な HTTP 応答ペイロードは何ですか?
- A. <status>healthy< 'status>
- B. {"status" -healthy-}
- C. status('healthy')
- D. status: healthy
正解：B
解説：
When an API client makes an HTTP request with an Accept header containing the value "application/json", the API server should respond with a payload formatted as JSON. Here's a detailed explanation:
* Accept Header:
* Purpose: The Accept header indicates the media type(s) that the client is willing to receive from the server.
* Value "application/json": Specifies that the client expects a response in JSON format.
* Valid JSON Response:
* Format: JSON (JavaScript Object Notation) is a lightweight data interchange format that uses key-value pairs.
* Example: A valid JSON response for the requested format would be {"status": "healthy"}.
* Key: "status"
* Value: "healthy"
References
* JSON Standard: JSON.org
* HTTP Headers: MDN HTTP Headers
質問 # 29
MuleSoft 開発者は、API 実装を構築する前に API 仕様を作成するためにどの AnypointPlatform コンポーネントを使用する必要がありますか?
- A. ランタイムマネージャー
- B. API マネージャー
- C. API デザイナー
- D. マルチユニット
正解：C
解説：
Creating an API specification before building the API implementation is a critical step in API development.
MuleSoft's API Designer is the tool designed for this purpose. Here's a detailed explanation:
* API Designer:
* Purpose: API Designer is a web-based tool within Anypoint Platform that allows developers to design, document, and test APIs.
* Features:
* Specification Languages: Supports RAML and OAS (OpenAPI Specification) for defining APIs.
* Interactive Editing: Provides a graphical and text-based interface to design API specifications interactively.
* Mocking Service: Allows developers to create mock services to simulate API behavior before the actual implementation.
* Process:
* Define API: Use API Designer to create a detailed API specification, including endpoints, methods, request/response schemas, and security schemes.
* Documentation: Automatically generate API documentation that can be shared with stakeholders.
* Testing: Test the API design using the built-in mocking service to ensure it meets requirements.
References
* MuleSoft Documentation: API Designer
* API Design Best Practices: Designing APIs
質問 # 30
Kubernetes コントローラーは、アプリケーションの負荷の増加に応じて、別のポッドレプリカをリソース プールに自動的に追加します。コントローラーはどのスケーラビリティ オプションを実装していますか?
- A. ダウン
- B. 水平
- C. 対角線
- D. 垂直
正解：B
解説：
Kubernetes offers several scalability options to handle varying application loads. The scenario described involves adding another pod replica in response to increased load, which is a form of horizontal scaling. Here' s a detailed explanation:
* Horizontal Scaling:
* Definition: Horizontal scaling, also known as scaling out, involves adding more instances (pods) to distribute the load and increase capacity.
* Implementation in Kubernetes: Kubernetes uses controllers like the Horizontal Pod Autoscaler (HPA) to automatically adjust the number of pod replicas based on observed CPU utilization or other select metrics.
* Benefits:
* Load Distribution: By adding more pod replicas, the load is evenly distributed, reducing the risk of any single pod being overwhelmed.
* Fault Tolerance: Horizontal scaling enhances fault tolerance and availability, as multiple pod replicas can handle requests if one fails.
* Automatic Scaling:
* Kubernetes Controller: The HPA continuously monitors the application load and adjusts the number of pod replicas accordingly, ensuring optimal performance.
References
* Kubernetes Documentation: Horizontal Pod Autoscaling
* Kubernetes Scalability: Understanding Kubernetes Scaling
質問 # 31
統合開発者が再利用可能な API、コネクタ、テンプレートを検出して共有するのに役立つ AnypointPlatform コンポーネントはどれですか?
- A. あらゆるポイントの交換
- B. エニーポイントスタジオ
- C. API マネージャー
- D. デザインセンター
正解：A
解説：
Anypoint Exchange is a component of the Anypoint Platform that helps integration developers discover and share reusable APIs, connectors, and templates. Here's a detailed explanation:
* Anypoint Exchange:
* Purpose: Acts as a centralized repository for discovering, sharing, and reusing APIs, connectors, templates, and other integration assets.
* Discovery: Developers can search for and find existing APIs, connectors, and templates within the organization or from the wider MuleSoft community.
* Sharing: Allows developers to publish their APIs and assets, making them available for reuse by others in the organization.
* Benefits:
* Reusability: Promotes reuse of existing assets, reducing development time and effort.
* Collaboration: Facilitates collaboration and sharing of best practices among development teams.
* Documentation: Provides comprehensive documentation and usage examples for each asset.
References
* MuleSoft Documentation: Anypoint Exchange
* Anypoint Platform Features: Discover and Share with Exchange
質問 # 32
組織は、クロスセルの機会を増やし、見込み客データをより適切に追跡するために、エンタープライズ ソフトウェア システムを調達する必要があります。
典型的な目的や意図された目的で使用される場合、これらのコア機能を持つエンタープライズ ソフトウェアのカテゴリはどれですか?
- A. 企業間取引 (B2B)
- B. サプライ チャネル管理 (SCM)
- C. 顧客関係管理 (CRM)
- D. IT サービス管理 (ITSM)
正解：C
解説：
Customer Relationship Management (CRM) systems are designed to manage an organization's interactions with current and potential customers. Here's a detailed explanation:
* Core Capabilities:
* Cross-Selling Opportunities: CRM systems track customer interactions, preferences, and purchasing history, helping businesses identify opportunities for cross-selling and upselling.
* Prospect Data Management: CRM systems manage prospect information, track leads, and nurture relationships through the sales funnel.
* Typical Use:
* Sales Management: Helps sales teams manage and analyze customer interactions and data throughout the customer lifecycle.
* Marketing Automation: Assists in automating marketing campaigns, segmenting customer lists, and tracking campaign effectiveness.
* Customer Service: Provides tools for managing customer support cases, improving customer
* satisfaction, and retaining customers.
References
* CRM Overview:What is CRM?
* Benefits of CRM: Why CRM Matters
質問 # 33
一般的な MuleSoft 統合プロジェクトの一環として API 実装を構築する主な責任を持つ役割はどれですか?
- A. 統合アーキテクト
- B. 操作
- C. API 開発者
- D. API デザイナー
正解：C
解説：
In a typical MuleSoft integration project, the role of building API implementations is primarily assigned to an API Developer. Here's a detailed explanation:
* API Developer:
* Responsibilities: Focuses on implementing the technical aspects of APIs, including coding, testing, and deploying API endpoints.
* Skills: Requires proficiency in MuleSoft Anypoint Platform, MuleSoft connectors, and API development best practices.
* Typical Tasks:
* API Implementation: Writing code to implement API logic and data processing.
* Integration: Connecting APIs to backend systems, databases, and external services.
* Testing: Developing and executing unit and integration tests to ensure API functionality and reliability.
References
* MuleSoft Role Descriptions: API Developer
* API Development Lifecycle: Building APIs
質問 # 34
経営幹部との計画セッション中に、開発チームのディレクターは、会社の注文データベースのデータを公開するための新しい API の計画を提示します。このデータに基づいて API を構築する以前の取り組みは失敗したため、ディレクターは設計優先のアプローチを推奨しています。
デザインファーストアプローチのどの特性がこの API の成功に役立ちますか?
- A. API にグローバルポリシーを追加して、すべての開発者がコーディングする前に実装を自動的に保護できるようにします。
- B. 管理者がデプロイメント中にコードカバレッジ率を確認できるように MUnit テストを構築する
- C. 完全に実装された API を Exchange に公開し、すべての開発者が API を再利用できるようにします。
- D. 実装が構築される前に消費者がテストできるように仕様を開発する
正解：D
解説：
A design-first approach emphasizes creating the API specification before implementation, ensuring better alignment with consumer needs and reducing the risk of project failure. Here's a detailed explanation:
* API Specification:
* Definition: An API specification is a detailed, formal description of the API's endpoints, request
/response formats, and protocols.
* Consumer Testing: Allows API consumers (developers) to understand, test, and provide feedback on the API design before actual development begins.
* Advantages:
* Early Feedback: Consumers can test the API design using mock services or tools like API Designer and provide feedback, ensuring the API meets their requirements.
* Reduced Rework: Identifies potential issues and design flaws early, reducing costly changes during the implementation phase.
* Documentation: Provides comprehensive documentation that aids in the development and future maintenance of the API.
References
* Design-First Approach: Design-First API Development
* API Mocking: API Designer Mocking Service
質問 # 35
MuleSoftCatalyst 配信アプローチの中心的な柱は何ですか?
- A. 技術の集中化
- B. プロセス思考
- C. スコープの縮小
- D. ビジネス成果
正解：D
解説：
MuleSoft Catalyst is a unique delivery approach designed to help organizations achieve successful digital transformation. Here's a detailed explanation of the core pillar of Business Outcomes:
* Focus on Business Outcomes:
* Customer Success: MuleSoft Catalyst emphasizes the importance of aligning technology initiatives with business objectives to drive measurable outcomes.
* Value Realization: By prioritizing business outcomes, the approach ensures that the integration solutions deliver tangible value and support strategic goals.
* Methodology:
* Discover: Identifying and understanding the key business challenges and opportunities.
* Design: Crafting solutions that directly address business needs, ensuring alignment with overall strategy.
* Deliver: Implementing the solutions effectively to achieve the desired business outcomes.
* Optimize: Continuously improving and adapting the solutions to sustain and enhance business value.
References
* MuleSoft Documentation: MuleSoft Catalyst
* Business Outcomes Focus: Catalyst Methodology
質問 # 36
開発者は、インターネット技術特別調査委員会 (IETF) によって定義されたハイパーテキスト転送プロトコル (HTTP/11) に準拠した RESTful Web サービスからの応答を調べています。
この HTTP/1 複合 Web サービスでは、クライアント要求が Web サービスによって正常に受信、理解、受け入れられたことを示すために、どのクラスの HTTP 応答ステータス コードを指定する必要がありますか?
- A. 2xx
- B. 4xx
- C. 5xx
- D. 3xx
正解：A
解説：
In HTTP/1.1, response status codes are categorized to indicate the result of a client's request. Here's a detailed explanation of the 2xx class of HTTP response status codes:
* 2xx Success Codes:
* Definition: The 2xx class of status codes indicates that the client's request was successfully received, understood, and accepted by the server.
* Common Codes:
* 200 OK: The request has succeeded.
* 201 Created: The request has been fulfilled and resulted in a new resource being created.
* 202 Accepted: The request has been accepted for processing, but the processing is not complete.
* 204 No Content: The server successfully processed the request, but there is no content to
* return.
* Importance:
* Client Acknowledgment: These codes inform the client that their request was processed successfully, enabling appropriate client-side actions.
* RESTful Standards: Adhering to these standards ensures consistent and predictable API behavior.
References
* IETF RFC 7231: HTTP/1.1 Semantics and Content
* HTTP Status Codes:HTTP Status Code Definitions
質問 # 37
iPaaS (Integration-Platform-as-a-Service) の特徴は何ですか?
- A. コードファースト
- B. クラウドベース
- C. オンプレミス
- D. コードなし
正解：B
解説：
An Integration-Platform-as-a-Service (iPaaS) is characterized by being a cloud-based solution that provides tools to develop, execute, and manage integration flows connecting multiple applications and data sources.
Here's a detailed explanation:
* iPaaS:
* Definition: A suite of cloud services enabling the development, execution, and governance of integration flows.
* Deployment: Delivered and managed entirely in the cloud, offering high availability and scalability.
* Characteristics:
* Cloud-based: The platform is hosted on the cloud, allowing users to access and utilize the integration tools from anywhere with an internet connection.
* Managed Services: iPaaS providers handle infrastructure maintenance, updates, and security, freeing users to focus on integration development.
* Scalability: Easily scales to meet the demands of growing businesses without requiring additional on-premises infrastructure.
References
* iPaaS Overview: What is iPaaS?
* Cloud-based Integration: iPaaS Characteristics
質問 # 38
一般的な REST リクエストでは、API クライアント API 実装および API インターフェース コンポーネントはどのような順序で呼び出されますか?
- A. API クライアント > API インターフェース > API 実装
- B. API 実装 > API インターフェース > API クライアント
- C. API インターフェース > API クライアント > API 実装
- D. API クライアント > API 実装 > API インターフェース
正解：A
解説：
In a typical REST request, the components are called in a specific order to handle the client's request and provide the response. Here's the order and detailed explanation:
* API Client:
* Initiates Request: The client (e.g., web or mobile application) sends a request to the API endpoint.
* API Interface:
* Gateway/Proxy: This layer is typically managed by an API gateway or proxy, which handles the incoming request, applies security policies, and routes it to the appropriate backend service.
* Responsibilities: Includes request validation, rate limiting, authentication, and authorization.
* API Implementation:
* Backend Service: The actual implementation of the API logic resides here. It processes the request, interacts with the necessary databases or external services, and generates the response.
References
* REST API Design:RESTful Web Services
* API Gateway: What is an API Gateway?
質問 # 39
Anypoint Platform には、API の実装と管理の両方においてどのような生産性上の利点がありますか?
- A. API仕様の自動生成
- B. 自動 API セマンティック バージョン管理
- C. 自動APIプロキシ生成
- D. 自動 API ガバナンス
正解：C
解説：
Anypoint Platform, MuleSoft's unified platform for API design and integration, offers several productivity advantages for both implementing and managing APIs. Among these features, automatic API proxy generation is particularly beneficial. Here's a step-by-step explanation:
* API Implementation:
* Design Center: In the Design Center, users can create API specifications using RAML or OAS.
This environment provides tools to design and document APIs effectively.
* Exchange: After defining the API, it can be published to Anypoint Exchange where it can be shared and discovered by others within the organization.
* Automatic API Proxy Generation:
* When an API is published to Exchange, Anypoint Platform allows for the automatic creation of an API proxy. An API proxy acts as a facade for your backend API, providing a layer of abstraction and security.
* Advantages:
* Security: Protects backend services by exposing only necessary endpoints and handling authentication, authorization, and rate limiting.
* Traffic Management: Helps in managing traffic through throttling and caching.
* Monitoring: Facilitates monitoring and logging to track API usage and performance.
* This automation saves time and reduces the complexity of manual proxy setup, allowing developers to focus on core business logic.
* API Management:
* API Manager: Provides a dashboard to manage API policies, versions, and SLA tiers. Users can apply security policies, monitor traffic, and analyze API usage.
* Monitoring: Integrated with Anypoint Monitoring, users get insights into API performance and health, enabling proactive management.
References
* MuleSoft Documentation: API Proxies
* MuleSoft Anypoint Platform Overview: Anypoint Platform
質問 # 40
配信品質を向上させるために、MuleSoft 統合チームはどの主要な DevOps プラクティスと関連する Anypoint Platform コンポーネントを採用する必要がありますか?
- A. MUnit による自動テスト
- B. Anypoint Monitoring によるパッシブモニタリング
- C. Anypoint Studio を使用した手動テスト
- D. API デザイナーによる継続的な設計
正解：A
解説：
To improve delivery quality, a key DevOps practice is automated testing. Within the Anypoint Platform, MUnit is the tool specifically designed for this purpose. Here's a step-by-step explanation:
* Automated Testing:
* Definition: Automated testing involves using software tools to execute tests on the application automatically, ensuring that the code works as expected.
* Benefits: It increases efficiency, consistency, and coverage of tests, reducing the risk of human error.
* MUnit:
* Integration Testing: MUnit is MuleSoft's integrated testing framework for applications built with Anypoint Studio. It allows developers to create and run tests for Mule applications, ensuring they function correctly.
* Features:
* Test Cases: Create comprehensive test cases to validate various parts of the Mule application.
* Mocking: Mock external systems and dependencies, enabling isolated testing of application components.
* Assertions: Validate the behavior of Mule flows with assertions.
* Implementation Steps:
* Design Tests: Within Anypoint Studio, design MUnit tests to cover different scenarios and edge cases of the Mule flows.
* Run Tests: Execute these tests automatically during the CI/CD pipeline to ensure that new code changes do not break existing functionality.
* Continuous Integration: Integrate MUnit tests with CI tools like Jenkins, Bamboo, or GitLab CI for continuous testing.
References
* MuleSoft Documentation: MUnit
* DevOps Practices: MuleSoft DevOps
質問 # 41
CloudHub はどのクラウド コンピューティング サービス モデルの例ですか?
- A. サービスとしてのソフトウェア (SaaS)
- B. サービスとしてのプラットフォーム (PaaS)
- C. サービスとしてのモニタリング (MaaS)
- D. サービスとしてのインフラストラクチャ (laaS)
正解：B
解説：
CloudHub is MuleSoft's integration platform as a service (iPaaS) offering. It provides a platform for deploying and managing integration applications in the cloud. Here's a detailed explanation:
* Platform as a Service (PaaS):
* Definition: PaaS provides a cloud-based environment with everything required to support the complete lifecycle of building and deploying web applications and services without the complexity of managing the underlying hardware and software layers.
* CloudHub Features:
* Deployment: Simplifies the deployment of Mule applications to the cloud.
* Management: Provides tools for managing application performance, scaling, and monitoring.
* Connectivity: Offers out-of-the-box connectors and integration capabilities for various systems and services.
* Benefits:
* Scalability: Automatically scales applications based on demand.
* Availability: Ensures high availability and reliability with built-in disaster recovery and failover capabilities.
* Security: Provides robust security features to protect data and applications.
References
* MuleSoft Documentation: CloudHub
* Cloud Computing Models:PaaS Overview
質問 # 42
......
合格させるSalesforce MuleSoft-Integration-Associate日本語テスト練習問題 試験問題集：https://www.passtest.jp/Salesforce/MuleSoft-Integration-Associate-JPN-shiken.html