サンプル問題 1： A ListView shows related Policies for a policyholder. When a user clicks a Policy Number in a text cell, the UI should open a Popup showing details of that specific policy. The elementName property in the row iterator is currentPolicy. What is the correct syntax to open the popup?
A: Modify the Action property on the atomic widget to PolicyPopup.go(currentPolicy)
B: Modify the actionAvailable property on the atomic widget to PolicyPopup(currentPolicy)
C: Modify the actionAvailable property on the atomic widget to PolicyPopup.push(currentPolicy)
D: Modify the Action property on the atomic widget to PolicyPopup.push(currentPolicy)
正解：D
Explanation: In Guidewire PCF Configuration, navigating between different parts of the application requires a clear understanding of Location types and their corresponding Gosu methods. When a requirement specifically calls for a Popup, the developer must use the .push() method. The .push() method is used for” modal” or” semi-modal” navigation. It places the new location (the Popup) on top of the current navigation stack, allowing the user to perform a task and then return exactly where they were when the popup is dismissed. In contrast, the .go() method (seen in Option A) is used for” terminal” navigation, which replaces the current location entirely; it is used for moving between main Pages or Location Groups. Using .go() for a popup would violate the intended UI flow and likely result in a runtime error or unexpected navigation behavior. Furthermore, the logic to trigger this navigation must be placed in the Action property of the widget (typically a TextCell or Link). The actionAvailable property (Options B and C) is a Boolean expression used only to determine if the action is clickable (i.e., whether the link is active or grayed out based on permissions or data state); it cannot execute the navigation itself. By specifying PolicyPopup.push(currentPolicy) in the Action property, the developer ensures that the currentPolicy object (defined by the RowIterator’s elementName) is passed as a parameter to the popup, allowing it to display the correct details. This follows the standard PCF Architecture for drill-down interactions
サンプル問題 2： A developer wants to manually trigger a build chain in TeamCity to generate a deployable Docker image for a specific commit. According to the process described in the training, what are the key initial steps to achieve this? (Choose 2)
A: Update the application’s configuration resources in Lifecycle Manager.
B: Access the Automated Builds app in Guidewire Home.
C: Access TeamCity via Guidewire Home.
D: Configure a new monitor in Datadog.
E: Select the desired build configuration and trigger the build.
正解：A, C, E
Explanation: In the Guidewire Cloud (GWCP) ecosystem, the CI/CD pipeline is centrally managed through Guidewire Home, which serves as the primary portal for developers to access cloud-native tools. To generate a deployable Docker image, a developer must interact with the build server, which is TeamCity. The first critical step is navigating to TeamCity via the link or tile provided in Guidewire Home (often labeled under” Automated Builds” ). This ensures the developer is authenticated within the secure Guidewire Cloud environment. Once inside TeamCity, the developer must locate the specific Build Configuration associated with the project and branch they intend to build. Because a Docker image is specific to a commit, the developer must ensure they are triggering the correct” build chain.” A build chain in Guidewire Cloud typically involves several stages, including compiling the Gosu code, running unit tests (GUnit), and finally packaging the application into a Docker container. Manually triggering the build (Step E) involves clicking the” Run” button, often after specifying a specific branch or commit hash to ensure the resulting image contains the correct code changes. This process is distinct from Lifecycle Manager (LCM), which is used for managing environment-specific configurations (like database settings or API keys) and promoting already-built images to specific” Planets” (Dev, Pre-Prod, etc.). Datadog (Option D) is used for post-deployment observability and would not be used to trigger an image build. Therefore, the combination of accessing the correct tool and manually initiating the build configuration is the verified procedure for cloud developers.
サンプル問題 3： In the Extensions folder, there is a typelist file named BusinessType.ttx containing three typecodes: Insurer, Broker, and Agency. The business analysts have requested an additional typecode: Reinsurer. How should this typecode be added?
A: Create a reinsurer_Ext typecode in BusinessType.ttx
B: Create a reinsurer typecode in BusinessType.ttx
C: Create a .ttx extension file and add a reinsurer_Ext typecode to it
D: Create a Reinsurer_Ext typelist with a reinsurer typecode
正解：B
Explanation: When managing Typelists (Guidewire’s version of enumerations) in a Cloud-compliant environment, there is a distinct difference between adding codes to an existing typelist and creating an entirely new one. According to the InsuranceSuite Developer Fundamentals curriculum, if you are adding a new code to an existing typelist that is already an extension (indicated by the .ttx file extension), you simply add the new code to that existing .ttx file. One of the most common points of confusion is the use of the _Ext suffix. While new entities and new typelists require the _Ext suffix to follow Cloud Delivery Standards, individual typecodes (the values within the list) generally do not require the suffix unless the specific project guidelines demand it for every single metadata element. In standard Guidewire practice, a typecode named reinsurer (Option B) is sufficient and cleaner. Option C is incorrect because you should not create multiple .ttx files for the same typelist; you should consolidate extensions into the existing one. Option D is incorrect because it suggests creating a whole new list rather than modifying the existing one. Option A is less ideal because adding _Ext to individual codes within a list is not a mandatory platform requirement and can make logic like TC_REINSURER_EXT cumbersome to write in Gosu.
