[2024年01月17日]1z0-1091-22練習試験問題集で試験99%合格率があります
最新の検証済み1z0-1091-22問題と解答、合格保証もしくは全額返金
Oracle 1z0-1091-22 認定試験の出題範囲：
| トピック | 出題範囲 |
|---|---|
| トピック 1 |
|
| トピック 2 |
|
| トピック 3 |
|
| トピック 4 |
|
| トピック 5 |
|
| トピック 6 |
|
| トピック 7 |
|
| トピック 8 |
|
| トピック 9 |
|
質問 # 26
Why would you use an eligibility criteria in usage subscription?
- A. To configure an optional usage group within a usage subscription.
- B. To configure an optional usage calculation rule within a usage calculation group for the usage.
- C. To configure an optional validation group within a usage subscription.
- D. To determine whether a usage subscription generates a usage transaction.
正解：D
解説：
Explanation
A usage subscription is a record that defines how usage data are collected, processed, and exported for a service point or a device. A usage subscription can have various components that specify the logic and parameters for performing various operations on usage data, such as validation, estimation, editing, calculation, or export. According to the Oracle Utilities Meter Data Management Business User Guide, one example of a component that can be configured in a usage subscription is:
* Eligibility criteria: These are rules that determine whether a usage subscription generates a usage transaction or not. A usage transaction is a record that contains usage data that are ready for export to other systems, such as customer information system (CIS) or settlement system. Eligibility criteria can be used to filter out usage subscriptions that do not meet certain conditions or requirements for generating usage transactions.
References: Oracle Utilities Meter Data Management Business User Guide, Chapter 8: Usage, Section 8.1:
Usage Subscriptions
質問 # 27
The Vector and Service Quantity Math usage rule facilitates the configuration of complex vector calculations.
It is based on a series of underlying services with vectors configured as input to the calculations.
What are THREE typical uses of the usage rule?
- A. Performing Array math
- B. Performing math formulas on interval data
- C. Finding max values
- D. Converting interval data to scalar reads
- E. Finding coincident peaks
正解：A、B、E
解説：
Explanation
The Vector and Service Quantity Math usage rule facilitates the configuration of complex vector calculations.
It is based on a series of underlying services with vectors configured as input to the calculations. Some typical uses of the usage rule are:
* Finding coincident peaks: This is a calculation that finds the highest demand value for each interval across multiple service points or devices.
* Performing Array math: This is a calculation that performs arithmetic operations on arrays of interval data, such as addition, subtraction, multiplication, or division.
* Performing math formulas on interval data: This is a calculation that performs mathematical functions on interval data, such as logarithm, exponentiation, square root, or trigonometry.
Finding max values is not a typical use of the Vector and Service Quantity Math usage rule. Finding max values is a simple calculation that finds the highest demand value for each service point or device.
Converting interval data to scalar reads is not a typical use of the Vector and Service Quantity Math usage rule. Converting interval data to scalar reads is done by using other usage rules, such as Interval Data Scalar Read Rule.
質問 # 28
Which THREE statements are true about the Subtractive Interval Data functionality?
- A. A new reading condition field ensures that you do not lose the reading quality when a meter's consumption is estimated.
- B. The IMD load processes calculate consumption in engineering units.
- C. It validates consumption in initial measurement data (IMD).
- D. You can optionally validate for rollover exceptions and negative consumption calculations.
- E. It converts engineering units into reads.
正解：A、B、D
解説：
Explanation
The Subtractive Interval Data functionality is a feature that enables Meter Data Management (MDM) to process interval data from devices that do not provide interval readings, but only cumulative readings. The Subtractive Interval Data functionality performs the following actions:
* The IMD load processes calculate consumption in engineering units: The IMD load processes are batch processes that load initial measurement data (IMD) records from smart meter systems or other sources into MDM. The IMD load processes calculate consumption in engineering units by subtracting consecutive cumulative readings and applying conversion factors.
* A new reading condition field ensures that you do not lose the reading quality when a meter's consumption is estimated: A reading condition field is an attribute that indicates the quality or status of a measurement, such as valid, invalid, estimated, or substituted. A new reading condition field called Original Reading Condition is added to store the original reading condition of a cumulative reading when its consumption is estimated by using VEE rules.
* You can optionally validate for rollover exceptions and negative consumption calculations: You can configure VEE rules to check for rollover exceptions and negative consumption calculations when processing subtractive interval data. A rollover exception occurs when a cumulative reading reaches its maximum value and resets to zero. A negative consumption calculation occurs when a cumulative reading decreases instead of increasing.
It is not true that it validates consumption in initial measurement data (IMD), which are records that store the raw measurement data that is received from smart meter systems or other sources. Subtractive Interval Data functionality does not validate consumption in IMD, but calculates consumption from cumulative readings.
It is not true that it converts engineering units into reads, which are values that are recorded by devices at certain intervals or events. Subtractive Interval Data functionality does not convert engineering units into reads, but calculates consumption in engineering units from cumulative readings.
質問 # 29
Which THREE are best practices for measurement retention?
- A. Use Information Lifecycle Management (ILM) processes to help archive data.
- B. Keep scalar measurements in the customer read tables to stay consistent.
- C. Keep initial measurement data (IMD) for the same period of time as final measurements for cancel rebill purposes.
- D. Derive time-of-use (TOU) values with interval data to prevent storing extra data.
- E. Derive demand from interval data to prevent storing extra data.
正解：A、D、E
解説：
Explanation
Some of the best practices for measurement retention are:
* Derive time-of-use (TOU) values with interval data to prevent storing extra data: Time-of-use (TOU) values are scalar values that are calculated from interval data based on different TOU periods. Interval data is measurement data that is recorded at regular intervals, such as every 15 minutes or every hour.
To prevent storing extra data, you can derive TOU values with interval data instead of storing them separately.
* Derive demand from interval data to prevent storing extra data: Demand is a value that indicates the maximum power or load that is consumed or generated during a certain period. Demand can be calculated from interval data by using certain methods, such as block demand or rolling demand. To prevent storing extra data, you can derive demand from interval data instead of storing them separately.
* Use Information Lifecycle Management (ILM) processes to help archive data: Information Lifecycle Management (ILM) processes are features that enable MDM to manage the lifecycle of measurement data based on certain policies or rules. ILM processes can help archive data that is no longer needed or used by moving them to different storage tiers or deleting them.
You do not need to keep scalar measurements in the customer read tables to stay consistent, which are tables that store measurement data that is entered by customers or meter readers. Scalar measurements are measurement data that are recorded at certain events, such as billing cycle end or meter exchange. You can store scalar measurements in different tables based on their source or status.
You do not need to keep initial measurement data (IMD) for the same period of time as final measurements for cancel rebill purposes, which are records that store the raw measurement data that is received from smart meter systems or other sources. Final measurements are records that store the measurement data that has been validated, edited, and estimated. You can keep IMD for a shorter period of time than final measurements based on your business needs or requirements.
質問 # 30
In the SaaS solution, how should you configure equipment that attaches to an asset, such as a communication module attached to a meter?
- A. Set up a component
- B. Create a master child asset
- C. Add a sub-asset
- D. Add a constituent part
正解：A
解説：
Explanation
To configure equipment that attaches to an asset, such as a communication module attached to a meter, you should set up a component. A component is a part of an asset that can be installed and removed independently of the asset. You can define component types and associate them with asset types. For example, you can define a communication module component type and associate it with a meter asset type2.
You do not need to create a master child asset, which is a relationship between two assets that are installed at different service points but are functionally related. For example, you can define a transformer as a master asset and a meter as a child asset2. A master child asset is not suitable for equipment that attaches to an asset.
You do not need to add a sub-asset, which is an asset that is installed at the same service point as another asset but has its own measuring components and usage subscriptions. For example, you can define a meter as a sub-asset of another meter if they share the same service point but have different measurements2. A sub-asset is not suitable for equipment that attaches to an asset.
You do not need to add a constituent part, which is an attribute of an asset that cannot be installed or removed independently of the asset. For example, you can define a battery as a constituent part of a meter if it is embedded in the meter and cannot be replaced . A constituent part is not suitable for equipment that attaches to an asset.
質問 # 31
Which THREE commands are supported by the Smart Grid Gateway (SGG) adapters?
- A. Connect
- B. On-demand reading
- C. Disconnect service at pole
- D. Ping meter
- E. Request outage information
正解：A、B、D
解説：
Explanation
Smart Grid Gateway (SGG) is a product that provides integration between Oracle Utilities Meter Data Management and various head-end systems that communicate with smart meters. SGG supports different types of commands that can be sent to smart meters to perform various actions, such as reading, pinging, connecting, or disconnecting. According to the Oracle Utilities Smart Grid Gateway User Guide, some examples of commands that are supported by the SGG adapters are:
* On-demand reading: This is a command that requests a smart meter to send its current or historical usage data to the head-end system. On-demand reading can be used for billing purposes or for verifying meter readings.
* Ping meter: This is a command that tests the communication between the head-end system and the smart meter. Ping meter can be used for troubleshooting purposes or for checking meter status.
* Connect: This is a command that enables the service at a smart meter. Connect can be used for activating service for a new customer or for restoring service after a payment.
References: Oracle Utilities Smart Grid Gateway User Guide, Chapter 4: Commands, Section 4.1: Command Types
質問 # 32
Which THREE Validation, Estimation, and Editing (VEE) rules are provided by the base Meter Data Management (MDM) product that you can include in a VEE group?
- A. Negative consumption check
- B. Interval averaging
- C. Estimate data based on nearby addresses
- D. Positive consumption check
- E. High/low check
正解：A、D、E
解説：
Explanation
The base Meter Data Management (MDM) product provides several Validation, Estimation, and Editing (VEE) rules that you can include in a VEE group. A VEE group is a collection of VEE rules that are used to validate, estimate, and edit measurements based on certain criteria. Some of the VEE rules that are provided by the base MDM product are:
* Positive consumption check: This is a rule that checks if the consumption value of a measurement is positive. If the consumption value is negative, the rule flags the measurement as invalid and estimates a new value based on historical data or other methods.
* Negative consumption check: This is a rule that checks if the consumption value of a measurement is negative. If the consumption value is positive, the rule flags the measurement as invalid and estimates a new value based on historical data or other methods.
* High/low check: This is a rule that checks if the consumption value of a measurement is within a predefined range. If the consumption value is above or below the range, the rule flags the measurement as invalid and estimates a new value based on historical data or other methods.
Estimate data based on nearby addresses is not a VEE rule that is provided by the base MDM product. This is a custom VEE rule that can be developed by using Groovy scripting language or Java programming language.
Interval averaging is not a VEE rule that is provided by the base MDM product. This is a usage calculation rule that is used to calculate derived values from interval measurements by averaging them over a certain period.
質問 # 33
Which TWO functions can the service point-measurement cycle relationship of Meter Data Management (MDM) perform?
- A. Initiate request of bill determinants from subscribing systems.
- B. Create optimal meter reader routes by measurement cycle.
- C. Initiate push of bill determinants ta subscribing systems.
- D. Create hand-held download read activities.
正解：A、C
解説：
Explanation
The service point-measurement cycle relationship of Meter Data Management (MDM) can perform the following functions:
* Initiate request of bill determinants from subscribing systems: A subscribing system is an external system or service provider that receives bill determinants from MDM. A bill determinant is a value that is used to calculate a bill for a service point or device. The service point-measurement cycle relationship can initiate a request of bill determinants from subscribing systems based on the measurement cycle schedule. A measurement cycle schedule defines the dates on which devices are scheduled to be read for a given measurement cycle. A measurement cycle defines the schedule for manual meter reading of devices at service points in that cycle.
* Initiate push of bill determinants to subscribing systems: The service point-measurement cycle relationship can also initiate a push of bill determinants to subscribing systems based on the measurement cycle schedule. This means that MDM can send bill determinants to subscribing systems automatically or on demand.
The service point-measurement cycle relationship cannot perform the following functions:
* Create optimal meter reader routes by measurement cycle: A meter reader route is a sequence of service points or devices that are assigned to a meter reader formanual meter reading. A meter reader route is not created by the service point-measurement cycle relationship, but by using other configurations, such as route type or route sequence.
* Create hand-held download read activities: A hand-held download read activity is an activity that downloads measurement data from a hand-held device to MDM. A hand-held download read activity is not created by the service point-measurement cycle relationship, but by using other configurations, such as activity type or activity status.
質問 # 34
In which THREE situations would you use a dynamic option?
- A. The utility has a program where customers can optionally participate in demand response (DR) programs.
- B. An option is specified on a service point to allow Validation, Estimation, and Editing (VEE) processing to dynamically invoke a group of VEE rules depending on a characteristic.
- C. A consumer receives credit for consumption during a critical peak period (CPP) event that is lower than their "normal* consumption.
- D. The scalar meter-read download process creates an activity each time a scalar measuring component is scheduled to be read.
- E. The utility has a program that credits customers for conservation during critical peak periods.
正解：A、B、E
解説：
Explanation
A dynamic option is an option that is assigned to an entity at run time based on a characteristic value. Dynamic options are used to provide flexibility and customization for different scenarios. According to the Oracle Utilities Meter Solution Cloud Service Business User Guide, some examples of dynamic options are:
* The utility has a program where customers can optionally participate in demand response (DR) programs. A dynamic option is specified on a usage subscription to allow different DR programs to be applied depending on a characteristic value such as customer class or rate schedule.
* An option is specified on a service point to allow Validation, Estimation, and Editing (VEE) processing to dynamically invoke a group of VEE rules depending on a characteristic. For example, if the service point has a characteristic indicating that it is part of a net metering program, then a different set of VEE rules may be applied than for a regular service point.
* The utility has a program that credits customers for conservation during critical peak periods. A dynamic option is specified on a usage subscription to allow different credit calculations to be applied
* depending on a characteristic value such as customer class or rate schedule.
References: Oracle Utilities Meter Solution Cloud Service Business User Guide, Chapter 2: Options and Characteristics, Section 2.1: Options
質問 # 35
How do you configure the derived values that are relevant for a device?
- A. Configure the derived values an the final measurement type for the measuring components to be defined on the device.
- B. Configure the derived values on the device type for the derived values to be defined on the device.
- C. Configure the derived values on the measuring component for the measuring components to be defined on the device.
- D. Configure the derived values on the measuring component type for the measuring components to be defined on the device.
正解：D
解説：
Explanation
To configure the derived values that are relevant for a device, you should configure them on the measuring component type for the measuring components to be defined on the device. A measuring component type defines the type of measurement that a device can record, such as scalar, interval, or event. A measuring component type can also define the derived values that are calculated from raw measurements based on certain rules or factors. A measuring component is an instance of a measuring component type that is associated with a device.
You do not need to configure the derived values on the final measurement type, which defines how measurements are stored and processed in Oracle Utilities Meter Data Management. Final measurement types do not define derived values.
You do not need to configure the derived values on the device type, which defines the physical characteristics and attributes of a device, such as manufacturer, model, or serial number. Device types do not define derived values.
You do not need to configure the derived values on the measuring component, which is an instance of a measuring component type that is associated with a device. Measuring components inherit derived values from their measuring component types.
質問 # 36
In SaaS, which THREE configuration steps would you perform to convert natural gas volume to energy at the measuring component level?
- A. Configure a value derivation algorithm by using Groovy.
- B. Set up a factor to hold the conversion values.
- C. Create value identifiers far the energy Unit of Measure (UOM) on the device.
- D. Configure a value derivation algorithm by using Java.
- E. Create value identifiers far the energy UOM on the measuring component type.
正解：A、B、E
解説：
Explanation
To convert natural gas volume to energy at the measuring component level, you should perform the following configuration steps:
* Set up a factor to hold the conversion values: A factor is a value that is used to adjust or convert measurements based on certain criteria. You need to set up a factor to hold the conversion values that are used to convert natural gas volume to energy. For example, you can set up a factor that holds the heating value of natural gas in different units of measure (UOM).
* Configure a value derivation algorithm by using Groovy: A value derivation algorithm is a rule that is used to calculate derived values from raw measurements based on certain factors or formulas. You need to configure a value derivation algorithm by using Groovy scripting language to define how natural gas volume is converted to energy by applying the conversion factor.
* Create value identifiers for the energy UOM on the measuring component type: A value identifier is an attribute that is used to store measurement or derived values in different UOMs. You need to create value identifiers for the energy UOM on the measuring component type that is used for natural gas devices. For example, you can create value identifiers for energy in British thermal units (BTU) or kilowatt-hours (kWh).
You do not need to create value identifiers for the energy UOM on the device, which is an instance of a device type that is installed at a service point. Value identifiers are defined at the measuring component type level, not at the device level.
You do not need to configure a value derivation algorithm by using Java, which is a programming language that is used to develop custom applications or extensions. Value derivation algorithms are configured by using Groovy scripting language, not Java.
質問 # 37
For a Meter Data Management (MDM) implementation, a customer requires specific bill determinants along with bill determinant calculation validations to be executed, before the determinant values are exported to their customer information system (CIS).
Which THREE factors should you consider while configuring usage calculation groups?
- A. Device subscriptions
- B. Bill determinants or usage calculations
- C. CIS rates, that MDM bill determinants or the usage process are expected to support
- D. Bill determinants or usage validations
- E. Type of measurement (interval or scalar) data that needs to be used for bill determinants or usage calculation
正解：C、D、E
解説：
Explanation
Usage calculation groups are used to define how usage data are calculated, validated, and exported for different purposes, such as billing, settlement, or analysis. Usage calculation groups can have different components that specify the logic and parameters for performing various operations on usage data. According to the Oracle Utilities Meter Data Management Business User Guide, some examples of components that can be configured in usage calculation groups are:
* CIS rates: These are rate schedules that are defined in the customer information system (CIS) and imported into Oracle Utilities Meter Data Management. CIS rates can be used to specify which bill determinants or usage calculations should be applied for different rate schedules or customer classes.
* Bill determinants or usage validations: These are rules that check the quality or accuracy of usage data and assign condition codes or flags to indicate any issues or errors. Bill determinants or usage validations can be used to ensurethat usage data meet certain criteria or standards before they are exported to CIS or other systems.
* Bill determinants or usage calculations: These are rules that perform various calculations or adjustments on usage data, such as dividing usage into time-of-use periods, applying factors or multipliers, or deriving net usage. Bill determinants or usage calculations can be used to generate different types of bill determinants for billing purposes.
References: Oracle Utilities Meter Data Management Business User Guide, Chapter 8: Usage, Section 8.2:
Usage Calculation Groups
質問 # 38
Which relationship must be established with an external system or a service provider before creating bill determinants in Meter Data Management (MDM)?
- A. Usage subscription
- B. Usage rule
- C. Usage factor
- D. Usage transaction
正解：A
解説：
Explanation
A usage subscription is a relationship that must be established with an external system or a service provider before creating bill determinants in Meter Data Management (MDM). A usage subscription defines the external system or service provider that will receive the bill determinants, the usage calculation group that will be used to calculate the bill determinants, and the service points that will provide the measurement data for the bill determinants.
You do not need to establish a usage factor, a usage transaction, or a usage rule with an external system or a service provider before creating bill determinants. A usage factor is a value that is used to adjust or convert measurements based on certain criteria. A usage transaction is a record that stores the bill determinants and other usage information for a usage subscription. A usage rule is a rule that is used to calculate, validate, or estimate bill determinants based on certain criteria.
質問 # 39
A business needs a new Service Order process that includes meter commands. Which THREE options should you configure to build this process?
- A. Measuring component type
- B. Device configuration type
- C. Activity type
- D. Communication type Message sender
正解：A、C、D
解説：
Explanation
To build a new Service Order process that includes meter commands, you need to configure the following options:
* Measuring component type: This defines the type of measurement that a device can record, such as scalar, interval, or event. You can associate meter commands with measuring component types to perform actions on devices that have those types1.
* Activity type: This defines the type of work that needs to be performed on a service point or device, such as installation, removal, or inspection. You can associate meter commands with activity types to trigger actions on devices when an activity is completed1.
* Communication type Message sender: This defines the communication channel and protocol that is used to send meter commands to devices. You can configure message senders for different communication types, such as AMI, AMR, or manual1.
You do not need to configure device configuration type, which defines the physical characteristics and attributes of a device, such as manufacturer, model, or serial number1. Device configuration type does not affect meter commands.
質問 # 40
Momentary outages are very short-term outages where an outage event is sent and a restoration event is received in less than a few minutes.
Which TWO system components would you configure to ignore momentary outages?
- A. AMI commands
- B. Device events
- C. Activities
- D. Reporting categories
正解：B、C
解説：
Explanation
Momentary outages are very short-term outages where an outage event is sent and a restoration event is received in less than a few minutes. These outages may not requireany action from the utility and may be ignored for reporting or analysis purposes. According to the Oracle Utilities Meter Solution Cloud Service Business User Guide, two system components that can be configured to ignore momentary outages are:
* Device events: These are events that are sent by smart meters to indicate various conditions or situations, such as outages, tampering, or alarms. Device events can be configured with a minimum duration parameter that specifies the minimum time difference between an event start and an event end for the event to be processed. If the event duration is less than the minimum duration, the event is ignored.
* Activities: These are tasks that are created by the system or by users to perform various actions, such as meter reading, installation, or maintenance. Activities can be configured with a momentary outage threshold parameter that specifies the maximum time difference between an outage event and a restoration event for the activity to be created. If the outage duration is less than the momentary outage threshold, no activity is created.
References: Oracle Utilities Meter Solution Cloud Service Business User Guide, Chapter 5: Device Management, Section 5.2: Device Events; Chapter 6: Device Installations, Section 6.4: Activities
質問 # 41
When used with the SaaS Cloud services, the Oracle Smart Grid Gateway (SGG) adapters process usage and device event payloads via batch processing. Files are sent from a head-end system (HES) to an Oracle Cloud Object Storage location, where they are batch processed.
Which THREE operations are performed by the SGG processes?
- A. Parse payload into individual usage readings/device events.
- B. Load reads into a file directory.
- C. Transform usage readings into standard (unified) format.
- D. Invoke IMD/Device Event Seeder (as appropriate).
- E. Load reads into Object Storage.
正解：A、C、D
解説：
Explanation
In a SaaS environment, Oracle Utilities Meter Data Management and Smart Grid Gateway are deployed on Oracle Cloud Infrastructure (OCI) and use OCI Object Storage to store files and data. OCI Object Storage is a scalable and secure service that allows users to store and access data from anywhere using REST APIs or web consoles. Smart Grid Gateway adapters process usage and device event payloads via batch processing. Files are sent from a head-end system (HES) to an OCI Object Storage location, where they are batch processed.
According to the Oracle Utilities Smart Grid Gateway User Guide, some operations that are performed by the Smart Grid Gateway processes are:
* Parse payload into individual usage readings/device events. This is an operation that extracts usage readings or device events from the payload file and converts them into individual records.
* Invoke IMD/Device Event Seeder (as appropriate). This is an operation that invokes a web service that sends usage readings or device events to Oracle Utilities Meter Data Management for further processing.
* Transform usage readings into standard (unified) format. This is an operation that converts usage readings from vendor-specific formats into a standard format that can be processed by Oracle Utilities Meter Data Management.
References: Oracle Utilities Smart Grid Gateway User Guide, Chapter 4: Commands, Section 4.4: Command Configuration; Chapter 5: Device Events; Chapter 6: Usage
質問 # 42
Devices are often added to Meter Data Management (MDM) via a synchronization process. Device configuration business objects (BOs) can be configured to use Synchronization Add BO to determine the appropriate BO for the new device.
What is Synchronization Add BO associated with?
- A. Validation algorithm on Dl-Device Configuration BO
- B. Business service associated with Dl-Device Configuration BO
- C. Lifecycle algorithm on Dl-Device Configuration BO
- D. Options on Dl-Device Configuration BO
正解：C
解説：
Explanation
Synchronization Add BO is associated with the lifecycle algorithm on Dl-Device Configuration BO. A lifecycle algorithm is a custom logic that can be developed by using Groovy scripting language or Java programming language. A lifecycle algorithm is used to perform certain actions or validations when a business object is created, updated, or deleted. Synchronization Add BO is a parameter that can be configured on the lifecycle algorithm on Dl-Device Configuration BO. Synchronization Add BO is used to determine the appropriate business object for creating a new device based on certain criteria, such as device type or device configuration type.
Synchronization Add BO is not associated with the business service associated with Dl-Device Configuration BO, which is a component that provides the functionality and logic for processing data related to device configuration. Synchronization Add BO is not associated with the options on Dl-Device Configuration BO, which are configurable values that can be used to define business rules or relationships for device configuration. Synchronization Add BO is not associated with the validation algorithm on Dl-Device Configuration BO, which is a custom logic that can be developed by using Groovy scripting language or Java programming language. A validation algorithm is used to perform certain checks or validations on the data entered for device configuration.
質問 # 43
A time-of-use (TOU) template's interval size controls the values allowed as start and end times. A template can be used to generate TOU data for TOU maps whose seconds per interval (SPI) is divisible by the template's SPI.
For what can you use a 60-minute template?
- A. To only generate TOU data for minute TOU maps.
- B. To generate TOU data for 120-minute TOU maps.
- C. To generate TOU data for 6G-, 15-, and 5-minute TOU maps.
- D. To generate TOU data for 120-minute and 1440-minute TOU maps.
- E. To only generate TOU data for 30-minute TOU maps.
正解：A
解説：
Explanation
A time-of-use (TOU) template is used to define the start and end times of TOU periods for different days of the week and seasons of the year. A TOU template has an interval size that controls the values allowed as start and end times. For example, if the interval size is 60 minutes, then the start and end times must be multiples of
60 minutes, such as 00:00, 01:00, 02:00, and so on. A TOU template can be used to generate TOU data for TOU maps whose seconds per interval (SPI) is divisible by the template's SPI. For example, if the template's SPI is 3600 (60 minutes), then it can be used to generate TOU data for TOU maps whose SPI is 3600, 1800 (30 minutes), 1200 (20 minutes), 900 (15 minutes), 600 (10 minutes), 300 (5 minutes), and so on. Therefore, the correct answer is D.
References: Oracle Utilities Meter Solution Cloud Service Business User Guide, Chapter 4: Time-of-Use Data Management, Section 4.1: Time-of-Use Templates
質問 # 44
......
1z0-1091-22リアル有効かつ正確な問題集53問題と解答が待ってます：https://jp.fast2test.com/1z0-1091-22-premium-file.html