NFPA CFPS Exam Prep
Certified Fire Protection Specialist (Page 10 )

• Árvores de decisão: usam regras sequenciais, como “se característica X > valor, siga para este ramo”. São fáceis de visualizar e explicar. Atendem bem a problemas de classificação e regressão com alta interpretabilidade.

• Regressão linear: prevê um valor numérico contínuo, como preço, custo ou temperatura. Não é a escolha principal para classificar genes em categorias.

• Regressão logística: calcula a probabilidade de uma categoria. Pode atender à classificação, inclusive multiclasses, mas sua explicação costuma ser menos intuitiva que uma árvore para documentar decisões.

• Redes neurais: atendem a tarefas complexas, como imagens, texto e padrões não lineares. Porém, são menos interpretáveis, funcionando mais como uma “caixa-preta”.

• Import — Loads data into Power BI. It requires a refresh, so it may not reflect changes within two minutes unless refresh is configured appropriately.
• Live connection — Connects to an existing Power BI semantic model or Analysis Services model; it is not the normal choice for connecting directly to an Azure SQL database.

• A — Custom Button: A button can launch a flow, typically by passing the flow’s URL and record context.
• D — From a Process: A Process can invoke a flow using an Apex action configured for flow invocation. However, this is automation-triggered, not directly accessed by a user.
• B — Quick Action: In current Salesforce functionality, a Flow Quick Action can launch a screen flow directly from a record page. This makes B a valid modern method.
• C — Visual Workflow Launcher: This is not generally listed as a standard access method in current Salesforce terminology; Salesforce commonly uses the Flow component on Lightning pages instead.

• Use private connectivity from a cloud provider
• Set up SSO for federated authentication

• Private connectivity—such as a cloud provider’s private endpoint—keeps Snowflake access within the company’s private network path instead of exposing access over the public internet. This fits the VPN/VDI requirement.
• SSO for federated authentication allows Snowflake users to authenticate using the credentials already managed by the company’s identity provider—the same identity system used for VDI—eliminating separate Snowflake passwords.

• Tri-Secret Secure protects encryption keys; it does not provide private network access or credential reuse.
• A proxy Snowflake account outside the VPN conflicts with the requirement that Snowflake have no internet visibility and is not the normal solution for federated login reuse.

• Secret scope: A named container that groups related secrets and defines access permissions. Example: finance-prod.
• Secret key: The name of an individual secret stored inside that scope. Example: db-password.

text 
Scope: finance-prod 
  Key: db-username 
  Key: db-password

python 
dbutils.secrets.get( 
    scope="finance-prod", 
    key="db-password" 
)

• Primary and core nodes: Use On-Demand Instances because the workload is business-critical. These nodes manage the cluster and store/process HDFS data.
• Task nodes: Use Spot Instances in an instance fleet. Task nodes are suitable for interruption because they do not hold essential cluster data and can be replaced or diversified across instance types.
• Terminate the entire cluster after processing: The job runs only about six hours each morning, and EMRFS stores data in Amazon S3. Keeping the cluster running for the rest of the day would waste money.

• A: Using Spot for primary and core nodes risks interruption of the critical cluster.
• C: All On-Demand is reliable but unnecessarily expensive; terminating the cluster helps, but Spot task nodes provide greater savings.
• D: Leaving primary and core nodes running after the task finishes continues to incur costs. Savings Plans also are less appropriate for this intermittent workload.

• Restarting the device: may fix software problems, but not a directional connection issue.
• Swollen battery: is a safety concern, but would not typically cause recognition only in one orientation.
• Failing cable: possible in general, but less likely because it works on other similar devices.
• Dirty or damaged port: best matches the symptoms. Inspect and carefully clean the port, or have it serviced if damaged.

1. Ensure BOMs can include subcomponents ? Configure an entity relationship

1. Report changes made by engineers ? Enable auditing

• Configure entity relationship
• Configure auditing

• Date: 2018-12-31
• Time: 08:59

• B: The original value contains the text at, so it cannot be converted directly to a date.
• A: The last characters contain the time, not the date.
• D: Extracting the first 11 characters can leave an unwanted space and does not properly separate the time component.

• IPsec: Protects traffic at the network layer, commonly for VPNs; it is not WPA2’s authentication protocol.
• SSL: Protects specific application sessions and has largely been replaced by TLS.
• SSH: Secures remote command-line administration.

bash 
docker run -it microsoft/azure-cli:0.10.17

• docker run starts an Azure CLI container; it does not automatically connect to the AKS cluster.
• The command does not run kubectl apply.
• The container would need the appropriate Kubernetes tools and AKS credentials.
• The device or container must obtain cluster credentials, typically using an AKS credential command, before running Kubernetes commands.

bash 
az aks get-credentials --resource-group <resource-group> --name <aks-cluster> 
kubectl apply -f myapp.yaml

• Conserve public IPv4 addresses: IPv4 addresses are limited, so many internal devices share a smaller number of public addresses through NAT.
• Reduce direct exposure: Private addresses are not directly routable from the public Internet, which helps reduce unsolicited access to internal devices.

• Entradas grandes, de até aproximadamente 1 GB.
• Processamentos demorados, que podem levar até cerca de 1 hora.
• O cliente envia a solicitação e consulta o resultado depois, sem precisar manter uma conexão aberta durante todo o processamento.

• Real-time inference: indicada para respostas imediatas, com entradas menores e processamento rápido.
• Serverless inference: adequada para cargas variáveis e solicitações menores; não é ideal para processamento longo e arquivos grandes.
• Batch transform: processa grandes volumes em lote, mas não atende à necessidade de respostas próximas do tempo real.

• Encryption to preserve confidentiality
• Integrity protection to detect alteration
• Authentication of the server through certificates

• SHA-256: A hashing algorithm; it does not encrypt data for transmission.
• SSL 3.0: Obsolete and insecure. It should not be used.
• AES-256: A strong encryption algorithm, but by itself it does not provide the complete secure communication protocol needed for data in transit.

• Product Owner: May attend, but is not required unless also working as a Developer.
• Scrum Master: May attend to help facilitate or coach, but is not required.
• Developers: Must participate because the event is specifically for them.

• Compare each server’s drive specifications and performance data.
• Identify the drive that is faulty, slow, or mismatched.
• Replace it with a drive that matches the required interface, capacity, and performance characteristics.
• Avoid selecting a slower drive, because storage performance can bottleneck the entire server.
• In a redundant array, use a compatible replacement so rebuilding does not create unnecessary performance degradation.

• Planning — identify the need, objectives, resources and feasibility.
• Analysis — determine user requirements and examine the existing system.
• Design — specify how the new system will work.
• Implementation — build, test, install and introduce the system.
• Maintenance/evaluation — monitor and improve the system after implementation.

• Internal interface ? connected toward the corporate network/internal firewall
• External interface ? connected toward the Internet-facing firewall

1. A route for the internal corporate network through the internal-facing interface/firewall.
2. A default route (0.0.0.0/0) through the Internet-facing interface/firewall.

• Users retain their existing usernames and passwords.
• Existing accounts can be used to access Azure-based resources.
• Administrators avoid manually recreating thousands of accounts.
• The transition is less disruptive before the on-premises data center is retired.

• Default network device credentials: More associated with external attackers or poor device configuration.
• Spear phishing emails: Commonly used to compromise users, but less characteristic of an insider who already has access.
• Typosquatting and impersonation: Primarily social-engineering techniques aimed at deceiving users.
• Unidentified removable devices: Provide a direct way to transfer data outside the organization and may bypass network monitoring.

• Server — provides services or resources
• Endpoint — a user device connected to the network
• Ethernet — a networking technology, not a filtering device
• Firewall — filters and controls traffic

• The connecting host keeps the private key securely.
• The destination host stores the corresponding public key in its authorized keys.
• Authentication can occur without a person entering credentials each time.
• SSH also provides encrypted communication and host authentication.

• Biometric: Requires a human user and is difficult to automate.
• Smart card: Often requires user interaction or card access.
• Hard-coded password: Unsafe because passwords stored in scripts or applications can be exposed, reused, or difficult to manage securely.

1. Determine which host was infected first—the originating host.
2. Decide whether each other host is clean or infected based on communication and event logs.

• Compare timestamps and find the earliest suspicious event.
• Look for the host that initiated the malicious connection, file transfer, exploit, or command—not merely a host that later received traffic.
• Follow the timeline through the firewall:

• A host is likely infected if it both receives suspicious activity and then initiates related malicious traffic.
• A host may be clean if the firewall blocked the connection and there is no evidence of execution or follow-on communication.

• Business
• People
• Governance
• Platform
• Security
• Operations

• Cloud financial management
• Portfolio management
• Data governance
• Risk management
• Compliance

• vSmart controls the overlay control plane. It uses OMP to exchange routing information, distribute policies, and determine how WAN Edge devices reach one another.
• vManage is the centralized management and configuration platform.
• vBond is the orchestrator. It helps devices authenticate, discover controllers, and traverse NAT during onboarding.
• APIC-EM is not the SD-WAN control-plane component described here.

• The user starts in the corporate portal.
• The portal launches the Salesforce resource.
• The IdP sends the SAML response to Salesforce.

• Connected App + OAuth is for OAuth authorization and API/app access, not this SAML-based seamless login scenario.
• SP-initiated SSO would begin when the user first requests the Salesforce resource and Salesforce redirects them to the IdP. That is not the described starting point.

• Normalize casing in the data source—for example, convert all values to uppercase or lowercase.
• Add an index key to provide a unique, stable identifier for each row or value.

1. The sender hashes the original message and sends the message plus its hash.
2. The receiver applies the same hashing algorithm to the received message.
3. The receiver compares the newly calculated hash with the sender’s hash.
4. Matching values indicate that the message was not altered in transit.

• A binary image is not the normal description of a hash result.
• Using a different algorithm produces a different type of digest, so the values cannot be directly compared.
• Hashing verifies integrity, but by itself does not prove who sent the message. Digital signatures or MACs address authentication and integrity together.

1. Define Power Platform DLP policies

1. Add custom prompt modifications

1. Conduct adversarial testing

• Issuer: Identifies the party issuing a SAML message, commonly the IdP in the SAML assertion. It is not the Salesforce setting used to distinguish Salesforce from other service providers.
• Identity Provider Login URL: Specifies where Salesforce sends users for authentication; it does not identify Salesforce.
• SAML Identity Location: Specifies where the user identity is found in the SAML assertion, such as the subject or an attribute.

Simple explanation

• The Azure VPN gateway to connect to
• Authentication settings
• Routes for networks that the client can access

• A — Add a Path for Stage: A Path lets users update the Opportunity’s Stage directly from the record page, without opening the full edit form. It can also display guidance and key fields.
• B — Use a Kanban list view: Users can move Opportunities between stages by dragging records between columns, which is ideal when Stage is the only field they normally change.

• D — Create sibling resource pools for the Production VMs and Test VMs.

• B — Configure a memory reservation on the Production resource pool.

• Shares only determine relative priority when resources are scarce; they do not guarantee memory.
• A parent resource pool alone does not provide a guarantee.
• A child pool for Test VMs does not reserve memory for Production.

• Import mode loads the data into the Power BI model. Visuals query the in-memory model, which generally provides faster calculation and rendering than DirectQuery.
• Import mode also minimizes online processing because report interactions do not send queries back to the dataflow or SQL Server.
• A daily refresh can load data through the previous day, satisfying the freshness requirement without unnecessary hourly processing.

• DirectQuery keeps querying the data source or dataflow during report use, increasing online processing and potentially slowing visuals.
• Adding a gateway enables connectivity for on-premises sources, but it does not remove the performance disadvantages of DirectQuery.
• An hourly Power Automate refresh is unnecessary when the requirement is only data through the previous day and creates additional processing overhead.

• Identifying the communication strategy: Usually part of a business continuity or incident response plan.
• Evaluating the risk management plan: Part of risk assessment and risk management activities.
• Establishing backup and recovery procedures: Usually part of disaster recovery planning.
• Developing the incident response plan: Part of incident response planning.

• Import: Copies data into the Power BI model. It requires scheduled or manual refresh, so it may not meet the two-minute requirement.
• Live connection: Connects to an existing Power BI semantic model or Analysis Services model; it is not the appropriate choice for connecting directly to the Azure SQL database in this scenario.

• Writing with Apache Spark, typically as Delta tables.
• Reading with Apache Spark for processing and analysis.
• Reading with T-SQL through the lakehouse’s automatically generated SQL analytics endpoint.
• Reading with KQL through Fabric’s query capabilities that can access lakehouse data.

• Eventhouse: Optimized for real-time and KQL workloads, but it is not the natural destination for Spark-based writes or general lakehouse storage.
• Datamart: Intended mainly for relational analytics and Power BI; it is not designed for Spark-based data ingestion.
• Warehouse: Primarily T-SQL-based and structured. It does not provide the same native Spark write experience or flexibility for semi-structured data.

• The user authenticates with the external Identity Provider.
• Salesforce receives the SAML assertion.
• Salesforce uses attributes in that assertion—such as username, email, first name, last name, and profile/community information—to create the user during the first login.
• On later logins, Salesforce updates or uses the existing user record.

• On-the-fly provisioning is a general phrase; the Salesforce capability being tested is specifically JIT provisioning.
• Salesforce APIs would require a separate integration and provisioning process.
• Identity Connect is designed primarily to synchronize users from an identity directory, not to create users at the moment of their first SAML login.

• Reviewing security policies and standards checks whether controls are documented, not whether they work.
• Reviewing security logs may show that monitoring is occurring, but does not directly establish that preventive controls are effective.
• Analyzing technical security practices is broad and may assess implementation, but it is less objective than an actual controlled attack.

• Design/compliance effectiveness: policies, standards, and procedures
• Operational effectiveness: logs, records, and evidence that controls operate
• Technical security effectiveness: penetration testing or vulnerability testing

• The inference container image or built-in algorithm
• The location of model artifacts in Amazon S3
• IAM permissions through the execution role
• Optional environment variables and networking settings

1. Create AWS::SageMaker::Model
2. Create an AWS::SageMaker::EndpointConfig that references the model
3. Create AWS::SageMaker::Endpoint that references the endpoint configuration

• AWS::SageMaker::Endpoint hosts a model but does not define the model itself.
• AWS::SageMaker::NotebookInstance provides a development environment.
• AWS::SageMaker::Pipeline orchestrates ML workflow steps.

• A Layer 2 switch checks the destination MAC address in its MAC address table (CAM table).
• If the destination MAC is unknown, the switch cannot select a specific outgoing port.
• It therefore performs unknown-unicast flooding, sending the frame out every other port in that VLAN.
• The frame is not sent back through the port where it arrived.

• B — Prompts and suggestions retained for 28 days
• C — User engagement data kept for two years

• The key distinction is between content data—your prompts, code context, and generated suggestions—and engagement data, such as usage activity.
• Do not confuse retention with training: enterprise Copilot data is generally not used to train GitHub’s models without appropriate authorization.
• For a current exam, verify the policy version cited by the exam provider. The key’s C is likely correct, but B should be treated cautiously and may no longer reflect the current policy.

• Updating the CRL: Revokes compromised certificates, but does not fix the CA flaw that allowed them to be created.
• Changing passwords: May be necessary if accounts were compromised, but it does not address the certificate-generation vulnerability.
• Implementing SOAR: Improves security automation and response; it does not remediate the underlying PKI weakness.

• Use one Azure AD directory for the organization.
• Separate divisions with subscriptions and/or resource groups.
• Assign each division’s administrator appropriate Azure role-based access control (RBAC) permissions, scoped to their subscription or resource group.

• Accept: Acknowledging the risk without taking additional action.
• Transfer: Shifting responsibility or financial impact to another party, such as through insurance or outsourcing.
• Mitigate: Reducing the likelihood or impact of the risk through controls.
• Avoid: Eliminating the activity or condition that creates the risk.

• Planning – identifying the need, objectives, scope and resources.
• Analysis – understanding business requirements and current problems.
• Design/development – determining how the system will work.
• Implementation – installing the system and putting it into operation.

1. Which host originated the infection

1. Which remaining hosts are infected

• Azure Resource Manager (ARM) templates define Azure resources in a declarative JSON file.
• You can deploy the same template repeatedly for each business unit, ensuring that identical resources are created consistently.
• Templates reduce manual administrative effort and support repeatable, automated deployments.
• Parameters can customize values such as names, regions, and sizes while keeping the overall resource configuration the same.

• Authentication — verifies who the user is.
• Authorization — determines what the authenticated user is allowed to access.
• Accounting — records session activity, such as login time and resource usage.

• CIA — confidentiality, integrity, and availability; core security objectives.
• ACL — access control list; rules that permit or deny traffic or access.
• PEM — Privacy Enhanced Mail, an older email security standard.