ACE Fitness ACE-PERSONAL-TRAINER Exam Prep
American Council on Exercise (ACE) Personal Traniner (PT) (Page 16 )

Why B works

• AWS KMS keys are Regional resources. A normal customer managed key in Region A cannot be used directly in Region B.
• A customer managed multi-Region KMS key (MRK) has related key replicas in both Regions. The replicas share key material and key ID, although each has a Regional ARN.
• With client-side encryption, the application encrypts the data before storing it in S3. Cross-Region replication then copies already-encrypted objects, so S3 does not need to decrypt and re-encrypt them with a different Regional key.

Why the other choices are weaker

• A and C: SSE-S3 uses Amazon-managed S3 keys, not the required customer managed KMS key.
• D: SSE-KMS can work only if the solution creates and configures the appropriate KMS key or multi-Region key replica in each Region. As written, it says to create a customer managed KMS key in each Region, which implies separate keys—not the same KMS key. Replication also requires additional KMS permissions and destination encryption configuration.

• Who performed the action
• What action occurred
• When it occurred
• Where it originated
• Whether it succeeded or failed

• Investigating suspicious activity: Important, but investigation depends on having adequate audit data first.
• Storage allocation: Necessary for retention, but storage does not help if the records lack meaningful details.
• Actions after audit failure: Part of operational planning, not the primary assessment of the application’s audit capability.

• Answer: C – netstat -an

• netstat -an lists all active connections and listening ports with numeric addresses, without resolving names. This lets you spot DoS patterns such as a flood of connections to a specific port or many connections from a single or few IPs.
• The other options don’t help as directly:

• Windows: netstat -an and look for numerous ESTABLISHED connections to a service or many SYNs to a port.
• Filter by port, e.g., netstat -an | findstr :80, or on Linux: ss -tunap | grep ':80'.

• Netstat provides a snapshot. DoS detection often benefits from continuous monitoring, flow data, and IDS/IPS logs.

• Manage multiple organizations from one hierarchy.
• Enterprise-wide policies, including repository visibility, forking, and GitHub Copilot policies.
• Centralized identity and access management, such as SAML SSO, SCIM provisioning, and—where applicable—Enterprise Managed Users.
• Centralized billing and licensing, including organization and Copilot seat management.
• Enterprise audit log, which aggregates activity across organizations.
• Security and compliance oversight, such as organization security visibility and enterprise-wide controls.
• Enterprise support and account management features, depending on the plan.

• Organization: manages its own repositories, teams, members, and local policies.
• Enterprise: governs multiple organizations and can enforce policies across them.

• Answer: D. Select an IdP

• Why: To reduce the number of credentials across multiple SaaS apps, implement a single sign-on approach via an Identity Provider. The first step is choosing the IdP; once selected, you can enable SAML (A) or OAuth as supported by apps. Password vaulting (C) is not a true SSO solution, and B is not the foundational step.

• A. Tuning system software: This is a corrective action, not an analysis method. Tuning should be based on measured performance data.
• B. User dissatisfaction reports: Useful as an indicator, but subjective and insufficient for diagnosing the cause.
• D. Off-peak utilization and response time: This may hide problems occurring during peak periods. Performance analysis should cover representative or peak workloads.

1. Create a new AMI or copy the existing AMI while specifying EBS encryption and an appropriate AWS KMS key.
2. This creates an encrypted AMI backed by encrypted EBS snapshots.
3. Copy the encrypted AMI to the destination Region, using a KMS key available there.
4. Launch the application stack from the encrypted AMI.

• B: AWS KMS does not encrypt an existing unencrypted AMI in place. You must create an encrypted copy.
• C: AWS Certificate Manager manages TLS certificates, not EBS or AMI encryption.
• D: Enabling encryption by default affects newly created EBS volumes and snapshots; it does not encrypt an existing unencrypted AMI during copying.

• Correct answer: D — use the same hashing algorithm as the sender's to create a numerical representation of the file.

• Integrity is verified by recomputing the hash on the received data and comparing it to the sender’s hash. This must use the same hash function; if you use a different algorithm, the digests won’t match even if the data is intact.
• The hash output is a fixed-length digest (a numerical representation). Whether you call it a “binary image” or a “numerical representation,” the key is that you generate the same type of digest with the same algorithm and compare them.

• A: same algorithm but the result is described as a binary image instead of a digest; you still compare the digest, but the phrasing is less precise.
• B/C: using a different algorithm would produce a different digest, causing false mismatch or failure to verify integrity.

• Why: After listing all resources, you need to assign who is responsible for each task. A RACI chart (Responsible, Accountable, Consulted, Informed) documents these roles for every activity.

• What RACI means:

• Why the others aren’t suitable here:

• Quick example: Task "Create user authentication module" — Responsible: Developer, Accountable: Tech Lead, Consulted: Security Architect, Informed: PM.

• A. Implement retries with exponential backoff

• C. Reduce the frequency and/or size of requests

• B. Use PutRecord instead of PutRecords — PutRecord sends one record per call and does not remove the underlying throughput limitation. It may increase request overhead.
• D. Use Amazon SNS instead — SNS is not a direct fix for Kinesis shard throttling and changes the required streaming architecture.
• E. Reduce KCL consumers — KCL consumers read from Kinesis; they do not solve producer-side PutRecords throttling.

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

• Developed and maintained independently
• Deployed without changing the entire application
• Scaled separately based on demand
• More resilient when another service has problems

• A: Functional testing is useful, but it is not the main practice described.
• B: Automation helps deployment, but the scenario focuses on architectural decomposition.
• C: Multiple locations improve availability, not application modularity.

• Le rôle n’a pas de clés propres. Des identifiants temporaires (via STS) sont émis lorsque quelqu’un ou quelque chose « assume » le rôle.
• La trust policy déclare qui peut assumer le rôle (par ex. une instance EC2, un utilisateur IAM, ou un service comme Lambda).
• Une fois attaché à une ressource (par exemple comme un instance profile sur une EC2), l’application peut appeler les services AWS avec les permissions du rôle.

• Respect du principe du moindre privilège: on accorde uniquement ce qui est nécessaire.
• Pas de stockages de clés sur les instances; les credentials se renouvellent automatiquement.

• Rôles pour EC2, rôles pour Lambda, accès cross-compte, etc.

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

• User1 can sign in because the account is cloud-only. It does not depend on the on-premises domain.
• User3 can sign in because the account uses Password Hash Synchronization (PHS). Azure AD has a synchronized password hash and can validate the sign-in even when connectivity to on-premises Active Directory is unavailable.
• User2 cannot sign in because the account relies on Pass-through Authentication (PTA). PTA sends the authentication request to an on-premises PTA agent, which must contact a domain controller. With the internet connection from on-premises lost, that validation cannot occur.

• Key difference: DirectQuery leaves data in the on-prem SQL Server and queries it live. That means every visual request can trigger online processing on the source, which can be slower and adds load on the on-prem system. In contrast, Import loads data into the Power BI data model, so visuals render from the in-memory engine (faster).

• Why that helps with the requirements:

• Why not A or B: Both rely on live data via DirectQuery, which contradicts the goal to minimize online processing and visuals performance.

• Why not D: It uses Import, but refreshing hourly adds unnecessary processing and complexity when daily refresh already satisfies currency needs.

• L2TP uses UDP port 1701 for the L2TP control channel.
• The destination port is 1701; the source port is a dynamically chosen ephemeral port on the client (not 1701).
• Therefore the statement that both source and destination ports are 1710 is incorrect (and 1710 is not the standard L2TP port).

• The destination port should be 1701, not 1710.
• The source port should be an ephemeral port chosen by the client, not 1701.

• AWS Audit Manager continuously collects evidence from AWS services and helps assess whether workloads comply with regulatory frameworks and internal policies. It can produce audit-ready reports.
• AWS Config records resource configurations and evaluates them against compliance rules. For example, it can check whether encryption, logging, or access settings meet company requirements.

• Amazon Inspector identifies software vulnerabilities and unintended network exposure, not general policy or regulatory compliance.
• Amazon CloudWatch monitors metrics, logs, and operational events, but is not primarily a compliance assessment service.
• AWS CloudTrail records API activity for auditing and investigation. It supports compliance, but does not itself provide the structured compliance assessment capabilities of Audit Manager and Config.

• Side loading means installing software from sources outside official or trusted repositories.
• This process can bring in malicious payloads because the installed software hasn’t been vetted. A rootkit is a type of malware that hides its presence and maintains privileged access, making it a prime risk when using untrusted sources.
• Why not the other options:

• Only install apps from trusted sources; verify signatures.
• Use application whitelisting and security controls to block sideloading.
• Keep systems updated and use anti-malware tools capable of detecting rootkits.

1. Define Power Platform DLP policies
2. Add custom prompt modifications
3. Conduct adversarial testing

1. DLP policies first

1. Prompt modifications second

1. Adversarial testing last

• A limited lifetime
• Permissions defined by an IAM role or policy
• The ability to access AWS APIs without using long-term IAM user credentials

• Amazon API Gateway — Builds and manages APIs; it does not generally issue AWS credentials for applications.
• IAM users — Usually use long-term credentials, which are less suitable for applications.
• IAM instance profiles — Provide temporary role credentials to applications running on EC2 instances, but are specifically tied to EC2. The broader requirement described is best met by AWS STS.

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

• Improve QA testing efficiency: A prototype may help discover defects early, but that is not its greatest benefit.
• Decrease time allocated for user testing and review: Prototyping usually requires additional user involvement and review, not less.
• Minimize scope changes: Prototypes can actually reveal new requirements or cause scope changes. However, discovering those changes early is beneficial.

• The first step in risk management is to understand objectives, constraints, and drivers from those who care about the project. This stakeholder engagement helps identify what could go wrong and what risks are most critical.
• Only after you’ve gathered input from stakeholders should you identify risks and document them in the risk register. Updating the risk register (option C) is important, but it comes after identifying and analyzing risks.
• Options B (ensure resources) and D (revise the risk management plan) are actions that may follow once risks are identified and understood; they’re not the initial step.

• Assign users or their team an appropriate security role.
• Ensure the role has the required table privileges, such as read, create, write, and append.
• Share the app with that security role in the app designer.

• Dynamics administration center: Used for environment and service administration, not routine app access configuration.
• Manage Roles: Not the specific Dataverse area used to define app and data permissions.
• Security Roles: Define what users can access and which operations they can perform.

1. Ingestion Lambda receives requests from API Gateway and places messages in an SQS queue.
2. Processing Lambda is triggered by the queue and loads records into Aurora PostgreSQL.

• Decoupling: API request handling is separated from database loading.
• Buffering: SQS absorbs bursts when incoming traffic exceeds the database’s processing capacity.
• Controlled concurrency: Configure the SQS-triggered Lambda’s concurrency and batch size to avoid overwhelming Aurora or exhausting database connections.
• Automatic retries: Messages that fail processing can return to the queue and be retried. A dead-letter queue can capture persistent failures.
• Lower operational effort: The solution remains serverless and avoids managing EC2 servers or Kubernetes clusters.

• A: EC2 and Tomcat add server-management overhead.
• B: DynamoDB/DAX would require changing the database model and does not solve the Aurora ingestion design.
• C: SNS is useful for notifications and fanout, but SQS is better for durable buffering and backpressure in this producer-consumer workflow.

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

• Multi-pass wipe: Overwrites the drive’s existing data multiple times, making recovery much more difficult while preserving the drive’s functionality.
• Single-pass wipe: May be sufficient in some modern sanitization standards, but is presented here as less secure than multiple overwrites.
• Degaussing: Uses a strong magnetic field to disrupt data. It can render the drive unusable or unreliable, reducing its resale value.
• Pinning: Is not an appropriate data-sanitization method.

• Answer: A — EC2 Image Builder

• Why: EC2 Image Builder is AWS’s fully managed service designed to automate the creation, testing, and ongoing management of custom EC2 AMIs. It lets you build image pipelines that start from a base image, apply software/components, run tests, and publish/distribute the resulting AMIs across regions or accounts.

• How it works (high level):

• Why not the other options:

• Quick tip: Use EC2 Image Builder to reduce manual image maintenance and drift, and to enforce consistent, tested base images across environments.

• IaaS: You manage the virtual machine’s operating system, configuration, applications, and data. Azure manages the physical infrastructure and virtualization platform.
• PaaS: You deploy applications without managing the underlying operating system or servers.
• SaaS: You consume a complete application managed by the provider, such as Microsoft 365.

• Short answer: The correct term is Anti-forensics (option D), not “Felony.”

• Why: The actions described—hiding files in slack space, changing file headers, placing suspicious files in executables, and altering metadata—are classic anti-forensics techniques. They’re used to hinder or obscure forensic analysis, not to label the act as a legal category.

• About the options:

• Note: The provided answer key lists B (Felony), which is misleading for this exam objective. The exam typically tests knowledge of forensics concepts, where anti-forensics is the correct category.

• Elicited and documented customer requirements
• Converted them into clear, measurable specifications
• Validated the requirements with the customer
• Used them as the basis for design, quality checks, and acceptance

• A: Requirements should reflect the customer’s needs—not the supplier’s standards.
• B: Iteration review planning does not replace proper requirements collection.
• D: A retrospective occurs after work is completed and is mainly for process improvement, not initial requirements definition.

• What the goal is: You want to add guest (external) users to your Azure AD tenant contoso.com, one entry per external user in a CSV.

• The proposed solution uses New-AzureADUser for each external user. Why this isn’t correct: New-AzureADUser creates a regular (internal) user in your directory. It does not create a guest/B2B user invite. So you’d end up with 500 ordinary accounts, not guest accounts with external access.

• The correct approach: Use New-AzureADMSInvitation for each external user. This invites the external user to your directory and creates a guest user (a B2B collaboration user) in your tenant. The invited user then accepts the invitation and gains access as a guest.

• Azure AD vs directory/tenant: Azure AD is the cloud identity service. A directory (also called a tenant) is your specific instance of that service (contoso.com in your scenario). The terms are often used interchangeably in exams.
• Guest user vs internal user: A guest user is external to your organization; an internal user is created directly in your directory as a normal employee/user account.
• B2B invitation: The process of inviting external users so they can collaborate in your resources; New-AzureADMSInvitation is designed for this.

• AWS IoT Greengrass supports local ML inference using models trained in Amazon SageMaker.
• The model and inference code run on the factory’s local server, so processing continues even when internet connectivity is unavailable.
• A Greengrass component can:

• This provides low latency and avoids sending images to AWS for every inference.

• A: Uses AWS-hosted services and therefore depends on internet connectivity. It would fail during an outage.
• C: Snowball Edge is unnecessary for this use case and adds deployment complexity. A local Greengrass server is the intended edge-inference solution.
• D: Amazon Monitron is designed for monitoring industrial equipment health, not analyzing camera images with a custom SageMaker model.

1. Get Data ? Folder in Power BI Desktop.
2. In Power Query Editor, expand the Attributes column to expose metadata such as hidden status and other file attributes.
3. Remove the Content column (and any other data columns you do not need).

• Name
• Extension
• Date accessed
• Date modified
• Folder Path
• Attributes
• Content

• runParallel is defined as async, so it returns a Promise.
• To use the result, you attach a then handler (or use await inside another async function).

• A: “Async runParallel() .then(data);” is invalid. “async” is a keyword for function declarations, not something you put in front of a call, and you’d need a function as the then-argument.
• B: “runParallel().done(function(data){return data;});” .done is not standard in native Promises (it exists in some libraries). Without a compatible library, this won’t work.
• C: “runParallel().then(data);” is invalid because then expects a function as its argument; data is not a function.
• D: “runParallel().then(function(data){ return data; });” is valid (or equivalently, runParallel().then(data => data);).

• The robust, standard option is D.
• B could work only with a library that provides .done; otherwise it’s not reliable.

• Interactive development and exploration
• Small datasets
• Lightweight transformations or testing
• Avoiding the overhead and cost of multiple workers

• Automated reports: Jobs may benefit from job clusters or SQL warehouses.
• Working with SQL in Databricks SQL: Databricks SQL warehouses are the relevant compute option.
• Automatically scaling for larger data: A multi-node cluster with autoscaling is more suitable.
• Large amounts of data: Distributed worker nodes are generally needed.

• Azure Cosmos DB is a globally distributed NoSQL database service. It stores and retrieves application data, but it does not provide the tools needed to build, test, and deploy predictive analytics models.
• Azure Machine Learning—including the historical Azure Machine Learning Studio—is designed for the machine-learning lifecycle:

• prompt: the input or instruction given to the model
• completion: the desired response

json 
{"prompt":"Summarize this customer complaint.","completion":"The customer reports a delayed shipment."}

• B: A .txt file containing CSV-style lines is not automatically a valid fine-tuning dataset. The required structure and format must match the selected Bedrock model.
• C: Provisioned Throughput provides dedicated inference capacity; it does not fine-tune a model.
• D: Journals and textbooks might support domain adaptation or pretraining, but they do not provide the prompt-to-answer examples typically required for supervised fine-tuning.

• The correct AAA mapping (per Cisco objectives) is:

• Why the given options aren’t fully correct:

• Quick takeaway: when you configure AAA, you should conceptually map them as:

• Example commands (to reinforce concepts):

• I can’t view the images, so I can’t tell which table is labeled as A in your screenshot. But here’s how to decide:

• How to identify the fact table:

• How to identify the surrogate key in the Patient table:

• Relationship:

kusto 
Event | where EventType == "error"

• == is the KQL equality operator.
• -eq is a PowerShell operator, not KQL.
• is is not the correct equality operator in this context.

text 
Event | where EventType –eq "error"

• Event | search "error" — valid, broad search.
• search in (Event) "error" — valid, broad search.
• Event | where EventType == "error" — valid, targeted filter.

• Dynamics 365 Remote Assist — used for remote collaboration and mixed-reality scenarios.
• Dynamics 365 Finance — supports financial and operational management.
• Dynamics 365 Business Central — designed primarily for small and medium-sized businesses’ finance and operations.
• Dynamics 365 for Phones — provides mobile access to Dynamics 365 apps, including Sales, through the mobile Unified Interface.

• A larger question bank with verified answers
• Explanations tied to ISACA exam domains
• Current content aligned with the exam blueprint
• Useful review or progress features

• Disabling GPS: Affects location services, not email connectivity.
• Configuring 4G usage only: Does not enable international data access and could prevent connectivity if 4G is unavailable.
• Connecting using a hotspot: Could provide data, but it is not the most direct solution and depends on another network or device.

• B. Enable column profile — This turns on column profiling, which computes statistics like min and max for each column.
• C. Show column profile in details pane — This ensures the per-column profile is visible in the details pane.
• E. Enable details pane — This makes the details pane available so you can view the column profile there.

• A. Show column value distribution may help with distribution but isn’t specifically about min/max.
• D. Show column quality details shows data quality (valid/null counts), not min/max.

• Amazon GuardDuty: Detects suspicious activity and threats using security-related data sources; it is not primarily a software vulnerability scanner.
• Amazon Detective: Helps investigate and analyze the root cause of security findings after an event.
• Amazon Cognito: Provides user authentication and authorization for applications.

• In Microsoft Entra (Azure AD), admin roles can be scoped to either the entire directory (tenant) or to an Administrative Unit (AU). To assign a role at an AU scope, the user must be a member of that AU.

• Roles in question: Security Administrator and User Administrator can be scoped either to the Directory or to a specific AU.

• User1 is a member of AU1. Therefore, User1 can be assigned either at the AU scope (AU1) or at the Directory scope (global).

• User2 is not a member of AU1. Therefore, User2 cannot be assigned at the AU scope; the valid scope for User2 is only the Directory scope.

• User1: can be assigned at AU1 and at Directory scopes.
• User2: can be assigned only at the Directory scope.

• Active vs passive: Active assessment involves actively scanning targets by sending probes/packets to identify hosts, services, and vulnerabilities. Passive assessment observes traffic without probing.
• External vs internal: External assessment is about testing from outside the network perimeter; the scenario doesn’t specify external vantage, only that tools are identifying hosts/services across the enterprise network.