PRINCE2 PRINCE2 Foundation Exam Prep
PRINCE2 Foundation (Page 23 )

• Architects design overall Splunk infrastructure and data strategy.
• Administrators manage configuration, access, and system operations.
• Knowledge Managers create and maintain knowledge objects such as data models, field extractions, and event types. They may support pivots, but they are not the primary users of them.

• Custom domains are supported.
• It provides dedicated compute instances.
• It offers enough storage for the applications.
• It supports multiple instances with load balancing between them.
• It is less expensive than higher tiers such as Premium.

• Free and Shared use shared compute and have limited storage, so they cannot meet the dedicated-instance requirement.
• Basic provides dedicated compute and custom domains, but the question’s requirement for the broader multi-instance/load-balancing capability is intended to point to Standard.

• Which batches and markets are affected
• Whether the deficiency affects product quality, efficacy, or patient safety
• Whether the issue is an ongoing manufacturing problem
• Whether immediate containment or distribution suspension is needed

• A — Withdraw the product: may be necessary, but is premature before assessing the risk.
• B — “Dear Dr.” letter: may be appropriate later, depending on the risk.
• C — Notify global authorities: may become mandatory, but the scope and urgency depend on the assessment.

• Sales process: Controls which Opportunity Stage values are available.
• Record type: Associates the appropriate sales process with a business scenario and controls available picklist values.
• Page layout: Controls which fields are displayed and whether they are required or read-only.

• Energy Market Team 1 ? Record Type 1, Sales Process 1, Page Layout 1
• Energy Market Team 2 ? Record Type 2, Sales Process 2, Page Layout 2
• Services/Installation Team ? Record Type 3, Sales Process 3, Page Layout 3

• Custom domains: Supported by Basic and higher tiers.
• Dedicated compute: Basic and Standard use dedicated virtual machine instances; Free and Shared use shared infrastructure.
• Load balancing between instances: Standard provides scaling across multiple instances with load balancing.
• Storage: Standard provides more storage than Basic.
• Cost: Standard is the least expensive option that satisfies all the stated requirements.

• Free/Shared: Use shared compute and have limited features; they don’t meet the dedicated-compute requirement.
• Basic: Provides dedicated compute and custom domains, but does not provide the required Standard-level multi-instance capabilities in the exam’s feature comparison.

• Base table — the table containing common inherited fields
• Parent table — the table directly extended by the child
• Other tables in the hierarchy

• True positive: The scan reports a vulnerability that really exists.
• False positive: The scan reports a vulnerability that does not exist.
• True negative: The scan correctly reports no vulnerability.
• False negative: The scan fails to detect a vulnerability that is actually present.

• miami.weyland.com requires a custom domain, which is not available in the Free tier.
• Two instances require a tier that supports scaling out. Standard supports multiple instances.
• SSL support is available in Standard.
• 12 GB of storage exceeds the storage limit of the Basic tier in the older Azure pricing model used by this question.
• Standard provides sufficient storage and features while being cheaper than higher tiers—though higher tiers are not listed here.

• Free/Shared: insufficient features for custom domains, SSL, and multiple instances.
• Basic: supports some production features, but its storage capacity is insufficient for the required 12 GB.

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

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

• Training data for potential bias before model training
• Trained models for bias in predictions
• Model features to help explain how they influence predictions

• A: RAG workflows are typically built using services such as Amazon Bedrock, knowledge bases, and data sources.
• B: Monitoring model quality in production is primarily associated with SageMaker Model Monitor.
• C: Documenting model details is handled by capabilities such as SageMaker Model Cards.

• Disable high concurrency: Changes workspace-wide behavior and is not the targeted way to isolate these workloads.
• Modify the number of executors: Adjusts capacity and performance, but does not provide workload isolation.
• Set the default environment: Controls libraries and runtime configuration, not compute isolation.

• Plenum: Describes a fire-resistant cable jacket rating, not a transmission medium or speed.
• Ethernet: Describes a networking technology; Ethernet can use copper or fiber, so the term alone does not identify the fastest cable type.
• DAC (Direct Attach Copper): Uses copper and is typically intended for short-distance, high-speed connections in data centers.

• A single summarized value, such as total annual sales
• Progress toward a defined target or goal
• Whether performance is below, near, or above the target

• Table: Displays detailed records or summarized rows, but not goal progress visually.
• Stacked Bar: Compares multiple categories and their parts.
• Donut: Shows how a total is divided among categories, not progress toward a target.

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

• Verifies the sender’s identity using their private key.
• Confirms the transaction was not altered after signing.
• Provides evidence that the signer approved or originated the transaction.

• Digital certificates: Bind an identity to a public key, but do not themselves prove that a specific transaction was signed.
• Encrypted passwords: Protect confidentiality or authentication, but generally do not provide transaction-level nonrepudiation.
• One-time passwords: Authenticate a user for a session or transaction, but usually do not provide durable proof of who authorized the electronic record.

Correct reasoning

• Create storage5 as a General-purpose v2 (StorageV2) account.
• Configure Blob object replication from storage5 to an existing compatible storage account.
• The destination must support object replication—typically another StorageV2 or premium block blob account.
• Blob versioning must be enabled on both accounts.
• Blob change feed must be enabled on the source account.
• The accounts must meet Azure’s object-replication requirements, including being in supported regions and having compatible configuration.

• 25 – Traditional SMTP server-to-server mail transfer; often blocked for client submission and not inherently secure.
• 110 – POP3 for receiving email; unencrypted by default.
• 143 – IMAP for accessing email; unencrypted by default.
• 587 – Authenticated email submission and commonly secured with TLS.

• Structure requirements documents
• Draft user stories and acceptance criteria
• Create templates for functional and nonfunctional requirements
• Turn natural-language descriptions into organized documentation or implementation examples

• A: “Automatically generating detailed requirements documents” overstates Copilot’s role; it assists but does not independently determine complete requirements.
• C: /help provides guidance about Copilot features, not reliable requirements-conflict detection.
• D: Stakeholder communication and meetings remain human responsibilities.

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

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

• A — .gitignore: Controls Git tracking; it does not configure Copilot exclusions.
• B — copilot.ignore: This is not the standard GitHub Copilot Business exclusion mechanism.
• D — Renaming files: Adding _no_copilot has no recognized effect.

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.

• Authentication: Verifies who the user is.
• Authorization: Determines what the authenticated user is allowed to access.
• Accounting: Records activity such as login times and resource usage.

• CIA: Confidentiality, integrity, and availability—the three core security goals.
• ACL: Access Control List, which defines permitted or denied traffic or access.
• PEM: A certificate and key encoding format, not the primary function of RADIUS.

• 25 — Traditional SMTP server-to-server mail delivery; often restricted and not the usual client submission port.
• 110 — POP3, used for retrieving email; normally unencrypted.
• 143 — IMAP, used for retrieving and synchronizing email; normally unencrypted.

• WPA3: Secures wireless traffic but does not normally verify whether someone has paid.
• PSK: A shared Wi-Fi password gives access to anyone who knows it; it cannot easily validate individual receipts.
• IEEE 802.1X: Provides user/device authentication, commonly through an authentication server, but is excessive and not designed specifically for a simple receipt-based guest-access workflow.

• A — VARIANT "null" values are not the same as SQL NULL values: True

• B — Frequent, single-row DMLs: False

• C — Validate data before loading into the target table: True

• D — Use staging tables to manage MERGE statements: True

1. Create a temporary Onboarding OU.
2. Move the new account into it.
3. Move the restrictive SCPs from the organization root to the Production OU.
4. Allow the account to update AWS Config.
5. Move the account into Production after onboarding.

• An SCP attached at the organization root applies to every account and OU beneath it.
• An SCP attached to the Production OU applies only to accounts in that OU.
• Therefore, moving the restrictive SCP from the root to Production temporarily exempts the onboarding account without weakening the policies for existing production accounts.
• Once onboarding is complete, moving the account into Production subjects it to the normal restrictions.

• Act as the default gateway for devices in that VLAN
• Route traffic between different VLANs
• Provide management access to the switch

text 
interface vlan 10 
 ip address 192.168.10.1 255.255.255.0

Step 1: Calculate the rights issue price

Step 2: Calculate the number of new shares

Step 3: Calculate the value after the issue and project

• Rights issue proceeds: $21.6m
• Project NPV: $5m

Step 4: Calculate the theoretical ex-rights price

• Unrestricted data mining: Data mining is not automatically a privacy violation. It becomes an issue when personal data is collected or used improperly.
• Identity theft: This is a possible consequence of inadequate privacy protection, but it is not the central focus of privacy regulations.
• Human rights protection: Privacy can be considered a human right, but this option is broader than the specific regulatory focus.
• Identifiable personal data: Regulations such as HIPAA focus directly on controlling the collection, use, disclosure, and protection of personal information.

• Required response time
• Resolution time
• Availability or uptime
• Support hours
• Performance targets
• Consequences if targets are missed

• SOW (Statement of Work): Defines the project’s scope, tasks, deliverables, and schedule.
• MOA (Memorandum of Agreement): Describes the responsibilities and commitments between parties.
• MOU (Memorandum of Understanding): Documents a general mutual understanding or intent, often before a formal agreement.

• A — Use a custom controller: An Apex class can contain the page’s logic.
• C — Use a standard controller with extensions: The standard controller provides basic CRUD behavior, while an extension adds custom logic.
• E — Use a standard controller: Useful when the page works mainly with one Salesforce object and needs standard functionality.

• A page with no controller for static or controller-free content.
• A custom controller with extensions; extensions are not limited only to standard controllers.

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

• Undefined or blank values
• Relationship matching problems
• Duplicate or conflicting keys
• Errors when querying the model

• Normalize all values to upper- or lowercase in the source query or Power Query.
• Add an index or surrogate key when values that differ only by case must remain distinct.

• Crowd-sourced evaluation: Requires recruiting and managing many evaluators.
• Human-worker evaluation: Provides human judgment but requires coordination, labeling instructions, and quality control.
• RLHF: Is a training and alignment process, not simply a low-overhead model comparison method.
• Automatic model evaluation: Quickly evaluates outputs using predefined toxicity or quality metrics with minimal manual effort.

• Admin access to the deployment pipeline
• Contributor access to the Development and Test workspaces
• Viewer access to the Production workspace

• 10 minutes have elapsed, or
• 20 MB of accounting data has accumulated

• The message came from the claimed sender (authentication)
• The message was not altered (integrity)
• The sender cannot easily deny sending it (non-repudiation)

• Attackers can send unsigned phishing emails.
• Attackers may compromise a legitimate account and send signed malicious emails.
• Users may still be tricked by a validly signed message.

• host — simple, human-friendly lookups

bash 
  host example.com 
  host 192.0.2.1

• dig — detailed DNS troubleshooting

bash 
  dig example.com 
  dig example.com MX 
  dig @8.8.8.8 example.com

• nslookup — older, familiar, and widely available

bash 
  nslookup example.com

• Quick answer: host
• Detailed diagnosis: dig
• Compatibility or legacy environments: nslookup