Test Prep NREMT Exam Prep
National Registry Emergency Medical Technician (Page 51 )

• Standardize which services users can deploy
• Apply governance and access controls
• Manage approved product versions
• Give users self-service access to authorized resources

• AWS Control Tower: Sets up and governs a multi-account AWS environment.
• AWS Cloud Map: Provides service discovery for applications.
• AWS Clean Rooms: Enables privacy-preserving collaboration on data analysis.

• Namespace: The namespace associated with the code where the checkpoint was set.
• Time: When the checkpoint was captured or executed.

• Exception: Exceptions are viewed through debug logs or execution results, not as the primary Checkpoints tab information.
• Debug Statement: System.debug() output belongs in the Logs tab. A checkpoint captures program state, such as variables and their values, at a specific point in execution.

• Accept: Acknowledge the risk and take no additional action.
• Transfer: Shift the risk or its financial impact to another party, such as through insurance or outsourcing.
• Mitigate: Reduce the likelihood or impact of the risk, such as by implementing security controls.
• Avoid: Eliminate the activity or exposure that creates the risk.

• Products ? OrderHistory: Products is 1, OrderHistory is many (1:*)

• Date ? OrderHistory: Date is 1, OrderHistory is many (1:*)

• Measurement bias: Errors in how features or labels are measured, such as unreliable camera data or inconsistent labeling.
• Observer bias: A human evaluator’s subjective judgment influencing observations or labels.
• Confirmation bias: Favoring information that supports an existing belief.

• The ERSPAN source is the device or interface whose traffic is being copied.
• The ERSPAN destination is the device receiving the encapsulated copy and forwarding it to the traffic analyzer.
• The local monitor session number is locally significant. Therefore, the source and destination do not need matching session IDs such as 47 or 48.
• The erspan-id identifies the ERSPAN stream and must correspond between the source and destination configuration.

• Company documents
• Databases
• Knowledge bases
• Current web or business data

• A: Describes diversity and inclusive design, not grounding.
• B: Describes explainability or model interpretability.
• D: Describes documenting a model’s capabilities and limitations.

• Each team’s Bedrock workflow uses a separate IAM service role.
• The role’s Amazon S3 permissions can be limited to only that team’s customer folder or objects.
• This enforces least privilege and prevents one team’s Bedrock application from accessing another team’s data.
• Access is enforced by AWS permissions, not by asking users to provide a customer name in each request.

• A single role with broad S3 access does not provide team-level isolation.
• Asking teams to specify a customer name is not an access-control mechanism.
• Redacting data does not prevent unauthorized access.
• A bucket policy alone is insufficient unless it explicitly enforces the required team-role restrictions.

• Self-signed certificate — Causes a certificate trust warning, not incorrect name resolution.
• Nameserver record — A DNS record problem would usually affect multiple users, unless only this computer uses a different DNS server.
• IP helper — Relays certain network services, commonly DHCP, between subnets; it does not normally determine website name resolution.

• Atomicity: a write fully succeeds or does not appear.
• Consistency: table state remains valid.
• Isolation: concurrent operations do not corrupt one another.
• Durability: committed changes persist.

• Flexible schemas: common data lakes often support flexible or schema-on-read data.
• Open-source formats: common data lakes commonly use open formats such as Parquet.
• Scalable storage: cloud data lakes already provide scalable storage.

1. The original app version exists.
2. You create and publish a new version, so there are now two versions.
3. When you restore the previous version, Power Apps does not delete or overwrite the newer version. Instead, it creates another version based on the restored one.

• Original version
• Newly created and published version
• New version created by the restore operation

• 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

• 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.

• Maximum response and resolution times
• Expected uptime or availability
• Performance requirements
• Escalation procedures
• Consequences for failing to meet requirements

• SOW: Defines a project’s scope, tasks, deliverables, and schedule.
• MOA: Documents specific responsibilities agreed upon by two parties.
• MOU: Records a general understanding or intent to cooperate.

• 50% memory utilization baseline: The environment can be provisioned with excess capacity, leaving room for growth and workload spikes.
• Storage scalability: Cloud storage can generally be expanded as needed without redesigning the physical platform.
• Single circuit failure resilience: A properly designed IaaS provider uses redundant power circuits and infrastructure, so failure of one circuit should not take the platform offline.

• A — Dual PDUs: Helps with power redundancy but does not provide storage scalability.
• C — Network load balancing: Provides network-path resilience, not memory or storage scalability, and does not address a power-circuit failure.
• D — Multiple NAS devices: May improve storage capacity, but does not inherently provide power resilience or the required compute-capacity baseline.

• Determine the project budget — Budget development is a separate cost-management activity.
• Develop a communication plan — This belongs to project communications planning, not schedule completion.
• Establish baselines — Baselines are created after the schedule and related plans have been developed and approved. They formally capture the approved plan.

• 10.2.1.0 — network address
• 10.2.1.1 — usable host
• 10.2.1.2 — usable host
• 10.2.1.3 — broadcast address

• Disable default accounts: Default or unused accounts may have known usernames or predictable settings, making them targets. They should be disabled, removed, or securely configured.
• Remove unnecessary services: Every running service creates potential vulnerabilities. Removing services the server does not need reduces exploitable entry points.

• Add the server to the asset inventory: Important for asset management, but not a hardening step.
• Document default passwords: Default passwords should be changed or eliminated—not documented for continued use.
• Send server logs to the SIEM: Valuable for monitoring and detection, but generally performed as part of logging/monitoring configuration.
• Join the server to the corporate domain: May be necessary operationally, but does not itself harden the server.

• A. IDS attack signatures: An IDS mainly detects suspicious network traffic. It is not the best control for scanning uploaded documents.
• C. Load balancer: Distributes traffic among servers and can improve availability, but does not specifically detect malware.
• D. WAF: Protects web applications from attacks such as SQL injection and command injection. It may inspect web requests, but malware scanning of PDF files is not its primary function.

• Complete MFA, or
• Securely change their password

• Identity Protection: evaluates user and sign-in risk and can trigger remediation.
• Privileged Identity Management (PIM): manages temporary, just-in-time access to privileged roles; it does not automatically require password changes for risky sign-ins.

• A — Consumption-based pricing: AWS generally uses a pay-as-you-go model. You pay for the resources you consume rather than purchasing hardware upfront or paying for unused capacity.
• C — Economies of scale: AWS purchases and operates infrastructure at a very large scale, allowing it to reduce costs and pass some savings to customers through lower service prices.

• Perpetual licenses: These involve paying once for permanent software ownership and are not a primary AWS Cloud economic benefit.
• AWS Enterprise Support at no additional cost: Enterprise Support has an additional charge.
• Bring-your-own-hardware model: AWS provides and manages the underlying cloud infrastructure; customers do not normally bring their own physical servers.

• Data Category Groups e categorias;
• Visibilidade dessas categorias para perfis ou permission sets.

• B e C: regras de compartilhamento não são o mecanismo apropriado para restringir resultados de busca do Knowledge por divisão.
• D: a role hierarchy não é o mecanismo principal para controlar a visibilidade de categorias do Knowledge. Além disso, a configuração correta é atribuir visibilidade a perfis ou permission sets.

CIMA P3 topics

• IT governance and systems strategy
• Systems development and implementation
• Change and project governance
• Strategic and business risk

• A — Plan for new systems: The committee should help identify and prioritise systems requirements and ensure planned systems support organisational needs.
• D — Consider competitive issues: New information systems may affect Y’s competitive position, service quality and efficiency. These strategic implications should be considered.
• E — Ensure the system meets company goals: This is a key governance responsibility. The committee should ensure the project remains aligned with Y’s objectives and delivers business value.

• B — Develop new systems: Detailed system development should be performed by IT specialists and project teams, not the steering committee.
• C — Manage the project: The project manager should handle day-to-day project management. The steering committee should provide oversight, challenge and key decisions, rather than manage daily activities.

• Limiting the number of MAC addresses allowed on a switch port
• Restricting ports to specific known MAC addresses
• Taking an action—such as dropping frames or shutting down the port—when the limit is exceeded

• Load balancer: Distributes application traffic; it does not protect switch MAC tables.
• IPS: May detect some attack traffic, but is not the primary control for switch-port MAC limits.
• NGFW: Filters network traffic at the firewall, but does not directly control MAC addresses learned by a switch.

• Row counts
• Minimum and maximum values for columns
• Distinct-value information
• Other characteristics used for optimization

• MFA adds an additional authentication factor, such as a phone notification or verification code.
• It helps prevent unauthorized sign-ins, even if a password is compromised.
• It does not encrypt, store, or protect credentials used by deployment processes.

• Enforce organizational rules, such as allowed regions or required tags
• Audit resources for compliance
• Deny noncompliant deployments
• Aggregate compliance results across subscriptions

• SAS (Serial Attached SCSI):

• SSD (solid-state drive):

• Operating profit is affected because transfer price determines internal sales revenue.
• Return on investment (ROI) is affected because ROI depends partly on operating profit.
• Sales revenue is affected because the division records revenue from transferring its output.
• Cost of components purchased is not affected by the transfer price. These are input costs paid to external suppliers and are based on the supplier’s price.

• A — Use getRecordTypeInfosByDeveloperName()

apex 
  Id rtId = Schema.SObjectType.Account 
      .getRecordTypeInfosByDeveloperName() 
      .get('Business_Account') 
      .getRecordTypeId();

• C — Query the RecordType object

apex 
  RecordType rt = [ 
      SELECT Id 
      FROM RecordType 
      WHERE SObjectType = 'Account' 
      AND Name = 'Business Account' 
      LIMIT 1 
  ];

• B: An outbound SOAP call is unnecessary and inefficient.
• D: Hardcoding an ID is not dynamic, and IDs can differ between orgs.

• Scale out during the hours when customer traffic is high.
• Scale in during low-demand periods, reducing instance-hours and cost.
• Use scaling policies based on metrics such as CPU utilization or request count.

• Multiple Availability Zones: Improves availability and fault tolerance, but does not automatically reduce cost.
• Placement group: Helps with specialized performance or low-latency requirements, not cost optimization.
• Private subnets: Improve network security, but do not automatically adjust capacity or reduce EC2 usage costs.

• Allow the team to identify the causes of delays.
• Encourage improvements to processes, tools, and collaboration.
• Help remove impediments without dictating solutions.
• Protect quality and maintain a sustainable pace.

• A: An impediment log may help track issues, but merely recording them does not resolve the root causes.
• B: Directing teams toward solutions conflicts with the agile principle of a self-managing team.
• C: Adding impediments to the product backlog may delay their resolution and incorrectly treats them as product features.

• Azure DevOps Analytics views are accessed through the Power BI Azure DevOps (Boards only) connector.
• This connector authenticates directly to Azure DevOps Services and lets you select an Analytics view.
• Analytics views allow filtering and shaping data in the cloud before Power BI loads it.
• Azure DevOps Server (Boards only) is for an on-premises Azure DevOps Server instance, not Azure DevOps cloud.
• A generic OData Feed connection can access OData endpoints, but it is not the purpose-built connector for Azure DevOps Analytics views.
• “OData queries” describes the underlying technology or query approach, not the most appropriate Azure DevOps connector choice here.