Computer Networks

By default, all ports on a switch belong to a single broadcast domain. Broadcast frames are forwarded out all ports except the originating port. VLANs can create multiple broadcast domains, but a basic switch has one.

By default, all ports on a switch belong to a single broadcast domain. Broadcast frames are forwarded out all ports except the originating port. VLANs can create multiple broadcast domains, but a basic switch has one.

A basic switch (without VLANs) has exactly ONE broadcast domain. All ports on a switch belong to the same broadcast domain, meaning broadcast frames are flooded to all ports. This is different from collision domains where each switch port is a separate collision domain. Broadcast domains can be segmented using VLANs, but a default single-switch configuration has one broadcast domain.

In Informatica PowerCenter, a Router is an active transformation because it can change the number of rows that pass through it (e.g., dropping rows that do not match any group condition). Passive transformations must preserve the row count and row identity.

The Data Bus is bidirectional because it carries data both from the CPU to memory/devices (write operations) and from memory/devices to the CPU (read operations). The Address Bus is unidirectional (CPU to memory, carrying address information), and the Control Bus carries signals in one direction at a time (CPU controlling devices or status signals back to CPU).

On a home/single system with no network, Map Network Drive has nothing to connect to. The tool requires network infrastructure - either domain/workgroup membership or direct network path access. Without these, clicking the menu option does nothing because there are no network resources to map.

A Wide Area Network (WAN) connects networks over large distances, typically using high-speed telephone lines or leased lines. LANs cover small areas like buildings, URL is an address format, and World Wide Web is a service that runs over networks.

The false statement is that many Routers of the same name may exist in a single Visio flow - router names must be unique within a flow. Routers do tell Assignments where to go (A is true), Routers are not required on every Assignment (B is true - you can use connectors directly), and Routers execute specific Activities to determine routing (C is true). Option D is the false statement.

Statement A is false because Routers provide general routing logic and conditions, but they don't specify exact destinations. The flow engine determines the final assignment based on the Router's evaluation. Routers set up the decision tree but don't hard-code every destination, allowing for more flexible and reusable routing logic.

Routers can only be attached to Assignments in PEGA flows. Routers provide conditional routing logic for assignments, determining which path the flow should take after an assignment is completed. Utilities and Start Flow shapes are not valid attachment points for Routers - the routing logic is specifically designed to work with assignment-based decision points.

In workflow and process modeling systems, a Utility component is a versatile node that can emit various types of connectors: Always connectors for unconditional flow, When connectors for conditional triggers based on events, Status connectors that activate based on state changes, and Else connectors as default paths. This flexibility makes Utility components highly reusable in workflow design.

In Pega PRPC, Utility shapes support multiple connector types: Always (unconditional execution), When (conditional based on criteria), Status (based on flow status codes), and Else (fallback when no When conditions match). All four types can emanate from a Utility shape.

Utility shapes in Pega flows can have multiple types of connectors that determine when the utility activity executes. These include Always connectors (unconditional), When connectors (condition-based), Status connectors (based on work object status), and Else connectors (fallback). All these connector types can emanate from a Utility shape.

Routers in Pega are specifically designed to direct assignments to their destinations - whether to a workbasket, a specific user, or based on complex criteria. This statement about routers telling assignments where to go is TRUE and describes their fundamental purpose. The other statements are actually true: routers aren't required on every assignment (optional), they execute activities to determine routing, and multiple routers with the same name can exist in a flow.