ISC ISSEP Exam Prep
ISSEP Information Systems Security Engineering Professional (Page 9 )

• Custom domain: miami.weyland.com requires a paid App Service tier; Free and Shared are unsuitable.
• Two instances: Standard supports scaling to multiple instances.
• SSL: Standard includes SSL support.
• 12 GB storage: Basic provides only about 10 GB, so it does not meet the requirement. Standard provides substantially more storage.
• Cost minimization: Standard is the lowest tier among the choices that satisfies all requirements.

• Identifies which user or department owns the device
• Supports inventory and compliance requirements
• Enables tracking of lost, stolen, retired, or unauthorized devices
• Helps enforce security controls such as mobile-device management and secure configuration

• Vulnerability scanner: Finds known technical weaknesses in systems or applications, but does not provide complete supply-chain visibility.
• Penetration test: Simulates attacks against defined targets; it is narrower than a full supply-chain analysis.
• SCAP: A set of standards and protocols for automated security configuration and vulnerability assessment, not a comprehensive supply-chain mapping tool.

• Active-active routers: Provide redundant Internet connections/devices. Both can operate, so traffic can fail over or be load-balanced.
• Active-active firewalls: Avoid a single firewall becoming a failure point while maintaining security inspection.
• Load balancers: Distribute requests across multiple web servers. If one server fails, traffic can go to the other.
• Redundant power supplies: A server with separate power supplies should connect to independent power sources or circuits.
• UPS A and UPS B: Provide backup power and redundancy. Ideally, each power supply is connected to a different UPS.
• SONET ring: A ring topology provides alternate paths if a fiber link or segment fails.

• Honeypots: Decoy systems designed to attract attackers. Legitimate users should not access them, so activity there is a strong indication of unauthorized access.
• DNS sinkholes: Redirect requests for known malicious domains to a controlled internal destination instead of the real attacker infrastructure. Security teams can then identify infected systems making those requests.

• Tokenization: Replaces sensitive data with non-sensitive tokens; it protects data but does not detect intruders.
• CI/CD: Software development and deployment processes.
• Threat modeling: Identifies potential threats before or during system design, rather than detecting successful infiltration.
• Data obfuscation: Makes information harder to understand, but is not an attacker-detection mechanism.

• Restrict a port to a defined number of MAC addresses
• Use statically assigned or “sticky” MAC addresses
• Shut down or restrict the port when violations occur

• Load balancer: Distributes application traffic; it does not protect switch MAC tables.
• IPS: May detect suspicious network activity, but is not the primary control for limiting switch MAC entries.
• NGFW: Filters traffic at the network boundary; it does not directly prevent MAC table flooding on access switches.

• # Development
• # Testing
• # Production

• Separate endpoints: relate to compute or connectivity, not dashboard labels.
• Separate queries: retrieve or transform data but do not designate visual sections.
• Direct text written into the dashboard in editing mode: dashboards use text boxes, typically with Markdown formatting, rather than arbitrary text placed directly on the canvas.

• Accept: Acknowledging the risk and choosing not to take additional action.
• Transfer: Shifting the risk or financial consequences to another party, such as an insurer.
• Mitigate: Reducing the likelihood or impact through controls, such as patching or access restrictions.
• Avoid: Eliminating the activity that creates the risk.

• Recovery Services vault — stores Site Recovery configuration and recovery metadata.
• Hyper-V site — represents the on-premises Hyper-V environment.
• Azure virtual network — the target network where the replicated VM will run after failover. Since Azure VMs already use the same virtual network, that VNet can be selected as the target.
• Storage account or managed-disk target, depending on the ASR configuration and portal version.
• Provider/agent on the Hyper-V server — enables replication from Hyper-V to Azure.

• The selling division receives a credit based on a favourable transfer price, often market price or full cost plus a profit margin.
• The receiving division is charged a lower amount, such as marginal cost or another agreed price.
• The difference is accounted for centrally by head office or a corporate adjustment.

• B — The most significant risks are held by SQ.

• C — SQ should recognise the cars as inventory.

• F — SQ recognises revenue when LM sells a car to a third party.

• A: LM does not hold the most significant risks.
• D: LM does not recognise the cars as inventory.
• E: SQ should not recognise revenue when cars are merely delivered to LM.

• What information each stakeholder needs
• When and how often it should be communicated
• Which format or channel should be used
• Who is responsible for communicating it

• A: The team should not decide stakeholder communications without first checking the established plan and CEO’s needs.
• B: An executive summary may be appropriate, but choosing a solution before reviewing the plan is premature.
• D: The stakeholder engagement plan addresses how to engage stakeholders, but this is primarily a communication planning issue.

• Record changes — a flow can start when a record is updated or otherwise changes.
• Schedules — a flow can run at a specified date/time or on a schedule.
• Record inserts — a flow can start when a new record is created.

• Subflows are reusable flow components called by another flow; they are not normally trigger types.
• Record views do not generally initiate a Flow Designer flow.

• Wireshark captures packets and allows you to examine their contents, potentially revealing usernames and passwords sent without encryption.
• Netcat creates network connections and can send or receive data, but it is not primarily a packet-analysis tool.
• Nessus scans for known vulnerabilities and configuration issues; it generally would not prove that credentials are visible in transit.
• Nmap performs network discovery and port/service scanning, not detailed packet-content inspection.

• A: CEO-sponsored formal policy — demonstrates executive support, but sponsorship at one point in time may not sustain commitment.
• B: Security awareness training — primarily improves employee behavior, not senior management commitment.
• C: Periodic alignment reviews — ongoing reviews show that security remains relevant, supports business priorities, and uses resources appropriately.
• D: Senior management signoff on the strategy — useful for governance and accountability, but signoff is generally a one-time event.

• Group1 — security-enabled: Eligible.
• Group2 — mail-enabled and security-enabled: Eligible because it is still a security group.
• Group3 — Microsoft 365 group: Not eligible for group-based licensing.
• Group4 — Microsoft 365 group, not security-enabled: Not eligible.

• Which host first communicated with the suspected malicious source
• Whether that host initiated suspicious traffic or merely received it
• Which other hosts show evidence of infection, such as connections from the originating host
• Which hosts have no related suspicious activity and are therefore clean

• An outbound connection to a suspicious external address
• A downloaded or executed malicious file
• Later lateral connections from that host to other internal systems
• Firewall logs showing the direction and timing of the traffic

• Third-party attestation: Provides independent validation, but is typically periodic and performed by an external party.
• Penetration testing: Simulates attacks to identify exploitable vulnerabilities; it does not primarily track compliance.
• Vulnerability scans: Identify technical weaknesses, but do not provide a detailed review of procedures or compliance activities.

• Relationship cardinality:

• Filter direction:

• Active versus inactive relationships: only active relationships automatically propagate filters.
• Blank or unmatched values: a fact-table value without a matching dimension row can create the model’s blank/unknown member.
• Uniqueness: the “one” side must contain unique values; duplicate keys generally belong on the “many” side.

• Key-based authentication: Provides an endpoint secured with API keys.
• Real-time REST access: Supports online inference through an HTTP/REST endpoint.
• No VM vCPU quota consumption: Microsoft hosts and manages the underlying infrastructure, so your subscription’s VM quota isn’t used.

• Batch: Intended for asynchronous, large-volume processing rather than real-time requests.
• Self-hosted container: You manage the infrastructure and typically need compute resources and quota.
• Standard: This is not the clearest deployment type for the stated requirements; the specific Foundry option is serverless API.

• Data source: Folder
• Transformation: Remove the Content column (or keep only the file-metadata columns)

Why

• File name
• Extension
• Date modified
• Folder path
• Content — the binary contents of the file

• Microsoft Purview portal: Create and manage sensitivity labels and configure support for sensitivity labels used with Office files in SharePoint and OneDrive.
• SharePoint admin center: Primarily manages SharePoint settings. Older guidance and PowerShell procedures used SharePoint tenant configuration, which can make this question confusing.
• IRM: Concerns Information Rights Management and is a separate protection mechanism; it should not be used to identify the portal for configuring Microsoft Purview sensitivity labels.

• CHAP: Uses a challenge-response exchange, so the password is not directly transmitted.
• IPsec: Provides authentication, integrity, and encryption for IP communications.
• EAP: An authentication framework that supports stronger methods, such as certificates or token-based authentication.

• Red team: Offensive security; attempts exploitation and simulates attackers.
• Blue team: Defensive security; monitors, detects, and responds to attacks.
• Purple team: Combines red- and blue-team activities to improve defenses, but is not the best direct answer here.
• White team: Usually oversees or coordinates an exercise, including rules of engagement and scope.

• Use the grant-date fair value: $30
• Do not remeasure to the year-end value of $45
• Update the estimate of employees expected to vest

• Dr Share-based payment expense $450,000
• Cr Equity/share option reserve $450,000

• sn_si_admin is an SIR administrator role.
• The prefix helps prevent naming conflicts between applications.
• It does not refer to a “Secure Identity token” or an instance security check.

• IKE (Internet Key Exchange) negotiates the IPsec security association, including:

• ESP (Encapsulating Security Payload) protects the data after negotiation by providing encryption and optionally authentication.
• AH provides authentication and integrity but does not encrypt traffic.
• TLS is used for protocols such as HTTPS, not for negotiating IPsec parameters.

• MTTC: Time required to contain or limit the incident’s impact — best match.
• MTTR: Time required to remediate or recover from the incident; this may include eradication, restoration, and cleanup, which goes beyond merely stopping spread.
• MTTD: How long it takes to discover the incident.
• MTBF: Average time between failures, generally a reliability metric.

• 255.255.255.128 = /25: 128 total, 126 usable
• 255.255.255.192 = /26: 64 total, 62 usable
• 255.255.255.224 = /27: 32 total, 30 usable
• 255.255.255.240 = /28: 16 total, 14 usable

• One for the network address
• One for the broadcast address

• 8 total addresses
• 6 usable addresses
• Mask: 255.255.255.248

• C — Some risks cannot be eliminated.

• D — Accepting residual risk does not imply recklessness.

• E — Most companies in this industry will say something similar.

• Marketing users: Dynamic Forms can show all fields.
• Support users: Field visibility rules can display only the Support preference fields on the record page.
• Reporting: Both profiles can still report on all fields because Dynamic Forms controls page visibility, not the underlying field access.

• A — Two record types and page layouts: Page layouts can control field placement and editability, but they are less flexible for conditional field visibility and would not be the best fit here.
• C — Muting permission set: Permission-set muting is used with permission-set groups; it does not conditionally hide fields on a page.
• D — Field-Level Security: FLS would remove field visibility at the security level. If fields are hidden by FLS, users generally cannot report on or access those fields, conflicting with the requirement that both users report on all data.

• PC A: 192.168.1.10/24
• PC B: 192.168.2.10/24

• Both PCs have a correct default gateway
• A router or Layer 3 switch connects the subnets
• Routing and firewall rules allow the traffic

• Design Studio > Emails ? create an email-template folder
• Design Studio > Landing Pages ? create a landing-page-template folder
• Add the relevant assets to each folder
• Right-click the folder and choose Share Folder
• Select the destination workspaces

• Crash cart: Provides local physical access, not remote access.
• Jump box: A secured intermediary used to reach devices over the normal network; it may be inaccessible if the appliance has not booted.
• Secure Shell (SSH): Requires the device’s operating system and network services to be running properly.

• The vulnerability scan identifies a vulnerability.
• The administrator verifies that the vulnerability is not present.
• Therefore, the scan produced a false positive.

• True positive: A vulnerability is reported and genuinely exists.
• False negative: A vulnerability exists, but the scan fails to detect it.
• True negative: No vulnerability exists, and the scan correctly reports no issue.

• Each Case must follow defined support steps.
• Each step must be completed within a specified time limit.

• Case Escalation Rules: Escalate Cases based mainly on age or criteria; they do not model a complete sequence of service steps.
• Process Builder with Scheduled Actions: Can automate time-based actions but is not the standard framework for Case service-level commitments.
• Omni-Channel Routing: Routes work to agents based on capacity and priority; it does not track Case lifecycle deadlines.

• Two-part tariff pricing: $10 per unit
• Dual pricing: $20 per unit

Two-part tariff pricing

Dual pricing

• Division X, the seller, is credited with the market price: \(\$20\)
• Division Y, the buyer, is charged the marginal cost: \(\$10\)

• Security controls
• Processes and procedures
• Compliance evidence
• Performance against contractual requirements

• Service-level agreement (SLA): Defines expected service performance, such as uptime and response times.
• Memorandum of agreement (MOA): Documents a general agreement between parties, but does not necessarily provide audit rights.
• Supply chain analysis: Identifies risks across suppliers and dependencies, but is not a contractual mechanism for reviewing vendor controls.

1. Yes — Microsoft Foundry provides a secure, governed environment for building and managing generative AI applications and agents. It brings together models, data, tools, evaluation, deployment, and monitoring.

1. Yes — Foundry is designed for enterprise workloads and supports scaling AI applications as usage grows. Scalability comes from the underlying Azure services and managed infrastructure.

1. Yes — Foundry can be used in solutions involving image recognition and computer vision. Applications can use vision-capable models and Azure AI vision capabilities for tasks such as image analysis, object detection, and OCR.

• JDBC
• SnowSQL
• Snowflake Web Interface (UI)
• ODBC
• Python connector

• Build, measure, learn: Create something, assess real feedback or results, and adapt.
• Minimum viable product (MVP): Produce the smallest useful version to test assumptions and reduce uncertainty.
• Fail fast: Test ideas early so that unsuccessful approaches can be identified before significant time or cost is invested.

• Streams — track change data for tables or views.
• External tables — reference data stored in an external cloud storage location.

• Role — account-level security object.
• Warehouse — account-level compute resource.
• User — account-level security object.
• Share — account-level object used to share data.

• The product is already in production.
• The organization is examining the product’s functions and cost drivers.
• The objective is to reduce cost without reducing perceived value or required quality.

• Kaizen costing focuses on continuous, usually incremental, cost reductions during the manufacturing stage. It is not specifically the systematic examination of a product’s functions.
• Standard costing compares actual costs with predetermined standards; it is a control technique, not a product redesign method.
• Process innovation concerns developing significantly improved production processes, rather than analysing the product’s functions and value.

• Domínios personalizados.
• Armazenamento suficiente.
• Instâncias dedicadas.
• Balanceamento de carga.
• Menor custo entre os planos que atendem a tudo.

• Attack simulator — Used to run phishing and other attack simulations for user awareness training.
• Hunting — Used to proactively query security data and investigate potential threats.
• Incidents — Used to investigate and manage related alerts and active security events.

• Actions that call external APIs
• Subflows
• Connection and credential aliases
• Supporting integration logic

• Action — A reusable operation within a flow, such as “Create a record” or “Send email.”
• Connection — Defines how ServiceNow authenticates and communicates with an external system.
• Integration step — A general flow step, not the name for the packaged integration.

• Guest access: Controls external users invited into your teams as guests. It is not the primary setting for restricting federated communication by domain.
• Messaging policy: Controls messaging features, such as chat or message editing, rather than which organizations users can communicate with.
• Org-wide Teams settings: Contains broad Teams-wide configuration, but domain-based external communication is configured under External access.

• A static IP gives the surveillance system a predictable local address, so users can reliably reach it on the LAN.
• However, a static IP does not block internet-based login attempts. If the router exposes the device through port forwarding, attackers could still reach it.
• Port mapping normally exposes an internal service externally, so A is a poor choice as written.
• Subnetting alone also does not block traffic; it would require routing/firewall rules.

• Economy: Obtaining inputs at the lowest appropriate cost.
• Efficiency: Making the best use of resources, such as staff, money, and equipment.
• Effectiveness: Achieving the intended objectives or outcomes.

• The load balancer provides the listener’s frontend IP address.
• The active SQL Server node must also respond to that same listener IP.
• Enabling Floating IP allows the listener IP to be preserved and handled correctly by the active replica.
• Without it, SQL connections may be sent to a node that cannot correctly claim the listener address.

• A health probe for the SQL Server port
• A load-balancing rule using the listener port
• Floating IP enabled on that rule